Everything it takes to win the answer.
Your buyers ask ChatGPT, Claude and Google AI which tool to use, and right now it names someone else. Attensira reads those answers, works out why you are missing, and does the work to close the gap. You approve, comment, merge.
Attensira reads the answers ChatGPT, Claude, Perplexity, Gemini, Grok and Google AI Overviews give, and ships its changes into Next.js, Astro, Docusaurus, Mintlify and GitHub.
Optimizes for
ChatGPT
Claude
Perplexity
Gemini
Grok
Google AI Overviews
Copilot
Integrates with
GitHub
Gmail
Outlook
Notion
Search Console
Google Calendar
HubSpot
PostHog
Slack
Linear
Reddit
YouTube
- MCP server and API →
What's happening
The answer is already being given. It isn't you.
Buyers stopped opening ten tabs. They ask one question, they get one recommendation, and they act on it. Whoever the model names is the shortlist, and you never see the deal you were not on.
- 61sources decided one question
- listicles, community threads, competitor pages, review sites, transcripts
- 2of them were yours
- rewriting your own pages is necessary, and nowhere near sufficient
- 5smaller questions underneath it
- the model asks its own; you are present for two of them
You cannot fix an answer you have not read. And you cannot read them at the rate they change.
Why it gets worse
Models cite what other sources already cite. Listicles quote listicles, and a name that appears in the sources this month appears in more of them next month. Every week a competitor is the answer is a week they collect the citations that keep them the answer. The gap does not hold still while you get to it.
Built for
Technical founders and B2B SaaS teams of 5 to 200 whose site or docs live in a Git repo — Next.js, Astro, Docusaurus, Mintlify — with one or two marketers and no agency. If your content lives in a CMS instead, the drafts path is for you.
See it for B2B SaaSYour part
You're in the driver's seat. It does the heavy lifting.
Work arrives the way it would from a good colleague. A page change opens as a pull request on your repo: you read the diff, comment on it, merge it or close it. An email arrives as a draft with the person already found and the note already written, and it sits there until you send it. Nothing is done in your name.
How the inbox worksIt just gets on with it
Reversible work, done and logged. No ping, no approval, nothing to read.
- Schema and FAQ blocks
- Internal links and alt text
- Heading structure and entity density
- Stale-page refreshes
- Re-reading answers when a model changes its mind
It asks you first
Anything that speaks for you or ships in your name.
- Any sentence that makes a claim about your product
- Any sentence about a competitor's pricing or features
- A new page
- Anything sent to a person under your name
- The merge. That button is yours.
An approval you don't answer expires after 7 days and the run closes having changed nothing. Silence is never a yes.
How it works
What it takes, in four moves.
Meet the agentIt gets to know you. What you sell, who for, how you talk, and the questions you want to be the answer to. You set the destination, never the tactics.
It watches, continuously. Every tracked question to every tracked model, daily, stored verbatim with the sources it read.
It works out how to win. It reads the answers that beat you, follows the questions underneath, and names what's missing. Then it turns that into a plan.
It does the work. Pages rewritten, missing ones written, shipped to your repo as a pull request. Each result comes back for a yes or a no.
Day one
It starts by learning your business.
The first thing you do is talk to it. It asks what you sell, who buys it, how you talk, what you never claim, and which questions you want to be the answer to. Everything it writes later comes from that conversation.
How knowledge and skills workA conversation, not a form
Tell it in your own words. It asks the follow-ups, and every run it does later is a chat you can reply to in the same place.
What makes you different, written down
Positioning, proof, the competitors you actually lose to. It keeps a profile you can read and correct.
The claims you never make
Name them once. Nothing it drafts will cross that line.
How can we help?
We sell invoicing software to agencies that bill retainers
+Auto ↑
Good. Two follow-ups: which size of agency is the sweet spot, and what do you never want claimed about you?
Measurement
It measures the answers, and says when it can't.
Every tracked question, to every model, daily, stored verbatim with the sources it read. Every rate carries its sample size. A change is reported only once it clears 95% — below that, it says "no proven change", not a small number with an arrow.
How mention and citation rate are measured31% of sampled answers named you
n=214 · +4 pts vs last week · ✓ 95%
Cited 12% · n=214 · no proven change
| Model | Mentioned | n |
|---|---|---|
| ChatGPT | 38% | 70 |
| Perplexity | 29% | 63 |
| Claude | 27% | 51 |
| Gemini | unmeasured | — |
| Google AI | unmeasured | — |
Unmeasured is never zero. And no revenue attribution: there is no identity join between an answer and a signup, so we will not imply one.
On a schedule
Set it once. The work keeps arriving.
Describe the job you'd hand to someone every week. It runs on a schedule, and what comes back is finished work addressed to the right person, waiting on one click.
How automations workReach the sites AI keeps citing
Every weekIt found the editor who owns the listicle, wrote the note, and left it in your inbox as a draft. One click opens it in the chat, where you edit it in your words. You send it.
Flag questions a competitor took
Every dayA model changed its mind about who to recommend. You hear about it with the answer text and the source that moved it.
Write the page that doesn't exist
When you askThe comparison page, the integration page, the FAQ your page is missing — drafted and opened as a pull request against the repo your site builds from.
Find pages that lost citations
Every weekRefreshed, restructured, re-read. Reversible work like this runs without asking you.
The pull request
Every change arrives as a diff you can read.
Pages land in the repo your site builds from: a branch, the diff, and the reasoning in the description. You see what changed, what it was before, and which question it was for.
The GitHub integrationWritten to be read twice
Once by a person, once by a retrieval system. Structure, entities and schema are part of the draft, not a later chore.
Then measured
Each change is dated, so the next reading can say whether anything moved — and say "no proven change" when it did not.
It never merges
Three permissions, no secrets, no Actions, no admin. The merge button is yours.
content/pricing.mdx +42 −8
− Invoicing, simplified.
+ Invoicing for agencies that bill retainers.
+ $18 per seat, per month. No minimum.
components/faq-schema.tsx +31 −0
Why this waits for you
- ☐ "$18 per seat, per month" — a claim about your product
- ☐ "bill retainers" — a claim about what you support
ApproveReject
Off your site
Most of what AI cites isn't on your site.
How sources and citations are trackedAnswers get built from listicles, review sites, threads and transcripts. Your own pages are a small share of what gets read, so it works the pages you don't own: who runs them, why they'd say yes, and the note itself.
It never sends mail under your name. The brief is mechanical. The send is yours.
"We should do a podcast." Coming
- YouSay the sentence. That's the whole brief.
- ItShortlists the shows whose transcripts models already cite. Approve.
- ItWrites the pitch and the angle. Approve. You send it.
- YouShow up and do the talking. Never automated.
- ItWatches the episode like any other page.
- The Agency Ops Show · cited in 6 of 14 · transcript: public
- Freelance to Firm · cited in 4 of 14 · transcript: public
- Agency Growth Radio · cited in 1 of 14 · transcript: none · skip
Outreach to shows is coming. Today the same ladder runs for the sites AI already cites; what has shipped is in the changelog.
The kinds of source an answer gets built from
Forbes
G2
Capterra
TrustRadius
Hacker News
Spotify
Apple Podcasts
TechCrunch
Product Hunt
Stack Overflow
Substack
Medium
LinkedIn
Trustpilot
GetApp
Connections
It runs on the stack you already have.
Grant only what you want, per workspace, revocable. It reads the tools you already run so it has your context, and it writes back into the two places work actually lands: your repo, and your drafts.
All integrationsWrites into
A pull request on your repo, or a draft in your own mailbox. Never a send, never a merge.
Reads from
Context it would otherwise have to guess at, taken from where you already keep it.
Or drive it yourself
An MCP server and a REST API, so Cursor, Claude Code or an agent you wrote can ask it questions and start its runs. Bring your own MCP server and it will use that too.
The alternatives
Four ways to be the answer. Three of them stall.
Not on price. On what you actually end up holding at the end of the month.
See plans and what's includedDo it yourself
You know the pages and you know the listicles. It gets done at midnight, in bursts, and the ideas stall before the chores start.
What you end up with
The right work, at the rate one person can do it between everything else.
Hire an agency
A retainer, a monthly deck, and someone else's idea of your voice. The right call if you want a human on the phone.
What you end up with
Good work on their calendar, in their words, a round at a time.
Buy a dashboard
Tells you where you're missing and how far behind you are. Accurate, and the list is still yours to work through.
What you end up with
An accurate list of what is wrong. Every hour of the fixing is still yours.
Attensira
Reads the answers, works out the plan, writes the fix, drafts the pitch, and brings each one back for your yes or no.
What you end up with
Finished work in your repo and your drafts, waiting on one click from you.
Everything it takes to win the answer.
Tell it your business, pick the questions you want to win, connect the repo your site builds from. The work starts arriving, and nothing goes live without you.
What it does
Reads the answers, follows the sources, writes the pages, drafts the notes. Every week, without being asked.
What you do
Read a diff. Comment or merge. Send the draft in your own words if you like it.
Setup
A GitHub App scoped to the repositories you pick, three permissions, and the questions you want to win.
Your week
One inbox. Most weeks, a handful of clicks. It never merges and never sends.
Before you start
The eight a marketer asks.
Is this replacing my marketer?
No. It takes the chores: working out which questions to win, rewriting pages so machines extract them cleanly, schema, internal links, and drafting the notes to the pages that cite your competitors. Your marketer keeps the story, the relationships, the hour on the mic, and the final yes on anything that makes a claim.
Do you guarantee we'll get cited?
No. Some answers belong to the biggest brand in your category and no tool changes that. What we guarantee is the effort: nothing winnable is left undone, every result comes back for your approval, and every number is reported with its sample size.
How is this different from the other AI-visibility tools?
They report where you stand. Attensira does the work that follows: it reads the answers that beat you, writes the fix, opens a pull request in the repository the page actually lives in — a fresh branch, an attensira label, and a body stating which page, which finding, and why — and drafts the off-site pitch. It never merges. The measurement is the input; the finished work is the product.
Isn't this just optimising for one phrase?
No. When a buyer asks "best X for Y", the model asks itself several smaller questions on the way and reads sources for each. Attensira tracks the question and the ones you track around it, stores every answer verbatim with the sources it read, and works on the gaps in that whole tree — across ChatGPT, Perplexity, Google AI, Claude and Gemini, whichever your plan tracks — not on a single phrase.
Will it publish something wrong about us?
Nothing that makes a claim about your product or a competitor goes live without your approval. Reversible work — schema, links, alt text, refreshes — runs on its own. A new page or a rewritten claim waits in your inbox as a pull request, and an approval left for 7 days expires without changing anything. One caveat worth stating plainly: Attensira cannot read your branch protection settings, so if your repo auto-merges on green, turn on draft mode and every PR opens as a GitHub draft.
Does it send emails as us?
No. It finds the pages models quote instead of you, works out who runs them, and drafts the note. You send it from your own mailbox. It never touches your sending domain.
How do I know it's working if AI answers don't send clicks?
Every rate carries n, the number of successful runs behind it, so 33% at n=3 reads as one hit in three draws rather than a percentage floating free. Movement is gated by a two-proportion z-test at 95% significance; below that bar it reports no proven change instead of a number. Every answer is stored verbatim so you can read the evidence. What it will never tell you is that a mention produced a signup: there is no identity join between a model's answer and a later visitor.
What does it need access to, and how much of my time?
A first-party GitHub App you install into your own org, limited to the repositories you select, with exactly three permissions: Contents read/write, Pull requests read/write, Metadata read. No Actions permission, no Administration permission, no access to your secrets. It opens pull requests and never merges. Then: setup, and review. Everything that needs a human collects in one inbox, split into Needs you and In flight. Most weeks that is a handful of clicks.