PRODUCT

Watch. Decide. Brief.Ship. Prove.

The whole loop, unabridged. Every chapter from the front page, at working depth.

afterlaunch · the recordsample data
your recordTUE 11 AUG
3shipped
1receipt earned
5briefed and waiting
new since yesterday

Perplexity cited your /vs page for "ai search tools"

receipt
the board
  1. 1Reply to the r/SaaS thread naming two rivals
  2. 2Publish the comparison page people read last
  3. 3Add llms.txt so assistants read your site right
  4. 4Answer the Hacker News thread on AI search
founder@laptop ~ afterlaunchsample data
~ afterlaunch
AFTERLAUNCH · TUE 11 AUGyour record
3 shipped · 1 receipt earned · 5 briefed and waiting
NEW SINCE YESTERDAY
Perplexity cited your /vs page for "ai search tools"[receipt]
THE BOARD
1 Reply to the r/SaaS thread naming two rivals
2 Publish the comparison page people read last
3 Add llms.txt so assistants read your site right
> 1
brief loaded: 3 sources · your voice · acceptance bar
[your agent writes the reply here, in your voice]
1 revise 2 ship 3 skip
1.0 · DIAGNOSE

See how people find you.

The scan is where the loop starts. Every ranked move traces back to something these checks found, and every finding keeps its date.

1.1

Asked, answered, archived.

Four engines are asked the questions people ask in your category. Every answer is kept with the sources it cited.

ai visibility · 15 questions askedsample data

share of voice

ChatGPT3 / 15

Gemini5 / 15

AI Overviews1 / 15

Perplexity6 / 15

rivalapp leads 2 of 4 engines

"best ai visibility tool for saas"you

"how do i track chatgpt mentions"rivalapp ○

"ai search tools compared"rivalapp ○

"does my site show up in ai answers"you

"geo tools for small teams"rivalapp ○

"ai visibility tracker pricing"you

asked again each week, every answer archived with the sources it cited

1.2

Read like an assistant.

Crawlability, entities and llms.txt checked the way an assistant reads your pages. Each check names the page it failed on.

site audit · 9 of the checkssample data
  • robots.txt lets assistants crawlpass
  • Canonical tags on every pagepass
  • Product schema an assistant can parsepass
  • llms.txt missingfix
  • Slow LCP on /pricingfix
  • Sitemap fresh, 46 pagespass
  • Headings answer the questions people askpass
  • Your price is an image on /pricingfix
  • Wikidata entity matches your product namepass

every failed check names its page, so the fix is a task, not a hunt

the watch · cadencesample data
  1. 28 JulScan run. Four engines, your site, your surfaces.
  2. 04 AugScan run. Two answers changed.
  3. 11 AugScan run. Perplexity started citing you.
  4. 18 AugNext run, already scheduled.

Weekly, without asking.

The watch runs every week on its own. You never schedule it.

the archivesample data

Answers kept, with sourcessince 02 Jul

Pages the engines cited insteadevery run

What changed since the run beforeevery run

Nothing is thrown away.

Every answer, source and date stays on the record, so change is visible.

1.3

Where you show up.

Communities, directories and rival mentions watched for the threads people actually read. Absent is a finding too.

reach · where you show upsample data

r/SaaS thread found. 312 comments, no vendor has answered.present

Hacker News thread on AI search. 48 points, two rivals replied.present

G2G2 listing missingabsent ○

Trustpilot profile unclaimedabsent ○

Directories: 12 of 47 present35 absent ○

Product HuntG2G2TrustpilotGitHubcbCrunchbaseWikidatacommunitiesdirectoriescomparisonspressYouTubeLinkedIn

absent is a finding: the board can act on a listing you do not have

2.0 · DECIDE

One board. Ranked.

Ranking is the product decision. What reaches the top is what one founder can finish today, not everything that could be done.

2.1

One screen each morning.

What shipped, what earned a receipt, what is briefed and waiting. The same numbers your agent reads.

