How to Choose a Software Development Consultancy (2026 Buyer's Guide)

A single specialist. You manage them directly. They write code, design interfaces, or handle specific tasks. You provide direction, make decisions, and coordinate between multiple freelancers if needed.

A team covering design, development, marketing, and project management. They handle everything — you provide requirements and approve deliverables. Work is often done by juniors with senior oversight.

Have they built similar systems using the technologies your project requires? Look for specific examples, not just listed skills. "We've deployed 3 production apps on Cloudflare Workers" beats "We know JavaScript."

Can they explain WHY they'd choose a particular architecture? Do they consider scalability, maintainability, and cost? Ask: "How would you architect this if we expected 10x growth in a year?"

Do they have public code (GitHub, open-source projects), technical blog posts, or can they share anonymised code samples? Quality code is readable, tested, and documented — not just functional.

Do they understand your industry? A healthcare chatbot has different requirements than an e-commerce one. They should ask intelligent questions about your business, not just technical requirements.

Do they start with "what problem are you solving?" or jump straight to "here's what we'll build"? The best consultancies push back on requirements, challenge assumptions, and ensure you're building the right thing — not just building a thing right.

Can they explain technical concepts in plain English? Will they give you regular, honest updates — including bad news early? The initial sales conversations reveal this: if they're clear now, they'll be clear during the project.

Are case studies detailed with measurable outcomes? "Increased page speed by 60%" and "reduced support tickets by 45%" are real results. Vague claims like "beautiful, modern website" tell you nothing.

Will they connect you with past clients? What do those clients say about the experience (not just the output)? Were they on time? Responsive to problems? Easy to work with?

How long have they been operating? A consultancy that's survived 5+ years has proven they deliver (otherwise they'd have no repeat clients). New doesn't mean bad — but check for stability indicators.

Will the same people who sell to you also do the work? Agencies often have sales teams who promise the world, then hand off to different (often more junior) developers. Ask: "Who will actually be writing the code?"

How do they work? Agile sprints? Weekly demos? Daily standups? The specific methodology matters less than having one and being transparent about it. You should always know what's happening, what's next, and what's blocked.

