What to Prepare Before Approaching a Software Company

The single biggest factor in getting a fast, accurate quote and a project that actually delivers what you wanted is how clearly you can describe what you need before the first conversation. You do not need a formal specification document (very few founders arrive with one, and that's fine), but a bit of preparation genuinely changes the quality of the conversation you'll have.

Start with the problem, not your solution

It's tempting to arrive with a fully-formed idea of features. It's more useful to be able to explain the underlying problem first: what is currently slow, manual, error-prone or missing in your business, and who it affects. A good software company will help you work out the right solution; what they need from you is an honest picture of the problem, because the 'obvious' feature list is not always the cheapest or best way to solve it.

A practical checklist

• Who will actually use it, and roughly how many of them: your own staff, your customers, or both, and at what kind of scale.
• What it needs to do, in plain language, ideally as a short list of the two or three things that matter most, not everything you can imagine it doing eventually.
• Anything it must connect to: existing software, a payment provider, an accounting system, a booking calendar you already use.
• Whether it needs to be a mobile app, a website, a web app, or some combination (our guide to website vs web app vs native app can help here).
• Any examples of things you like: a competitor, a similar app in a different industry, or even a spreadsheet you're currently using and want to replace.
• What kind of information it will handle, particularly anything about customers or staff, since that shapes the privacy and security work needed (see our guide to UK GDPR for business apps).
• A rough sense of timeline and, if you have one, a rough budget range: even an approximate figure helps a software company propose something realistic rather than guessing at your expectations.
• Whether this is a first version to test an idea, or something you already know needs to be built properly from day one.

If you've already built a prototype or MVP yourself

If you've used AI tools to build a working prototype or an early MVP yourself (see our guide on building an app with AI), bring it. Being able to show a working version of your idea, even a rough one, is far more useful to a software company than any written description, and it usually means the conversation starts from 'let's make this properly reliable' rather than 'let's work out what you actually mean'.

Questions worth asking in return

• Who owns the source code once it's built? (Our guide on hosting, domains and ownership covers why this matters.)
• What happens after launch: is ongoing maintenance included, optional, or something you have to arrange separately?
• How will they handle personal data, and can they explain their approach to UK GDPR without you having to ask twice?
• Will you get a fixed quote, or is pricing based on time, and why?
• What does the actual working process look like: will you see progress regularly, or only a finished result at the end?

None of this needs to be perfect before you reach out. Even a rough version of the checklist above is enough to start a genuinely useful conversation, and a good software company will help fill in the gaps rather than expect you to have all the answers already.