What you are actually buying #
Most AWS consulting sold to US companies is staff augmentation with a consulting invoice attached. You buy a team, the senior name on the proposal appears at the kickoff and the quarterly review, and the work is done by whoever is available.
This is the opposite arrangement. One principal engineer scopes the work, writes the Terraform, and is on the call when something breaks. That constrains how much we can take on at once, which is a real limitation and worth knowing before you start. It also means there is no delivery pyramid built into the price.
Fixed price, in dollars, agreed before we start #
Every engagement is quoted as a fixed USD figure against a written scope. No hourly meters, no discovery phase you pay for, no invoice that arrives larger than the conversation implied.
If we scope it wrong, we absorb it. If you change what you want, we price the change separately and you agree it in writing first. Engagements generally start at $15,000.
We will not take a percentage of savings on cost work. That model rewards finding numbers that look good in one quarterly dashboard rather than ones that survive a year, and it puts us on the wrong side of the table on the day the honest answer is "leave this alone".
Compliance-driven infrastructure #
If you are heading into SOC 2, ISO 27001 or a HIPAA assessment, most of what an auditor examines in your AWS account is infrastructure work that should have been done anyway: least-privilege IAM rather than broad managed policies, encryption in transit and at rest with keys you control, signed container images that fail admission when unverified, centralised audit logging, and every control defined as code so the evidence is reproducible rather than screenshotted.
We are not auditors and do not issue attestations. We build the layer the attestation is about.
What you own at the end #
Everything is Infrastructure as Code, in your repository, in your AWS account. No proprietary
tooling, no managed console you rent from us, no lock-in by design. If you take it in-house in a
year, the handover is a git clone and a walkthrough.
That is deliberate, and it is the part most consultancies quietly omit. A platform only one vendor understands is a liability on your balance sheet, not an asset.
Working across timezones #
Our day overlaps the US morning. Calls are scheduled in your business hours. The default mode is asynchronous and written — scopes, findings documents, pull requests you review when it suits you — which is how the work stays reviewable rather than dependent on being in the same room.
If what you need is someone physically in a US timezone for daily standups, say so on the first call and we will tell you honestly whether we are the right fit.