01
Intake
You complete the questionnaire and send the document package. We ask follow-up questions until the picture is complete.
The engagement, step by step
Ten steps from first conversation to handover. Nothing moves before step four.
The ten steps
Before anything moves
- 02
Assessment
We review your infrastructure, spend and funding position, and tell you whether you are a realistic candidate for the credit programmes.
- 03
Cost estimate
We produce a written estimate covering one-off migration cost and ongoing AWS run rate, with assumptions listed.
- 04
Your approval
You sign off the scope, the sequence and the estimate. You also sign the expectation confirmation sheet. Nothing moves until this is done.
Nothing moves before this line Credit applications
05Credit routes
We identify which programmes apply to you, in what order, and what evidence each one needs.
- 06
Applications
We prepare and submit the applications. Each one is tracked separately because each one is decided separately.
Migration
07Migration
Workloads move in the agreed sequence, lowest risk first, with rollback available at each stage.
- 08
Attestations
We assemble the proof of completed migration that AWS requires before releasing staged credits.
After go-live
09Monitoring
We watch actual spend against the forecast for the first billing cycles and flag divergence early.
- 10
Handover
Documentation, access, cost dashboards and open items are handed to your team in a recorded session.
What you hold before anything moves
By the end of step four you have all of this in writing. If any of it is missing, the migration does not start.
01
A written cost estimate
One-off and ongoing, with every assumption listed next to the figure it affects.
02
A defined scope
Named workloads, named services, named regions. What is in and what is explicitly out.
03
The credit programmes that apply
Which ones you can apply to, which you cannot, and the honest read on each.
04
The migration sequence
The order workloads move in and why, with rollback defined for each stage.
05
A document checklist
Everything we need from you, listed once, so there are no repeated requests.
06
A timeline
Calendar dates for each stage, including the parts that depend on AWS rather than on us.
07
Status clarity
One current status for the engagement, which you can ask about at any time.
08
Named owners
Who does what, on our side and yours, with a single point of contact each way.
Step four
The expectation confirmation sheet
Before any work begins you sign a short document confirming you understand the following. It exists because credit expectations are the most common source of dispute in this work.
It is one page. We would rather have an uncomfortable conversation in week one than an expensive one in month six.
Expectation confirmation
The expectation confirmation sheet
- Estimated amounts are projections based on the information provided and are not guaranteed.
- Maximum amounts published by AWS represent a ceiling, not an entitlement.
- All credit decisions are made solely by AWS. Alventara does not influence or guarantee any outcome.
- Migration credits and AWS Activate are separate programmes with separate criteria and separate decisions.
- Approved credits may be released in stages against proof of completed work.
- You remain responsible for AWS charges regardless of whether any credit is approved.
- Work outside the agreed scope is quoted separately before it is started.
Client signature
Date
Page 1 of 1
Engagement statuses
Every engagement sits in exactly one of these at any moment. Ask us which, at any time.
0 of 12 complete0%
DoneCurrentAheadHover or tap a status to move the engagement there.
Start at step one
The intake takes most teams a couple of hours to complete properly. The assessment that follows costs you nothing.