What a real scoping call covers
In 30 minutes a senior engineer can establish:
- What user persona and what core flow you're building for v1
- What scope is in vs out (we'd write this down on a whiteboard if we were in person)
- What stack we'd default to and whether you have constraints (existing infra, BAA requirements)
- What the first-deploy date looks like
- What the flat price is, or what's left to scope before quoting
What scoping calls turn into when they go wrong
- A sales pitch. Vendor uses the call to qualify you, not to scope. You leave with no quote and a follow-up email asking for a "deeper discovery session" — which is paid.
- A multi-call ceremony. 30 minutes becomes 3 hours across 3 meetings. Vendor is billing-without-billing — using your time as their unpaid discovery work.
- Vague hand-wave. Vendor doesn't actually engage with your spec; sends a templated "starting from $25K" range. No real scope was created.
- The opposite — too tight. Vendor demands a 20-page PRD before they'll quote. You don't have one. You don't engage.
What founders should bring
A one-pager — bullet points, even hand-written. One persona. One core flow. Examples of similar products. Hard constraints (deadline, budget cap, existing stack).
Don't bring a 20-page PRD. Don't bring "I think we should build a platform for..."
What it costs
Free, if the vendor's any good. If you're being asked to pay for the first scoping call, the vendor is using scoping as a revenue stream. That's a different shape of relationship — usually one to avoid for product engineering.