How quickly do they respond to emails during the sales process? That's a preview of how they'll communicate during the project. If it takes 3 days to reply now (when they're trying to win your business), imagine mid-project.

Is their pricing clear? Do they explain what's included and excluded? A good consultancy itemises costs and explains trade-offs. A bad one gives a vague "from £10K" and adds surprises later.

Who owns the code at the end? (It should be you.) Can you take it to another developer if needed? Are there any licensing restrictions on frameworks they use? This must be crystal clear in the contract.

What happens after launch? Do they offer maintenance? At what cost? Is there a warranty period for bugs? The best partners plan for the long term, not just the launch date. Software needs ongoing care.

1. Walk me through how a typical project runs from start to finish.

2. How do you handle scope changes mid-project?

3. What does your weekly communication look like? How will I know what's happening?

4. Can you show me an example project timeline with milestones?

5. What happens if the project is running behind schedule?

6. Who specifically will be working on my project? Can I meet them?

7. What percentage of your team are senior engineers vs junior?

8. Will the same people stay on the project throughout, or will team members rotate?

9. How many projects is my team working on simultaneously?

10. What's your employee retention rate? How long has your team been together?

11. Why would you choose this tech stack over alternatives? What are the trade-offs?

12. How do you handle security? What's your approach to testing?

13. What does deployment look like? How do you ensure nothing breaks when releasing updates?

14. If we wanted to bring development in-house in 2 years, how easy would it be to hand over?

15. What happens to our data if we stop working together?

16. How do you price your work? Time-and-materials, fixed-price, or hybrid?

17. What's included in the price and what's extra? (Hosting, third-party services, content, testing?)

18. What's your warranty period for bugs after launch?

19. Tell me about a project that went wrong. What happened and what did you learn?

20. Can I speak to a client whose project had challenges? (Not just your happiest clients.)

"This project costs £25,000." The consultancy takes on the risk of overruns — but they'll protect themselves with a detailed scope document and change request fees for anything outside it.

"£800/day, estimated 30 days." You pay for actual time spent. Flexible — scope can evolve — but the final cost is uncertain. You carry the risk of overruns.

Daily: Async update (Slack/email) — what was done, what's next, any blockers

Weekly: 30-min sync call — demo progress, discuss upcoming decisions, raise concerns

Bi-weekly: Sprint review — show working software, get sign-off, plan next sprint

Monthly: Bigger picture — are we on track for the overall goal? Budget check. Any strategic shifts?

Missed Deadline

Ask: "What caused it? How can we prevent it next time? Is the overall timeline at risk?" One missed deadline is normal. A pattern of missed deadlines is a problem. If it becomes systemic, refer to your termination clause.

Quality Concern

Be specific: "This feature doesn't work correctly when X" or "The performance is slower than expected." Vague complaints ("it doesn't feel right") are hard to action. If you struggle to articulate the issue, ask for a technical review by an independent third party.

Budget Overrun

The consultancy should flag this early — not after it's happened. If they're approaching the cap, discuss: cut scope, extend budget, or stop and ship what's done. Never continue without a clear decision about the new boundary.

Communication Breakdown

If you're not getting updates, say so immediately. "I haven't heard anything this week — can we have a quick catch-up?" If it continues after raising it, escalate to their management or invoke contract terms.

IR35 and Contractor Status

If hiring individual contractors or very small firms (1-2 people), understand IR35 rules. A properly incorporated Ltd company consultancy (like most UK consultancies) handles their own tax — you're not responsible. But be aware of the distinction between a genuine consultancy engagement and disguised employment.

VAT

UK consultancies above the VAT threshold (£90K turnover) charge 20% VAT. If you're VAT-registered, you reclaim this — so it's cost-neutral. If you're not VAT-registered, factor in the 20% on top of quoted prices. Some smaller consultancies are below the threshold.

GDPR and Data Residency

A UK consultancy handling personal data needs to be registered with the ICO (check: ico.org.uk). If they're processing customer data, you'll need a Data Processing Agreement. UK data should stay within UK/EU/adequate jurisdictions unless the user consents to transfer.

Contract Law

Ensure the contract specifies English or Scottish law (depending on your location). Payment terms in the UK are typically 14-30 days. The Late Payment of Commercial Debts Act protects you if they owe you work product, and protects them if you delay payment.

R&D Tax Credits

If your project involves genuine technological innovation (AI, novel algorithms, solving technical uncertainty), the development costs may qualify for HMRC R&D tax relief — saving 20-33% on eligible expenditure. Your accountant can advise, but it's worth mentioning to your consultancy as they may have R&D claims experience.

Companies House Verification

Any reputable UK consultancy is a registered Ltd company. Check them at Companies House (free): how long they've been trading, their accounts filing status, director information. A company with overdue accounts is a cash flow red flag.

Scope Alignment

Does the proposal cover everything you asked for? Are there items they've excluded that others include? Sometimes a lower price means less scope — not better value. Compare like-for-like by listing what's in and what's out.

Assumptions and Risks

A good proposal explicitly states assumptions ("assumes existing branding provided", "assumes API documentation available"). It also identifies risks and how they'll be mitigated. A proposal with no risks section is naive or dishonest.

Specificity of Approach

Does the proposal explain HOW they'll solve the problem? Generic proposals ("we'll build a modern, scalable solution") are copy-pasted. Specific proposals ("we'll use Cloudflare Workers for edge computing because your users are global") show genuine thought.

Timeline Realism

If one consultancy says 4 weeks and another says 10 weeks for similar scope, the 4-week estimate is either cutting corners or hasn't understood the complexity. Ask the faster one: "What are you assuming that allows you to deliver in half the time?"

What Happens After Launch

Does the proposal include post-launch support? Handover documentation? Ongoing maintenance options? A proposal that ends at "deploy to production" is planning to walk away. Software needs ongoing care — your partner should acknowledge this.

Payment Structure

Typical structures: 30% upfront, 40% at midpoint, 30% on completion. Avoid 100% upfront. Milestones tied to deliverables protect both parties — you don't pay for unfinished work, they don't work for months without payment.

1. Don't rush. Three weeks of evaluation prevents three months of regret. Bad partnerships are incredibly expensive — not just money, but time, stress, and opportunity cost.

2. Talk to the actual builders. If you can't meet the developers before signing, that's a red flag. The person doing the work should understand your business directly — not through three layers of telephone game.

3. Start small. A paid discovery week tells you more about a consultancy than any number of sales calls. It's a low-risk way to test the working relationship before committing tens of thousands.

4. Choose someone who challenges you. A yes-person is dangerous. The best partners tell you when your idea won't work, suggest better alternatives, and help you avoid waste. That honesty is worth paying for.

5. Plan for the long term. Software isn't a one-off purchase. It's a living system that needs care, updates, and evolution. Choose a partner you'd want to work with for years, not just weeks.

6. Trust the process. Use this framework systematically. Score candidates objectively. Check references. Read proposals carefully. The structured approach protects you from emotional decisions and charming salespeople.