What to prepare before you start building software
You do not need a 40-page spec to start a software project. You do need enough clarity that nobody is guessing what "done" means.
Projects move fast when people show up with a few plain answers. They stall when the goal shifts every week. Preparation fixes most of that.
1. One sentence on the problem
Who has the problem, and what are they trying to do today without your product?
Example shape: "Small shop owners forget to follow up with leads because everything lives in DMs."
If you cannot say it in one sentence, spend time there first.
2. Who uses it
List your main user types. For each one, write what they need to accomplish in the app or site.
You do not need personas with fake names. You need real jobs: book a slot, upload a file, pay an invoice.
3. Must-haves vs nice-to-haves
Must-haves are features without which the product does not launch. Nice-to-haves wait for version two.
Be ruthless. Every must-have adds time and testing. A shorter first version that ships beats a long wish list that does not.
4. Examples you like
Links to sites or apps that feel close to what you want help more than abstract mood words. Note what you like: layout, speed, tone, how checkout works.
Also say what you do not want. That saves round trips.
5. Content and assets
Who provides copy, photos, logos, legal text? If content is missing, plan time for that or budget for help. Empty placeholders in a launch build always show.
6. Integrations and accounts
List tools you already use: email, payments, analytics, auth, storage. Say if you have accounts ready or need setup guidance.
Surprises here are a common source of delay.
7. After launch
Who fixes bugs, handles support, and pays for hosting? Even a simple site has a owner after go-live.
What you can skip for now
Perfect wireframes of every screen. Detailed database diagrams before the first conversation. A fixed timeline before scope is agreed.
Bring honesty about budget and deadline instead. We would rather tell you early if the scope fits than pretend.
Ready to talk through your list? Contact us or read how we build software.