SALES ENABLEMENT · REVENUE ENABLEMENT · PRODUCT MARKETING · CUSTOMER SUCCESS

A kit for the Claude desktop app. Paid Claude plan required.

Your rep needs a battlecard by Thursday.Give them an answer they can back up.

Bring the buyer’s objection, your deal notes, and the proof your company already has. StoryOS helps you draft what the rep can say, see which claims need checking, and choose the question to ask next. You review the wording before it goes into the call.

$197$79

Needs the Claude desktop app on a paid plan, Pro or above · Founding price · One payment · Yours forever · No renewal · No refunds

EXAMPLE ONE · THE BATTLECARD

It checks your numbers too.

Every asset closes with a list of what it could not prove, sorted by who has to act. Your side gets the same treatment as the competitor’s. You see which claims need checking before a rep repeats them to a buyer. Read the full battlecard and its evidence check →

FROM THE REVIEWED EXAMPLE · HARBORLINE VS. IRONCLAD

×Sentence flagged: “Ironclad is powerful, and you’ll spend a quarter configuring it and an admin maintaining it.”

×Why: the competitor publishes no rollout timeline. The line was company-approved wording, and nobody could source the quarter.

What the rep can say instead: “With two people on your legal team, who would own configuration in the first month, and how much time would they need?”

EXAMPLE TWO · THE SALES TO CS HANDOFF

The deal as sold. The deal as delivered.

Every deal is won with a story. Then it’s handed to somebody who wasn’t in the room.

AS SOLD AS DELIVERED the seam
Sales said: they’re buying a behaviour change across the team. CS heard: roll out the tool, hit activation numbers.
One quarter later the renewal is at risk and the champion feels oversold. The handoff is a first-class play here, not an afterthought.
What Sales promised
Live in under two weeks. A drop in median contract cycle time within 60 days, measured against the customer’s own baseline. Counsel approves every AI redline. Each promise carries the wording it was made in and a check-by date.
Who heard it
The Head of Legal Ops, who owns the cycle-time number. The CFO, who bought the revenue story. The GC, who agreed once she heard that nothing sends without counsel. CS knows who is holding which promise before kickoff.
How the customer will judge success
In the champion’s words: “If sales stops escalating contracts to my inbox, it’s working.” The rep quoted that from memory, so the brief flags it for CS to confirm.

From the handoff brief that ships in the kit, written on the fictional demo company.

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.

Describe the moment in plain words. The asset comes back written from 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.

More plays are in the kit. See everything inside → · Read a complete reviewed example →

WHAT IS IN THE FOLDER

One company brain. Every asset is written from it.

Add your positioning and proof once. Each asset starts from them and closes with what still needs checking. The agents, the plays and how a request gets routed are in Inside the kit.

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?

Yes. Claude can draft a battlecard and flag claims that need a source. StoryOS gives you a ready-made process for doing that every time a rep asks for help. Add your positioning and proof once. For each deal, start with the buyer’s objection and get a talk track, the evidence behind it, and the open questions to resolve. You decide what the rep takes into the call.

What the process is made of, piece by piece: Inside the kit.

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 (the kit has a product launch play and a marketer agent), 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, the plays, the agent definitions, the skills, and the guides. The full list is on Inside the kit. 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.
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 reviewed example. 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 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.

$197$79

FOUNDING PRICE

Own it once. It doesn’t renew.

$197 list. $79 founding price. One payment, one seat, yours forever, updates included. Needs the Claude desktop app on a paid plan, Pro or above. No refunds.