// services
Five engagement shapes.
One senior team.
Pick the shape of the work. The team behind it doesn’t change.
rot8 ships software in five engagement shapes — full-build, MVP, embedded team, native mobile, and rescue. Same senior designers and engineers across all of them. We don’t keep junior bench staff or rotate clients between offices. The shape changes. The team doesn’t.
// the five shapes
Pick the one that matches the moment.
- 01
Custom software development
- Problem
- You need software built and you don’t have the team to build it.
- Outcome
- Production-grade software, designed and engineered end-to-end.
- 02
MVP development
- Problem
- You have an idea and a deadline. The two don’t agree yet.
- Outcome
- MVP from sketch to production in 8–16 weeks, fixed scope, fixed quote.
- 03
Embedded engineering team
- Problem
- Your roadmap is full and hiring a senior team takes nine months you don’t have.
- Outcome
- Senior designers and engineers in your stack, your standups, your Linear — by Monday.
- 04
Native mobile development
- Problem
- The web wrapper isn’t enough. You need iOS and Android done properly.
- Outcome
- Native apps, Swift and Kotlin, by people who’ve shipped them at scale.
- 05
Technical rescue
- Problem
- The codebase is on fire and the team that lit it is gone.
- Outcome
- In, out, better than we found it. Documented. Stable. Yours again.
// philosophy
Why we don’t list capabilities.
Most studios pad a services page with twenty-three capability tags — “PM, design, iOS, Android, backend, frontend, QA…” That tells you what the studio can do. It tells you nothing about what you'd hire them for.
We list shapes. A shape is the actual deliverable, the actual cadence, the actual team. Pick the one that matches the moment you're in. If none of them do, tell us anyway — sometimes the shape is custom.
// constants
What’s the same across every shape.
- Senior team only — no juniors on your project, no offshore augmentation.
- Designer + engineer paired from day one. No design-then-engineering relay.
- Bi-weekly demos. Async daily updates. Shared Linear. Shared codebase.
- Documentation and handoff at every milestone. You own the work.
- One contact, not an account manager.
// quick answers
Services, common questions.
Can I combine shapes?
Yes. The most common path is Sprint → Ship → Embed: a 2-week sprint to validate fit and scope, an 8–16 week build, then we transition into your team for ongoing work. Each shape stands alone, but they snap together if the relationship works.What if my project doesn't fit any shape?
Tell us anyway. Roughly one in five engagements is a custom shape — a strike on a single hard module, an architecture spike, a 4-week diligence project for an investor. If we can do it well, we will. If we can’t, we’ll say so.How fast can a shape start?
48 hours from your application to a response. If we say yes, kickoff is typically 7–14 days from there — sometimes faster, never slower than 21. We don’t run “kicks off in 6 weeks” pipelines.Do you sub-contract any of this?
No. The team you meet on day one is the team that ships. We don’t farm work to offshore studios or freelancer pools. If you see a name in the proposal, that name is on your project.
// next step
Three projects this quarter. Two remain.
Apply with the four-step form. We respond inside 48 hours, every time, with a real reply from a named founder.