It's 10pm the night before you sign. The vendor's agreement is open in one tab, and you've checked the monthly number three times. It's fine.
Toptal's client agreement, revised 17 July 2026, prices one of its engineers at $50,000 if you hire them directly, and keeps that clause alive for twelve months after they stop working for you [C1]. It's easy to read a dedicated development team's rate card twice and that clause never.
A dedicated development team contract is the agreement under which a vendor supplies a standing team that works inside your roadmap for months, billed by the period rather than by the deliverable. The terms that differ most between vendors are the conversion fee, the minimum term and notice window, the IP assignment, the replacement and key-person rules, and the exit obligations.
Key takeaways
You negotiated the rate because it's on the first page. The clauses that decide the next year sit further down: the cost of hiring the people, how you leave, whether the IP transfers, who approves a swap, and what the vendor owes you on the way out.
If you haven't settled on a model, start with our buyer's guide to software development staffing models. This post assumes you're about to hire a dedicated development team on the vendor's paper. Each section shows what other vendors publish, then what yousource publishes for Dev Team as a Service, including two terms you might push back on.
Where a vendor allows it, published conversion fees run from $20,000 to $50,000 per person [C1] [C3] [C2].
Six months in, one engineer knows your billing service better than anyone on payroll. Whether you can offer them a job was decided on day one.
Toptal's agreement sets "a buyout fee of Fifty Thousand United States Dollars (USD $50,000)" for the engagement "and twelve (12) months thereafter" [C1]. Turing's terms, last updated 4 June 2025, charge "fifty thousand dollars ($50,000) per individual Technical Professional", with a restricted period of the term plus 24 months [C2]. Lemon.io's terms, as checked on 19 October 2026, say $20,000 [C3].
Lemon.io calls the payment "a direct placement fee and not as a penalty" [C3], and that's fair: the vendor paid to find and vet the person. Full Scale's 2026 hiring guide answers the question in its FAQ: "Vendor-specific, but most reasonable vendors allow conversion after a defined period with a placement fee." [C10] Negotiate the size of the fee and the length of the tail, not its existence.
Our answer is the first of the two you might not like: "No." Team members stay with yousource and rotate to other clients when the engagement ends. You keep what they produced: "Your codebase, IP, runbooks, and documentation are yours throughout." It's stricter than the market, and deliberate: the team is a standing unit, not a bench to hire from. If a path to hiring matters, pick a vendor that publishes a fee.
If it isn't working in month two, how long until you stop paying?
Toptal allows termination for convenience "upon ten (10) business days' prior written notice" [C7]. Turing lets either party terminate "upon thirty (30) days' written notice" [C2]. Full Scale runs month-to-month, with "30 days' notice to cancel" after the first two weeks [C10].
Two full-team vendors we checked put the floor at around three months. Unified Infotech's dedicated-teams page, checked in October 2026, lists "Minimum 3 months" with "Give notice anytime" and a 30-day handover, though another section of the same page says there's no minimum commitment beyond the current sprint [C8]. Ask which one goes in the contract. UP2DATE Software's page sets no minimum "beyond the first 90-day ramp-up window" and asks for 60 days' notice for full termination [C11].
Ours is the second term you might push back on: "Three-month initial term. Auto-renews. Add or swap roles anytime."
With auto-renewal, the date that matters is when notice has to land, and it's easy to miss while the team is doing fine. Get the renewal notice window in writing before you sign, from every vendor on your shortlist.
Under 17 U.S.C. §101, a commissioned work is a "work made for hire" only if it falls into one of nine categories, from contributions to collective works to atlases [C4]. Software isn't one of them [C4]. The Copyright Office's Circular 30, revised in August 2024, also requires a written agreement that expressly says "work made for hire", signed by all parties [C5]. Its verdict: "If a work fails to satisfy any of these requirements, it is not a work made for hire." [C5]
So the clause that protects your code is a signed assignment, not the words "work made for hire". Section 204(a) says a transfer of copyright ownership "is not valid unless an instrument of conveyance, or a note or memorandum of the transfer, is in writing and signed by the owner of the rights conveyed" [C6]. Look for present-tense assignment language and a signature.
Three published terms to read closely:
Payment conditions are reasonable for the vendor. But under Lemon.io's wording ownership waits on full payment, so in a billing dispute the vendor holds the code [C12]. Toptal assigns up front and ties only the hand-back of work output to undisputed fees [C13].
Ours: "All code, artefacts, rights — yours from day one. No licence-back." The page's FAQ adds "Standard IP-assignment, no carve-outs." Our vendor evaluation scorecard treats a written IP assignment as a gate, not a weighted score.
Every dedicated team has one or two people the rest depend on. The contract decides whether you get a say when one of them leaves.
Toptal's clause: "Toptal will, as its sole obligation and your exclusive remedy, use commercially reasonable efforts to replace such Talent." [C7] Lemon.io replaces "for no additional cost" during its four-week trial [C12]; UP2DATE replaces under-performers "at our cost" after the first sprint [C11]. Unified publishes the strongest key-person terms we found. Replacements are surfaced 10 business days in advance [C8]. Senior-architect substitution requires "your written approval and a 60-day overlap" [C8].
The US federal key-personnel clause, 48 CFR 852.237-75, is a ready template: the contractor must notify "at least 30 days prior to" diverting a named person, "submit a justification" that the replacement's credentials "meet or exceed" the requirements, and get "the written consent of the Contracting Officer" [C9]. Swap in your CTO and it works as a private clause.
Ours: a tech lead "Named at signing, accountable for delivery and code quality." If someone isn't working out, "Re-pair inside 5 days, no charge." And "Team members rotate rarely, with overlap and handover." The wider problem is in bus factor and key-person risk.
UP2DATE quotes "~€8k–11k/mo per senior engineer" [C11]. Matt Watson's Full Scale guide estimates "a fully-loaded rate of $35 an hour per engineer", which puts a five-person team at "roughly $25,000 to $35,000 per month all-in" [C10]. A per-role card is easy to compare, and it turns every change in team shape into a line-item conversation.
Ours: "Single monthly invoice covering the whole team." / "No T&M, no role-by-role line items, no surprise add-ons." The default team is 3–9 people: a project manager, experience designer and tech lead, two to five engineers, a QA engineer, and DevOps "Shared across teams at our cost". "Roles scale as the roadmap shifts — same contract, no renegotiation." We don't publish a price; after a call, "We'll come back with a team shape, a monthly number, and named people to meet before signing."
Our page puts it in one line: "What you see at proposal lands on the invoice." Ask every vendor to sign that sentence.
You'll read the exit clause most carefully on the day you need it, which is the worst day to read it.
ENSafrica's Kayla Ferreira and Ridwaan Boda note that a termination assistance clause "will only be triggered in the event that the main contract expires or is terminated" [C14], and that the parties "should agree on the charges payable for any termination assistance" [C14]. Agree them at signing, while both sides still want the deal. Unified publishes a handover of "code, documentation, runbooks, in-flight artifacts within 30 days" of notice [C8]. UP2DATE's 60-day termination notice includes a knowledge-transfer sprint [C11].
If the team touches EU personal data, GDPR Art. 28 applies [C15]. It bars new subprocessors "without prior specific or general written authorisation of the controller" and requires audit rights [C15]. At the end, the processor deletes or returns "all the personal data", at the controller's choice [C15]. Our vendor security questionnaire covers what to ask before that data moves. The EU Data Act's switching rules don't bind dev vendors, but they're a useful yardstick; see EU Data Act switching charges.
Whoever you sign with, write down what gets handed over, by when, and at what cost.
Published ramps cluster around two to three weeks from signature, and the contract should tie the end of ramp to a milestone you can check. Full Scale says "2 to 3 weeks from signed agreement to developers in your standups" [C10]; UP2DATE, two to three weeks from signature to first sprint [C11]; Unified, "to first commit in 21 days on average" [C8]. Ours is a "Two-week ramp on your codebase before they pick up real tickets." and "Productive by Day 14."
Don't accept "productive" as the milestone, ours included. Name one you can check: a first merged pull request, or the first sprint demo. Our teams run "Two-week sprints by default" inside your rituals. Then put review on the calendar: "An outside senior reviews your codebase every 90 days. No extra cost."
If your work arrives as discrete tickets and nobody needs to sit in your standups, Dev On Demand runs it as a task stream instead: $3,495 a month for one task at a time with a 3-day turnaround, or $6,795 a month for two tasks in parallel. "Cancel any time. No notice period." If it's a fit, the trial task is free, and a wrong fit gets a new engineer within 5 business days.
If you do need a team inside your sprints, take six questions into the next vendor call. What does it cost to hire someone, and for how long after they leave? When does renewal notice have to land? Is there a signed, present-tense IP assignment? Who approves a swap of the tech lead? Is the invoice one number or a rate card? What gets handed over at exit, by when, and at what cost? Get every answer in writing. Ours are on the Dev Team as a Service page, including the two you might not like.
It depends on the vendor, and the price is in the contract. Toptal's client agreement (revised 17 July 2026) charges a $50,000 buyout during the engagement and for 12 months after [C1]. Turing's terms (last updated 4 June 2025) charge $50,000 per person, with a restricted period of the term plus 24 months [C2]. Lemon.io's terms (as checked on 19 October 2026) say $20,000 [C3]. yousource's Dev Team as a Service doesn't allow it: team members stay with yousource, and the codebase, IP, runbooks and documentation are the client's.
Whoever the signed assignment says. Under US law, software written by a contractor is almost never a "work made for hire", because software isn't one of the nine qualifying categories [C4] [C5]. A transfer of copyright needs a signed writing [C6]. Look for a present-tense assignment, not just work-made-for-hire wording.
Published notice windows run from 10 business days in Toptal's agreement (revised 17 July 2026) [C7] to 30 days in Turing's terms (last updated 4 June 2025) and on Full Scale's site [C2] [C10]. Some full-team vendors, such as Unified Infotech, list a three-month minimum term [C8]. Whatever the term, get the renewal notice window in writing before you sign.
A key-person clause names the people an engagement depends on and controls how they are replaced. The US federal template, 48 CFR 852.237-75, requires at least 30 days' notice, a written justification that the replacement meets or exceeds the requirements, and written consent before a named person is diverted [C9]. A private contract can copy that structure with the client's CTO in place of the contracting officer.
At minimum: the conversion fee and its tail, the minimum term and renewal notice window, a signed IP assignment, replacement and key-person rules, the billing shape, and exit terms covering handover, data return and their cost. If the team touches EU personal data, add the GDPR Art. 28 processor terms [C15].
