Dev agency client onboarding playbook 2026

Dev agency client onboarding is the structured 7-to-10-day window between a signed SOW and the first shipped deliverable. It covers deposit collection, access provisioning across GitHub, AWS, Slack, Notion, and 1Password, a written kickoff brief, an agreed cadence of standups and retros, and a 30/60/90-day relationship plan. Done well, it compresses time-to-first-commit to under 72 hours and protects your first invoice.

Most agencies wing this. They treat onboarding as a Slack channel and a calendar invite, then spend the first two weeks chasing AWS console access while the engineer sits idle on the clock. The fix is a repeatable kit you run identically for every new client, anchored by one non-negotiable rule: no work before the deposit clears.

The 2026 client onboarding model

A modern dev agency onboarding has six artifacts and one rule. The artifacts are: the signed SOW, the deposit invoice (typically 50% of phase one), an access checklist, a written kickoff brief, a first-deliverable commit date, and a cadence agreement. The rule is no engineering hours billed before the deposit settles in your account.

That last point is where agencies bleed. We have seen shops run two weeks of discovery on a verbal promise, then watch the prospect ghost when the invoice lands. The deposit is not just cash flow; it is a signal. Clients who refuse to wire 50% upfront almost always become the clients who refuse to pay the final 50% on delivery.

Compare this to the typical onboarding most shops actually run:

Onboarding approach	Time to first commit	Risk of payment dispute	Engineer idle hours week 1
Ad-hoc (Slack invite + good vibes)	10-14 days	High	20-30
Documented playbook, deposit-first	3-7 days	Low	4-8
Cadence booked engineer (no SOW needed)	24-48 hours	None (weekly billing)	0-2
Toptal contractor onboarding	5-10 days	Medium	10-15
In-house hire	30-60 days	N/A (salaried)	N/A

The middle row is what we are building toward in this post. The bottom rows are what you stop your agency from competing against on speed, by routing spiky work through booking platforms instead.

Step 1: SOW signed, deposit invoiced same day

The moment the SOW comes back signed, you have roughly 72 hours of warm-prospect energy. Use it. Send the deposit invoice within the same business day, ideally within the same hour, and use a payment processor that supports ACH and card (Stripe, Mercury, or Wise all work).

Your invoice should specify three things in writing: the exact deposit amount, the work it unlocks (phase 1 scope), and the start date contingent on payment. We recommend this exact line: "Engineering work begins the next business day after this deposit clears." That sentence has saved more agencies from sunk-cost spirals than any contract clause.

The deposit standard for 2026 is 50% upfront for projects under $50k, 30% upfront with monthly milestone billing for projects above. Anything less than 30% upfront and you are functionally lending the client your payroll.

Step 2: Access provisioning checklist

Once the deposit clears, you have one job for the next 48 hours: get your engineer keyed into every system they need before kickoff. This is where most agencies lose three to five billable days because the client's IT person is on PTO.

The standard 2026 access stack:

• GitHub (or GitLab/Bitbucket): repo invite as collaborator or org member with the minimum-needed scope. Ask for a dedicated agency-team org if the client has 10+ repos.
• AWS (or GCP/Azure): IAM user with scoped policy. Never accept root credentials. Send the client a JSON policy template they can paste into IAM.
• Slack: single-channel guest at minimum, full member if the engagement is multi-month. Negotiate a dedicated #agency-name channel up front.
• Notion (or Confluence/Linear): read access to existing docs, write access to a dedicated project page you create.
• 1Password (or Bitwarden): shared vault, not a wall of pasted secrets in Slack. This is the single biggest security improvement most agencies can make.
• Vercel / Netlify / Render: team membership for staging deploys. Production should still gate behind a client-controlled approval.
• Linear / Jira / Shortcut: project access. Decide who is creating tickets (you or them) before kickoff.

Send this list to the client as a single PDF or Notion page the moment the deposit clears. Do not let it dribble out over Slack messages. Agencies that send a consolidated access kit get 80% provisioned within 24 hours; agencies that ask piecemeal get to 80% in five days.

