How we engage
Scope from discovery, not from a tier sheet.
Four ways to work with the studio. Every one of them starts the same way — a short discovery where we map your environment or your thesis, then come back with a plan, a team, and a timeline before anyone commits.
Why no price list
A migration of twelve store systems and a migration of one look nothing alike. Publishing a tier sheet would mean either over-charging the simple case or under-scoping the hard one.
So we scope after discovery — and the discovery itself is fixed-fee or AWS-funded, so you know that number up front.
4
Engagement models
1–2 wks
Typical discovery
Fixed-fee
Discovery basis
Client-owned
IP on engagements
The four models
Pick the shape, then we size it.
Most conversations land on one of these within the first call. They are not packages — they are how the commercial relationship is structured.
Discovery & assessment
A short, bounded review that ends in a plan. Every other model starts here, and it stands alone if all you need is a defensible direction.
- Well-Architected review of the estate
- Workloads mapped to 6R patterns
- Costed migration or build plan
- Architecture diagrams you keep
Fixed fee — often AWS-funded
Scoped project
A defined outcome with a defined end — a migration, a modernization, a platform build. Scope, price, and milestones agreed before kickoff.
- Named senior team for the duration
- Milestone-based delivery and demos
- Full handover package on completion
- Fixed scope with a change process
Fixed price per milestone
Embedded pod
A senior cross-functional team working inside your organization on a rolling basis, for roadmaps that are still moving.
- Product, engineering, and platform in one pod
- Your rituals, your backlog, our standards
- Monthly rolling commitment
- Knowledge transfer as you go
Monthly retainer per pod
Venture partnership
We build and back the company with you. Studio capital, engineering, and infrastructure in exchange for structured ownership.
- Studio funding through formation
- Full build team at venture cost
- Shared platform and security posture
- Operating support into the first raise
Equity, structured up front
How scoping works
You see the number before you commit.
Discovery is a deliverable, not a sales call. You end it with an architecture, a scope, and a price — whether or not you go ahead with us.
See AWS-funded programsIntro call
Thirty minutes to understand the problem, the constraints, and whether we are the right fit at all.
Discovery
We review the estate or thesis properly — architecture, dependencies, cost, and risk — and write it down.
Proposal
A scope, a named team, a timeline, and a price. Plus what we would not do, and why.
Kickoff
Environments provisioned, pipeline running, and the first demo scheduled inside week one.
What is always included
The same standards, every model.
These are not upsells. They are how we build, so they are in every engagement regardless of shape or size.
Well-Architected review
Every design checked against the six AWS pillars before build.
Infrastructure as code
No console-clicked environments — everything reproducible.
Automated delivery
Build, test, scan, and deploy on a pipeline from week one.
Observability
Metrics, logs, and traces wired before the first user lands.
Handover package
Runbooks and diagrams maintained as deliverables.
Security by default
Least privilege, encryption, and audit trails from the start.
Because the same offering can differ by an order of magnitude in effort. A migration of one workload and a migration of twelve estates are both 'a migration'. We would rather scope honestly after discovery than publish a number that is wrong for most people who read it.
Start with discovery
Tell us the problem.
We will scope it.
One call to understand where you are. A short discovery to map it properly. Then a plan, a team, and a number — before you commit to anything.