PMFKit v1.8: CMO-First Report and Role-Specific Views
February 2026 · 6 min read
We're shipping v1.8 with two things that change how PMFKit is used and how reliably it runs: a dedicated CMO-first report and intern behavior that works for real product sites (including SPAs).
What We're Building in v1.8
- CMO-first report: exec summary, score, priorities, quick wins, 90-day roadmap, asks
- Role-specific views: CMO, COO, BD — same evidence, right lens
- Intern reliability: SPA-friendly (domcontentloaded fallback, higher timeouts)
- Routing and UI fixes for result and dashboard flows
What Didn't Change
Core flow (paste URL → PMF report), free tier, "see value before we ask for anything," and the same pipeline and evidence. We're only changing how we document and present it for the CMO and other roles.
The CMO-First Report
Until v1.8, the main output was one report for everyone. Powerful, but not framed for the person in the room who owns GTM.
The CMO-first report is a single document a CMO can open, skim, and use to align with product and growth. It includes: executive summary (stage, composite score, recommendation), main constraint and primary opportunity, score breakdown, current state narrative, priorities, quick wins, 90-day roadmap, asks (resource/decision/access), and success metrics. All derived from the same crawl and enrichment pipeline. Export to PDF or JSON.
Role-Specific Views
The same analysis can serve different roles. In v1.8 we're formalizing that with role-specific views: CMO (positioning, distribution, conversion), COO (operations), BD (business development). Same evidence, same crawl; different lens and narrative. Each role gets a dedicated UI and export path so they can document and present what they're building.
Intern Reliability
Many product sites are single-page applications. Our intern previously waited for networkidle before extracting content; SPAs often never reach it, so we'd hit timeouts and return partial pages. In v1.8 we fall back to domcontentloaded when networkidle times out and we've increased navigation and wait timeouts. Result: fewer incomplete runs and a CMO report based on a more complete picture of the product surface.
Routing and UI Fixes
We fixed a routing issue that could affect the result page and dashboard flows. Minor UI/UX and sizing fixes so the CMO report and role views read clearly on different screen sizes and in different themes.
Why This Matters (CMO Lens)
We're building PMFKit so that marketing leaders can get a first read on PMF without running a full internal audit. v1.8 is the version where that "first read" is explicitly a CMO document: one report that a CMO can open, skim, and use to align with product and growth. The intern updates mean that report is based on a more complete picture; the role views mean the same investment in analysis can be reused by COO and BD. We're not changing the product's soul—we're changing how we document and present it.
Try It Now
Run an analysis on any product URL. When the run completes, open the CMO view to see the first report. Use "Export" for PDF or JSON. Sign in to run your first analysis. Free tier: 5 analyses/month, unlimited projects, full access to CMO (and other role) views.
Try PMFKit v1.8
CMO-first report. Role views. SPA-friendly crawl. Same evidence, better document.
Status: Production (v1.8.x)
Date: February 2026