Cloud bill went up and nobody can say why
Cloud bill went up and nobody can say why: usually orphaned resources, missing tags, or one shared account. Fix ownership first.
·
3 min read
Eight Mile · Writing
Engineering notes, write-ups and the occasional opinion.
Cloud bill went up and nobody can say why: usually orphaned resources, missing tags, or one shared account. Fix ownership first.
·
3 min read
If one person knows how to deploy it, you have a person, not a process. Fix ownership, access, and a path the team can run.
·
3 min read
Quotes and invoices stuck in email fail as a system of record. Use one quote→job→invoice workflow with clear status instead.
·
3 min read
Field team software fails without offline-first: vans need capture, queue, and sync that works when signal dies.
·
3 min read
Multi-tenant SaaS mistakes that show up after launch: isolation, roles, files, billing, and when to stop and fix.
·
3 min read
Taking software in-house after a consultancy build: when to move, what must be true, and what a real handover includes.
·
3 min read
You don’t need a 40-page spec to start: what to bring instead, ruthless v1 must-haves, and how a first release gets priced.
·
3 min read
What “first working link in week two” actually means: a real URL for feedback, not a finished SaaS on day 14.
·
3 min read
Rescue a SaaS someone else built: when to take over an inherited product, stabilise vs rewrite, and own the accounts.
·
3 min read
VLAN and payment systems — what a survey actually covers: coverage, segmentation, kit, and a fixed price after the site visit.
·
3 min read
Office network for a growing London team: when the ISP router fails, what a proper office network includes, and why survey first.
·
3 min read
Security audit checklist before you go live: access, secrets, backups, auth, deps, alerting, and when to bring in an auditor.
·
3 min read