Workflow intake

Send us one workflow.

You get three answers — what it will cost, the most cost-effective configuration, and where the money goes. Deterministic, replayable, and written for decision-makers. One short form below; it runs on the structure of your workflow, not the data those steps process.

See pricing

How intake works

You describe the shape. We do the math.

Tell us the structure of your workflow — the steps, in order, and what each one does. That's what a forecast is built from, and there's no usage history to dig up. Everything is on this page: no download, no spreadsheet, structure only, no production data.

Rough figures are fine. Once we've modeled it, we walk the design back through with you and confirm it against what you told us — before anything runs.

The workflow · about 4 minutes

Tell us who you are, then walk us through the steps.

Your name for it, not ours — it goes on the cover of the report and at the top of every page.

How much this workflow runs

Volume drives the forecast more than anything else. Give a single number, not a range — if it genuinely varies, send both ends and we'll run it twice. These two multiply into your daily volume, so count only what starts a run — people who review or rework inside the workflow are steps, and the table below already counts them. If one system starts everything, put 1 and the day's total.

We need one of these two — either will do. The period tells you what you will have spent by the end of it; the budget tells you the date you cross it. We never assume either one.

Impact of any kind — regulatory, financial, safety, reputational. Whichever sort matters in your work.

Your workflow, step by step

One forecast covers up to six AI steps. Human and system steps do not count toward that — add as many as your workflow needs.

Why six? Six AI steps is 7.5 million configurations to score, each one simulated 64 times over. Length compounds the same way inside your workflow — every step inherits whatever came before it, so a wrong answer early travels a long way. Six keeps both contained.

List every step in order, including the ones a person or a system handles.

Retries means how many times a step re-does its own work because the output was wrong — code that will not compile, a check that does not pass. It does not mean retries after a timeout, an API error or a rate limit. Those are not forecast.

After the retries is what happens once they are used up and the answer is still wrong: a person picks it up, it moves on anyway, or it stops there.

Prefer email? Write to contact@tierzerosolutions.io and we'll send you an intake spreadsheet to fill in instead.

Step What this step does Performs Input → output How hard Retries After the retries Starts new work?
1
2

Longer workflow? Add as many steps as you need — only the ones marked AI count toward the six. Already know what you want to run? Email us and we'll price that configuration on its own, without a recommendation.

Prefer email? Write to contact@tierzerosolutions.io and we'll send you an intake spreadsheet to fill in instead.