MARS strategy note · 2026-07-24 · Competitive analysis

PitchBook's Daily Pitch: can we replicate it, do it better, and what do their MCPs tell us?

Elise forwarded the Daily Pitch email of Francisco Partners' $21B fundraise. Three questions came with it: can we replicate this newsletter, can we do it better, and should we look at their MCP docs. Short answer to all three: yes — and one number below tells the whole story.

Yeswith one big footnote

The Francisco story is not a PitchBook scoop. It is a repackaging of SEC Form D filings that hit EDGAR five months ago. MARS had every filing they cite in real-time on 2026-02-24, when the core Francisco Partners VIII and Agility IV vehicles filed. PitchBook broke the story on 2026-07-24. A MARS-native newsletter would have moved this five months earlier at zero marginal cost.

The one thing they can do that we cannot yet: name specific LP commitments (Boston Retirement System, CalPERS, PennSERS committed to Francisco VIII). That is the lp_data/ vertical gap. Everything else in the newsletter, we can beat.

Their MCP docs are worth studying carefully. PitchBook and Lumonic have both shipped MCP servers into the Claude and ChatGPT connector directories. The joint valuation-workbook template is the pattern our own MCP push should emulate — but MARS's substrate advantages let us build tools that PitchBook structurally cannot.

The Francisco receipt: substrate proof

Before arguing what MARS could do, look at what MARS already has on the specific story that ran today.

Francisco Form D filings in MARS today
14
Core VIII, VIII-A/B/C, Agility IV, IV-A/B/C, plus iCapital and AlphaKeys feeder vehicles
Days MARS had the story before PitchBook broke it
151
Core VIII / Agility IV filed 2026-02-24; PitchBook Daily Pitch 2026-07-24
Francisco entities in investors_v2
8
Including Francisco Partners Management, L.P. — $47B AUM, CRD 160272, SEC registered

Every SEC-derivable claim in the PitchBook article was in MARS substrate months before the newsletter went out. The "war chest doubling to $21B across VIII and Agility IV" narrative is the sum of Form D filings we ingested in Feb–June. The iCapital-Francisco Partners VIII, L.P. feeder that ADVISORS use to route retail LP commitments has been in our substrate since May.

Andrew Brown, quoted in the article as Francisco's global head of fundraising, is also already in persons_v2 (UUID 680ae52a-7130-462f-a5cb-fff25e44e433). Bio data thin — we know he's at Francisco but not that he leads fundraising. That's a gap Qwen-from-Grok-web extract could close cheaply.

The Francisco fundraise story didn't need a journalist. It needed a Form D watcher that publishes when the filing hits EDGAR. MARS has been the Form D watcher for months. We just haven't been publishing.

Q1 — Can we replicate the Daily Pitch newsletter?

Section-by-section coverage check on the actual email Elise forwarded.

Newsletter itemMARS substrate coverageVerdict
Lead: Francisco $21B 14 Form D filings; 8 Francisco entities; Andrew Brown in persons_v2; 5-month lead time Full — earlier
Named LPs (Boston Retirement / CalPERS / PennSERS) CalPERS and PennSERS in investors_v2 as text entities; no LP-to-fund commitment link; Boston Retirement absent Gap: lp_data/
PitchBook × Lumonic MCP announcement Competitor promotion — not our story to run N/A
Catch-up: Blackstone AI infra, Partners Group $5.5B secondaries Blackstone family fully mapped (10+ RIA entities, $70-270B each). PE fundraise news via GDELT + Form D signal. Full
AI tokenomics startups feature (Atlas Cloud, Ramp) Companies present, funding rounds tracked; VC quote analysis (Joanne Chen, Tomasz Tunguz) requires editorial voice Data yes, journalism no
Side letters (Meta StoryKit, data-center town negotiations, Japan rates) News-aggregation from GDELT + classifier substrate; well-suited Full

