Derplins for teams
Engineering work you pay for only when you accept it.
Your team scopes an outcome. A prompter runs it against your repo and delivers. Your money sits in escrow the whole time and moves when your reviewer accepts — not when someone logs hours.
No seats. No retainer. No minimum commitment.
Escrow by default
Charged up front, held by Derplins, released on your acceptance.
A 3-day window
Accept, request a revision, or open a dispute. Silence accepts on day 3.
A dispute path
The Resolution Center is on the order itself, not behind a support queue.
Public track record
Every prompter carries their own reviews and level. Nothing is anonymous.
One accepted outcome is the unit of purchase.
Not an hour, not a sprint, not a seat. You are buying a scoped piece of work with a price attached before it starts — a reproduced and fixed bug, a reviewed diff, a migration that ran. If it comes back wrong you ask for a revision or dispute it, and the money has not moved.
That makes the spend legible to whoever signs it off: every line item is one deliverable somebody on your side already accepted.
- 01Placed
You buy a package. Card charged, funds held.
- 02Awaiting requirements
You hand over scope and whatever access the work needs.
- 03In progress
The prompter runs it. The order thread stays open while it is in flight.
- 04Delivered
Work comes back on the order, with whatever proof the package promised.
- 05Completed
Your reviewer accepts. Only now does the prompter get paid.
Buy one run before you buy a hundred
The smallest possible pilot is a single order on a single bug. No procurement cycle, no pilot agreement, no onboarding call — the same flow a solo developer uses is the flow your team uses.
A named person, not a queue
You pick the prompter and talk to them on the order while the work is in flight. Their reviews and level are public, so a good one is worth going back to — and you can.
Scope is fixed before money moves
The package says what you get and what it costs before you buy. Scope creep is a new order rather than a variable invoice, which is the whole reason this is easier to approve than an hourly contractor.
Easier to approve than the alternatives.
The finance question about a new vendor is usually “what are we committing to?” Here the answer is one order.
Instead of a seat licence
Nobody on your side has to be provisioned, trained, or deprovisioned. There is nothing to roll out.
Instead of a retainer
No monthly floor to justify in a quarter where you did not need us. Zero orders costs zero.
Instead of an hourly contractor
You are not buying time and hoping it converts into work. The price is attached to the deliverable.
What a prompter can touch, and what we can’t see.
Being straight about this is more useful to you than a badge. Derplins does not sit between the prompter and your environment. We hold the money, carry the order, and run the dispute — we do not proxy the work, so nothing on our side inspects or blocks what happens inside your systems.
Treat a prompter the way you would treat any external contributor: grant the narrowest access the order actually needs, prefer a fork or a branch over write access to main, and revoke it when the order closes. If that model does not fit the work, the work does not belong on a marketplace yet — and we would rather say so before you buy.
Questions your security review will ask that we have not built answers for yet — SSO, per-order audit export, a signed MSA — are worth raising with us directly. support@derplins.com.
Start with one bug and a reviewer.
That is a small enough purchase to make without a meeting, and it tells you more about whether this works for your team than we can.