What we do
Tools
Industries
Department
How we workLet's talk →
Home/Hiring a Freelance Developer? Protect the Build
Hiring a Developer

Freelance Developer or Agency? It Depends on How Long the Software Has to Live

A good freelance developer and a good agency write code of the same quality. What differs is what happens when the one person is ill, busy with a bigger client, or gone for good. For a build that's done in a month and rarely touched, that risk is small. For software your orders, invoices or customers pass through every day, it's the main thing you're buying.

Match the hire to the life of the project

The project Lean toward The risk to price in
A landing page, a plugin tweak, a one-off data cleanup A freelance developer. Small, clear and done in days. Very little, as long as the accounts it lives in are yours.
A defined feature on an app that's already healthy A freelancer, ideally one who already knows the codebase. Make sure the change lands in your repository with a short note on what it does, so it isn't locked in one head.
A new product or internal tool you'll keep extending A small team, whether in-house or an agency, or a freelancer with a second developer reviewing the work. Months of decisions living in one person. A long illness or a better contract stalls everything.
Software the business runs on daily: orders, billing, your CRM syncing with accounting A team that answers when it breaks. This is the work n-frames takes on. Downtime costs more than the build did. Ask who's on call, not just who's writing the code.
Not sure anything needs building yet An off-the-shelf tool first. Custom software development only earns its cost when existing tools keep forcing workarounds. Paying anyone, freelance or agency, to build what a subscription already does.

Six things to set up before a freelancer writes a line

These protect you whoever you hire, n-frames included.

  • The code lives in a repository your company owns

    On GitHub, GitLab or similar, under an organization account you control, with the developer invited in. If it only lives on their laptop, you're one dead hard drive away from starting over.

  • Hosting, domains and API keys are in your name

    Cloud accounts, app store accounts and payment provider keys included. Developers get their own logins that you can switch off.

  • The contract assigns the code to you

    In many places, the US included, code a contractor writes stays theirs unless a written agreement transfers it. Have a lawyer look at that clause before work starts.

  • You see working software every week or two

    A demo on a link you can click, not a status update. Problems show up as missed demos long before they show up as a missed deadline.

  • Someone else could run it from the notes

    A short README covering setup, deployment and where the credentials are kept. Ask a second developer to try it once. It's the cheapest insurance on the whole project.

  • Payment follows delivered milestones

    Not a large deposit up front on a long build. Milestones tied to features you've seen working keep both sides honest.

Your freelancer went quiet mid-project: the first week

It happens to careful people too. Work through it in this order.

  1. 1

    Secure the accounts

    Change passwords on everything in your name, and remove the developer's access to production, payments and customer data. Do it politely. It's housekeeping, not an accusation.

  2. 2

    Get a copy of the code

    From the repository if there is one. If there isn't, ask for it in writing and check the live server, where the deployed copy may be the only one that exists.

  3. 3

    List what was promised against what exists

    Go through the quote and your messages, and mark each feature as working, half-built or missing. That list is what the next developer will price from.

  4. 4

    Have someone else get it running

    A second developer setting it up from scratch finds the missing pieces quickly: a secret that only existed on the old laptop, a build step nobody wrote down.

    Watch for: paying for a rewrite before anyone has tried to run what's there. Most half-finished projects can be finished.

  5. 5

    Decide whether to finish, fix or restart

    With the list and a working copy, the choice becomes a cost comparison instead of a guess. n-frames takes over stalled projects like this and finishes them as a team, so the same gap can't open twice.

Let's talk

A team on the project, not one person holding all of it

n-frames is an agency, not a marketplace. We take the project on with our own developers, so it keeps moving when one person is out. We build custom software, integrations and automations for businesses whose daily work runs through them, From the first week, the code sits in a repository you own, accounts stay in your name, and you see working software every week or two.

Hand the stalled build to a team →

Questions people ask

Are you saying freelancers are bad?

No. Many of the best developers work freelance, and for small, short, well-defined work a freelancer is often exactly the right hire. The point is that the risk grows with how long the software has to live and how much depends on it.

What's the actual failure mode with a freelancer that doesn't happen with an agency?

The single point of failure. Illness, a bigger client, burnout or a full-time job offer leaves code only one person understood. An agency spreads that across several people by default, with the knowledge kept in shared repositories and notes rather than one head. Agencies have failure modes of their own, mostly cost and junior staff on your work, so ask who will actually write the code.

How do I know which one fits my project?

Use the table above: how long the software has to live, and what stops if it breaks. Short-lived with nothing waiting on it points to a freelancer. Orders, billing or customer data running through it points to a team. In between, a freelancer with the six safeguards and a second reviewer is a fair middle path.

Is an agency always more expensive than a freelance developer?

Usually by the hour. Per finished project, it depends on how much rework, waiting and handover the freelance route adds. Compare quotes against the same written scope, including testing, deployment and the first month after launch.

Can you take over a project a freelance developer started?

Yes. We get the code running first, list what works and what doesn't, and price finishing it before anyone talks about a rewrite. The walkthrough above is the same order we follow.

How does n-frames work compared with hiring developers directly?

n-frames works as an agency: our team takes the project on, rather than one contractor working alone. Other ways of adding developers have their own pages, including staff augmentation, remote developers and hiring a programmer.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.