Step 1: Decide whether to build at all
Not every problem needs custom software. If an off-the-shelf tool covers most of what you need, buy it. Building makes sense when your workflow is what makes you different, when you're paying for several tools that don't talk to each other, or when the tools you have can't grow with you. Build vs buy gives you a framework, and 7 signs you've outgrown off-the-shelf software helps you spot the moment.Step 2: Write down the problem, not the solution
Describe who will use the software, what they do today, where it breaks, and what a good result looks like. You don't need technical language; you need real examples. How to brief a software agency when you're not technical includes an outline.Step 3: Choose the kind of team
A freelancer, an agency and a dedicated team suit different jobs. The main questions are who manages the work, who's accountable, and what happens if someone leaves. Freelancer, agency or dedicated team compares them, and in-house vs outsourced covers hiring your own developers.Step 4: Shortlist and check past work
Look for teams that have built something with similar moving parts: several user types, payments, an admin panel, integrations. Use their live products, run a short reference call, and meet the people who'd build yours. How to check an agency's past work shows how, and our 12 questions to ask before hiring an agency cover the first call.Step 5: Get proposals you can compare
Send the same brief to two or three teams and ask for itemised proposals with assumptions and exclusions. When the prices are far apart, find out why before you choose. Read why software quotes vary so much, then score each one with our proposal scorecard.Step 6: Decide whether you need paid discovery
If your project has several user types, connects to other systems or replaces something you rely on, a short paid discovery phase can save far more than it costs. For a small, clear job, a written scope is enough. Is a paid discovery phase worth it? helps you decide.Step 7: Settle ownership and the contract
Paying for software doesn't automatically make you its owner. You need a signed transfer of the code and IP, and every account in your company's name. The contract should also settle scope, acceptance, changes, warranty, data protection and what happens if either side stops. See who owns the code when you outsource and what a software development contract should cover.Step 8: Agree how you'll pay
Pay in milestones tied to working software you can test, never the whole project upfront. Choose a pricing model that matches how clear your scope is. Read milestone payments and fixed price vs time and materials.Step 9: Kick off and stay involved
Name one decision-maker, set up the accounts before kickoff, join the weekly demo, and answer questions quickly. Projects usually stall waiting for decisions, not for code. Your role as the client lists what to expect each week.Step 10: Test and sign off each release
Test each milestone against your real workflows with the people who'll use it, report problems clearly, and sign off when the agreed criteria are met. User acceptance testing for business owners shows how.Step 11: Plan for after launch
Software needs updates, monitoring and fixes after it goes live, and it has running costs. Agree support before launch, not after the first problem. See what a maintenance plan should cover and what it costs to run your app every month.The five checks that matter most
- The team has live work with similar moving parts to yours.
- The scope says what's included and what isn't.
- The code, IP and every account are yours, in writing.
- You pay for working software, milestone by milestone.
- You see working software every week.
How we work with new clients
It starts with a free scoping call about your business and workflows. After that you get a written scope with what's in, what's out, milestones and the team, so you can compare it with anyone else's. Nothing starts until the agreement is signed, and the code and accounts are yours from day one. You can see what we've built on our projects page.FAQ
How long does it take to hire a software development company?
Typically a few weeks from first calls to a signed agreement: time to brief, shortlist, compare proposals and review the contract. Rushing this step is the most expensive shortcut in a project.How many software companies should I talk to?
Talk to three to five, and get detailed proposals from two or three.Can I hire a software development company if I'm not technical?
Yes. Your job is to explain your business and make decisions. A good company explains its technical choices in plain language and shows you working software every week.What's the biggest mistake when hiring a software company?
Choosing on price before checking that every proposal covers the same scope, and leaving the code or accounts in someone else's name.Ready to start step 2? Book a free scoping call and talk through your workflows with the people who'd build your software.