Replicable share: ~70% of the newsletter as it stands. The 30% gap is the LP-commitment field (needs lp_data/) and the editorial voice / quoted-source journalism (needs reporters).

Q2 — Can we do it better?

Where MARS uniquely wins vs where PitchBook still owns the moat.

What MARS does better

Speed

Form D + SEC ingest is hourly. PitchBook's editorial cadence is weekly. Every fundraise gets a MARS signal 5–30 days before the PitchBook narrative catches up.

Entity graph

Person mobility across GPs is a MARS specialty they don't emphasize. "Which fundraisers just left KKR for Ares," "which Francisco alums are now at rival PE shops" — natural queries against persons_v2 + person_work_history_v2.

Deal graph roll-up

Francisco has 8 registered entities plus 6+ feeder vehicles. MARS canonicalizes them into a single-firm view. PitchBook shows each as separate rows.

MCP + AI-native surface

MARS was built MCP-first. PitchBook bolted MCP onto a legacy dashboard product. Analyst asks natural-language questions and gets structured answers with integrity_tier provenance.

Cost

Qwen tier chain runs at ~$0 marginal. PitchBook's cost structure carries an editorial team + 20 years of legacy schema.

Where PitchBook still wins

LP↔commitment data

The Boston Retirement / CalPERS / PennSERS attribution is the one thing today's article does that MARS cannot. Scraped from public pension CAFRs + consultant board packets. Our lp_data/ vertical is scoped for this but not built.

Coverage volume

8.5M companies (them) vs 286K (us). 2.8M deals vs 91K canonical. 597K investors vs 100K. But volume ≠ signal density — much of theirs is shell-companies-and-inactive.

Fund performance

IRR / TVPI / DPI benchmarks. Mostly private; leaks through CAFR disclosures. Same source as LP commitments — solves together via lp_data/.

Editorial voice + distribution

A named reporter with GP relationships pulling GP-quote color. 20-year subscriber list (~100K+ analysts on Daily Pitch). Not a substrate problem; a market-position problem.

Brand-recognized product

Institutional buyers already have Preqin and PitchBook subs. Selling a substitute is hard; selling a complement is not.

The MARS-native newsletter is not a substitute for the Daily Pitch. It is a SEC-first signal service that runs 5–30 days ahead of what PitchBook editorial can publish, at a fraction of the cost, with an entity graph the incumbents don't have. Different product, adjacent market.

Q3 — What their MCP docs tell us

PitchBook and Lumonic both shipped MCP servers into the Claude and ChatGPT connector directories. Live today.

PitchBook MCP

Endpoint: https://premium.mcp.pitchbook.com/mcp

Auth: SSO + existing PitchBook seat license

Pricing: Bundled with PitchBook subscription; no separate MCP price

Access: Read-only; works in Claude Desktop / Web / Mobile / Code and via Claude API

Exposed tool categories

  • Entity Search — companies, investors, funds, people, LPs, deals by name/ticker
  • Company Profiling — business description, financing history, financials, team, investor list
  • Investor Intelligence — portfolio holdings, AUM, focus, LP commitments
  • Deal Analytics — participants, valuations, cap tables, ownership %
  • Network Mapping — co-investors, shared portfolio companies, team histories

Data granularity claimed

8.5M private companies · 2.8M deals · 597K investors · 154K funds. Deep on LPs and cap tables.

Lumonic MCP

Endpoint: https://mcp.lumonic.com/mcp

Auth: Lumonic account sign-in (OAuth-style)

Pricing: Bundled with existing Lumonic license

Access: Read-only; zero retention on MCP layer; Excel formula integration for live values

Exposed capabilities

  • Covenant status + EBITDA monitoring in natural language
  • Cash-runway + borrowing-base queries
  • Mark movements, leverage ratios, off-plan identification
  • Every value returns a traceback link to source document cell — audit-safe

Prompt library

Organized by asset class (private credit / VC / PE). Includes borrower tear sheets, covenant dashboards, quarterly portfolio review templates.

