What does the discovery sprint produce?

Scoping is real engineering work. A senior engineer reads your codebase, designs the system, and writes the technical plan. The sprint produces a clear scope, a week-by-week plan, and a named team — an artifact you can use whether you proceed with us or not. Skipping it is how a project ships with the wrong scope.

How do you handle scope changes?

Written change orders. If we're partway into a build and you need an extra integration, we estimate the delta, you approve in writing, the plan and timeline update. We don't slip scope quietly to "stay on schedule" — that's how products ship buggy and trust evaporates.

What happens after a project ships?

A few options. Hand the keys to your team with a 30-day stabilization window. Transition into an embedded engagement where we keep running engineering for you. Or shift to a sprint-as-needed cadence — we book occasional sprints when you need a senior strike. Either way, you own everything from day one, so there's no lock-in.

Who owns the code and the accounts?

You do, from day one — the code, the designs, the repos, the cloud and tooling accounts. We work inside your environment as collaborators, not behind a wall. When we leave, nothing leaves with us. You don't have to trust us; you watch it ship every week.

Yes — before the discovery sprint if the conversation requires sensitive disclosure. Standard mutual NDA, our template or yours. We don't sign NDAs to receive a marketing pitch, but for any real product or technical disclosure, NDA first, conversation after.

Accepting projects

Process

What happens
when we say yes.

A senior engineering studio runs on a clear cadence. Here's ours — week by week, deliverable by deliverable. You don't have to trust us. You watch it ship every week.

Last updated: 2026-05-04
Senior team only

Start a project See services

Phase 01 · understand

Discovery — the first step.

Cadence: 48-hour response · short discovery sprint

Within 48 hours of your application, you hear from a founder. If the fit is right, we start a short discovery sprint. One senior engineer and one senior designer go deep on your problem — your users, your business model, your existing system if there is one, the constraints you're really under (deadlines, regulators, investors).

What discovery produces

Technical audit — written assessment of the system you have (or the system you need), in language a non-technical founder can read.
Scope — the explicit list of what we will and won't build.
Plan — a week-by-week schedule with named milestones and demo dates.
Team lineup — the names of the senior designer and engineers who will own your project.

You can stop here.Many founders use the discovery output to scope an in-house plan or take it to another team. It's yours to keep either way — you own everything from day one, so there's no lock-in.

Phase 02 · build

Build — you watch it ship.

Cadence: weekly demos of working software · async updates with a sync call on demand · shared codebase you own

Cadence

Daily. Async written update in your Slack at end of business. Three lines: shipped today, blocked on, shipping tomorrow. No standups, no theater.
On demand. An immediate sync call whenever you need one. No waiting for the next scheduled meeting.
Weekly. Live demo of working software. 30 minutes max. Real software, not slides. Recorded for stakeholders who can't attend, plus a written summary with the next week's tickets prioritized.

Yours from day one

Your repo, with our team as collaborators — you own the code.
Your designs and design files, handed over as we go.
Your project board, with our team writing tickets in your conventions.
Your CI/CD, your staging environment, your error tracking — under your accounts.
A dedicated Slack channel with ROT8 STUDIO and your team.
Production deploys early, behind a feature flag if you'd prefer.

What we won't ask for

Weekly status meetings. The async update replaces them.
Approval for every line of code. Your team reviews PRs the way they always do.
Scope changes mid-sprint without a written change order. Scope is the contract.

Phase 03 · ship

Week N+1 — Ship.

Cadence: production cutover · monitoring · runbook · handoff

A real production launch — not a “soft launch in staging while we wait for QA.” We do production cutovers on Tuesdays or Wednesdays (never Friday) and stay on call for 72 hours after.

What ships with the launch

Production deploy on the infrastructure agreed at discovery. DNS, SSL, CDN, edge caching configured.
Monitoring + alerts — Sentry for errors, analytics, uptime checks, on-call rotation.
Runbook — what to do when X breaks at 3am. Specific commands, not “consult documentation.”
Architecture decision record — every structural decision we made, why we made it, what we'd revisit at scale.
Handoff session — 90 minutes with your team. We walk the codebase, the deployment, the recovery procedures.
30-day stabilization window — we fix any production issues that surface in the first 30 days at no additional cost.

Constants

What's the same in every engagement.

Constant	Why it matters
Senior team only	No juniors on your project. No bench-warming. The names you meet on day one are the names that ship.
Designer + engineer paired from day one	Design-then-engineer relays kill products. Pairing kills the relay.
One named lead	One contact. Not an account manager. The lead writes code on your project.
Weekly demos of working software	Working software is the only honest project signal. You don't trust us — you watch it ship every week.
You own everything from day one	Code, designs, accounts — all yours, all along. No lock-in, nothing leaves with us.
Async updates, sync call on demand	Async updates replace status theater. When you need to talk, we're on a call immediately — no waiting for the next meeting.
Documentation by default	Every change ships with notes. The work has to outlive us.
30-day stabilization	Production is the start of the relationship, not the end.

When we say no

When we're not the fit.

We turn down plenty of the projects we get applications for. When we do:

You hear within 48 hours. No three-week silences.
You hear why. Specifically — not “not the right fit at this time.” Maybe the work is outside our specialty, maybe the timeline is unrealistic, maybe it isn't the kind of build we're right for. Whatever it is, we tell you.
You get a referral if we have one. If we know a freelancer or studio that fits your shape better, we'll name them. We don't take referral fees.

Quick answers

Process, common questions.

What does the discovery sprint produce?
Scoping is real engineering work. A senior engineer reads your codebase, designs the system, and writes the technical plan. The sprint produces a clear scope, a week-by-week plan, and a named team — an artifact you can use whether you proceed with us or not. Skipping it is how a project ships with the wrong scope.
How do you handle scope changes?
Written change orders. If we're partway into a build and you need an extra integration, we estimate the delta, you approve in writing, the plan and timeline update. We don't slip scope quietly to "stay on schedule" — that's how products ship buggy and trust evaporates.
What happens after a project ships?
A few options. Hand the keys to your team with a 30-day stabilization window. Transition into an embedded engagement where we keep running engineering for you. Or shift to a sprint-as-needed cadence — we book occasional sprints when you need a senior strike. Either way, you own everything from day one, so there's no lock-in.
Who owns the code and the accounts?
You do, from day one — the code, the designs, the repos, the cloud and tooling accounts. We work inside your environment as collaborators, not behind a wall. When we leave, nothing leaves with us. You don't have to trust us; you watch it ship every week.
Do you sign NDAs?
Yes — before the discovery sprint if the conversation requires sensitive disclosure. Standard mutual NDA, our template or yours. We don't sign NDAs to receive a marketing pitch, but for any real product or technical disclosure, NDA first, conversation after.

Next step

See if we're a fit.

Tell us what you're building. We respond inside 48 hours, every time. We'll scope the right option for you — and you watch it ship every week.