You built it with Claude Code over a few weekends. Now 40 people use it every day, and you're the only one who knows how it works. So every bug report and every change request lands with you.
Who should own it now: a fractional engineer, a freelancer or an agency? Your budget matters less than one number: what a mistake would cost you.
If a bug means you fix it tonight, keep it yourself or hire a freelancer. If a bug means leaked customer data, a payment charged twice, or a team that can't work until it's fixed, you need an owner who reviews every change before it ships and has cover when they're away.
TL;DR: A fractional engineer is a senior software engineer who works for you part-time on a standing retainer and owns the systems they cover. Choose between a fractional engineer, a freelancer and an agency by what a failure would cost: a freelancer for low-risk tools, a fractional engineer for one system with moderate risk, and a team with review and cover when data, payments or daily operations depend on it.
- What is a fractional engineer
- Fractional engineer vs freelancer vs agency
- The ownership test: 4 questions
- Which option fits, by cost of a mistake
- What an AI-built system needs from its owner
- The one-person problem
- Where Brocoders fits, and where it doesn't
- FAQ
What is a fractional engineer
A fractional engineer is a senior software engineer who works for your company part-time on a standing arrangement, usually a set number of days a week on a monthly retainer, and owns the technical decisions and upkeep for the systems they cover.
The term comes from fractional work, where one professional serves several companies part-time. Tall Karol's definition describes the same shape: one senior person, embedded, on a retainer.
Three distinctions matter when you compare options:
- Fractional engineer vs freelancer. A freelancer delivers a scoped task and moves on. A fractional engineer stays, and owns the outcome over months. Frachion puts it as project-based work versus an ongoing, retainer-based role.
- Fractional engineer vs fractional CTO. A fractional CTO sets technical direction, hires and advises, and may not write code. A fractional engineer builds and maintains.
- Fractional engineer vs contractor. A contractor executes the scope you hand over. A fractional engineer decides what the scope should be.
Fractional engineer vs freelancer vs agency
Here's how the options compare once your business runs on the system. In-house hire is added because most operators consider it first.
| Freelancer | Fractional engineer | Agency or dev team | In-house hire | |
|---|---|---|---|---|
| How they work | Scoped tasks, paid per task or hour | Part-time, standing retainer | A team on a monthly or project contract | Full-time employee |
| Commitment | Per task | Ongoing, a few days a week | Ongoing or per project | Permanent |
| Who reviews changes | Usually nobody else | Usually nobody else | A second engineer or a lead | Nobody else, unless you hire two |
| Cover when they're away | None | None | Another team member | None |
| Who answers when it breaks | Whoever is free | The fractional engineer, if available | The team, on agreed terms | The hire |
| Fits when a mistake costs | An evening of your time | Money, or a few unhappy users | Data, payments or stopped operations | Depends on who you can hire |
The pattern in the table is the point: three of the four options put one person between you and every change.
The ownership test: 4 questions
Run the system through 4 questions before you pick an option.
- What does a mistake cost here? An evening, a bill, a customer, or a stopped operation. Put a number on it if you can.
- Who reviews a change before it ships? If the answer is "the person who wrote it," there's no review.
- Who answers when it breaks, and what happens when that person is away? Holidays, sick days and a better job offer all count.
- Who can sign under the result? Someone has to be accountable for the change, in writing.
Rodion Salnik, our co-founder, answered a commenter on this exact point: "What stays people work is signing your name under it. Nobody sues a model."
Which option fits, by cost of a mistake
AI moved the line of who can build software a long way. As Rodion wrote, "the 'what deserves engineering' line barely moved." Sort your system into one of 3 tiers.
Tier 1: you fix it tonight. An internal tool, a handful of users, no payments. Build it yourself, or bring in a freelancer for the parts you can't do. Rodion's wife built an admin panel for her ceramic studio with Claude. When a page slowed down, it was a fix for the evening (Claude had loaded the whole table into the browser to filter it). Hiring an agency here is money spent on risk you don't have.
Tier 2: a mistake costs money. Customers see it, or it calls paid APIs. A fractional engineer with a clear remit fits. One operator we spoke with had built a drive-time table so his app never called a maps API live. A new dashboard, added later with AI, skipped the table and called the API on every 30-second refresh. A bill of £30 to £100 a month became a €4,500 invoice in about 5 days. No staging, no second review.
Tier 3: a mistake stops the business. Payments, customer data, or staff who can't work when it's down. One UK service business we spoke with has about 200 field staff on its internal tools every day. At this tier you need review before every release, staging, and cover, which means more than one person.
What an AI-built system needs from its owner
Whoever owns it, an AI-built system needs the same 5 things:
- A staging environment, so changes are tested before users see them
- Code review by someone who didn't write the change
- Tests on the paths that touch money and data
- Spend limits on paid APIs
- Monitoring that tells you something broke before your users do
The reason is in the numbers. Veracode's 2025 GenAI Code Security Report tested over 100 models on 80 coding tasks and found that AI-generated code introduced security flaws in 45% of tasks. And in the 2025 Stack Overflow Developer Survey, 46% of developers said they don't trust the accuracy of AI output, up from 31% a year earlier.
The failures also tend to sit at the seams. Nightlamp's maintenance guide points to configuration, integrations and webhooks, the places where generated code meets the outside world.
Hand-built systems miss the same basics. When we started on Lake's vacation rental platform, there was no staging environment and developers pushed from their own machines straight to production. Lake had worked with other teams before. Our team of 5 included a part-time QA engineer and DevOps on demand, and the platform was rebuilt in 3 months.
The one-person problem
Most pages comparing these options skip one thing: a fractional engineer and a freelancer are both one person.
That's fine at tier 1 and often at tier 2. At tier 3, one person moves the single point of failure from you to them, and when they're on holiday, the "it's broken" message still lands in your inbox.
Hiring in-house has the same limit, and it's harder in businesses that don't sell software. A CFO at a UK pest control company put it plainly in a comment on Rodion's post: a small dev team at a company like his "can't offer engineers the career they want. It's maintenance work."
What cover looks like, whichever option you choose:
- A second engineer who reviews and can step in
- Documentation written in the same week as the code
- Repositories, cloud accounts and credentials in your name from day one
Where Brocoders fits, and where it doesn't
We're an agency, so read this section with that in mind.
For tier 1 tools, we're the wrong choice. Keep building, or hire a freelancer.
For tier 2 and 3 systems, we usually start with a Code and Architecture Audit: 5 business days for $5,000, or 10 business days for $9,900. You get a map of what can break and what it would cost, and a keep, fix or rebuild plan. If the answer is that you don't need us, we'll write that down, and you keep every artifact either way.
After that, ongoing work goes to a senior engineering pod: a small team with a named lead, review on every change, and cover built in. If you only need extra hands on your own team, team augmentation is the closer fit.
We build with AI ourselves. Fieldera, our field service platform, was generated from one requirements document in 5.5 days: 82 database models, 343 API endpoints and about 454 automated tests.
For where that team should sit, see nearshore, offshore and onshore and what IT outsourcing is.
Frequently Asked Questions
A fractional engineer is a senior software engineer who works for your company part-time on a standing arrangement, usually a set number of days a week on a monthly retainer. They own the technical decisions and upkeep for the systems they cover.
A freelancer delivers a scoped task and leaves. A fractional engineer stays on a retainer and owns the system over time, including decisions about what to build next.
No. A fractional CTO sets technical direction and may not write code. A fractional engineer builds and maintains the system.
There's no reliable public benchmark yet. It's usually priced as a monthly retainer for a set number of days a week, so compare it with one full-time salary and with the cost of a mistake at your tier.
It depends on what a failure costs. You or a freelancer for an internal tool, a fractional engineer for a paid or customer-facing app, and a team with review and cover once payments, data or daily operations depend on it.
Yes, for low-risk tools. The limit is that nobody reviews their changes and nobody covers them when they're away.
When a mistake would stop your business or expose customer data, and one person can't give you review before release and cover when they're out.