Skip to content
DTCS

Intake

What we need from you

A complete intake is the difference between a real estimate and a guess. Here is everything we ask for, listed once, so you can gather it in one pass.

The questionnaire

Ten sections. Most teams complete it in an afternoon with their finance and engineering leads in the room.

  1. A. Company

    Legal name, jurisdiction of incorporation, date of incorporation, trading name, website, headcount and the person authorised to sign.

  2. B. AWS account

    Whether an AWS account already exists, its ID, who owns it, which region it is set up in, and whether it sits under an organisation or a reseller.

  3. C. Current infrastructure

    Where you run today: on-premise, another cloud, colocation or a mix. Providers, regions, and the contracts that would need to be exited.

  4. D. Migration scope

    Which workloads are in scope, which are explicitly out, and what has to keep running throughout.

  5. E. Spend

    Current monthly and annual infrastructure spend by provider, plus licences and support contracts. Invoices rather than estimates.

  6. F. Funding

    Rounds raised, amounts, dates, lead investors, and whether any investor is an approved AWS Activate provider.

  7. G. Founders

    Founder names, roles, LinkedIn profiles and any previous companies — relevant because prior credits follow founders as well as entities.

  8. H. Product

    What the product does, who uses it, stage of development, and whether it is live in production.

  9. I. Credit history

    Any AWS credits previously applied for or received, by this entity, a related entity or any founder. This must be complete.

  10. J. Readiness

    Target timeline, internal technical capacity, change-freeze windows, compliance constraints and who signs off on downtime.

Per-workload detail

For each workload in scope we need the following. This is what turns a scope into a cost model.

  • Workload name
  • What it does
  • Environment (production, staging, development)
  • Current provider and region
  • Instance or server count and sizes
  • CPU and memory profile
  • Storage type and volume
  • Database engine and version
  • Bandwidth and data transfer profile
  • Availability requirement and acceptable downtime
  • Compliance or data-residency constraints
  • Target AWS region
  • Target migration date
  • Internal owner

Document package

Send what you have. Missing documents do not stop the assessment, but they do limit how firm the estimate can be.

  • Certificate of incorporation or trade licence
  • Proof of domain ownership
  • AWS account ID and ownership confirmation
  • Recent infrastructure invoices, last three months
  • Current infrastructure inventory or architecture diagram
  • Workload list with the detail above
  • Growth or usage forecast, if you have one
  • Any existing migration plan or internal assessment
  • Current pitch deck
  • Founder profiles or CVs
  • Funding confirmation: term sheet, SAFE, or bank confirmation
  • Investor letter, where an Activate route applies
  • Record of any AWS credits previously received
  • Identification for the authorised signatory

The investor letter

Where an Activate route runs through your investor, AWS expects a letter from them. It needs to contain all of the following, on the investor's letterhead:

We provide a template on request. We do not draft the letter on the investor's behalf and we do not sign it.

  • Investor's official letterhead and contact details
  • Date of issue
  • Your company's full legal name
  • Confirmation of the investment relationship
  • Amount invested and the round it relates to
  • Date the investment closed
  • Confirmation of the investor's AWS Activate provider status
  • Name, title and signature of an authorised signatory
  • A contact AWS can verify the letter with

What we will never ask for

No passwords, secret keys, access keys or MFA codes — not in the questionnaire, not by email, not over the phone. If you ever receive such a request appearing to come from DTCS, it is not from us. Report it to us immediately.

Where technical access is genuinely required for a migration stage, it is arranged through a scoped IAM role you create, that you can revoke, with the permissions written down in advance.

Ready to send it over

Email the package or start with a call and we will send the questionnaire in a format that suits your team.