Connectors
One for each system, with its own permission to read and, only where needed, to write.
Harnesses: the agents, connected to your own systems.
Your customer list, your analytics, your search data, your pages and your partners sit in different tools. A harness lets an agent work across them for one job, inside rules you set, and leaves a record. Each of the twelve letters has its own plan.
Not built yetA design, with two building blocks started. No live connector, MCP client, sign-in flow or approval queue is built, and no vendor named has approved, certified or partnered with us. The CRM read rules and pipeline story, and the Google Analytics and Search Console read rules and analytics story, run on example data only.
Where a vendor publishes an official MCP server, the plan is to use it. MCP is an open standard for connecting AI applications to outside systems. Where there is none, the plan is the vendor’s public API, and where there is no API, a person does that step.
FIRST BUILDING BLOCK
CRM read: the pipeline story
The first harness being built reads Salesforce or HubSpot, read only, and works out where open pipeline and won business came from, by letter of FOUND and DRONICS. Deals with no source are shown as unattributed, not guessed.
DemonstrationThe read-only rules, the audit log, the Salesforce and HubSpot mappers and the pipeline story calculator are written and tested in this repository. They run here only on example data for a company that does not exist. Not connected to any CRM.
SECOND BUILDING BLOCK
Analytics read: how buyers found you
The second harness reads Google Analytics 4 and Search Console, read only. It works out which letter of FOUND and DRONICS brought visits and key events, keeps searches for your own name apart from the rest, and lists the searches where you sit below the top three. Visits with no clear letter are shown as they are.
DemonstrationThe read-only rules, the audit log, the Google Analytics 4 and Search Console request builders and mappers, the channel-to-letter rules and the analytics story calculator are written and tested in this repository. They run here only on example data for a company that does not exist. Not connected to Google.
What a harness has
Shared memory
One place for your approved claims, partners and past results, so each letter starts from what the last one found.
Rules and approvals
Checks that stop an action, and a gate where a named person says yes or no.
A record
A log of what was read, drafted, approved and sent, in order.
BE THE ANSWER WHEN THEY LOOK
FOUND
Owner: your CMO.
F: Findable
Asks buyer questions of answer engines through their official APIs, reads the company’s own search and analytics data, and drafts answer-first fixes for the CMS. A person publishes.
6 systems named; 3 with an official MCP server that we checked.
O: Opinions
Reads what reviewers and communities say, how recent it is and whether it is true, and drafts replies and customer asks. Reviews are never written, bought or edited. A person replies.
6 systems named; 2 with an official MCP server that we checked.
U: Underdog Moves
Finds topics where nobody has published a useful answer, helps build the study, benchmark or free tool from data the client may share, and checks every number against its source.
6 systems named; 6 with an official MCP server that we checked.
N: Nods
Maps which analysts, marketplaces and press buyers and AI rely on, checks how each describes the company, and drafts briefing notes and correction requests. Nothing is bought or manufactured.
7 systems named; 0 with an official MCP server that we checked.
D: Distinctions
Lists every claim of difference, finds the evidence behind it, marks it verified or not yet, and drafts proof pages with the source beside the claim.
5 systems named; 2 with an official MCP server that we checked.
MAKE THE MARKET AND YOUR PARTNERS SELL YOU
DRONICS
Owner: your CMO and channel head.
D: Digital demand
Reads search, ad and email results each week, drafts plain landing copy and email variants, and proposes which small test to stop or continue. A person sets and changes spend.
7 systems named; 4 with an official MCP server that we checked.
R: Referrals and resellers
Maps resellers, distributors and referrers by fit, drafts a pitch each can repeat, and records which partner activity led to a conversation or a deal. A person talks to partners.
6 systems named; 5 with an official MCP server that we checked.
O: Owned content
Turns the story spine into briefs and drafts, checks each claim against the register, and plans where each piece goes. A person approves and publishes.
8 systems named; 7 with an official MCP server that we checked.
N: Networks and alliances
Maps the marketplaces and ecosystems where buyers already look, checks that each listing is current and accurate, and drafts listings, joint statements and co-sell briefs. A person negotiates and submits.
7 systems named; 3 with an official MCP server that we checked.
I: Influence
Maps the analysts, creators and advisors a buyer’s audience follows, drafts a separate note for each, and records what they publish. A person approaches every one.
6 systems named; 1 with an official MCP server that we checked.
C: Community
Drafts meetup agendas, member notes and academy updates, and records who returned and what members asked for. People host and own the community.
5 systems named; 4 with an official MCP server that we checked.
S: Sales enablement
Drafts battlecards, one-pagers and talk tracks from the claim register and proof, flags any claim without a source, and keeps versions in step. A person decides what sellers may say.
7 systems named; 7 with an official MCP server that we checked.
No harness is connected to a real system. The CRM and analytics read rules run on example data only. We have no integration, partnership or approval with any vendor named, and named vendors are examples of the systems a marketer is likely to use.
Harnesses are planned, and the score is live today.
Start with the free FOUND Score. Talk to us when you want to plan a harness around your own systems.