Current read
We are not starting from zero
Known customer relationships, live usage in parts of the platform, and an existing contract path mean this launch does not need a full-market GTM stack before beta can start.
Founder overview
This reporting site is now designed as a guided founder briefing. The goal is to make the launch system legible first, then show where the work is strong, where it is incomplete, and where your calls still shape the outcome.
How the launch system is structured
Where we stand now
Current read
Known customer relationships, live usage in parts of the platform, and an existing contract path mean this launch does not need a full-market GTM stack before beta can start.
Current read
For warm-account private beta, the real gates are a credible website, minimum company and legal basics, clear beta scope, a coherent founder walkthrough, and a simple onboarding path.
Current read
A lot of what remains on the GTM board now sits in the 'helpful during beta' or 'needed for broader GA' layers. That work matters, but it should not be confused with permission to begin.
Decisions to be made
Put together a short commercial explainer that helps the founder talk through pricing without improvising.
Open on decisions pageThe launch benefits from group credibility, but the BU also needs to feel commercially distinct. The founder has to decide where the market should see inherited trust and where it should see a separate operating unit.
Open on decisions pageEnterprise SaaS is the current default stance, but the strategy work explicitly leaves room for assisted and software-under-service pilot modes. The decision is not which model looks best in theory; it is which one fits actual pilot maturity without dragging the team into bespoke services gravity.
Open on decisions page