The blank page, abolished.
The desk deals pitch slips built from the client’s own brand brain — topic, platform, format and a suggested day, and never more than two on the same platform. Take one and it opens a new post with the topic and platform filled in. Spike a theme three times and it sinks to the bottom of the pile for a fortnight.
Suggestions on every plan · credit-metered — opening the desk can regenerate the pile, which is charged
Ideas argued from their knowledge base — not a trending-topics feed.
Suggested: Tuesday
Suggested: Thursday
Suggested: Monday
Spiked: the one signal it learns from
Argued from the brand brain, filtered like an editor.
Pitches aren’t random and they aren’t trending-topic scrapes — every slip traces back to the client’s own knowledge base, and the desk remembers what you spike.
The theme map
The knowledge base is distilled into weighted core themes per client — pitches draw from the map, so a skincare brand gets barrier science, not generic “5 productivity hacks”.
The dashboard counts your empty days
The dashboard counts the days your calendar has left empty and prompts you against them. The pile itself is not ordered by date — each pitch carries a suggested day, which you can move.
Two per platform, and nothing thrown away
No more than two pitches on the same platform reach you at once, so one channel cannot take the pile over. Nothing is merged and nothing is deleted — the pile is ordered, not filtered, and a low-scoring pitch can still be dealt when there is little else.
It learns what you spike
Dismiss a pitch and it’s remembered. Spike the same theme three times and it sinks to the bottom of the pile — still there if the pile is thin, and back at full weight after a fortnight. It’s the one learning behaviour we claim, because it’s the one that exists.
What the engagement data will teach — the thresholds, printed in advance.
Published posts report their engagement back. Three instruments are written to read it, each with a printed threshold — because statistics on four posts would be astrology. None of the three is switched on yet: the thresholds below are the gates they will use, not gates you are approaching.
Written to estimate a rate, not a reach
Written to estimate a post’s engagement rate from your own history — hook style, length, day, quality score. Not wired to anything you can open, and the history it reads is not being recorded yet.
Written to learn your audience
Correlation maths that would check which quality dimensions actually predict engagement for this client. No score is re-weighted today — the six dimension weights are fixed, and nothing in the product can start one.
Written to spot a tired topic
Watches the trend across repeated keywords so a real decline flags the topic. The badge is not shown anywhere in the product.
Straight answer: none of these three is running yet. The code and the thresholds are real and printed above so you can hold us to them; what they don’t do is steer which topics the pitch desk deals, or change your score. Two desks, side by side, and only one of them open. When any of it switches on, the changelog says so first.
The scoring gate itself lives on the AI Pipeline pageToday the pitch desk learns from one signal: your dismissals. It does not yet learn from what you use, save, or edit — plenty of tools imply otherwise about themselves; we’d rather under-claim and ship the rest later.
There are no predictions yet. The code is written and its gate is printed above, but nothing in the product calls it and the history it would read is not being recorded. When it runs it will give an engagement-rate estimate from your own posts — never a promised reach number, and never a crystal ball.
The pile is dealt
Take tomorrow’s pitch.
Start free with 5,000 credits — paste a client’s URL and the desk starts pitching from their world the same day. Roughly a fortnight of real production, on us.
No card · No trial countdown · No per-client fees