the standup · tue 11 augsample data
your recordTUE 11 AUG
3shipped
1receipt earned
5briefed and waiting
new since yesterday

Perplexity cited your /vs page for "ai search tools"

receipt
the board
  1. 1Reply to the r/SaaS thread naming two rivals
  2. 2Publish the comparison page people read last
  3. 3Add llms.txt so assistants read your site right
  4. 4Answer the Hacker News thread on AI search
  5. 5Claim the Wikidata entity for your product
2.2

Leverage against effort.

Every move is scored on what it could move and what it costs you to do. The board is the order that comes out.

the board · why nowsample data
rankmoveareawhy now, measured
1Reply to the r/SaaS thread naming two rivalsReach312 comments, your category, no vendor has answered
2Publish the comparison page people read lastAI Visibility4 of 4 engines cite a rival comparison, not yours
3Add llms.txt so assistants read your site rightSite3 of 4 engines misread your pricing page
4Answer the Hacker News thread on AI searchReach48 points, two rivals already replied
5Claim the Wikidata entity for your productEntity1 of 4 engines knows what your product is
6List on the two directories rivals are onReach35 directories absent, two of them cited
7Put your price in text on the pricing pageSite2 of 4 engines quote the wrong price

ranked by leverage, capped at shippable

the capsample data

found this week

19worth doing
5on the board

the rest keep their place and wait

Capped at shippable.

The board holds what a founder can finish, not the whole list of what exists.

move 2 · why nowsample data

WHY NOW

4 of 4 engines cite a rival comparison when people ask which tool to choose. Observed 9 Aug, across fifteen questions.

Every rank has a why.

The reason is a measurement with a date, never a hunch about your market.

2.3

Ship one, get the next.

Ship or skip a move and the next one is drafted from fresh findings. The board is never empty and never endless.

the board · replenishedsample data
rankmoveareastatus
1Answer the Hacker News thread on AI searchReachnew · replaces shipped move
2Add llms.txt so assistants read your site rightSite
3Claim the Wikidata entity for your productEntity
4List on the two directories rivals are onReach
Publish the comparison page people read lastAI Visibilityshipped Tue
Reply to the r/SaaS thread naming two rivalsReachshipped Mon
3.0 · BRIEF

Briefed, not suggested.

A suggestion is a sentence. A brief is the evidence, the voice and the bar, assembled so the work can start at once.

3.1

Every claim has a source.

Each line carries the page, the engine and the date it was observed. Nothing in a brief arrives unattributed.

brief · move 2sample data

Publish the comparison page people read last

4 of 4 engines cite a rival comparison when people ask which tool to choose.

EVIDENCE

  • rivalapp.com/vs-guidecited by ChatGPT · observed 8 Aug
  • g2.com/categories/ai-searchcited by Perplexity · observed 9 Aug
  • reddit.com/r/SaaS/comments/1f2k9dcited by Gemini · observed 9 Aug
  • rivalapp.com/pricingcited by AI Overviews · observed 9 Aug
  • yoursite.com/vs (missing)not cited by any engine · checked 11 Aug

WHAT PEOPLE SAID

"We went with rivalapp because their comparison page was the only one that answered the pricing question."r/SaaS thread, top reply · observed 9 Aug

VOICE

your voice · 12 samples
3.2

Written in your voice.

Voice samples from your own writing shape the draft before you ever read it. The samples come from what you already published.

brief · voicesample data

FROM YOUR OWN WRITING

"We built this because we kept losing the thread ourselves, three tabs deep on a Tuesday."

"No dashboards. Just the next thing worth doing, and the reason it is worth doing."

"We would rather ship one small honest thing this week than plan a big one."

your site, 5 pagesloaded

your posts, 4 samplesloaded

your docs, 3 pagesloaded

house style: short sentences, no jargonapplied

voice loaded from 12 samples

acceptancesample data

THE BAR THIS DRAFT MUST CLEAR

  • Names both rivals and links their pages
  • Answers the pricing question in the first 100 words
  • Ships with a comparison table engines can parse

The bar comes first.

