Back to Brand, Positioning, and Website
In progressOwner: Founder + DesmondFounder decision required

Workstream

Category and positioning

The current category story is clear: help insight teams answer faster, stay in control, and make research travel further by running the lifecycle rather than only storing finished outputs. The remaining job is founder sign-off and consistent use across the website, deck, demo, and proof materials.

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 official pitch and current website now lead with speed, human control, and making insight travel, supported by the whole-lifecycle distinction.

Confidence, defensibility, and audit trail remain useful supporting language for quality, evidence, and procurement questions, but they are no longer the category lead.

The refreshed proof sheet separates live product proof from controlled beta, in-build, and directional capability so the sales story no longer relies on Research Guard or Research Architect being generally available.

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

What still has to happen

Foundation

The minimum decisions and assets needed so the launch story is coherent rather than aspirational.

Ready for betaImportant before first customers

Lock the one-line external description

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.

Ready for betaImportant before first customers

Keep the public story today-biased while preserving platform ambition

The decision register already gives a defensible rule: do not lead with the full suite vision before product truth can support it.

In progress

Translate the positioning into sales-ready proof statements

The proof-claims draft now reflects the current narrative and product maturity, but it still needs founder validation before it is used externally.

What exists

Differentiated strategic narrative

The current pitch and positioning evidence support speed, human control, insight travel, and whole-lifecycle ownership; earlier confidence work remains supporting material.

Website-ready message system

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.

Competitive white-space evidence

The competitive reviews show that incumbents cover important slices of the workflow. Our broader distinction is connecting research execution, live quality review, and evidence reuse without pretending current parity on every enterprise surface.

Investor-grade moat validation

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

  • The current proof-claims draft needs founder validation and integration into the deck, one-pager, and demo.
  • The founder-facing narrative still needs to keep the wedge crisp without overstating current parity on builder integration, post-field response quality, or enterprise proof.

Open strategic questions

  • Approve the speed / control / travel narrative and the whole-lifecycle distinction as the launch default across all customer-facing material.
  • Confirm where confidence, defensibility, safeguards, or audit-trail language should appear as supporting proof rather than headline positioning.
  • Decide how overtly to use competitive contrast in founder and sales storytelling: against point-feature incumbents, against generic AI automation, or both.

Source evidence

Underlying materials