Day 1 · FrameWe agree the questions with you, or with your investors.
We agree the goal, what is in the way and how we will both know it worked, and write it down.
Week 1 · JoinRead access to code, cloud and documents, and interviews with your team are booked.
Our people get access and start inside your team, your tools and your routines.
Week 2 · DeliverArchitecture, data and delivery are reviewed, with the costs and risks priced.
The work lands in small pieces you can see and use. When the evidence changes, so does the plan.
Week 3 · DeliverFindings are checked with your engineers, so nothing in the report is a surprise.
The work lands in small pieces you can see and use. When the evidence changes, so does the plan.
Week 4 · HandoverA written report: the red flags, what they cost to fix and a 90-day plan, then a read-out.
Code, setup and know-how move to your team, so it all runs without us.
Day 1 · FrameWe agree what the first 40 hours should answer.
We agree the goal, what is in the way and how we will both know it worked, and write it down.
Week 2 · JoinRead-only access to your AWS accounts and diagrams.
Our people get access and start inside your team, your tools and your routines.
Week 3 · DeliverAn architecture review: what holds, what will not, and what it costs to change.
The work lands in small pieces you can see and use. When the evidence changes, so does the plan.
Week 5 · DeliverDecision records for the open choices, ready for your team to sign off.
The work lands in small pieces you can see and use. When the evidence changes, so does the plan.
Week 8 · HandoverA roadmap you can act on. Draw down the next block only if you need it.
Code, setup and know-how move to your team, so it all runs without us.
Day 1 · FrameWe pick the use case together and agree what a good answer looks like.
We agree the goal, what is in the way and how we will both know it worked, and write it down.
Week 2 · FrameA test set of real questions from your team, to score every version against.
We agree the goal, what is in the way and how we will both know it worked, and write it down.
Week 3 · JoinAccess to your AWS account and data. The first prototype runs on your own documents.
Our people get access and start inside your team, your tools and your routines.
Week 6 · DeliverThe first version answers in staging, scored against the test set.
The work lands in small pieces you can see and use. When the evidence changes, so does the plan.
Week 9 · DeliverConnected to your systems, with guardrails on and the running cost measured.
The work lands in small pieces you can see and use. When the evidence changes, so does the plan.
Week 11 · DeliverLive for the first users, with a trace behind every answer.
The work lands in small pieces you can see and use. When the evidence changes, so does the plan.
Week 12 · HandoverCode, evaluations and runbooks handed to your team.
Code, setup and know-how move to your team, so it all runs without us.
Week 1 · FrameWe agree what is in scope and which criteria apply. Security always does.
We agree the goal, what is in the way and how we will both know it worked, and write it down.
Week 3 · FrameA gap list in priority order, and a first draft of your system description.
We agree the goal, what is in the way and how we will both know it worked, and write it down.
Week 5 · JoinWe start in your AWS accounts and tools, next to the people who will own the controls.
Our people get access and start inside your team, your tools and your routines.
Month 2 · DeliverPolicies written, controls on your landing zone, and evidence collected automatically.
The work lands in small pieces you can see and use. When the evidence changes, so does the plan.
Month 4 · DeliverA mock audit, tested the way an auditor would. We close what is left and shortlist auditors.
The work lands in small pieces you can see and use. When the evidence changes, so does the plan.
Month 5 · DeliverType I: an independent auditor checks the design of your controls on one date.
The work lands in small pieces you can see and use. When the evidence changes, so does the plan.
Month 6 · HandoverThe Type II window opens. Your team runs the controls, and we check in every month.
Code, setup and know-how move to your team, so it all runs without us.
Month 12 · HandoverThe window closes. The auditor tests it and issues your Type II report.
Code, setup and know-how move to your team, so it all runs without us.
Week 1 · FrameWe agree the goals, the shape of the team and how we work with yours.
We agree the goal, what is in the way and how we will both know it worked, and write it down.
Week 3 · JoinOur people join your stand-ups, your repositories and your on-call rota.
Our people get access and start inside your team, your tools and your routines.
Month 2 · DeliverThe first releases from the joint team reach your users.
The work lands in small pieces you can see and use. When the evidence changes, so does the plan.
Month 6 · DeliverA review together: grow the team, shrink it, or keep it as it is.
The work lands in small pieces you can see and use. When the evidence changes, so does the plan.
Month 12 · HandoverWhat we know has moved to your own people, and we step out.
Code, setup and know-how move to your team, so it all runs without us.