It writes what your team needs. In your words.

IF NOTHING CHANGES

The quarter goes like this.

WEEK ONE

The competitor turns up in three deals.

You write the battlecard yourself, at night. It’s good. It takes four hours you did not have.

WEEK SIX

A rep quotes a number nobody can source.

It came off a slide from last year. The prospect checks it. You find out in the loss review.

WEEK TWELVE

You still have not started the AI project.

It has been on the plan since January, under the things that only happen when the quarter is quiet. The quarter is never quiet.

WHAT COMES OUT

Six of the things you make every week.

You never pick a tool or name an agent. You describe the moment, and the right specialist shows up already knowing your positioning, your proof and your objections.

Competitive battlecard

Where they are strong, said honestly, then the three angles you win on, each with the approved words to say out loud.

Objection handling

“You’re more expensive.” The reframe, the proof behind it, and the question that moves the conversation on.

ROI and the business case

The hours, the arithmetic, and the one number it refuses to guess because the CFO is the person who holds it.

Discovery call prep

Who is in the room, what each of them is measured on, and the questions that surface how they actually buy.

Sales to CS handoff brief

Every promise made in the room, who made it, and what CS has to deliver in the first ninety days.

QBR narrative

Value promised against value delivered, line by line, with the gap named before the customer names it.

Twelve moves in all, and Athena builds you a new one whenever you keep hitting something the twelve do not cover. Read a complete one, unedited →

THE PART A CHAT WINDOW WILL NOT DO

It checks your numbers too.

Paste your positioning into any chat window and it will hand your own claims back to you as fact, because you said them. This one doesn’t. Every asset closes with a list of what it could not prove, sorted by who has to act, and your side gets the same treatment as theirs. It’s the difference between an asset your rep forwards and one that gets them caught out in front of a customer.

FROM A REAL RUN · THE LIST ABOUT YOU

×Your “40% faster onboarding” has no date and no source in the brain.

×Your “most customers see value in week one” was never measured.

×Your win rate against them is from Q1. It’s five months old.

This isn’t the competitor’s audit. It’s yours, and your reps are already using these numbers.

WHAT IS IN THE FOLDER

One company brain. Eight specialists reading from it.

You never pick a tool or name an agent. You say what is happening, a competitor came up, a call is tomorrow, a deal just closed, and the right specialist shows up already knowing your positioning, your proof and your objections.

The company brain

Your voice, your differentiators, your proof, your objections, your Sales to CS handoff. Every specialist reads it before it writes a word. It refuses to write from anything else.

The competitive read

Researches the competitor first and carries a source and a date on every fact. It refuses a rival vendor’s own blog as a source.

The Sales to CS handoff

The promises made, the stakeholder map, the first ninety days, carried across the wall intact. Every promise still open ships tagged with who holds it and the question that closes it.

The audit, on everything

Nothing reaches you unaudited. Every open item ships with the move that closes it: the question to ask, the person who holds it, or the search that settles it. It refuses to assert what it cannot source, including about you.

Human Always

When instructions conflict, the order is you, then the brain, then the play, then the agent. You win, every time.

THE FAIR QUESTION

Why not just Claude and a good prompt?

You can. Nothing here is magic, and anyone telling you otherwise is selling something. What you’d be doing is building the thing below, on your own time, and then finding out on live deals which parts of it were wrong.

69 files, about 37,000 words

That’s the whole kit, and you can count it after you buy. Eight agent definitions, twelve plays, thirteen skills, the brain template, the governance rules and the guides.

The routing, which is the hard part

A prompt gets you one good answer. The work is deciding which move a situation calls for and pulling the right knowledge into it, every time, without you naming a tool. That decision table took the longest to get right and it’s the difference between a system and a folder of prompts.

The refusals

Any model will confidently repeat your own unproven number back to you, because you said it. Getting one to stop and tell you it can’t prove your claim takes rules that survive a long session, and it’s the part a single prompt never holds.

What it costs you to build

A quarter of evenings, if you already know what good looks like. The certification that teaches you to build it is about nine times this price and you still do the building. This is the same work, finished, for the cost of a decent lunch for two.

BEFORE YOU BUY

The questions worth asking first.

The ones a careful buyer asks, answered where you can read them before paying rather than after.

Who is this for, exactly?

The person who produces what the revenue team says out loud. That is usually Sales Enablement or Revenue Enablement, often Product Marketing (play 07 is a product launch, and the marketer is one of the eight), and Customer Success leaders, who get their own edition with the post-sale plays and the renewal read. It is written for one person doing that job well, in a company of roughly 50 to 500 people. It is not a tool you roll out to reps, it is the thing you use to arm them.

What am I actually receiving?

A zip file. Inside it is a folder of markdown files: a company brain, twelve plays, eight agent definitions, thirteen skills, and the guides. You open that folder in the Claude desktop app and it becomes a working system. There is no app to log into and no account on our side. The files sit on your machine and stay there.

Can I use it in Claude on the web, or in Cowork, or in Gemini?

The web version of Claude won’t work, because it can’t read a folder on your computer. StoryOS is built and tested for the Claude desktop app, using its Code tab, on a paid plan. Other tools that can read a local folder may well run it, and we haven’t tested them, so we won’t claim they do. Gemini is not supported.

Why not just do this in a chat window for free?

You can get one good battlecard from a chat window in ninety seconds. What you can’t get is the second list. A chat window will happily repeat your "40% faster onboarding" back to you as fact, because you said it. StoryOS treats your claims the way it treats theirs, and tells you which of yours carry no date and no source. That’s the difference, and it’s the whole product.

Can I add my own agents and capabilities?

Yes, and that is a real feature rather than a promise. Athena, the guide inside the kit, builds new plays, new skills and whole new specialists on request. You describe the situation you keep hitting, she proposes the play, shows you the exact change, and writes nothing until you say yes. She never touches your brain or your finished work while extending the system.

What does it cost me beyond the $79?

A paid Claude plan, from $20 a month. Nothing else.

How much work is it before it sounds like my company?

About 20 minutes to install. Loading your brain is the part that is yours, and how long it takes depends on what you already have written down. You can start with a link to your site, two things that sound like you and one deal you remember well, and sharpen it every time you run a play. The five day guide inside walks the thorough version.

What is your refund policy?

None. It’s a file, and a downloaded file can’t be returned. So everything you need to decide is published before you pay, including a complete unedited output. Read that first.

Where does my data go?

Your brain, your outputs and your notes are files on your machine. We never see them and there is no server of ours involved. What you type goes to Anthropic exactly as the rest of your Claude session does, under your own plan. If your organisation blocks outbound lookups, one setting turns research off and it works from your files alone.

I am buying for a team, not for me.

The licence is one seat per person, and there is a team tier built for exactly this: one canonical company brain that every seat reads from, so eight people write from the same truth instead of eight versions of it. Team pricing →

Does it break when Anthropic changes the interface?

The kit is markdown files, so there’s nothing to break in it. What can change is the click path inside Claude for opening a folder. When that moves, the install guide is updated and the update reaches the email you bought with, at no cost, because you own the kit rather than rent it.

Who built this?

It was built by a sales enablement professional who has led enablement inside large companies and small ones. That’s why the twelve plays are the moments that actually come up in a quarter rather than the ones that look tidy in a framework, and why the handoff to CS is a first-class play instead of an afterthought. Need something? Email storyos@connecthedots.co.

Your team needs the battlecard Thursday.Not an AI project.