The Two-Week Replacement Guarantee, Explained Properly
Not a marketing bullet. Here is exactly what the window covers, what it does not, how to use it, and why it exists at all — because our vetting is good, not infallible.
What the Window Actually Covers
From the day a developer starts on your project, you have two weeks to request a replacement at no extra cost if the fit is wrong. That window covers three things specifically: pace that does not match what was scoped, communication that falls short of what was agreed, and AI-assisted work quality that does not hold up to what our vetting indicated it would. You do not need to build a formal case — a clear, specific account of what is wrong is enough for us to act on.
What Happens After It Closes
The no-cost guarantee applies to that two-week window specifically, because most genuine mismatches surface early — usually within the first few days of real work, once the developer is inside your actual codebase and not just the interview. After the window closes, you can still ask for a change, but it moves through the same process as bringing on any new hire rather than an automatic, no-cost swap. If something feels off, telling us early is what keeps this simple.
What Qualifies, In Plain Terms
The distinction is whether the problem is a fit issue with the developer or a change on your side. Fit issues are ours to fix.
Pace that does not match what was scoped
If the agreed engagement was full-time and the output reflects something closer to part-time, that is a fit problem, not something you should have to manage around.
Communication that falls short
Missed check-ins, unclear updates, or responsiveness that does not match what was agreed before the engagement started.
AI-assisted output that does not match the vetting signal
If the judgement or AI-tool fluency shown in real work falls short of what the evaluation suggested, that is exactly the gap the guarantee exists to catch.
A request made after the two-week window
Still possible, but treated as a new match through the standard process rather than an automatic no-cost replacement.
You changed your mind about the project scope
A different project, a different direction, or requirements that shifted after the brief was set is a new brief, not a developer-fit issue.
You decided you actually need a different discipline
Realising partway through that a backend hire should really have been a frontend hire, for example, is a scoping change on your side, not a mismatch with the developer you were matched with.
How to Request a Replacement
Tell Us Specifically
Pace, communication, or AI-assisted output quality — name which one, and since when, rather than a general sense that it is not working.
We Review It
Against the original brief and the vetting signal, to understand what went wrong and whether it points to something we should have caught.
A New Match Is Proposed
On a timeline similar to the original one — typically within days, because the search criteria are already known from the first brief.
You Interview and Confirm
The same way you did the first time. Nothing about the replacement process skips the step where you choose.
Because Vetting Is Imperfect, and Pretending Otherwise Helps No One
A live coding evaluation and a review of AI-assisted work samples are strong signals. They are not certainties. Some gaps only show up once someone is working inside your actual codebase, on your actual constraints, at your actual pace — not in an interview built to approximate that.
Claiming a perfect process would be exactly the kind of overconfidence this site argues against when it comes to AI-generated code. We would rather say plainly that mismatches happen sometimes, and commit to fixing them fast at no cost to you, than pretend our screening never misses anything.
Read the full vetting processThe Replacement Guarantee, in Detail
What exactly does the two-week window cover?
From the day a developer starts, you have two weeks to request a replacement at no extra cost if the fit is wrong. That covers pace, communication, and whether the quality of their AI-assisted output matches what our vetting indicated. It does not require you to prove anything formally — a clear, specific account of what is wrong is enough to act on.
What happens after the two-week window closes?
The no-cost guarantee applies to that window specifically, because most genuine mismatches surface early. After it closes, you can still request a change, but it is handled through the same process as bringing on any new hire rather than as an automatic free replacement. Tell us as soon as something feels wrong — earlier requests are easier for everyone to act on.
What counts as a legitimate reason to request a replacement?
Pace that does not match what was scoped, communication that falls short of what was agreed, or AI-assisted work quality that does not hold up to what our vetting suggested it would. These are exactly the things vetting is meant to predict, so when one of them is wrong in practice, that is on us to fix, not on you to absorb.
What does not qualify for a free replacement?
Changing your mind about the project scope or direction is not a developer-fit issue, so it does not fall under the guarantee — that is a new brief, not a replacement. The same goes for deciding partway through that you actually need a different discipline entirely, such as swapping a backend hire for a frontend one because the project changed shape.
How do I actually request a replacement, and how fast does one arrive?
Contact us with specifics — what is wrong and since when — and we review it against the original brief and vetting signal. A new match is proposed on a timeline similar to the original one, typically within days rather than weeks, because the search criteria are already known. You interview and confirm the replacement the same way you did the first hire.
Why offer a replacement guarantee if the vetting process is supposed to work?
Because it is imperfect, and claiming otherwise would be exactly the kind of overconfidence this site argues against elsewhere. A live evaluation and a review of AI-assisted work samples are strong signals, not certainties. Some gaps only show up once someone is working inside your actual codebase under your actual constraints. The guarantee exists because we would rather fix that honestly than pretend it cannot happen.
More on pricing and terms in pricing and engagement models.
Hire With the Guarantee Built In
Every developer we match comes with the same two-week, no-cost replacement window. Tell us about your project and get matched within days.