The short answer
Outsourcing is not a sign that a business lacks ability. It is a decision about where your own people's attention is best spent. The work that defines your business deserves that attention. The work that supports it can often be done faster by someone who does it every week.
The risk is not in outsourcing. It is in outsourcing without a clear brief, clear ownership and a plan for what happens afterwards. This guide covers all three.
Signs it is time to outsource
- A project has been on the list for months and never reaches the top.
- The work needs a skill nobody in the business has, and you will not need it again soon.
- A date is fixed and your team is already full.
- The same manual task is eating hours every week and nobody has time to fix it.
- Your one technical person is the bottleneck for everything.
None of these means you need a permanent hire. Our comparison of in-house developer vs agency sets out when each one fits.
What to outsource and what to keep
A useful test is to ask whether the work is what customers pay you for. If it is, keep the thinking in-house even if outside hands help with the building. If it supports the business without defining it, an outside team can usually own it from start to finish.
| Kind of work | Outsource? | Why |
|---|---|---|
| A website or customer portal | Usually yes | Defined, with a clear finish |
| Connecting two systems you already use | Usually yes | Specialist, and done once |
| An internal tool such as a CRM or booking system | Often yes | Supports the business, with a clear brief |
| Your core product | With care | Keep the direction and the knowledge inside |
| Anything nobody can describe yet | Not yet | Work out what you need first |
The last row matters. Handing over a vague idea and hoping for a product is the most expensive way to find out what you wanted.
Three ways to work with an outside team
Outsourcing is not one thing. The model should match the shape of the work.
A fixed project
You agree a scope, a price and a date. It suits work with a clear finish. It suits less well anything likely to change as you learn.
An ongoing retainer
You pay for a set amount of capacity each month. It suits steady improvement and maintenance, as long as someone on your side sets the priorities.
An embedded team
Outside developers work inside your team, in your tools and meetings. It suits ongoing work that needs real knowledge of the business. Storm's embedded engineering service is built this way, and our guide on freelancer vs embedded developer explains how it differs from hiring a contractor.

How to brief an outside team
A good brief is short and concrete. It describes the problem, not the solution, and it says what finished looks like.
- What is happening now, and what it costs you in time or lost work.
- Who will use the result, and what they need to be able to do.
- What it must connect to: the systems, accounts and data you already have.
- What is out of scope.
- Who on your side makes decisions, and how quickly.
Technology choices come after the brief, not before. If the work is a website, our guide to WordPress vs Webflow vs custom development shows how that choice follows from who will edit the site and what it must connect to.
Staying in control
The worries people have about outsourcing are reasonable, and each has a plain answer. Put the answers in the agreement before work starts.
- The code is held in a repository your company owns.
- Hosting, domains and third-party accounts are in your company's name.
- Documentation is part of the work, and is delivered with it.
- You see working software regularly, not a single reveal at the end.
- There is a handover, and someone on your side can run what was built.
What it costs
Outside development is priced by the project or by the time involved. A fair quote says what is included, what is not and what would change the price. Be careful of a figure offered before anyone has asked how your business works.
Add the running costs too. Hosting, licences and any services the software depends on continue after the build, and they should be itemised.
What a good first month looks like
You can tell early whether an outside team is the right one. In the first few weeks you should see three things.
- Questions about your business, not only about the software.
- Something working that you can click on, however small.
- A written record of what has been decided and why.
If a month passes with nothing to look at and no questions asked, raise it then. Problems found in week four are cheap to fix. The same problems found at delivery are not.
If it goes wrong
Projects do go off course, and it is rarely one side's fault alone. Go back to the brief and ask whether it still describes what you need. Often the requirement has shifted and nobody wrote it down.
If the relationship cannot be repaired, your protection is what you already own. With the code, the accounts and the documentation in your name, another team can pick the work up. Without them, you may be starting again.
Common mistakes
- Outsourcing a problem nobody has defined.
- Choosing the cheapest quote for the most important system.
- Having no one inside the business who owns the project.
- Accepting delivery without documentation or access.
- Disappearing for six weeks, then being surprised by the result.
Common questions
Will we lose control of our own systems?
Not if ownership is settled at the start. Control comes from owning the code, the accounts and the documentation, and from having someone inside who understands what was built.
Should the team be in the UK?
It is not essential, but overlapping working hours and an easy conversation make a real difference. Ask who you will actually speak to, and when.
How do we judge quality if we are not technical?
Ask to see working software early and often. Ask for references you can call. If it matters enough, pay an independent developer for a short review.
Can an outside team work with our existing developer?
Yes, and it often works well. Your developer keeps the knowledge and sets the direction, and the outside team adds capacity and cover.
What to do next
Write a one-page brief for the project that keeps slipping: the problem, the users, the connections and what finished looks like. That page is useful whoever does the work.
If the project is your website, ask for our free 24-hour audit. A founder records a personal video walkthrough of your website within 24 hours, showing what we would look at first. No call is needed.
Want this applied to your website?
George or Nicholas will record a personal walkthrough of your site within 24 hours.
Not ready for an audit? See Embedded engineering.
