Cloud consultants send quotes before migrations, infrastructure builds, security reviews, and cost audits, and often after a short discovery call or assessment. Clients compare scope, timeline, who owns the accounts and code, and how much of the cloud bill is separate from your fee.
When to use estimates: Use estimates to provide project quotes and get client approval before starting work. Once approved, convert your estimate to an invoice with one click to collect payment.
Create an invoice for payment collection
Upload logo
PDF will be generated with filename:
Invoice_1001_Client_2026-10-14.pdf
Naming the applications, accounts, regions, and environments such as dev, staging, and production keeps scope from quietly expanding.
Terraform modules, diagrams, runbooks, reports, and training sessions should be listed so the client knows what they receive.
State what you expect to find, like documented architecture or access to source code, and that findings that differ may change the price.
Delays often come from waiting on admin access, approvals, or staff time. Spell out what the client must provide and when.
Clarify that provider charges and software licenses are paid by the client and are not part of your fee, or give an estimate if you will pass them through.
Migrations depend on maintenance windows and testing. Dates and acceptance criteria avoid arguments over when work is done.
State who owns the infrastructure code and docs after payment, and whether you retain reusable components.
Define how extra requests are priced and whether post-cutover support is included, and for how many days.
| Service | Priced | Typical range |
|---|---|---|
| General cloud consulting and advisory | per hour | $120-250 |
| Senior architecture or security/compliance consulting | per hour | $175-325 |
| Cloud cost optimization audit (FinOps review) | flat fee | $3,000-12,000 |
| Well-architected or security review | flat fee | $4,000-15,000 |
| Landing zone / multi-account setup with infrastructure as code | flat fee | $8,000-30,000 |
| Application or server migration (lift and shift) | per workload | $2,000-10,000 |
| Ongoing advisory retainer | per month | $1,500-7,500 |
| After-hours or emergency support | per hour | $200-400 |
Typical US ranges. Rates vary by region, experience, and job size.
If the environment is unknown, quote a short paid assessment first. Credit part of the fee toward the project if you like, but do not guess at a migration price blind.
Cloud migrations commonly hit surprises such as legacy dependencies, networking quirks, or undocumented services. Add a buffer of 15% to 25% or quote a range with clear assumptions.
Present a basic option, such as a review and report, and a fuller option, such as review plus implementation. Clients can choose by budget and you avoid one take-it-or-leave-it number.
Include an estimate of expected monthly cloud spend and optional ongoing support. Clients compare total cost over the year, and this builds trust in your numbers.
Fixed price works when scope is well defined. If there are unknowns, give a range with stated assumptions or use time and materials with a not-to-exceed amount.
Thirty days is common. Cloud pricing and your availability both change, so state an expiration date.
Many consultants ask for 25% to 50% on acceptance for fixed-fee projects, especially with new clients. It secures your schedule and reduces payment risk.
Provide an estimate separately, clearly labeled as a projection from the provider's pricing, not a guarantee. Actual usage and pricing can differ.
Use the Cloud Consultant invoice template to bill the client, or convert this estimate once it's approved.
Cloud Consultant invoice template