<un>peelFounder GTM
Back to GTM checklist
BlockedFounder decisions linked

GTM pillar

Trust, Legal, and Launch Operations

Make sure the business can support broader beta selling safely: legal identity, trust posture, procurement answers, and an operating rhythm that keeps launch under control.

What this covers

  • Legal scaffold, trust pack, privacy, and procurement readiness
  • Launch governance, measurement baseline, and review cadence
  • What has to be true before selling widens beyond tightly controlled founder-led pilots

Why it matters in GTM

This is the difference between an exciting beta story and one that enterprise buyers can take seriously. Even a founder-led motion needs enough legal, trust, and operating structure to feel controlled rather than provisional.

Where we are now

The planning and reporting structure now exists, but wider beta selling is still held back by legal setup and trust basics.

Biggest gap

We still need clear company identity, basic procurement answers, and a trust pack strong enough for safer selling beyond tightly controlled founder-led pilots.

Underlying items

The strategic and tactical work inside this pillar

Open checklist slice
BlockedFounder decision

Trust, legal, and procurement

The product promise already leans heavily on trust, governance, and defensibility, but the external trust pack is still pilot-stage. This is the clearest blocker between private founder review and confident enterprise procurement conversations.

Open tactical detail
In progress

Launch governance and measurement

Launch governance is no longer a blank area: the reporting system now provides a lean launch-stage model, a single operating surface, and a reusable weekly review template. What is still missing is the populated baseline and metric definitions that turn this from a snapshot into a measurable operating system.

Open tactical detail

Founder decisions

Calls affecting this area

Open readiness checklist
Needs a call

Confirm we set up as our own separate company

Confirm the separate company. If the founder wants this kept inside Empathy instead, that needs to be said now, because the legal, brand, and certification work all branch from this one call.

Review in readiness checklist
Needs a call

Green-light the new entity and its legal document set

Green-light the entity registration and the new legal set now, since the lead time runs to months, and plan to re-contract Empathy Research, DB, Futavista, Musgrave and UKOmnibus under the new company.

Review in readiness checklist
Needs a call

Agree the certification plan and timing (ISO and security)

Commit to a scoped certification plan for the new entity and the dev team, with a realistic timeline, and treat it as a launch dependency rather than an afterthought.

Review in readiness checklist
Needs a call

Set the official public go-live date

Set a target go-live date anchored to the legal and certification lead time, and confirm it once those timelines are known. Do not announce publicly before the entity and contracts exist.

Review in readiness checklist
Needs a call

Decide how much we reference Empathy Research and <un>known

Lead as our own company, and reference Empathy Research where it adds credibility, especially as an early customer. Keep the <un>known lineage light, present where useful but never the headline.

Review in readiness checklist
Needs a call

Approve the gates for widening sales beyond founder-led beta

Keep founder-led pilots and explicitly approved referrals as the current perimeter. Widen only after the contracting identity, privacy/DPA minimum, product-maturity map, proof rules, support capacity, and approved sales promises are in place.

Review in readiness checklist