Part 2 · Set up
What you sell
The single input that everything downstream reads. Get this one right.
01What it is
What the venture sells, the problem it solves, who buys it and what they care about. Read from your website first, then corrected by you.
02Why it exists
Every draft, every read and every content idea is written from this. A vague context produces vague output on every channel at once, and the failure is hard to trace back because nothing looks broken.
The correction step matters more than the reading step. The reader gets you roughly right from a website; you are the only one who knows which half is wrong.
03How to use it
- 01Let it read your site, then read what it came back with, line by line.
- 02Correct the problem statement first. It carries more weight than the product description.
- 03Name the buyer by role and situation, not by company size alone.
- 04Say what you are not. An exclusion prevents more bad output than an inclusion creates good output.
04What good looks like
- You give it
- "We help heads of RevOps at 50-to-300-person B2B software companies replace a Salesforce setup nobody trusts, usually after a failed migration."
- You get
- Content ideas about failed migrations and trust in reporting. Reads that fire on hiring in RevOps and on tooling changes.
- Why
- The context names a role, a situation and a trigger, so both engines have something specific to match against.
Example data, from the demo workspace
05What weak looks like, and what it costs
- You give it
- "We help businesses grow with AI-powered solutions."
- You get
- Content anybody could have written and reads that fire on any company doing anything.
- Why
- Nothing in that sentence excludes a company, so nothing downstream can rank one company above another.
Derived from the rules in the code