<un>peelFounder GTM briefing
Back to Proof, Pilots, and Onboarding
In progressOwner: Desmond + GaryFounder decision required

Workstream

Onboarding and pilot operations

The operating model is already visible in the repo: high-touch pilot, bi-weekly feedback, direct support, and annual-conversion intent. What is missing is the reusable package that explains exactly what happens after a buyer says yes and how success is measured.

Why this matters

This is where GTM claims meet product reality. If the team cannot show how a new buyer gets to value safely and quickly, even a strong narrative loses force.

In an assisted beta, onboarding is not a later customer-success layer. It is part of the product and part of the GTM itself.

Current state

The strategy docs already define a likely pilot structure: a small number of customers, around three months free with a break clause, bi-weekly conversations, high-touch onboarding, direct support, and annual-conversion ambition.

The missing layer is operational packaging: onboarding agenda, first-project template, time-to-value definition, demo-environment and sample-data assumptions, and a founder-ready explanation of what a successful pilot looks like.

Checklist

What still has to happen

Foundation

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

In progressLaunch critical

Define the onboarding and pilot flow

The delivery mode is conceptually clear, but the step-by-step beta flow is not yet documented as a reusable operating path.

Private preview

The hardening work required for founder sharing, pilot conversations, and limited buyer-facing use.

In progressLaunch critical

Package time-to-value and pilot success criteria

The strategy doc already names directional success signals, but there is no packaged pilot scorecard or time-to-value definition yet.

In progress

Stand up demo-environment and training expectations

Customer walkthroughs and training feedback show that the operating motion can be made concrete quickly once the team defines the default environment and enablement rhythm.

What exists

Defined pilot stance

The strategy decisions doc already states a plausible pilot structure, including close support, product feedback loops, and conversion intent.

Live enablement signal

Musgrave follow-ups and workflow walkthroughs show the kinds of training, product guidance, and operational support the team is already providing in practice.

What is missing

  • No formal onboarding agenda, first-project template, or pilot success framework exists yet.
  • No packaged demo environment and sample-data story exists in the repo yet.

Open strategic questions

  • Confirm the default beta delivery mode: assisted high-touch pilot first, not self-serve onboarding.
  • Confirm the minimum pilot success bar that should trigger annual conversion, extension, or exit.