Insights / Product development
How to scope a software project before you ask for quotes
When a brief says "we need an app like X", every studio will price a different product. The quotes will be far apart, and it will be hard to tell why. A short scope fixes that.
Describe the problem, not just the product
Write who is struggling, with what, and what happens today. A clear problem lets a studio suggest simpler solutions than the one you imagined.
List the users and what each must be able to do
Name each type of user, such as customer, supplier or administrator, and the three to five things each must do. This is the backbone of any estimate.
Separate must-have from nice-to-have
- Must have: the product is not useful without it.
- Should have: valuable, but the first release can launch without it.
- Later: good ideas that can wait.
Note what it must connect to
Payments, messaging, existing systems, data you already have. Integrations are a common source of cost and delay, so name them early.
Share your constraints
Launch date, budget range, languages, devices, regulations. Constraints are not a weakness. They help a studio recommend what is realistic.
Ask for a phased plan
Ask each studio to show what the first release contains and what it costs, then what comes next. A phased plan lets you start smaller and decide with evidence.
A good studio will help you improve the scope during discovery. Arriving with a clear one makes that conversation faster and the quote more accurate.
More from Insights
Practical notes from our project work.
Designing an offline-first point of sale
A point of sale that stops working when the connection drops costs a shop real sales. These are the design decisions that keep a till running offline and in agreement with the server afterwards.
Milestone payments in a marketplace: what to model
When money is held until work is approved, the states, rules and disputes need to be designed as carefully as the screens. Here is what to define first.