60-Minute Architecture Call
An hour with a senior engineer on your architecture, prepared for in advance and followed by written notes.
60-minute video call with a senior engineer, recorded for you to keep
Tech Advisory
Fixed scope
Cloud Bill Sanity Check
Share one month of cloud billing and we will point out what looks wrong and roughly what fixing it would save.
Overview
What this engagement is
A quick, experienced read on whether your cloud spend makes sense for what you run. Export a month of billing data, give us a brief description of the workload, and we will highlight the lines that look out of place: an oversized database, cross-zone data transfer, storage left on its default tier, or an environment nobody remembered to switch off. This is a skim rather than a full audit, so it will not catch everything, but it is designed to surface the obvious savings quickly.
Deliverables
What you receive
- Review of one month of billing data from your cloud provider
- The 5 most questionable line items, with our reasoning
- Estimated monthly saving for each item
- A view on whether your spend is typical for a workload like yours
- A recommendation on whether a full cost audit would be worthwhile
- Written summary delivered by email
Outcomes
What changes once it ships
A fast, independent opinion on whether your bill is reasonable
Obvious waste identified within days for the price of a dinner
A straight answer on whether deeper work would pay for itself
Process
How the 4 stages run
Send
You export the billing detail and briefly describe the workload
Review
An engineer reads the bill against the architecture you describe
Rank
Questionable lines ordered by their monthly value
Report
A written summary of what looks wrong and what to do about it
A strong fit for
- Founders whose cloud bill has quietly doubled
- Finance teams without a technical view of infrastructure spend
- Anyone wondering whether a full cost audit is justified
What we need from you
- A billing export covering one full month, ideally with resource-level detail
- A few lines on what you run and roughly how much traffic you handle
You share these through the brief that opens in your client dashboard once payment is confirmed. The timeline starts when they arrive.
Answers
Questions about this engagement
The audit examines three months against live utilisation and models commitments. This is a single month, read by eye, giving you the headlines.
We will tell you so. That is a legitimate result and spares you an audit you do not need.
All the major public clouds, as well as smaller developer-focused hosting providers.
This is a digital service — nothing is shipped. Work is delivered to the timeline above, into systems you control, and our refund terms explain what happens if a date is missed.
Often paired with
Engagements that work well alongside.
Technical Hiring Brief Review
We review your engineering job description and interview process and explain why strong candidates are walking away.
Rewritten job description that is honest and specific rather than aspirational
Second Opinion on One Error
Send one error message or stack trace and a senior engineer will explain in writing what it really means.
A plain-language written explanation of what the error means