For a deeper look at how the access stack ties back to your contract, our note on dev agency contract templates and gotchas covers the IP, security, and access clauses you want pre-baked into the MSA.

Step 3: The written kickoff brief

The kickoff brief is a one-to-two-page document you write before the kickoff call, not after. It is the spec the engineer codes against. Vague briefs are how scope creep starts.

Required sections:

1. Goal: one sentence describing the outcome (not the feature). "Reduce checkout abandonment by 20% in 90 days" beats "Build a new checkout."
2. Scope (in): bullet list of what is included.
3. Scope (out): bullet list of what is explicitly excluded. This is the most important section.
4. Constraints: stack, deadlines, compliance, accessibility requirements.
5. Success criteria: how you both know it shipped.
6. First deliverable date: a calendar date, not "week 1".
7. Cadence agreement: standup frequency, retro frequency, who attends, demo cadence.

Circulate this 24 hours before the kickoff call. Use the call to edit it live and walk through every line of the "scope out" list. Get a verbal "yes" on each. If you skip this and a single feature request blows past your scope-out boundary later, it is your fault for not naming it. (We wrote a whole guide on how to handle scope creep in agency projects that pairs with this.)

Step 4: First deliverable date and cadence agreement

The first deliverable should land within 7 to 10 calendar days of kickoff. It does not need to be the marquee feature; it needs to be something demoable. A working staging deploy of the existing app on your infra. A migration script that runs in dry-run mode. A clickable mockup of the redesigned page. Pick something that proves the engineer is real and the workflow works.

The cadence agreement formalizes the rhythm. The 2026 default that most healthy agency engagements settle on:

• Daily async standup in Slack (3 lines: yesterday / today / blockers), posted before 11am client time.
• Weekly 30-minute sync on Mondays, screenshare optional.
• Friday demo + retro for engagements over 4 weeks. 15 minutes. Recorded.
• Monthly business review for retainer relationships. 45 minutes. Review margin, NPS, scope, renewal terms.

Write this into the kickoff brief and confirm it in the kickoff call. Cadence drift (skipped standups, slipped demos) is the leading indicator of an engagement going sideways. If you catch it in week 2, you can save the relationship; if you catch it in week 6, you cannot.

Step 5: The 30/60/90-day relationship plan

A relationship plan is not a project plan. The project plan tracks features and dates; the relationship plan tracks trust and expansion.

Day 0-30: prove competence. Ship the first deliverable on time, run cadence on schedule, raise problems before they become billables. The goal is one explicit "this is going well" signal from the client by day 30. Solicit it. "Hey, we're 30 days in. How is this working for your team?"

Day 30-60: prove judgment. The engineer surfaces opportunities the client did not ask for, scoped as suggestions rather than tickets. A perf win they noticed. A security issue. A cost optimization on their AWS bill. This is where retainer conversations happen organically.

Day 60-90: prove fit. By day 90, you have a renewal conversation, a referral conversation, or a graceful wind-down conversation. None of these are accidents. They are the result of running the first 60 days well enough that you have earned the right to ask.

Most agencies skip the 30/60/90 plan and end up renewing reactively, which means they price the renewal from a position of weakness. Agencies that run it explicitly price renewals from strength and renew at higher rates roughly 60% of the time.

Common onboarding traps to avoid

Five patterns we see kill agency margin during onboarding:

1. Starting work before the deposit clears. Always. The exception is never worth it.
2. Sending access requests piecemeal. Send the full kit at once.
3. Skipping the written kickoff brief. A 30-minute kickoff call without a brief is a sunk cost.
4. Letting the client run the cadence. You are the agency. You set the rhythm.
5. Not naming the first deliverable date. "Soon" is not a date. Calendar dates create accountability on both sides.

A sixth trap, less common but more expensive: scoping a fixed-price engagement without a written change-order clause. When the inevitable scope expansion happens, you have no contractual mechanism to bill for it. Every dollar of expansion becomes a negotiation. Build the change-order clause into the SOW template once and never think about it again.

Where booking platforms fit into agency onboarding

