The question people search is "Shopify developer." The question they usually mean is "who should I hire to do this thing, and what will it cost me if I get it wrong."
Those are different questions with different answers depending on what you are building. This guide compares the four realistic options by capability, cost, and risk, and gives you a decision framework based on project type rather than store size alone.
The four options
| Hourly rate | Project range | Best for | |
|---|---|---|---|
| Offshore freelancer | $25-$75 | $300-$8,000 | Well-specified, self-contained work |
| Experienced freelancer | $75-$200 | $500-$30,000 | Clear-scope single-discipline work |
| Agency | $150-$300 | $3,000-$100,000+ | Multi-discipline projects, migrations, integrations |
| In-house | $70k-$140k/yr | Continuous | Ongoing development need at scale |
Geography accounts for more of the spread than seniority does. US-based providers typically charge 30-60% more than equivalent certified Shopify Partners offshore for comparable work. Whether that premium is worth paying depends on how much timezone overlap and communication bandwidth matter for your specific project.
Decide by project type, not store size
Store size is a weak signal. A $10M store that needs a product page fix should hire a freelancer. A $400k store doing a Magento migration should hire an agency. Project type is the better filter.
| Project | Best fit | Why |
|---|---|---|
| Theme bug or layout fix | Freelancer | One discipline, clear scope, no coordination needed. An agency's minimum engagement makes this uneconomic. |
| Custom section or block | Freelancer | Hours of Liquid work. Specify it clearly and it is a clean handoff. |
| Premium theme setup and customization | Freelancer or small agency | Doable by one capable person if design is already decided. Agency if you also need the design. |
| Full store design and build | Agency | Design and development need to be integrated, and someone has to manage content dependencies. |
| Platform migration | Agency | Redirect mapping, plugin gap analysis, and post-launch monitoring are three different skills. This is where cheap goes expensive. |
| Speed and Core Web Vitals work | Specialist freelancer or agency | Needs someone who reads field data and understands app weight, not someone who installs a speed app. |
| Third-party integration (ERP, 3PL, PIM) | Agency | API work plus error handling plus ongoing maintenance. A freelancer who disappears leaves you with an integration nobody understands. |
| Custom app (private) | Freelancer or agency | Depends on complexity. A simple private app is freelancer work; anything with a UI and business logic is not. |
| Custom app (public, App Store) | Agency | Shopify review process, billing API, GDPR webhooks, and ongoing maintenance. Not a project to learn on. |
| Headless build | Agency | React or Hydrogen plus commerce plus CMS plus deployment. Rare skillset, and you will need ongoing engineering after. |
| Ongoing maintenance and small improvements | Retainer (freelancer or agency) | A retained relationship beats hiring fresh for every small task. |
When a freelancer is genuinely the better choice
Not just cheaper. Better.
- Direct accountability. One person, no account manager relaying instructions to someone you never speak to.
- Speed on small work. A freelancer can ship a custom section in a day. An agency's process, however good, adds overhead to small tasks.
- Cost efficiency on clear scope. If you can write the specification, you are paying for execution only, which is the cheapest thing to buy.
- Depth in one discipline. A Liquid specialist who does nothing but theme work is often better at theme work than a generalist agency developer.
The freelancer risks worth managing
- Capacity and continuity. One person gets sick, takes other work, or disappears. Ask about availability and get key work documented as it happens rather than at the end.
- No QA layer. Nobody checks their work but you. Budget your own testing time.
- Specification burden falls on you. Vague briefs cost more with freelancers than with agencies, because there is no one to interpret intent.
- Single-discipline blind spots. A strong developer may not think about SEO, tracking, or conversion. Those gaps surface after launch.
When an agency earns the premium
- Multi-discipline coordination. Design, development, QA, SEO, and tracking on one project needs someone whose job is making those fit together.
- Migration work. Redirect mapping, plugin gap analysis, data integrity, and post-launch monitoring. Migrations are where cheap becomes expensive: stores that skip redirect work routinely lose 30-60% of organic traffic.
- QA. A separate pair of eyes on the purchase path across devices, payment methods, and shipping regions.
- Continuity. If one person leaves, the project continues and someone else knows the codebase.
- Recourse. A company with a contract and a reputation behaves differently from an anonymous marketplace profile.
The agency risks worth managing
- Senior pitch, junior execution. Ask who writes the code, by name, and what proportion of hours is senior.
- Change-order creep. Get the change process and rate in writing before signing.
- Scope inflation. Agencies have larger cost bases and an incentive to recommend larger projects. Ask what they would not build for you.
- Minimum engagement sizes that make small work uneconomic.
When in-house makes sense
A full-time Shopify developer costs $70,000-$140,000 a year plus tools and management overhead. That is roughly equivalent to a $6,000-$12,000 monthly retainer, so the comparison is not obviously in favour of either.
In-house wins when:
- You have continuous development need rather than projects, typically above roughly $5M revenue
- You run multiple storefronts or markets that need constant attention
- Institutional knowledge of your merchandising model has real value
- You need same-day responsiveness on production issues
In-house struggles when:
- The work is genuinely project-shaped, with long quiet periods between builds
- You need design, development, CRO, and tracking. One person will be strong at one and adequate at the rest.
- You cannot provide technical management or code review
The verification that applies to all four
Whoever you are considering, the check is the same. Ask for live store URLs, then:
- View source and confirm it is on Shopify. Look for Shopify markers in the source.
- Run PageSpeed Insights on a product page, and read the field data (real user metrics) rather than the lab score. LCP under 2.5 seconds on mobile is the bar.
- Browse it on your phone. Add something to cart. Notice whether it feels considered or generic.
- Check whether it uses Online Store 2.0 sections or looks like a legacy build. A 2026 build on legacy conventions tells you something.
- Ask what specifically they did on that project. "We did the build, the design came from the client" is a fine answer and changes what you are buying.
Portfolio screenshots prove nothing about build quality, speed, maintainability, or authorship. Live URLs prove all four in about ten minutes.
What to specify before you hire anyone
The single biggest cost variable you control is specification quality. A well-specified project lands at the low end of any provider's range; a vague brief lands at the high end and then generates change orders.
Write down:
- Template count. Every unique page type you need, named.
- Theme approach. Premium theme customised, or custom from scratch? This alone can be a 5x cost difference.
- What "done" means for each template, in terms of what a shopper can do on it.
- Integrations required, with the specific system names and versions.
- Content status. What exists, what needs producing, and by when.
- What you will maintain yourself after handover, which determines how much documentation you need.
If you cannot write this, a paid discovery engagement to produce it is money well spent. It costs a fraction of a build and it makes every subsequent quote comparable.
Red flags that apply regardless of provider type
- A quote before any discovery, with no template count. There is no scope, so everything becomes a change order.
- Portfolio screenshots instead of live URLs.
- No mention of SEO or redirects in a migration or rebuild quote.
- Any structure where they own the store, the code, or the domain. You should own all three from day one.
- A custom theme recommended before they have seen your catalogue.
- Headless recommended below $2M revenue. Over-engineered, with ongoing engineering cost most brands at that scale cannot absorb.
- No stated change request rate.
- A timeline that ignores content dependencies. Development waits on copy and imagery far more often than the reverse, and anyone who has managed builds knows it.
- Everything you asked for is possible and recommended. A provider who will not scope you down is quoting the most expensive version of your description.
A decision shortcut
| If your situation is... | Hire... |
|---|---|
| One clearly defined task, design already decided | Freelancer |
| Several tasks in one discipline over a few months | Freelancer on retainer |
| Full store build with design needed | Agency |
| Migration from another platform | Agency |
| Speed problem you cannot diagnose | Specialist (freelancer or agency) |
| Integration with a business system | Agency |
| Continuous development need, $5M+ revenue | In-house plus retainer for specialist work |
| Not sure what the problem actually is | Paid audit or discovery first, then decide |
That last row matters more than the others. A meaningful share of "we need a rebuild" projects turn out to be a mobile PDP problem, a checkout friction problem, or a speed problem, any of which is a $5,000 fix rather than a $30,000 rebuild. Finding that out costs an audit fee and saves the difference.
How we work
We will tell you when you do not need us. If your project is a well-specified single task, a good freelancer will do it faster and cheaper, and we would rather say so than sell you a larger engagement.
Where we are the right call: full builds where design and development need to be integrated, migrations where the redirect and SEO work matters, and integrations that need to keep working after launch.
See what our Shopify development services cover, how we scope by template count, and the live store URLs you can verify yourself.
Frequently Asked Questions
Should I hire a Shopify freelancer or an agency?
Freelancer when the scope is clear and the work is one discipline: theme customization, a specific feature, a fix. Agency when design and development need to be integrated, when the project involves migration or integrations, or when you need a QA layer and project management. The rough guide is freelancer for most stores doing $200k-$3M with clearly scoped work, agency when brand experience or multi-discipline coordination is material.
What does a Shopify developer cost per hour?
Offshore freelancers run $25-$75 per hour. Experienced freelancers charge $75-$200. Agencies charge $150-$300, with enterprise specialists reaching $350. US-based providers typically charge 30-60% more than equivalent certified Shopify Partners offshore for comparable work.
When should I hire an in-house Shopify developer?
When you have continuous development need rather than projects, typically above roughly $5M in revenue or when you are running multiple storefronts. Below that, a full-time salary buys fewer specialist hours than a retainer does, and one person cannot cover Liquid development, design, CRO, and tracking well. Many stores at that scale run a retainer plus internal content and merchandising capacity instead.
Where do I find a good Shopify developer?
The Shopify Partner directory for vetted agencies, referrals from other merchants in your category, and communities where Shopify developers actually work rather than general freelance marketplaces. Wherever you find them, the verification is the same: live store URLs you can check yourself, run through PageSpeed Insights and browsed on your phone.
Can one person build my whole Shopify store?
For a premium theme with customization, yes, and often better than a team would. For a custom theme build with design, integrations, and migration, one person means either a long timeline or gaps in one discipline. The honest question is not whether they can but whether design, development, QA, and SEO will all be handled properly by the same hands.
Want a real number for your store?
Send us the URL and the catalog size. We will come back with a fixed quote and the template list it covers, no call required unless you want one.
Get a build quote