Families ask AI under stress and act on the first clear answer: how to start, home health or hospice, who pays, grief support. Eidomai shows you which of those questions name your organization, and which send the family somewhere else.
Questions families really ask. Illustrative example, not a real business.
Google Analytics cannot show you a question that never reached your website. Eidomai asks the engines those questions and shows you who they name.
| A family asks | Who AI recommends |
|---|---|
| “Hospice care options in the county for a parent, how do I start” | A national eldercare site |
| “Home health versus hospice, what is the difference and who pays” | You |
| “Grief support groups near me for adults” | A community calendar |
| “Hospice that comes to a memory care facility” | A competitor |
| “Pediatric hospice in the county” | You |
Illustrative example: a sample hospice business, not a real one. Your own map covers the questions families in your market ask, across the eight major AI engines, every month.
These are the shape of the questions on a hospice set: the problem, not your name. Whoever published the best answer to each one holds the family. Yours are drafted from your market and your competitors, then shown to you before anything runs. In this vertical a wrong contact detail is not a marketing problem. It is a family that could not reach you on the day they needed to.
Eidomai shows you which page is winning, why the engines trust it, and what you need to publish to compete for that answer. A person checks every fact before it ships. Then the same question is asked again.
Each question a family asks becomes one job: a page that answers it, checked by a person against facts you confirmed. The brief is built from your verified facts and your voice and what the winning page said, and the page is written to earn the Google rank and the AI citation together. Watch three hospice questions go through.
Twelve to twenty buyer questions, drafted from your market, confirmed by you, run across eight engines every month. The map says which ones you are losing, and to whom.
An engine has no memory of your business. It starts from zero every time. So the brief carries everything: your facts, your voice, what the winning page said, the shape engines lift from. The words come out right because what went in was.
Written from the brief by you or by us, checked against the facts before it ships, published on your site. One page built to earn the Google rank and the AI citation together, because the engines cite what already ranks.
Same question, same eight engines, next month. One page can move several of them, because every engine reads the same map. The ledger records what changed after the page went up, with the query named. Then the next question.
Illustrative rows for a hospice set. Holders, pages and facts are placeholders for what the diagnosis finds in your market; nothing here describes a real business.
Single-month moves are noise. Flips take 60 to 90 days after indexing, and a win only counts once it holds across the deeper sample. Trend, never truth.
It is a hospice.
Eidomai catches wrong phone numbers, wrong websites, wrong service areas and the wrong company under your name before a family acts on them, and sends the correction to the source.
More real answers from the libraryEvery claim an engine makes about you is pulled from the saved answers, judged against the fact sheet you confirmed, and traced to the page that taught it when one can be identified. A wrong claim gets a fix plan: the source page, the correction, and the date it was sent. The next run checks whether the engine still says it.
Every wrong claim in the public library is one of these, names removed. Quotes are verbatim.
Which family questions name you, and which name a competitor.
Asks the eight AI engines the questions your families ask, every month, and saves every answer word for word.
On The map, you read the diagnosis and pick the question worth competing for first. On Done for you, a person at Eidomai reads it and proposes; you approve.
A page on your site that answers the question you are losing.
Builds the brief from facts you confirmed, in your voice, shaped the way the engines lift from, and checks the draft against those facts before it ships.
On The map, you or your writer write from the brief and publish. Add a person to read the draft with The map with review. On Done for you, Eidomai writes, checks, publishes and places it; you approve every word.
The same questions, asked again, and what changed.
Asks the same questions next month, every engine, and lines the answers up against last month.
On The map, you read what moved and pick the next question. On Done for you, a person at Eidomai reads it, tells you plainly, and picks the next one with you. Then around again.
Nobody controls what the engines say. What you control is what they find when they look: a page that answers the question, built from checked facts. That is what moves the answer, and the proof is the same question asked again. A change after the work is evidence to read, not proof that one page caused it.
Both plans see, answer and prove. What changes is who does the work.
Every month the system asks the engines the questions your customers ask and shows you every answer: who wins each question, and what the engines get wrong about you. For each lost question, what to write. You write the page. The system asks again next month and shows you what moved.
A person at Eidomai on your account every month: reads your answers, writes and checks the pages, publishes them, and shows you what moved. You approve every word. Not software you log into. A partner who does the work.
Month to month. No contract. Have a writer? The map with review. For teams with a writer: you copy the prompt, your writer writes, we check the draft against the facts before it ships. Let's talk. Full pricing.
Done for you is a growth partner, not a subscription: a person at Eidomai looks at everything and helps you execute. The map is the software on its own, and it is where most people start. The cookbook was never the hard part. The cook always was: The Cookbook Problem, on the Nimbletoad Insights.
Free check on ChatGPT and Claude. Confirm your email, get a link to your results; no call required. Want the full eight-engine walkthrough? Book a demo and it is ready before the call.
It starts with an eye. It ends with AI. Eidomai, by Nimbletoad.