The brief says what done looks like before a single word is drafted.

sourcessample data

SOURCES, WITH DATES

  • rivalapp.com/vs-guideChatGPT · 8 Aug
  • g2.com/categories/ai-searchPerplexity · 9 Aug
  • reddit.com/r/SaaS/comments/1f2k9dGemini · 9 Aug

Dated, not just linked.

A source without a date is a rumour. Each one carries the day it was seen.

3.3

Read by your agent.

Your agent reads the board and the briefs over the MCP server. There is no copying between windows.

afterlaunch mcp · get_movesample data
> get_move 2
{
"title": "Publish the comparison page people read last",
"area": "ai_visibility",
"rank": 2,
"why": "4 of 4 engines cite a rival comparison",
"evidence": [5 sources, each with an observed date],
"quotes": [1 thread reply, observed 9 Aug],
"voice": "12 samples",
"acceptance_criteria": [3 checks],
"status": "briefed"
}
read over the MCP server · no copy and paste

the same brief the record shows you

4.0 · SHIP

Ship from your terminal.

The move, the draft and the decision happen in one conversation. Nothing leaves your account until you say the word.

4.1

One state, two views.

The same window shows the terminal or the record. Whichever you open, you are looking at the same state.

founder@laptop ~ afterlaunchsample data
~ afterlaunch
AFTERLAUNCH · TUE 11 AUGyour record
3 shipped · 1 receipt earned · 5 briefed and waiting
THE BOARD
1 Reply to the r/SaaS thread naming two rivals
2 Publish the comparison page people read last
3 Add llms.txt so assistants read your site right
> 1
brief loaded: 3 sources · your voice · acceptance bar

one state, two views

afterlaunch · the recordsample data
your recordTUE 11 AUG
3shipped
1receipt earned
5briefed and waiting
the board
  1. 1Reply to the r/SaaS thread naming two rivals
  2. 2Publish the comparison page people read last
  3. 3Add llms.txt so assistants read your site right

one state, two views

4.2

Saved to the record.

Shipped work, its brief and its sources stay together in one permanent entry. Opening it later gives you all three.

the record · move 2sample data

Publish the comparison page people read last

Shipped Tue 11 Aug. Drafted by your agent, sent by you.

THE DRAFT AS IT SHIPPED

"A rival's comparison page is what people get when they ask which ai search tracker to use. Here is ours, with both products' real limits and a pricing table engines can read."saved from your terminal · 11 Aug

KEPT WITH IT

  • the brief it was written from3 sources · acceptance bar
  • rivalapp.com/vs-guidecited by ChatGPT · observed 8 Aug
  • g2.com/categories/ai-searchcited by Perplexity · observed 9 Aug

draft saved · Tue

founder@laptop ~ afterlaunchsample data

> update_draft --move 2

writing the draft back to the record

✓ saved. brief and sources kept with it.

The draft goes back.

Your agent writes the draft into the record itself, so nothing lives in a chat log.

after you shipsample data

the thread you replied inwatching

the page you publishedwatching

the four engines, weeklywatching

The watcher arms.

Shipping starts the watch. What you sent is checked for weeks afterwards.

4.3

Nothing ships alone.

The agent drafts and waits. You say ship, and only then does anything leave. Skip is a decision the record keeps.

founder@laptop ~ afterlaunchsample data

> 2

brief loaded: 3 sources · your voice · acceptance bar

A rival's comparison page is what people get when they

ask which ai search tracker to use. Here is ours, with

both products' real limits and a pricing table engines

can read.

ship? 1 yes 2 revise 3 skip

> 1

✓ Shipped. Logged (move 4, Tue). Watching the thread.

nothing ships without your word

5.0 · PROVE

Receipts, not promises.

Shipping is not the outcome. A move is called proven when something outside your own account moves, and the record says which.

5.1

Watched after it ships.

Citations, ranks and answer changes tracked per move, for weeks after it ships. Nothing is marked proven early.

outcomes · last 14 dayssample data

DAY 1DAY 14

