The gap between you and your competition is often the time wasted on the wrong problem. Are you solving the right one?

Most organizations move straight from ‘we have a problem’ to ‘let’s hire someone to fix it.’ The Premis™ Brief sits in between. It takes the problem you’re dealing with — the one where the team is split, or the initiative that keeps stalling, or the decision nobody wants to make — and runs it through a rigorous diagnostic before anyone spends budget or commits a direction. You get a structured read on what’s actually broken, three strategic options with one recommendation, and a 90-day execution plan — without a retainer.

Business leaders and strategy teams who need to move — without waiting months for a consulting engagement. If you’re dealing with a problem that keeps resisting straightforward solutions, preparing for a difficult board conversation, or facing a decision where every option has a credible argument, this is built for you.

The ones where reasonable people disagree on what’s actually wrong. An initiative that’s stalling despite the right team and resources. A market position that isn’t holding. A strategic decision where the data points in different directions. The Premis™ Brief is not designed for simple operational problems with clear answers — it’s built for problems where the framing itself is uncertain.

Most AI tools take your framing at face value and generate a response. The Premis™ Brief probes the framing of the problem first — running a structured four-stage diagnostic before any answer is produced. It classifies the problem type, builds a primary hypothesis grounded in what you’ve described, stress-tests it against alternatives, and designs the specific tests that would confirm or overturn it. Only then does it move to strategy. The output isn’t a generated answer. It’s a reasoned position with the logic visible.

Unlike a standard AI tool that responds to a single prompt, The Premis™ Brief runs a pipeline of specialized agents. Each has a distinct task, a structured input from the previous stage, and a defined output that feeds the next. An agent doesn’t chat — it receives a specific job, reasons through it, and hands a structured result forward.

After the diagnostic completes, three agents run in sequence:

Blueprint — converts the diagnosis into a scored problem blueprint: root causes, constraints, evidence gaps, and the fastest available test. Everything downstream reasons from this structure.

Strategy — generates three distinct strategic options, commits to one recommendation, names what it sacrifices, and states the single assumption it can’t survive being wrong about.

Execution — converts the chosen strategy into a 90-day task-level plan with action-first tasks, functional owners, binary success metrics, dependencies, and the decisions that need a human in the room.

The methodology governing each stage is built into the system. It doesn’t change with how the question is phrased.

It will tell you when it’s uncertain. Every diagnostic includes a confidence level and a list of what the analysis is working without — the specific evidence gaps that would sharpen or change the conclusion if filled. The diagnosis is a committed hypothesis to pressure-test, not a verdict to act on without review. The strategy names the single assumption it can’t survive being wrong about.

Each diagnostic runs independently — your input is not used to train the underlying model, and you always get a fresh analysis grounded in the specific details you provide. What does carry forward is your organization context: authenticated accounts can save standing constraints, what’s already been tried, and current strategic priorities. That context is injected into every diagnostic automatically, so the analysis reflects your situation rather than a generic one. Deeper memory — tracking decisions across runs and building on prior diagnostics — is on the roadmap.

Six stages. Three downloadable outputs.

Output	What’s in it
The diagnosis	What kind of problem this is and what decision needs to be made Primary hypothesis grounded in what you wrote — alternatives ranked by probability, falsifiability condition for each An issue tree built to pressure-test the diagnosis — each branch marked as supporting or challenging it Specific tests that would confirm or abandon it — and where analysis hands back to you
The strategy	Three meaningfully distinct strategic options One committed recommendation with constraint-aware justification The assumption it cannot survive being wrong about The leading indicator that a pivot is needed When Deep Research + Competitive Context is on, options are developed with awareness of the external market landscape — not just the internal problem frame.
The execution plan	90-day task-level plan with action-first tasks Functional role owners, binary success metrics, dependencies Failure modes with early signals Decisions that need a human in the room

The diagnosis and strategy download as PDFs — formatted for a leadership conversation. The execution plan downloads as a structured Excel workbook, organised by phase, ready to assign.

Treat it as a serious first position, not a final verdict. The diagnosis tells you its confidence level. The strategy names the assumption it can’t survive being wrong about, and the leading indicator that would signal it’s failing. The execution plan names the calls that need you in the room — the ones that depend on knowing your organization, your people, and what’s actually feasible. The system is honest about where it runs out.

Yes. The diagnostic and strategy brief download as structured PDFs — formatted for a leadership conversation and designed to be presented directly. The execution plan downloads as a structured Excel workbook, with one tab per 30-day phase, pre-filled with tasks, owners, success metrics, and dependencies — ready to take into a meeting and start assigning.

The diagnostic PDF includes a section marked Sensitive Analysis: the handoff note, which names the specific political, relational, and contextual calls the analysis cannot make on your behalf. This section is included by default but can be excluded from the download using the toggle next to the download button — useful if you’re sharing the report more broadly and want to keep that layer of the analysis internal.

The plan is designed to be taken into a meeting, not acted on in isolation. It gives you tasks, owners, success metrics, and dependencies. It also names what it can’t resolve — the missing evidence that would sharpen the diagnosis, the single assumption the strategy cannot survive being wrong about, and the decisions that need a human in the room. Those aren’t disclaimers. They’re the specific things that require you. Read both: the plan tells you what to do, and the flags tell you where your judgment replaces the analysis.

The Premis™ Brief runs on enterprise-grade infrastructure with encrypted connections and security headers applied to every response. The Premis™ Brief retains a partial record of each run — including the problem classification, confidence level, and a summary excerpt of your input — for product improvement and quality review. The full content of your submission is not retained. Apply the same standard you would to any professional tool that processes text through an external AI provider: describe the problem with enough specificity to be useful, without including information subject to confidentiality obligations or regulatory restrictions.

Your input goes to the Anthropic API to generate the diagnostic. The Premis™ Brief retains a partial record of each run — problem classification, confidence level, and a summary excerpt of the input — for product improvement and quality review. The full content of your submission is not retained beyond what is needed for the diagnostic to run. Your email address is associated with your runs if you are signed in.

We ask that you don’t — not because of a technical limitation, but because it’s the right standard to apply to any tool that sends text to an external AI provider. The diagnostic works on the structure of a problem, not its identifying details. Describe the situation with enough specificity to be useful, without naming clients, internal financial data, or anything subject to a confidentiality agreement.