Run the audit on every client.

Take each client’s site live from Claude or your coding agent. Their requests arrive with what the buyer’s agent asked first, so they close faster, and you show them the research that didn’t convert.

Hand every client the context to close.

When a buyer’s agent uses a client’s site tools, each visit is recorded in that client’s workspace as one conversation: what it asked, exactly what the site answered, and how far it got.

  • Their team acts faster: each lead arrives with what the buyer’s agent asked first, and a link to replay the conversation
  • You win them the next one: every question agents ask the site, how often, and which ones it could not answer
  • Contact details are masked when a question is recorded, and conversations are kept a year by default
  • Recording is on from day one for a new workspace
Lead email request_estimate
What their agent asked first

  answered          Do you replace roofs after hail damage?
  answered          Do you work in 80204?
  partly answered   How soon could someone come and look at it?

Replay the conversation →

A brief you run for them from Claude.

Connect Claude to a client’s workspace and ask what buyers’ agents asked this week. The brief comes back for marketing, sales and leadership, and every number keeps its denominator.

  • The questions asked most, and the ones the site had no real answer for
  • Where conversations stopped: the agent got real answers and left, or the person did not say yes at the confirmation step
  • For each lead, the two or three questions its agent asked first
Ask Claude Inception Agents connector
What did buyers' agents ask client.example this week,
and which of their questions could the site not answer?

You take them live.

The go-live playbook runs as a conversation with Claude or your coding agent: approve the tools agents will see, choose who gets leads, install with a one-time code, and send a test lead through the real site.

  • WordPress: the plugin, installed with WP-CLI or uploaded by the site owner
  • Cloudflare: a small Worker, deployed with a narrowly scoped token
  • Each step counts as done only when a check from outside proves it
  • Someone on the client’s team confirms the TEST lead arrived; it is never billed
How the install works →
get_go_live_state 8 stages
client.example

  ✓  Your account
  ✓  Your website
  ✓  What agents will see
  ✓  Where leads go
  ✓  Install on your site
  ✓  Agents can reach it
  →  A test lead reaches you
     Live

The lead, where the client works.

Every request can also go out as a signed lead.captured event. Point it at a Zapier or Make hook and map it into GoHighLevel or HubSpot; the recipe and the field mapping are in the docs.

  • Signed with HMAC, so the receiver can check it came from us
  • The person’s own words travel with the lead, and it records how they said yes
  • Direct adapters for Clio, Jobber, Entrata and eighteen more are built, each awaiting a sandbox run
The Zapier and Make recipe →
lead.captured application/json
{
  "event": "lead.captured",
  "data": {
    "lead": {
      "ref": "IA-7KQ2ZM",
      "intent": "request_consultation",
      "verbatim_ask": "I was rear-ended two weeks ago and my neck still hurts. What are my options?",
      "qualification": { "verdict": "may_qualify" },
      "provenance": { "surface": "mcp_hosted", "approval_method": "agent_authorized" }
    },
    "contact": { "name": "Ada Lovelace", "email": "ada@example.com", "phone": "+14155550100" }
  }
}

Accounts, pricing, and what is not built yet.

Accounts

One login, every client

Each client is its own workspace, and one login switches between them in the dashboard. Leads, conversations, settings and billing stay separate per client.

Pricing

Per request, per client

A service business pays one price per request that reaches it, set for its industry, with no monthly fee. Software clients pay per demo request, plus each Revenue Moment inside their product. The prices are on the pricing page.

Not built yet

A roster, and your brand on the report

A view of every client on one screen, and an audit report under your own name. Today you switch between workspaces, and the report carries ours.

Questions agencies ask.

Who does the install?

You do, or the client’s web person. On WordPress it is the plugin, installed with WP-CLI or uploaded by the site owner, then connected with a one-time code. On Cloudflare it is a small Worker deployed with a narrowly scoped token. The go-live playbook walks through either one from Claude or a coding agent, and a test lead proves it.

Can we see what buyers’ agents asked a client’s site?

Yes, in the client’s workspace: each conversation, what the agent asked, exactly what the site answered, and how far it got. Contact details are masked when a question is recorded, and conversations are kept a year by default.

Which clients is it built for?

Legal, home improvement, elective health, senior living and multifamily businesses, and software companies. Each vertical has its own pack: the tools an agent can call, the questions the intake asks, and the compliance rules.

What about regulated clients?

The rules are in the code. A health tool cannot ask a clinical question and a housing tool cannot ask about a protected class; either one fails the build. Talk to us before you take a health client live.

Can we run the audit on prospects?

Yes. The audit is free and runs on any public site, so it works as well on a prospect as on a client.

How does an agency get paid?

Terms are set per agency, whether you refer clients, resell, or build with us. Tell us about your clients below and we will walk through them on a call.

Does it replace our SEO or paid media work?

No. It answers the agents researching your clients and takes their requests. The SEO, content and paid media that bring people and agents to the site stay with you.

Tell us about your clients. We'll be in touch within two business days.

Which clients do you serve? — pick all that apply
We read every inquiry. No mailing list, no drip. A human will reply.

Inception Agents