You do not need a technical specification to start a software project. But a few pages of clear thinking before the first meeting will save weeks later on — and make quotes from different companies much easier to compare.
1. The problem, in one paragraph
Describe what is slow, expensive or impossible today. “Our staff copy orders from WhatsApp into Excel every evening” is far more useful than “we need an ERP”.
2. Who will use it
List the types of user — customers, staff, managers, admins — and the main thing each one needs to do.
3. The must-haves for version one
Separate what you need at launch from what would be nice later. A smaller first version reaches users sooner and teaches you what to build next.
4. Examples you like
Links to apps or websites you admire — and what you like about them — help a team understand your expectations quickly.
5. Budget and timeline
Sharing a realistic range is not a weakness. It lets a good team suggest what can be achieved within it, instead of guessing.
Questions to ask the company
- Who will actually work on my project, and how will we communicate?
- How often will I see working progress?
- Who owns the code when the project is finished?
- What happens after launch if something breaks?
