How to Scope a Custom Web App: A 7-Step Checklist

Last updated: October 4, 2026 · 3 min read · By Ali Raza

Most software projects that go over budget have the same root cause: nobody agreed on exactly what was being built. “We need a system to manage jobs” means something different to the owner, the office manager and the developer.

A good scope fixes that before any code is written. Here is the checklist we use with clients in the US, Canada and the UK. You can fill in most of it yourself before talking to any developer.

1. What problem should the app solve?

Write one or two sentences: what is going wrong today, and what will be different when the app works? For example: “Job updates live in texts and spreadsheets, so the office can’t see status. The app should show every job’s status in real time and cut status calls in half.” A measurable goal keeps every later decision honest.

2. Who will use it, and what can each role do?

List every type of user: office staff, field crews, managers, clients, vendors. For each, note what they need to see, create, edit and approve. Roles drive a large part of the design and cost, so being specific here pays off.

3. What are the main workflows?

Describe each workflow as numbered steps, from trigger to finish. For example: “1. Client submits a request. 2. Office reviews and assigns a crew. 3. Crew updates status and uploads photos. 4. Manager approves. 5. Invoice is created.” Include what happens when things go wrong, such as a rejection or a missed deadline.

4. What data will the app hold?

List the main records (clients, jobs, properties, assets, invoices) and the key fields for each. Note where existing data lives today, because it may need to be cleaned and imported. Our data migration guide explains how.

5. Which tools must it connect to?

Accounting, CRM, payments, email, calendar, maps, file storage: list each one and what should flow between them. Integrations are often where hidden effort sits, so naming them early avoids surprises.

6. What goes into version one?

Split features into “must have for launch” and “later”. Version one should solve the core problem for the main users; everything else waits. This is the single most effective way to control budget and get the app into use sooner.

7. What are the rules for security, compliance and reporting?

• Who can see sensitive data, and does anything need an audit trail?
• Do privacy laws apply, such as GDPR, UK GDPR or PIPEDA?
• Which reports or dashboards does management need?
• Does it need to work on phones, or offline on site?

What should you get back from a developer?

A good developer turns your scope into clickable screen designs, a written list of features per stage, a timeline and a price for the first stage. Our guide to custom web app costs explains what affects that price. Still deciding whether to build at all? Read internal tools vs off-the-shelf SaaS.

Upstack Web helps clients complete this scope on a free call as part of our custom web application development service.

Frequently asked questions