Agency, freelancer or in-house Shopify developer?

Most articles on this question end by recommending whoever wrote them. This one tries not to. Each option is right for some stores and wrong for others, and the difference is rarely price alone. It is the shape of the work: how much of it there is, how varied it is, and who on your side will manage it.

The three options, defined

• In-house developer. An employee who works on your store and nothing else. They build deep knowledge of your business, and you carry the cost of hiring, managing and keeping them busy.
• Freelancer. An independent developer who works with several clients. You get one person’s skills, usually with low overhead, and depend on that person’s availability.
• Agency or studio. A company with more than one role, from a small specialist studio to a large team. You buy a process as well as skills, with more coordination on both sides.

Five questions that decide it

1. Is the work continuous or project-shaped? A steady stream of changes every week points to someone in-house or on a retainer. A defined project, such as a new theme, a custom app or a migration, has a start and an end, and hiring an employee for it rarely makes sense.
2. How many skills does it span? Theme work, a custom app, Shopify Functions, an ERP integration and design are different skills. One person may cover some of them well. Work that crosses several usually needs more than one person, or one person who knows where their limits are.
3. What happens if one person is unavailable? If a single developer’s holiday or illness would stop sales-critical work, you need either documentation good enough for someone else to take over, or a team.
4. Who will own the knowledge afterwards? With any outside help, the code and the reasoning behind it should end up with you: in version control, documented, and understandable by the next developer.
5. Who on your side can brief and review the work? An in-house developer needs a manager. A freelancer needs a clear brief and someone to check the result. An agency adds its own project management but still needs a decision-maker who answers questions quickly.

The trade-offs side by side

Size is not the same as quality in any column. A small studio and a large agency differ in process and capacity; a senior freelancer and a junior employee differ in experience. Judge the people who will actually do the work.

Compare total cost, not rates. An hourly or monthly figure leaves out what each model costs you in other ways: recruiting and management time for an employee, onboarding time each time a new freelancer starts, coordination with an agency, and rework when knowledge leaves with the person who had it. The cheapest option on paper is often the one whose hidden costs were not written down.

Combinations that often work

• In-house plus a specialist. Your developer handles daily changes; an outside specialist takes the parts outside their skills, such as a custom app or moving Scripts logic to Functions.
• Studio for the build, freelancer or in-house for upkeep. A project team builds the new theme or app with documentation; a smaller arrangement maintains it.
• Freelancer plus a second opinion. For sales-critical changes, an independent review of the plan before the work starts is cheap insurance.

Questions to ask any candidate

The same questions work for an interview, a freelancer call or an agency pitch. The answers matter less than whether they are specific:

1. Who will do the work? Names and roles, not the company in general.
2. What work like this can you show, and whose was it? Proof should say whether it was their own client work, work done as an employee, or a demo.
3. How do you test before changes go live? Look for an unpublished theme copy or a development store, not edits on the live theme.
4. Where will the code live, and what will I own at the end?
5. What happens when the scope changes? A clear answer now avoids a dispute later.
6. What would you not take on? Anyone who claims every skill is telling you something too.

Warning signs in any model

• Asking for your password instead of a collaborator request.
• A fixed price given before anyone has asked about your theme, apps or plan.
• Guarantees of rankings, conversion rates or revenue.
• No written scope, or a scope that lists deliverables but no exclusions.
• Code kept only in the developer’s own account, with no handover plan.

Safeguards, whichever you choose

• Access through collaborator accounts, not shared passwords. A Shopify Partner requests access with a code you provide, and you approve it with only the roles the work needs. Collaborators don’t count toward your store’s user limit and must use two-step authentication.
• Duplicate the theme before code changes. Shopify recommends it; it makes discarding a change simple.
• Code in version control you can access. Not only in the developer’s account.
• Scope in writing. What is included, what isn’t, and how changes are priced.
• Know how billing works. A Partner hired through Shopify’s Partner Directory bills you directly; the charges don’t appear on your Shopify bill.

To find candidates, Shopify’s Partner Directory is a curated list of Partners by service, and it replaced the Shopify Experts Marketplace in October 2023. Partners are required to follow Shopify’s Partner Program Agreement, and Shopify has a form for reporting a Partner you believe is breaking it. Whoever you shortlist, a clear brief is what makes their quotes comparable.

Where Lintel fits, honestly

Lintel is a studio founded by Gencer Karakaya, who reviews every project enquiry himself. It fits project-shaped Shopify engineering: theme engineering, custom apps, Shopify Functions and integrations. If your need is a full-time person for daily store changes, an in-house hire may serve you better, and we will say so.