AI Solution Shape: Decide What to Build Before You Build It

Most AI projects choose the shape first and justify it afterwards. Someone says “let us build an agent”, and six weeks later the team is debugging a multi-agent system for a process that three deterministic rules would have handled.

The shape is the decision that everything else inherits. Get it wrong and no amount of prompt engineering, model upgrades or budget recovers it.

The seven shapes

Every automation candidate lands in one of these:

  1. No AI. Rules, or the status quo, done properly.
  2. Deterministic automation. Predictable input, clear rules, no judgement.
  3. Search and RAG. The answer already exists in your documents.
  4. AI-assisted workflow. AI extracts or drafts, a deterministic step executes, a human owns the outcome.
  5. Copilot. A person stays in the loop and asks as they work.
  6. Single agent. One system, multiple steps, real autonomy.
  7. Multiple agents. Several systems, genuinely separate responsibilities.

Most teams reach for 5, 6 or 7. Most problems belong in 2, 3 or 4.

Describe the situation, see the shape

The tool takes plain sentences. Your goal, the systems involved, what has to stay inside the EU, how many engineers you have, whether accuracy matters more than speed. It captures each signal as you type and ranks the shapes against them.

It also tells you when it disagrees with you. Ask for a copilot and it will still rank a copilot, but if what you described is really an extraction step with a review gate, it will say so and show you why. A tool that only confirms your assumption is not worth the download.

Open the AI Solution Shape tool

What you get

A ranked recommendation with the reasoning, plus the detail layer that usually takes a workshop to produce: the integration spine from source system to system of record, who owns a record once an agent creates it, how it is labelled as agent-created, and how it gets rolled back.

That last part is the part most pilots skip and most production deployments fail on. Governance is not a phase after the build. It is part of the shape.

You can download the result as a PDF, or share a link to it, and bring either one into a scoping call so the conversation starts from a diagram rather than a blank page.

It runs on your machine

The model is a 26 million parameter function-calling model, downloaded once and run inside your browser. Your text is never sent anywhere. That is a deliberate constraint: a tool that asks you to describe your internal processes should not be quietly collecting them.

It also means the tool is honest about its limits. It is small, it is fast, and when a sentence does not land it asks for more rather than guessing.

From pilot to production

Running an AI pilot that is not production-ready yet? That is exactly what I do: audit, fixed-price scope, delivery in 2–6 weeks.