Start Assessment

BOFU MCPfor B2B SaaS teams

Product Marketing Context for your entire company

Load your product from its own repo once. Every AI your team and your agents use reads the same personas, positioning and features, and it updates every time you ship.

  • Free
  • No credit card

Or grab the free playbook

Plugs into

  • Claude
  • ChatGPT
  • Cursor
  • HubSpot
  • Slack
  • Salesforce
1. Offline-First Reports: Every Site Visit Captured, Even in Dead Zones We designed Fieldkit around a simple idea: site data should survive the site. Every report that enters your workspace — from a tablet in a dead zone, a subcontractor upload, or a manual entry — gets a local-first save, a sync-state tag (SYNCED, PENDING, CONFLICT), and any photos or signatures the crew attached. Fieldkit Reports / Riverside 12 / #4128 SYNCED Report #4128 — Riverside 12 Filed by J. Mercado · Thu 7:42 AM PHOTOS OFFLINE SYNC TIME FORMS SIGNATURES CONFLICTS 38 6h 12m 45 sec 12 of 12 2 0 PHOTOS (38) +34 Take the report above — filed from a dead zone: 38 photos and 12 forms captured across 6h 12m offline, then synced in 45 sec at the first bar of signal — no re-entry, no Monday backlog. KNOWLEDGE ARTIFACT PRE-EXTRACTED VISUAL ARTIFACT EXTRACTED IMAGE CONTEXT

How it works

One context graph. Every AI in your company reads it.

Build it from the repo, set the positioning in a chat, then every draft, deck, proposal and agent reply starts from the same facts.

1 · Sync the repo

Your repo is the source of truth.

Run /bofu-sync in Claude Code. It reads your product’s own code and docs and loads every feature, capability and persona into BOFU, each cited to the file and line it came from.

2 · The context graph

Your product positioning DNA.

Every pass over the repo adds to it. Features and capabilities form the backbone, personas pair with their pains across it, and every entry cites its code. It’s what each AI reads before it writes.

3 · Set your positioning

Then tell it how you win.

Talk it through like you would with a content strategist: your hit product, who you lose to, what they can’t match. The answer bonds into the graph, so every AI writes from the same positioning.

Your team and your agents

Every answer starts from the buyer, not a blank page.

Someone asks. The AI pulls the contact from your CRM, matches their persona in BOFU, picks the framework, then writes. The same steps for a marketer in Claude as for your support and BDR agents.

You · Marketing asks: “Write a post for Dana Ruiz at Ledgerline on why AI drafts invent features.” The AI looks up Dana Ruiz, Head of Content at Ledgerline, in the CRM; pulls Imports from code, the Content lead persona’s pains and how BOFU compares with Jasper from BOFU; applies the Product-led article framework; and writes the blog post, each line traced to its source.

Always in sync

Ship a feature once. Every AI knows by the next prompt.

Ship a feature and BOFU retakes its screenshots and adds it to your product DNA. Every AI that reads BOFU over MCP says it on the next prompt, so nobody re-briefs marketing, sales, support or the agents.

Connect

Plug it into the tools you already use.

One endpoint, then a sign-in with your BOFU account. Pick your tool for the steps.

Claude Desktop

Works with Claude Desktop and claude.ai.

  1. Open Settings → Connectors.
  2. Click "Add custom connector".
  3. Paste the endpoint below.
  4. Click Connect and sign in with your BOFU account.

MCP endpoint

https://staging.api.bofu.ai/mcp

Plug it in.
Ask from anywhere.

Connect your BOFU knowledge base once — every tool your team works in gets the same grounded answers your published pages ship with.

  • Free
  • No credit card

See what it powers