The joint template that ships in the MCP library

A valuation workbook that pulls PitchBook comps and Lumonic portfolio financials into the same Excel model. Both MCPs run in the same Claude conversation. Every number carries a traceback link to source cell.

This is the product pattern to study: two independent MCP servers, both hosting focused tool sets, discovered and combined by the model on demand. The user gets a compound workflow neither vendor could build alone.

Bad news: PitchBook shipped MCP first. Good news: they built theirs on top of legacy schema. Ours can be MCP-native from substrate up. When customers ask "why the second option," the answer is real-time SEC + entity graph + traceback provenance — MARS-only features their bolt-on cannot match.

Recommended play

MoveEffortWhat it unlocks
Ship the MARS SEC Daily Signal — an automated newsletter driven by Form D + Schedule 13D/G + Form 144 substrate ~1 week to first edition Publishing lead time on stories PitchBook is 5+ months behind on. Direct pitch to top-50 pensions + Callan-class advisors as complement to their Preqin sub.
Prioritize lp_data/ vertical — public pension CAFR ingest 4–6 weeks scaffold Closes the "Boston Retirement committed $X to Francisco VIII" gap. Unlocks the middle-tier pension market where PitchBook and Buyouts Insider still own the moat.
Publish MARS MCP tool catalog to the Claude connector directory (mars-funding.kscope.io endpoint) ~1 week (specs exist; deploy remaining) Same discovery surface PitchBook and Lumonic use. Beats their volume with our provenance model (integrity_tier + identity_decisions_v2 already delivers what their "traceback" pitches).
Investigate an MCP interop template like PitchBook × Lumonic — e.g. MARS × Lumonic joint fundraise-monitoring workbook ~2 weeks + partner conversation Copies the exact pattern that's getting PitchBook editorial attention. Different substrate → different combined product.
Draft coverage benchmark study — 20 recent PitchBook LP News stories vs MARS surfacing per story ~2 hours Concrete numbers for advisor and pension pitches. Yesterday's Elise brief flagged this; today's Francisco data point is proof of concept.

Bottom line for Elise

Yes, we could replicate the newsletter — ~70% of what's in this specific edition, and we could have run the Francisco Partners lead 151 days earlier because the SEC filings were in our substrate on Feb 24. The gap is LP commitments (which needs lp_data/) and named-source journalism (which needs a reporter).

Yes, we can do better — but not by copying their newsletter. The MARS advantage is speed (hourly SEC signal), depth (entity graph, person mobility), and MCP-native surface. Pitched as the "SEC-first signal service that runs ahead of Preqin and PitchBook," not as a Daily Pitch substitute.

Yes, look at their MCP docs — and take the template. PitchBook's premium.mcp.pitchbook.com/mcp and Lumonic's mcp.lumonic.com/mcp are the market-anchor examples. Our tool specs are already written (mars_feed/mcp_specs/). Ship them into the Claude connector directory next. First-mover matters less than first-mover-with-the-right-substrate.

Substrate figures cited: live queries against mars.form_d_filings_v2, mars.investors_v2, mars.persons_v2, mars.deal_investors_v2 as of 2026-07-24. Francisco Partners flagship RIA AUM ($47B) from ADV Part 1A; article-quoted $75B firm AUM includes fund-level commitments not directly in ADV.

Competitor figures: PitchBook's 8.5M companies / 2.8M deals / 597K investors / 154K funds from their public Claude connector documentation; MCP tool categories and endpoint from PitchBook + Lumonic connector pages and the joint-template announcement in today's Daily Pitch. Lumonic MCP details from their public marketing page at lumonic.com/mcp.

Not covered here: direct pricing comparison (PitchBook and Lumonic both bundle MCP with existing seat licenses; no separate MCP price disclosed publicly), Preqin's parallel MCP offering (they've announced but not shipped as of this note), and cross-vendor auth compatibility for a hypothetical MARS × Lumonic template.