Skip to content
YOUR WEB PAGE

Newsletter

How to scope a custom software project

Turn a messy workflow into a first release: describe the loop, list the roles, cut the extras and ship in two-week stages.

August 22, 20265 min readSaaS · Software · Scoping

Custom software rarely fails because the framework was wrong. It fails because version one tried to cover every edge case at once and took a year to arrive.

Good scoping is mostly subtraction. Here is the process we use with clients.

Step 1: Write the core loop in five sentences

Describe the work as it happens now, without features. For example: "A manager builds next week’s schedule on Thursday, publishes it, staff check their shifts on their phones, and swap requests get approved or declined by the manager."

Every screen in version one should serve that loop. If a screen does not, it belongs on the later list.

Step 2: List the roles before the screens

Write down every type of person who signs in — owner, manager, staff, client — and what each can see, create, edit and approve. Permissions decided late cause data model rewrites, which are the most expensive kind.

Include the awkward cases: a manager who is also staff, a client with two companies, someone who leaves and must lose access the same day.

Step 3: Separate day one from phase two

  • Day one: login, the core workflow screens, input validation, email notifications, an audit trail of who changed what, and a CSV export.
  • Phase two: custom report builders, theming options, multi-currency billing, mobile apps, and anything that depends on data you do not have yet.
  • Never on day one: an AI feature, a redesign of the whole workflow, or a second user type "just in case".

Step 4: Test with the person who does the job

A clickable prototype reviewed by the staff who will use the tool daily will surface missing fields and wrong wording faster than any specification. They will also tell you which step is genuinely annoying, which is usually the one worth automating first.

Step 5: Ship in two-week stages

Deploy to staging every two weeks, demo it, and adjust priorities with what you learn. Real software in front of real users beats a status report every time.

Before launch, agree on support: error monitoring, automated backups, who answers user questions and how fixes get prioritised. Software people depend on daily needs an owner, not just a release date.

Start a conversation

Have a project in mind?

Tell us what you are building. We will come back with questions, ideas and a clear plan.