The structural reality of running a dev shop in 2026 is that you cannot keep your bench fully utilized. There are weeks where two clients hit you with simultaneous spikes and weeks where your senior engineer is paid to read Hacker News. Both are margin killers.

Booking platforms solve the spike side. When a client signs a SOW that needs a React engineer for 3 weeks and your team is booked, you have three options: turn the work down, hire a contractor through your network and hope they are good, or book an engineer through a vetted platform with a 48-hour trial. Every engineer on Cadence is AI-native by default, vetted on Cursor, Claude Code, and Copilot fluency before they unlock bookings, which compresses ramp time meaningfully. Median time to first commit across the platform is 27 hours.

The math: a mid-tier Cadence engineer at $1,000/week, billed to the client at your standard agency rate (commonly $150-$300/hour, so $6,000-$12,000/week at 40 hours), yields a gross margin of 80-92% on that line item. That is structurally better than the margin you get on a junior employee you carry through the slow weeks.

Agencies that run this hybrid model (core W2 team + booked spike capacity) tend to keep utilization above 75% without the margin collapse of a 100% W2 model. The booked engineers work under your project management, in your repos, attending your standups, invisible to the client. This pattern is documented more fully in our piece on white-label development services.

There is also a referral angle. If the client work is something you do not want to take on at all (wrong stack, wrong size, wrong industry), passing it to Cadence as a referral via the dev agency partner program earns 10% recurring on whatever they spend, indefinitely. That can be a meaningful line of revenue for shops that say no to a lot of bad-fit work.

If you want to test the booking path for a single spike before changing how you operate, you can earn 10% recurring as a partner by referring a single founder client this quarter and seeing how the platform handles them.

What to do this week

Pick one open SOW you have signed in the last 30 days. Audit it against the 6-artifact checklist (signed SOW, deposit invoice, access checklist, kickoff brief, first deliverable date, cadence agreement). If you are missing any of them, build the missing one as a template in your team Notion this week and use it on the next engagement.

If you do not have a partner program slot for spike capacity, set one up. The 30-minute investment to add a booking platform as a backup channel pays for itself the first time a client signs and your bench is full.

Running a dev agency is operations work disguised as engineering work. The agencies that scale past 12 people are the ones that treat onboarding, cadence, and capacity as systems with checklists, not vibes with goodwill. If you want to add booked spike capacity to your bench, Cadence's partner program pays 10% recurring on every founder you refer.

FAQ

How long should dev agency client onboarding take?

7 to 10 calendar days from signed SOW to first demoable deliverable. The deposit-to-access window should be 48 hours; the access-to-kickoff window 24 hours; the kickoff-to-first-commit window 72 hours. Anything longer signals a process gap.

What is the standard deposit for a dev agency project?

50% upfront for projects under $50k, 30% upfront with monthly milestone billing above $50k. Anything under 30% upfront means you are lending the client your payroll and bearing the credit risk yourself.

What access does an agency engineer typically need on day one?

GitHub repo access, scoped AWS IAM credentials, Slack channel membership, Notion or Confluence read/write, 1Password shared vault, Vercel or Render team membership for staging, and Linear or Jira project access. Send all requests as one consolidated kit rather than piecemeal.

Should I require a written kickoff brief or is a kickoff call enough?

Always require the written brief. The call is for editing the brief live and getting verbal agreement on the "scope out" list. A call without a brief is a 30-minute conversation that produces zero contractual artifacts; a brief reviewed on a call produces a document both parties have aligned on.

How do I handle clients who push back on the deposit?

Treat it as a qualifying signal. Clients who refuse to wire a 30-50% deposit are statistically the clients who refuse to pay the final invoice. Hold the line, offer a smaller phase 1 scope if budget is genuinely the issue, and walk away if they still refuse. Lost deals from deposit policy are cheaper than bad-debt write-offs.

Can I onboard a client and engineer simultaneously?

Yes, and you should, but only after the deposit clears. The 48-hour window between deposit clearance and kickoff is where you provision access, brief the engineer, and circulate the kickoff doc. Trying to run client onboarding and engineer ramp in parallel before the deposit hits is how agencies eat the cost of a deal that never closes.