after, citations earnedbefore, fourteen days of nothing

Perplexity cited /vs · Thu

Rank 9 to 4 for "ai search tracking" · Mon

ChatGPT now answers with your page · Tue

Your reply is the top comment · Wed

two of five shipped moves moved something outside your own account

inboxsample data

from afterlaunch · sunday 09:00

Your week: 2 shipped, 1 receipt

what moved, what did not, what is next

Arrives on Sunday.

The movement report lands once a week, whether the week was good or quiet.

inboxsample data

from afterlaunch · day 14

Day 14. Here is what changed.

your before and after, side by side

Arrives on day 14.

One letter at the end of the trial, with the two states next to each other.

5.2

What moved this week.

One note each week: what moved, what did not, and what is next. The same numbers the record shows.

weekly report · sundaysample data

from afterlaunch · sunday 09:00

Your week: 2 shipped, 1 receipt

2shipped
1receipt earned
4briefed and waiting

WHAT MOVED

Rank 9 to 4 for "ai search tracking" · Mon

WHAT DID NOT

The llms.txt fix shipped Thursday. No engine has read it again yet.

WHAT IS NEXT

Answer the Hacker News thread. Briefed and waiting since Friday.

5.3

Your before and after.

At the end of the trial the two states sit side by side. Shipped is counted separately from proven.

day 14 · your before and aftersample data

DAY 14

Day 14. Here is what changed.

Rank for "ai search tracking"94

Engines citing you02

Questions where you are named26

Directories you are listed on1215

Five moves shipped. Two of them moved something you can point at.

6.0 · THE OBJECTION

Why not just ask your agent?

Your agent is not missing intelligence. It is missing today's answers about you, and the record of what you already shipped.

6.1

One shared timeline.

Every shipped move, its brief and its sources stay in one timeline your agent can read at any time.

the product timelinesample data
  1. 02 AugDeep scan archived. A hundred-plus checks, four engines.
  2. 03 AugBoard built. Nineteen worth doing, five on the board.
  3. 05 AugShipped: reply to the r/SaaS thread naming two rivals.
  4. 07 AugSkipped: claim the Wikidata entity. Kept for later.
  5. 08 AugReceipt: Perplexity cited your /vs page.
  6. 09 AugShipped: llms.txt published, engines told where to read.
  7. 11 AugRank 9 to 4 for "ai search tracking".
  8. 11 AugBoard replenished. Hacker News thread now rank 1.

one memory, shared by you, the record and your agent

6.2

Today's answers, already read.

Four engines, search, communities and rivals watched each week, so today's answers are already on the record.

the watch · this weeksample data
ChatGPTGeminiPerplexityAI OverviewsGoogle SearchBingRedditHacker NewsLinkedInXYouTubeG2G2TrustpilotProduct HuntGitHubcbCrunchbaseWikidatayour siteyour docsllms.txtdirectoriescommunitiescomparisonspress

watched each week, so today's answers are already on the record

afterlaunch mcp · get_activitysample data

> get_activity --since 02aug

8 entries: 3 shipped, 1 skipped, 1 receipt, 3 scans

each entry carries its brief and its sources

The memory, in one call.

Your agent asks once and has the whole history, not the last few messages.

any mcp clientsample data
Claude CodeCodexCursorWindsurfZed

Works with what you use.

One server, added once. The client you already work in stays the client.

6.3

The same ritual everywhere.

Claude Code, Codex, Cursor and anything else that speaks MCP read the board and the briefs over one server.

any mcp clientsample data
> afterlaunch
AFTERLAUNCH · TUE 11 AUGyour record
3 shipped · 1 receipt earned · 5 briefed and waiting
THE BOARD
1 Reply to the r/SaaS thread naming two rivals
2 Publish the comparison page people read last
3 Add llms.txt so assistants read your site right
open a move by number, or ask for the whole board

same ritual in every client

See it on your own company.The scan is free.

curl https://afterlaunch.io/agents/snippet.md >> CLAUDE.md

First findings in about a minute. No card.