The best cloud architects I've worked with can tell you what their design will cost before a single resource exists. Few do.
Plenty of designs sail through approval with no number attached. The diagram is elegant and the technology choices are defensible, then three months later the running cost lands on someone else when the bill arrives. Without a cost, a design tells you what you'll build but not what you're committing to.
What owning the number changes
| Without a price | With a price |
|---|---|
| "Do we need the premium tier?" gets asked in production, as a migration project | It gets asked at the whiteboard, as a five-minute conversation |
| The business hears "it depends" and the decision waits | The business hears "three shapes, at roughly £8k, £14k and £22k a month, and here is what each buys in performance and resilience" |
| Nobody owns the outcome once the diagram is handed over | The architect who priced it owns it, which tends to produce more conservative, better-justified choices |
How it gets done
You need the Azure pricing calculator, a sizing model per environment, and assumptions about growth and data egress written down where anyone can challenge them. The number will move, and that's fine, because a figure with stated assumptions can be reviewed and refined.
The ask
When a design lands on your desk, ask what it costs to run, and what that number depends on. If your architect can design it but can't price it, you're carrying a risk you can't see yet.
Next: turning architecture into decisions the business can act on.