Agency, freelancer or in-house: how to staff ecommerce work
Hire a freelancer for defined single-discipline tasks. Hire in-house when you need one skillset full-time for the long term. Use an agency when work spans design, development and integration at once, or when it must not stop because one person became unavailable. The deciding factor is continuity, not project size.
We are an agency, so treat this with appropriate suspicion. We have tried to write the version we would want to read if we were buying.
The three options, honestly
Freelancer
Best for: a defined task in one discipline with a clear end. A theme customisation, a plugin fix, a set of designs, a performance audit.
Strengths: cheapest per hour, often available within days, and you deal directly with the person doing the work. No account management layer, no overhead.
Weaknesses: one skillset. When they are ill, on holiday or busy with another client, work stops. Continuity depends entirely on one person’s availability and continued interest.
The hidden cost: coordination, once there is more than one. Two freelancers is manageable. Four means you are running a project — briefing each of them, resolving conflicts where their work meets, and holding the context nobody else holds. That management time is real and almost never budgeted.
In-house
Best for: one discipline needed full-time, long term, with enough work to keep that person genuinely occupied.
Strengths: deep context on your business that no external party accumulates. Immediately available. Cheaper over years than an equivalent retainer.
Weaknesses: four to twelve weeks to recruit and onboard before producing anything. One skillset again — and most stores need design, frontend, backend and integration work. Four employees to cover that costs considerably more than a retainer.
Single points of failure are absolute here. When your only developer leaves, your store development stops until you have hired again.
Agency
Best for: work spanning multiple disciplines, or work that must not stop.
Strengths: design, development and integration in one team. Continuity when someone is unavailable. Starts in a week or two. Scales up and down without recruitment or redundancy.
Weaknesses: more expensive per hour than a freelancer. Less embedded context than an employee. Quality varies enormously between agencies, and the good ones are not obvious from their websites.
The comparison
| Freelancer | In-house | Agency | |
|---|---|---|---|
| Cost per hour | Lowest | Middle | Highest |
| Disciplines covered | One per person | One per person | Multiple |
| Time to start | Days | 4–12 weeks | 1–2 weeks |
| Continuity if unavailable | Work stops | Work stops | Team covers |
| Context on your business | Moderate | Deepest | Moderate |
| Management overhead | Yours | Yours | Included |
| Scales down | Stop booking | Redundancy | Pause or reduce |
| Minimum commitment | None | Employment contract | Varies |
| Best when | Defined single tasks | One discipline, long term | Continuous, multi-discipline |
Two of those three columns win their own row. That is the point — this is not a table designed to make agencies look good.
When you should not hire us
Being specific, because vague qualification is not qualification.
Your project is a theme setup with light customisation. Hire a freelancer. You do not need us, and we will tell you so if you ask.
You need one developer full-time for the next three years and can recruit. Hire in-house. It is cheaper and they will know your business better than we will.
You need someone physically present for product photography, on-site systems testing, or workshops with a large stakeholder group. Hire locally for those parts, whatever you do about the rest.
Your real problem is traffic quality or product-market fit. No amount of development work will fix that, and spending a development budget on it is an expensive way to find out.
When an agency genuinely earns the difference
- The work spans design, development and integration simultaneously
- The store cannot stop improving because one person is unavailable
- Volume varies month to month and you want to scale without recruiting
- You want one accountable party rather than coordinating several
- You need a discipline occasionally but not enough to employ it
That last point is underrated. Most stores need design work sometimes, backend work sometimes, and automation work occasionally. Employing all three is expensive; hiring three freelancers means managing three relationships.
A hybrid that works well
The arrangement we see succeed most often is one in-house person who knows the business deeply, plus external capacity for the disciplines they do not cover and the peaks they cannot absorb.
The employee owns context and continuity. The agency or freelancers supply breadth. Neither is asked to be something they are not.
How we structure it
Our answer for continuous work is ProNuts — a fixed monthly amount of capacity across design, frontend, backend and AI, with a dedicated project manager, published at a real price rather than “contact us”, and cancellable at any time.
For a single defined project with a clear end, we quote it as a project instead. A monthly retainer for finite work is worse value than a fixed quote, and recommending one would be selling you the wrong thing.
How to evaluate whichever you choose
The choice matters less than the quality of who you pick. These separate good from plausible.
Ask what they would not do. Anyone who says yes to everything is either inexperienced or telling you what you want to hear. A useful partner has opinions about what is a bad idea.
Ask about a project that went wrong. Not to catch them out — to see whether they can describe a failure honestly and what they changed afterwards. Everyone has one.
Ask who actually does the work. Particularly with agencies. If the people in the pitch are not the people on the project, that should be stated openly rather than discovered.
Ask how they hand over. What documentation exists at the end, who owns the code, and what happens if you leave. A reluctant answer here is informative.
Ask for a reference you choose, not one from a curated list.
Setting the arrangement up to work
Whichever you pick, the same things determine whether it goes well.
Written scope before work starts, however brief. Most disputes come from two parties holding different assumptions nobody wrote down.
One person on your side who owns the relationship. Work routed through three stakeholders with different priorities goes slowly and expensively.
Access sorted early. Hosting, platform, analytics, the systems being integrated. Waiting on credentials is the most avoidable delay there is.
Agreement on what “done” means for each piece of work, before it starts.
A regular short check-in rather than a long monthly one. Problems surface earlier and cost less.
None of that is specific to agencies, freelancers or employees. It is what makes any of the three work, and its absence is what makes all three fail.
The uncomfortable summary
Most businesses asking this question have already decided and are looking for confirmation. If that is you, the useful exercise is to argue the opposite case for ten minutes and see whether it holds.
If you are set on hiring, ask what happens to your store during the three months before they start and the two weeks a year they are on holiday. If you are set on an agency, ask whether one full-time person would cost less for the work you actually have. If you are set on freelancers, count how many hours a week you will spend coordinating them.
Any of the three can be the right answer. The wrong answer is the one chosen without asking those questions.
