A clear process, from first question to handover.
You work directly with your builder. We check the builders, hold the payment and step in if something goes wrong.
How a project runs
You describe the need
A short guided chat records your process, tools, project size and timing.
A person approves three builders
Filters use facts each builder has declared, such as tools and languages. Builders who fit are offered in turn, so nobody is ranked by a score. A person then approves the three you see.
A person checks thisYou choose one
You see each builder's name and checked past work. When they accept, a private project room opens.
You agree scope and milestones
The builder writes the scope and splits the price into milestones of up to 60 days. Nothing starts until you accept.
You pay the first milestone
Stripe processes the payment, and it is held until the work is accepted.
The builder delivers
They can only mark work as delivered once every item on the handover checklist is confirmed.
You test and accept
You have 7 days to accept or raise a problem. With no reply, the work counts as accepted. If you raise a problem, a person reviews it and decides.
A person checks thisThe builder is paid and the warranty runs
The payout goes out 14 days after acceptance, less our commission. The 60-day warranty starts when the last milestone is settled.
The handover standard
A milestone cannot be delivered until the builder confirms each item.
- You own the accounts used for this work
- API keys and credentials are transferred to you
- Documentation is in the project room
- Workflow exports are in the project room
- Someone else could take over from here
Warranty
For 60 days after the project ends, the builder fixes anything that stops doing what the agreed scope says. New features are new work.
Where your money goes
Payments run through Stripe. The price you agree with the builder includes our 15% commission, and you see the split before you pay. Refunds follow the client terms.
Who this suits
Companies of any size can use it. It works best when you have a repeated process with enough volume to be worth automating, and someone who can test the result.
Ready to fix this?
Tell us what you need. A person will read it and propose up to three checked builders.