Hiring Your First Developer (What to Ask)

You've got maybe ninety minutes a day that are actually yours, and you've already spent three of those days this month trying to make an app do something it was never built to do. Here's the quick version, before you read another word: if you've genuinely hit the edge of what templates and apps can handle, the fix isn't more tinkering — it's bringing in someone who writes code for a living, for the one specific thing you need, without handing over your whole business to do it.

This isn't a "should you build it yourself" article. You've already decided. What nobody tells you next is how normal, practical, and un-scary hiring a developer actually is once you know what to ask — and what it genuinely costs, in real numbers, not vague "it depends" hand-waving.

And to be clear about what this actually is: you're not replacing yourself or handing your business over to a stranger. For most of what this article covers, you're bringing on a developer to extend your own team, for the one specific thing you genuinely can't DIY, while you keep running everything else exactly as you already do.

Is This a Developer Problem or an App Problem?

Before you spend a cent, it's worth being honest about which problem you actually have. Most store snags are app problems — a plugin that's misconfigured, a setting buried three menus deep, a workflow you haven't found yet. Those get fixed with a Google search or a support ticket, not a developer.

A developer problem looks different. It's checkout logic that no app quite handles — say, a discount that only applies when three unrelated conditions are all true at once. It's an integration between two systems that were never designed to talk to each other, and every app that claims to bridge them breaks something else. Or it's a feature made of three different apps duct-taped together, each one almost doing the job, none of them actually doing it. If you're nodding along to any of those, you're past the "just add another app" stage.

What Hiring a Developer Actually Costs

There are three rough shapes this can take, and they cost very different amounts.

A one-off freelance project — fix this one thing, hand it over, done — is the cheapest entry point. For a contained task on an existing store (a custom checkout rule, one integration, a specific bug), you're typically looking at a few hundred to a couple of thousand US dollars, depending on complexity and who you hire. Ongoing or retainer help costs more overall but buys you someone who already knows your store, so the second and third request move faster and cheaper than the first. The third shape is what's usually called staff augmentation — rather than hiring a full-time employee or gambling on a stranger from a freelance marketplace, you extend your own team with an outside developer for as long as you actually need the extra hands, without the overhead of employing someone outright.

These are ballpark figures, not quotes — get two or three real ones before you commit to anything. US freelance developer rates typically run somewhere between $40 and $150 an hour depending on experience and specialty, and a small, well-scoped project often lands as a fixed price rather than an open-ended hourly tab. If a quote feels wildly low, that's worth more scrutiny than a quote that feels high.

What to Ask Before You Hire Anyone

A short list of questions, asked before any money changes hands, will save you more grief than almost anything else here.

Can you show me something similar you've built on [your platform]? Not just any portfolio — the same platform, ideally a similar type of fix.
Who owns the code and access when we're done? You should walk away owning everything, with your own logins, not theirs.
How do you handle a bug that shows up after launch? A good answer includes a specific window (a week, two weeks) where fixes are covered, not a vague "just message me."
What do you need from me, and how much of my actual time will this take? If the answer is "nothing, I'll handle it all," be a little suspicious — a good developer will need a few real conversations from you, not zero.

Ask these over a call or in writing before you agree to anything. How someone answers tells you almost as much as what they say.

Red Flags to Skip

A few signs are worth walking away from outright, no matter how good the price looks.

No contract or written scope. If what you're paying for isn't written down, you have no way to hold anyone to it — including yourself.
No plan for handing over access when it's done. You should never be locked out of your own store's code or accounts.
Pressure to pay the full amount upfront. A deposit is normal. All of it, before any work starts, is not.
They can't explain their fix in plain English. You don't need to understand code, but a developer who can't explain what they changed and why, in a sentence you follow, is a developer you can't manage later either.

What This Looks Like in Practice

Picture a Tuesday morning. You've got a half-written email to three different app support teams, none of whom can fix the one thing you actually need: a shipping rule that charges correctly for bundles but not for single items, something your current app just can't do. Instead, you post the job with a clear, two-paragraph description of exactly that rule, get two quotes back within a day, pick the one who asked you a smart clarifying question instead of just saying yes to everything, and by Friday the rule is live and tested. You didn't learn to code. You didn't hand over your store. You spent maybe ninety minutes total across the whole week — writing the brief, answering one follow-up question, and testing the result — and the rest of your ninety-minutes-a-day went back to running your actual business.

Common Mistakes First-Time Hirers Make

A handful of mistakes come up again and again with first-time hires, and all of them are avoidable.

Hiring on price alone. The cheapest quote with no portfolio and no questions asked is usually the most expensive mistake, once you count the redo.
Skipping a written scope. "Just fix the checkout thing" isn't a brief. Write down exactly what should happen, with an example, before you ask for a quote.
Skipping a small paid test task first. For anything bigger than a quick fix, a small paid trial — one clearly scoped task — tells you more about working together than any portfolio can.
Jumping straight to a full rebuild. A scoped fix to one thing is almost always cheaper, faster, and lower-risk than "let's just redo the whole site while we're at it."

FAQ

How much should I expect to pay for a small custom fix?

For a contained task on an existing store, a few hundred to a couple of thousand US dollars is a realistic ballpark — get two or three real quotes rather than relying on a single number.

Freelancer or agency — which is right for a small store?

A solo freelancer is usually faster and cheaper for one specific, well-scoped task. An agency or an augmented team makes more sense when you expect ongoing needs, want more than one skill set, or want someone accountable beyond a single person.

Do I need to know how to code to manage a developer?

No. You need to be able to describe what you want in plain language and ask the questions in this article — the developer handles the technical side.

What's the difference between hiring a developer and hiring a staff augmentation team?

A single freelance hire is one person for one task. Staff augmentation means bringing on a developer (or a small team) to extend your existing setup for as long as you need them, which fits better if you expect more than a one-off fix.

How long does a first project usually take?

A small, well-scoped task often takes anywhere from a few days to two or three weeks, depending on complexity and how quickly you can answer follow-up questions.

What happens if it doesn't work out with the developer I hired?

This is exactly why a written scope and your own account access matter from day one — if it's not working, you can end the engagement, keep your access, and take what's been built to someone else.

The Bottom Line

Hiring your first outside developer doesn't have to feel like a leap of faith. Know the difference between an app problem and a developer problem, get a real sense of what it costs, ask the four questions above before any money moves, and walk away from the obvious red flags. You're not replacing yourself or outsourcing your whole business — you're bringing on a developer to extend your own team for the one part that genuinely needs one.

If you'd rather skip the guesswork entirely, that's exactly what we help mums do. Our done-for-you packages and coaching take the heavy lifting off your plate so you're never figuring this out alone.