Use case · Launch
Launching: what will the AIs read about you first?
On day one, the engines have nothing on you yet: a blank record, and everything they will read first is yours to write. Epovest orders that work and dates every first.
Views from the app. Your figures replace the sample at the first survey.
From zero, everything is signal
A launch inverts the usual order: you write before you measure. The canon states who you are, the first surfaces put it where engines read, and the tracker starts while the rates still sit at zero. That zero is a dated baseline: from there, the first mention, the first cited source and the first point of answer rate are events you can attribute to something you did.
What you measure
A dated zero
The launch tracker starts before the answers do: every first has a before to be measured against.
First mentions
The first time an engine cites your name, on which prompt and from which page: caught by the checks, kept with its date.
The market's bibliography
The sources feeding your category's answers today: the pages your launch has to reach, ranked by weight.
The launch, as a record
Canon written, pages aligned, first mention, first climb: the story of the launch stays dated in one place.
The recipe
How to run a launch on Epovest: write first, measure from zero
The full working guide for this use: the canon before anything else, the first pages in the order engines find them, a measurement that starts at zero, and the market's bibliography as your target list.
Write the canon before there is anything to measure
Day one is a writing day. The canon states, once, what every page and every answer should repeat: what you are, for whom, since when, at what address.
Name, one-liner, category, the facts that identify you, the perks you want quoted: settle the exact wording now, while nothing contradicts it yet. A launch is the one moment the record is entirely yours to set. Every page published afterwards inherits its language from this sheet, and the sheet stays versioned as the story firms up.
The first pages, in the order engines find them
Engines answer from pages. The surfaces registry turns the launch checklist into a work order: your site, your llms.txt, your profiles, your listings.
Create each surface from its checklist so nothing is forgotten while everything is still fresh: the exact name, the canon's one-liner, the same facts everywhere. Date each alignment: the registry becomes the log of where you exist. When the canon evolves, and in the early weeks it will, the registry names the pages left behind.
Start measuring, and read the zeros
Create the tracker the week you go public: your name as favorite keyword, discovery on, and two families of prompts, your name and your category's buying questions.
"What do you know about [your brand]?"
"Which [category] would you recommend?"
"Best [category] for [the segment you serve]?"
"Alternatives to [the incumbent of your market]?"
Weekly in hd is the launch setting: the early signal is coarse, and repetition matters more than finesse. The zeros are a dated baseline: they record what the engines had before you moved, and they make every later point attributable.
Learn the market's bibliography while you build
From the very first checks, the Atlas maps the sources feeding your category's answers: that map is your target list.
Sort it by AI Authority, engine by engine: the top of each column is where a mention would count most. That is where launch outreach goes: the directory every engine already cites, the comparison your category reads, the publication that covers your niche. Discovery suggests the recurring names and domains on its own; what you accept joins the tracked landscape.
The first mention is an event: catch it, bank it
One check, one prompt, one engine: the first time your name comes back, it comes from somewhere.
Candidates surface the pages where engines showed your name in their own answers: record the real ones as corroborations, exact page and publication date. Arm monitoring on the first heavy one: a young record is thin, so each early page carries real weight in it. Date the mention in the Logbook next to what you shipped that week: the curve starts reading as cause and effect.
From launch to routine
The launch ends the day the rate stops being zero and starts being a curve. The tracker stays; your reading changes.
Keep the series: the launch tracker becomes your standing measure, versions carrying every setting change. From here the reputation playbook takes over for your name and the ranking playbook for your market, and the Logbook you kept from day one remains the launch's story: what you wrote, where you appeared, when the engines started answering.
Worked example
Six weeks from blank record to first mention
Week one: canon written, site and llms.txt aligned, eight surfaces created from their checklists. Week two: tracker on, four prompts, weekly, zeros on the record. The Atlas already names the two comparisons and the directory feeding your category's answers: three quests, one per target. Week five: a listing goes live, dated in the Logbook. Week six: a check finds the first mention, candidates surface the page, the corroboration is recorded and monitored. The rate leaves zero, and from here on it is a ranking story.
With your AI assistant
Your AI assistant runs this recipe with you
Connect Epovest to the assistant you already use, one-click connector or API key. It creates trackers, reads the results and keeps the registers with you; a payment only ever happens with your approval.
The instruction to give it
Connect to Epovest and set up my launch: create the project and its canon from [my site], the first surfaces from their checklists, then a weekly tracker mixing prompts on my name and my category's buying questions, discovery on. Read me the zeros as a baseline and flag the first mention.
$0.10
per prompt, per engine, per check
Pricing
Whatever you configure, the unit never changes. Your total shows live in the configurator before anything runs; you start whenever you want, from a $10 top-up. No subscription: only the checks that run are debited.
The tracker grows with the launch
Start with a handful of prompts and weekly checks; add keywords as competitors emerge, raise the cadence for launch week, switch discovery on when the answers begin citing sources. Every change opens a new version and the series continues.
The other use cases
Make AIs recommend you
Create a tracker in minutes: your prompts, your engines, your cadence. First checks within 24 to 48 hours.
No subscription. Credits from $10, valid 12 months. Pause anytime: the history stays yours.