How contracts work
Hire someone or get hired on DevNet, paid milestone by milestone, with each payment held by DevNet until the client approves the work.
A contract is hired work between a client and a developer, split into milestones. The client pays each milestone up front, DevNet holds the money, the developer delivers, and the client approves. Then the money is released to the developer, minus DevNet's 5% fee.
Contracts are in Contracts in the sidebar. They're paid in US dollars by card through Stripe. Robux aren't supported.
The steps
- The client writes the contract: a title, the scope and terms, and the milestones with an amount each. See Hiring with a contract.
- The developer accepts it (or declines). Both sides have now agreed to the scope and terms, and the contract page records when.
- The client funds a milestone when work on it should start. The money is held by DevNet, not sent to the developer.
- The developer delivers: a note saying what was done, with links to the files, build or repository.
- The client approves and the money is released. Or they ask for changes, and the milestone goes back to the developer with a note. If nobody can agree, either side opens a dispute.
- When every milestone is paid out, the contract is completed. It joins both sides' work history and each side can leave a work review.
Everything that happens is on the contract's timeline: who did what, and when. The other side gets a notification for anything they need to act on.
Where contracts start
- From a profile: the Hire button on a developer's profile.
- From a studio page: Send a contract hires the studio.
- From a job post: in Studio HQ, Offer a contract on an applicant. The title is filled in from the job, and the applicant is marked hired when they accept.
- From a commission: when a studio accepts your request, the notification takes you to a new contract with them.
- From Contracts: New contract and their username.
You can't make a contract with yourself or your own studio, or with an account that blocked you or that you blocked.
What DevNet does and doesn't do
DevNet holds each milestone's payment on its Stripe account until it's released or refunded, and a DevNet moderator decides disputes. DevNet is not a licensed escrow service, a bank or a law firm: the scope and terms are an agreement between you and the other side, and a moderator's decision only settles where the held money goes.
Statuses
| Contract status | What it means |
|---|---|
| Draft | The client is still writing it. Only they can see it. |
| Offered | Sent to the developer, who can accept or decline. |
| Active | Accepted. The client funds milestones and the developer delivers them. |
| Completed | Every milestone is settled, or both sides agreed to end it, with some work paid. |
| Declined | The developer said no. |
| Cancelled | Ended before any work was paid. |
| Milestone status | What it means |
|---|---|
| Not funded | Not paid for yet. The client can still change or remove it. |
| Funded | The client paid and DevNet holds the money. The developer works on it. |
| Delivered | The developer delivered. The client has 7 days to approve, ask for changes or open a dispute. |
| Disputed | Frozen while a moderator decides. Nothing is released or refunded automatically. |
| Released | Approved and paid to the developer, minus the fee. |
| Split | A moderator split the money between both sides. |
| Refunded | The money went back to the client. |
| Removed | Removed before it was funded. |