What to bring to your first call about a software product
You do not need a specification. What the introductory call covers, and what happens afterwards.
Getting started2 min read
It is easy to assume you need a specification before you talk to anyone who builds software. You do not.
The short version
A plain-language explanation of the problem and the product you have in mind is enough. If you have a sketch, the spreadsheet you run the process on today, or a prototype you built with an AI tool, bring it. If nothing is written down yet, that is fine too.
What we talk about
- The problem, and who it is for.
- What you have so far, if anything.
- When you would like to start.
- Whether Planning fits, and what it costs.
What you hear from us
Whether Planning fits, what it costs, and what it would give you: a clickable prototype of the main workflows, a clear scope for the first version, and a proposed Build budget and timeline. If it does not fit, we say so.
Ready when you are
Send your name and email, and we reply within one working day to set up a time.
Book an introductory callWhat happens after
If it fits, you get a short written proposal to read in your own time. Nothing starts until you sign.