Khalid ShamsPrincipal Solutions Architect

Tools · reference calculators for cloud and AI architecture

Check the number before you say it out loud.

The numbers that end up in contracts usually start as a guess in a design review: the availability we can promise, what a run will cost, when a tenant needs the next tier, how long the restore takes. These are the calculators I use to make those guesses honest first. Each one runs entirely in your browser, uses your figures rather than mine, and ends in a short note you can paste into the design document.

On the bench

The next four, in the order I reach for them.

Each one answers a question I have watched a room get wrong. They land here as they are finished, one at a time, with the same shape as the first.

  1. 02

    Agent cost per run

    What a run costs today and at ten times the volume: steps, tokens, the model mix, retries, caching, and the cost per accepted answer. Gate 07 of the method, as arithmetic.

  2. 03

    Tenant tier rules

    Write the graduation criteria once, then test tenants against them. Tiering a support engineer can apply without a meeting, instead of whoever complains loudest.

  3. 04

    Detection-first log budget

    List what you need to detect, trace back to the sources that feed it, and see what the rest of the log bill is actually buying.

  4. 05

    The honest estimate

    A range instead of a number, the assumptions that put you at each end, and what it would cost to resolve the biggest unknown early.

Your numbers, not mine

No vendor prices or SLAs are baked in as truth. Every figure loaded on first open is an example, labelled as one, and meant to be replaced with the number for your SKU, your contract, or your own measurements.

Your inputs stay in your browser

The tools run in your browser. Nothing you type is sent anywhere. A link you copy carries your inputs in the address itself, so a colleague sees exactly your version.

Every tool ends in a note

The output is a short plain-text record with an owner, a date, and the condition that reopens it. A calculation nobody writes down gets redone, differently, in the next meeting.

A range, the assumptions that put you at each end, and what it costs to resolve the biggest unknown early. Less satisfying in the meeting. Far better in month seven.