You do not need a technical specification to start talking to a software partner. But a little preparation goes a long way. It leads to better proposals, more realistic estimates and a project that starts on solid ground. Here is what to think through before your first conversation.
Start with the problem, not the solution
It is tempting to arrive with a list of features. It is far more useful to explain the problem you are trying to solve. "Our team spends two days a month reconciling orders" gives a partner much more to work with than "we need a dashboard". A good partner will help shape the right solution, and it may be simpler than you expect.
Define what success looks like
How will you know the project worked? Try to describe success in terms you can measure, for example:
- Orders processed in minutes instead of hours
- Fewer customer support calls about the same issue
- A share of customers ordering through the app instead of by phone
Clear goals help everyone prioritise and make trade-offs during the project.
Separate must-haves from nice-to-haves
Write down everything you would like the software to do, then split it into two lists. Must-haves are the features the product cannot launch without. Nice-to-haves can follow in later phases. This one exercise does more than anything else to keep budgets and timelines under control.
Be open about budget and timing
Many people hesitate to share a budget, worried it will simply be spent. In practice, a budget range helps a partner suggest the approach that delivers the most value for what you can invest. The same goes for deadlines. If a launch date is fixed, say so early.
Know who will make decisions
Projects move fastest when there is one clear decision-maker on your side, with enough time to review progress and answer questions. Agree internally who that person is, and who else needs to be consulted.
Gather what already exists
Collect anything that helps explain your current situation:
- The tools and systems you use today, and what you like or dislike about them
- Examples of your data, such as spreadsheets, forms or reports
- Brand guidelines, if the product will be customer-facing
- Apps or websites you admire, and what specifically you like about them
Questions to ask a potential partner
- How do you learn about our business before recommending a solution?
- How will we see progress during the project, and how often?
- Who will we work with day to day?
- How do you test the software before launch?
- What happens after launch? Who handles fixes, updates and improvements?
- Who owns the code and data when the project is finished?
Ready to start?
If you have worked through even half of this list, you are better prepared than most. And if you have not, that is fine too. Helping you shape these answers is exactly what our Discover and Define stages are for. Start a conversation whenever you are ready.