How to write down your idea so a builder can price it

When a builder cannot price your idea, it is usually not because they are being difficult. It is because you have handed them a cloud, not a shape. A price needs a boundary, and a boundary needs words on a page. The good news is the page is short, and writing it clears up your own thinking too.

Step by step

1. Start with one sentence: who, problem, actionOpen the page with a single sentence naming who it is for, the problem it solves, and the one thing they do with it. This is the spine of the whole brief. A builder reading this alone should already picture roughly what you mean and what kind of thing you are describing. If it takes a paragraph, the idea is still tangled; keep compressing until one sentence carries it, then build the rest of the page underneath it. Everything that follows is there to add detail to this one sentence, not to introduce a second or third idea alongside it.
2. Describe the main journey in a few stepsWalk through what a user actually does, start to finish, in plain steps: they arrive, they do this, then this, and this happens. Do not describe screens or technology, describe the human path. A builder reads this to understand the real work behind the idea. A booking tool might be "they pick a time, enter their details, and get a confirmation", which quietly tells a builder about a calendar, a form, and an email.
3. List the must-haves, separately from the nice-to-havesMake two lists. Must-haves are things the first version genuinely cannot work without. Nice-to-haves are everything you would love eventually but could launch without. Being honest about this split is the single biggest thing you can do to get an accurate price, because it lets a builder quote the small real thing rather than padding for the whole imagined thing.
4. Write down what is deliberately out of scopeName the things you are choosing not to build yet: the mobile app, the admin dashboard, the integrations. Writing out-of-scope items down protects both sides, because it turns unspoken assumptions into agreed boundaries that neither of you can drift past by accident. Without it, a builder either quotes high to cover everything you might mean, or quotes low and hits surprises that become awkward conversations later. An explicit boundary is what makes a fixed price possible, and it is one of the kindest things you can do for the relationship.
5. Note anything that constrains the buildAdd the practical facts a builder needs: any deadline, a rough budget range, whether it must connect to a tool you already use, and where any data lives. These constraints shape the price as much as the features do. A builder who knows you have a real deadline and a real budget can tell you honestly what fits, rather than designing something the constraints will not allow anyway. Constraints are not admissions of weakness; they are the frame that makes a sensible plan possible, and hiding them only leads to a proposal you cannot afford or a timeline you cannot meet. Be upfront, and the whole conversation becomes shorter and more useful.