Question 1

How are outcomes verified?

Accepted Answer

Every case study follows the same loop: the agency enters the client outcome through the intake form, the AI drafts a tight challenge → approach → result narrative, and the client signs off through a one-click approval link. The approval link is sent to /approve/[token] — public, token-gated, and noindex so it never appears in search. Only after the client clicks approve does the story publish to /p/[slug]. The published proof page itself is fully public. The approval link is the only piece that stays private to the client.

Question 2

What does a proof page show?

Accepted Answer

A proof page at /p/[slug] carries four pieces of proof, in this order: Client outcome — the challenge, your approach, and the measurable result, in tight narrative form. Closed-won metric — the dollar value captured at intake finalise, surfaced front-and-center so the page reads as revenue attribution, not social proof. Testimonials — ranked by the AI placement engine so the strongest quote lands where it converts. Agency branding — your logo, palette, and accent color run across the page. Agency tier removes OutcomeStory co-branding entirely.

Question 3

What's the pricing?

Accepted Answer

Three tiers, every one routes through the same intake loop so you feel it before you pay: Free — one end-to-end client story across intake, approval, and publish. Five AI drafts a month, one published proof page, OutcomeStory co-branding. Pro — for active agencies scaling closed-won proof weekly. Unlimited drafts, unlimited published proof pages, client-ready branding (logo, palette, fonts), custom domain on proof pages, and AI-driven testimonial placement. Agency — white-label, multi-client workspaces. Everything in Pro with unlimited team members, the OutcomeStory co-brand removed, per-client intake forms, and dedicated onboarding. Full breakdown, per-tier features, and the most-popular call-out on the pricing page.

Question 4

How is data isolated?

Accepted Answer

Every draft and proof page is scoped to the owning agency. You only see your own rows in the dashboard; cross-agency reads are rejected at the query layer. Proof pages are only rendered when publishedAt is set — the loadPublishedCaseStudyBySlug guard returns a 404 for unpublished slugs, so drafts never expose content at the public /p/[slug] route. Approval tokens (sent to clients) are scoped to a single draft and expire after the workflow completes.

Question 5

Who owns the content?

Accepted Answer

You do — the agency owns every row of client data. Export. Every published proof page carries a PDF download button, so a client story is portable the moment it goes live. Publish. A story goes from draft to /p/[slug] only after you confirm the client's approval. Unpublish. You can take a story down at will from the dashboard, and the slug begins returning a 404 the same day.

All questions

How are outcomes verified?

What does a proof page show?

What's the pricing?

How is data isolated?

Who owns the content?