This page follows one fictional initiative through all nine steps, from a persona to a batch plan and a CSV file for Jira's bulk import. Each step passed its output to the next with one click, inside the browser, and each step links to the run it produced, so you can judge the output itself. Seven of the nine steps call an AI model to draft; the persona needs no AI call, and the journey map's AI fill is optional. In real use, people revise those drafts and approve them at each gate.
PetHealth is fictional. The company, people, source records, metrics, approvals, and operating environment in this example were created for demonstration. The displayed artifacts use the structures produced by the tools and are intended for evaluation.
The example contains four kinds of information: scenario facts (fictional inputs intentionally supplied to keep the test coherent, such as the 22% support-contact baseline), fixture evidence (fictional records with source-like identifiers used to test provenance and propagation), model-generated content (draft requirements, assumptions, estimates, NFRs, risks, and narrative), and deterministic results (selected calculations and structural conditions recomputed in code).
A fixture citation shows that a generated claim was associated with a supplied record. It does not make the fictional claim independently true. The review gates shown in this case are modeled checkpoints, not records of approvals by real PetHealth employees.
PetHealth is a fictional mid-size pet insurer with a common problem: members don't trust the claims process. Claim-status questions account for 22% of all support contacts, members describe the wait after submitting a claim as a black hole, and leakage (money lost to errors and fraud in claim adjudication) cuts into margin. The company context, evidence, and competing priorities stay the same across every tool, and each tool takes its input from the one before it, so no step gets a hand-tuned prompt.
Each artifact below is output captured from the tools themselves.
Marcus Chen, a software engineer and PetHealth member, whose quote frames the initiative: "I just want to know it's working." The card carries his Jobs to Be Done statement, his comfort with each channel, key interactions marked with friction badges, and an estimate of what his unmet job costs the organization.
A stage-by-stage map whose clusters of pain points become opportunity seeds: short statements of where the experience breaks and what it costs, exported to the next step.
Each epic lists its riskiest demand, feasibility, and viability assumptions, and a plan for measuring its benefits, including the tracking that would need to exist first. The main benefit target: claim-status share of support contacts falls from 22% to ≤12%.
Five business cases in a standard format, including the Real-Time Claim Status Tracking case that the rest of this page follows.
A ranking with a funding cutoff. Real-Time Claim Status Tracking falls above it, so it becomes the epic the rest of the workflow plans.
A roadmap, one of the workflow's four main outputs.
The BRD for Real-Time Claim Status Tracking with eight business requirements (BR-01 through BR-08), an assumptions section, and the executive sign-off package.
The delivery plan, plus the workflow's last handoff: a CSV file for Jira's bulk import, with Summary, Issue Type, Epic Link, Priority, Original Estimate, Sprint, Acceptance Criteria, and Issue Links columns. A person reviews it and imports it into Jira. The stories in the chosen batch carry their build prompt in the description: context, the requirements and acceptance criteria copied from the plan, dependencies, a suggested approach, checks, and what to leave alone.
I'll update this list as outside evaluations come in. Current issues visible in the example:
The fastest way to evaluate these tools is to open the two or three captured runs above that your role would be accountable for, and ask whether they would survive review in your organization. If the answer is "mostly, and I can see what I'd change," that's the conversation the beta is for.