Gurugram B2B SaaS, 30 engineers, AWS Mumbai, EC2 instances configured by hand.
Weeks 1–2AssessCost and usage report, architecture and security review, deployment process mapping.Findings and prioritised roadmap.
Weeks 2–6CodifyTerraform modules for network, compute and databases; remote state with locking; environments rebuilt from code until terraform plan reports no changes.Reproducible environments.
Weeks 4–7PipelineGitHub Actions build, test, scan and deploy with approvals; container images in Amazon ECR.Push-button deploys with rollback.
Weeks 6–9Cut costCost Explorer rightsizing, Graviton instances, Savings Plans, non-prod schedules, S3 lifecycle rules, cost allocation tags.Cost dashboard by team and environment.
Week 10 onwardsOperateCloudWatch alarms, patching and a monthly cost review; most common surprise line: NAT Gateway data processing charges.Monthly operations and cost report.
Where it starts₹9 lakh/month AWS bill, deploys twice a month over SSH, three environments drifting apart.
Where it endsThe SaaS deploys daily from code-defined environments; it watches cloud cost per customer, deployment frequency and change failure rate monthly.