How to Scope an App With a Non-Technical Client
Turn a vague idea into users, jobs, screens and connections the client agrees to.
Start with people and jobs
Clients describe apps by features they have seen elsewhere. Steer the meeting to people and jobs instead. Who will use it, and what do they need to get done? A sweet shop might say customers order for pickup, staff see the orders and the owner sees the day's sales. Each job becomes a small set of screens. This keeps the scope tied to value and makes later trade-offs easier.
- Who uses it: customers, staff, managers, partners
- What each person needs to get done
- What happens today without the app
Map the must-haves and the later list
Ask which jobs the app must do on day one and which can wait. Write two lists in front of the client. The first version should handle the core jobs well; extras go to a later phase. This one step prevents most budget disputes, because the client chose what waited. Ask about connections too: payments, WhatsApp or SMS, accounting software or an existing website.
Note where the client is today: an idea, designs, an old app to replace or a live app to extend. That changes how much discovery the build needs.
Confirm in writing
Send a one-page scope summary within a day: users, must-have jobs, later list, connections and the client's success measure. Ask the client to confirm it. This document becomes the brief for your build partner and the reference for every future change request.
Worked example: a sweet shop order portal
A family sweet shop wanted an app like a big delivery platform. The agency asked who would use it: customers ordering for pickup, two counter staff, and the owner. Customers needed to browse, order and pay; staff needed to see and mark orders ready; the owner needed daily sales. Delivery, loyalty points and a mobile app went to the later list by the owner's choice.
The confirmed scope fitted on one page, with payments and WhatsApp order updates as the two connections. That page became the brief for the build partner and the quote came back without surprises.
Common scoping mistakes
Scoping errors become budget disputes later. Most can be avoided with one disciplined meeting and a written summary.
- Copying a big platform's feature list
- Not asking who uses each screen
- Forgetting connections like payments or accounting
- Skipping written confirmation
- Scope by people and the jobs they need done.
- Separate must-haves from a later list, chosen by the client.
- Record connections and where the client is today.
- Get a one-page scope confirmed in writing.
Run a 45 minute scoping conversation with a real or practice client using the people and jobs method. Produce the one-page scope summary and ask them to confirm it.
Check your understanding
1. What should scoping start with?
2. Why should the client choose what goes to the later list?
3. What becomes the brief for the build partner?
Turn what you learn into monthly income
Resell AI agents and apps under your own brand. Up to 30% off credits, up to 30% recurring share, and apps built by XDQ Labs for your clients. Free to join.
From USD 49 or INR 2,999 a month. A person approves every step.
Templates from our playbooks
Copy ready templates with when to use each one and why it works.