Workstream
The category story is materially ahead of most other GTM assets: the repo already supports a differentiated confidence-across-the-workflow narrative, and the competitive work shows why that matters. The remaining job is to lock the shortest market-facing label and keep the moat story visibly tied to it across founder, website, and sales conversations.
Why this matters
If buyers only understand the company after a five-minute explanation, the founder ends up doing all the work in every conversation. A clean category frame reduces that drag immediately.
The category choice also determines whether the platform sounds like serious research infrastructure or generic AI research automation.
Current state
The strategy docs, external positioning copy, and website all align on the same core promise: help insight teams produce research that is defensible before launch, during fieldwork, and after reporting, while making answers stronger through connected evidence instead of letting knowledge disappear after the study.
The main beta one-line and supporting line are now chosen. What remains open is how far confidence, defensibility, and related language should still be translated for different buyer and procurement contexts.
The competitive material now gives this story sharper contrast than the workstream previously made visible. The deeper Research Guard benchmark shows the strongest wedge is governed pre-launch redesign: screening alignment, ordered issue handling, structured follow-up, change packaging, revision, final QA, and methodological provenance. It also makes the current maturity limits explicit: incumbents still lead on builder integration, post-field response-quality coverage, and enterprise security proof.
The external-signals strategy also strengthens the positioning case. Vista's data-sovereignty thesis supports making the connected evidence layer explicit as moat, while Thoma Bravo's mission-critical framing validates the long-term destination of becoming a system of record rather than a disposable point tool.
Checklist
Foundation
The minimum decisions and assets needed so the launch story is coherent rather than aspirational.
The working beta message stack is now set: a short website headline, plus the fuller positioning line and supporting line for founder-led and sales material.
Private preview
The hardening work required for founder sharing, pilot conversations, and limited buyer-facing use.
The decision register already gives a defensible rule: do not lead with the full suite vision before product truth can support it.
A first proof-claims draft now exists, but it still needs founder validation before it is used in the deck, one-pager, or demo.
What exists
The repo already articulates a coherent thesis around defensibility, audit trail, reduced uncertainty, and trust across the research lifecycle.
The current site copy, message architecture, and decision log already translate the strategy into headline, proof, and capability language that is coherent enough for beta use.
The competitive reviews now explain the white space more precisely: most incumbents cover slices of design, quality, analysis, or repository value, while the wedge here is connecting all three confidence phases with governed redesign and connected evidence without pretending current parity on every enterprise surface.
The external-signals strategy sharpens the top-line narrative by validating the connected evidence layer as a data-sovereignty moat and the longer-term ambition to become research infrastructure rather than a replaceable AI helper.
What is missing
Open strategic questions
Decisions to be made
Appendix briefs
Source evidence