GTM readiness

Detailed GTM readiness.

The supporting workstream tracker behind the revised public self-service launch. It includes launch work and later-phase improvements, so its item counts are not a measure of how much platform build remains.

Required now: 13 open / 8 doneHelpful in beta: 11 open / 3 doneFor broader GA: 4 open / 0 done

Current GTM thesis

The simple operating stance

Launch route: A public Research Workspace route lets individual researchers and small teams understand the offer and request access without founder-led selling; card-backed purchase follows the commercial-control release work.
Initial boundary: Launch one clear Research Workspace offer for one to five active builders, with a EUR 30 dormant workspace state. Cap the first wave at ten customer organisations and move additional demand to a waitlist while the operating model is proven.
Sales engine: The public website, self-serve demo, workspace request route, card-backed checkout, automated instance deployment, and lightweight onboarding form the intended sales path.
Demand test: A small capped advertising campaign supplies controlled traffic. Signup, payment, activation, repeated use, retention, and support load show whether demand is repeatable.
Operating model: The platform team owns launch and early operations. No leads, selling, marketing labour, implementation, delivery, or support are assumed from the other group companies.

Launch view: the core product build is complete. This page tracks checklist items of different sizes and time horizons; its percentages should not be read as percentage of total platform work remaining.

Return to the launch overview

GTM checklist

Expand a launch area to see the full checklist

Ready for beta67% checklist complete

Market and ICP

We know who private beta is for first: in-house research teams at larger companies. Agencies are still relevant, but they are not the main focus right now.

Still needs: We still need clearer outreach language, proof examples, and demo stories that speak directly to that first buyer.

Required now: 0 open / 1 doneHelpful in beta: 1 open / 1 doneFor broader GA: 0 open / 0 done

Market and ICP checklist
Done	Item	Status	Phase
Required for warm-account private betaThe true minimum needed to share the website, sell into known customer relationships, and run a controlled beta safely.
Done	Enterprise insight teams confirmed as the first buyer The first beta audience is already set: enterprise client-side research teams. Read detail for Enterprise insight teams confirmed as the first buyer This decision is already made and should not be reopened for private beta. It gives the website, proof, and demo one clear audience to serve.	Ready for beta	Foundation
Helpful during betaUseful hardening work that makes the motion cleaner and more repeatable while beta is underway, but does not need to block the first warm-account launch.
Still to do	Tailor outreach, proof, and examples to the first buyer Make sure the sales message, proof points, and examples clearly speak to enterprise client-side insight teams. Read detail for Tailor outreach, proof, and examples to the first buyer This item is about buyer fit, not demo structure. The job here is to make sure outreach, proof, examples, and follow-up material feel like they were made for enterprise client-side insight teams. The separate 'Write the demo path' item is about the order and structure of the walkthrough itself. What's still missing Rewrite the outreach opener so it speaks directly to enterprise client-side pressure, not a generic research-tech audience. Choose two or three proof points that feel specific to enterprise insight teams. Make sure the one-pager and deck describe the buyer clearly instead of sounding broad or abstract. Feed those buyer-specific choices into the final demo script once the demo path is locked.	In progress	Early selling beta
Done	Write down that agencies are secondary The secondary-audience rule is now written down so agencies stay visible without diluting the main beta story. Read detail for Write down that agencies are secondary This rule is now captured in a short reference note so messaging, outreach, and sales material can all treat agencies as secondary rather than co-primary.	Ready for beta	Private preview

Read full pillar detail

In progress30% checklist complete

Brand, Positioning, and Website

The website story is strong, but the company identity behind it is not fully settled yet.

Still needs: We still need clear founder decisions on the name, the parent-brand line, and the company wording people will see.

Required now: 4 open / 3 doneHelpful in beta: 2 open / 0 doneFor broader GA: 1 open / 0 done

Brand, Positioning, and Website checklist
Done	Item	Status	Phase	Workstream
Required for warm-account private betaThe true minimum needed to share the website, sell into known customer relationships, and run a controlled beta safely.
Still to do	Put together the basic company info customers need Prepare the minimum legal and company details a customer expects before taking the offer seriously. Read detail for Put together the basic company info customers need In practice this means clear company wording, contracting identity, a short company description, and footer copy that does not feel provisional or unfinished. What's still missing Confirm the legal and company wording customers should see. Write the short company description for website and sales material. Add the right company and footer wording to public-facing pages and documents. Make sure procurement-facing copy matches the real contracting setup.	Blocked	Private preview	Brand and company setup
Still to do	Get approval for Musgrave brand references The current website names Musgrave Group, SuperValu, Centra, and La Rousse Foods; those references need explicit approval before broader sharing. Read detail for Get approval for Musgrave brand references This is a permission item, not a copywriting item. Founder support may be needed to route approval through the correct Musgrave relationship owner so the site is not relying on unapproved customer or brand references. What's still missing Confirm exactly which Musgrave-related names appear on the public site and any sales material. Route approval through the right Musgrave relationship owner. Decide whether each reference can stay named, needs anonymising, or should be removed until permission exists. Record the approval status so the website and GTM material stay aligned.	Blocked	Private preview	Website and public presence
Still to do	Decide how the parent brand shows up Choose the exact way <un>known or Empathy Research is referenced in early customer-facing material. Read detail for Decide how the parent brand shows up This is the short brand line customers will see on the website, deck, and outreach. Once it is chosen, it should be used consistently everywhere instead of changing from page to page. What's still missing Choose the exact endorsed-brand line to use in beta. Apply that same line to the website, deck, one-pager, and outreach copy. Remove any older brand wording that conflicts with the chosen line.	In progress	Foundation	Brand and company setup
Still to do	Finish the website cleanup items Resolve the remaining proof, screenshot, navigation, and polish issues before sharing the site more widely. Read detail for Finish the website cleanup items This is the last-mile cleanup that makes the site feel intentional rather than obviously still under construction. What's still missing Replace any weak or placeholder screenshots and visuals. Tighten proof, trust, and CTA sections where the story still feels thin. Check navigation, page flow, and mobile polish before wider sharing. Remove any unfinished wording that still reads like internal draft copy.	In progress	Private preview	Website and public presence
Done	Keep the current site story as the beta baseline Use the current website narrative as the main public story unless there is a strong reason to reopen it. Read detail for Keep the current site story as the beta baseline This means treating the current website story as the source of truth for private beta. Changes should now be tightening, proof, and polish changes, not another wholesale rewrite.	Ready for beta	Foundation	Website and public presence
Done	Agree the one-line description The working beta hero stack is now set: a short website headline plus the fuller positioning line and supporting line. Read detail for Agree the one-line description The website now uses a shorter, faster headline while keeping the fuller positioning line and supporting line available underneath and in founder-led material. The alternative headline and main-line options are still kept in the artifact for founder review. Answer faster. Stay in control. Make it travel. (Current website preference) <un>peel is a research platform that helps insight teams turn isolated studies into a trusted body of evidence the business keeps learning from. (Working fuller line) Supporting line: Because we own the whole research lifecycle rather than just storing what others produce, quality and trust are built into every stage. (Working support line) Historical alternatives are retained in the artifact, but they are not active launch copy.	Ready for beta	Foundation	Category and positioning
Done	Lead with today’s reality, not the full future vision Keep the public story grounded in what is real now while still hinting at the larger platform direction. Read detail for Lead with today’s reality, not the full future vision Buyers should come away understanding what the product already does, not just what it may become later. This keeps the beta story credible.	Ready for beta	Private preview	Category and positioning
Helpful during betaUseful hardening work that makes the motion cleaner and more repeatable while beta is underway, but does not need to block the first warm-account launch.
Still to do	Freeze the beta name Decide whether <un>peel is the name we will keep through private beta and apply the same naming rules everywhere. Read detail for Freeze the beta name Customers should not see one name on the site, another in proposals, and a third in contracts. This item is about stopping that drift before it becomes confusing. What's still missing Confirm whether <un>peel is the beta name we are keeping. Apply the same naming rule across the website, artifacts, proposals, and contracts. Remove any wording that still makes the name look undecided or temporary.	Blocked	Early selling beta	Brand and company setup
Still to do	Turn the positioning into sales-ready proof claims Approve a short set of maturity-aware claims built around answering faster, staying in control, and making insight travel. Read detail for Turn the positioning into sales-ready proof claims The refreshed proof sheet no longer treats confidence as the headline differentiator or future products as current proof. The next step is founder approval before these claims are used externally. Answer faster without taking the researcher out of the loop. Run the research lifecycle rather than only storing finished outputs. Keep live quality visible and human-reviewable. Make insight travel by keeping research connected to its evidence. Label every proof hook as live, beta, selected preview, or directional. What's still missing Review the draft claims with the founder and remove any lines that feel too strong. Choose the final short set of proof claims for sales use. Thread the approved claims into the deck, one-pager, and demo.	In progress	Private preview	Category and positioning
Needed for broader GAWork that matters once the goal shifts from controlled relationship-led beta to broader public availability and repeatable market motion.
Still to do	Add the extra company and legal polish before wider launch Before the site reaches beyond a warm beta audience, add the missing company and legal confidence signals. Read detail for Add the extra company and legal polish before wider launch This is the step that moves the website from credible private-beta presence to something safer for broader public visibility. What's still missing Add the fuller company and legal confidence signals needed beyond warm beta traffic. Make sure privacy, terms, and company details feel production-grade. Check that broader public visitors can quickly understand who is behind the product and how to engage safely.	Blocked	Early selling beta	Website and public presence

Read full pillar detail

In progress33% checklist complete

Offer, Product, and Pricing

The beta offer is clearer now and the first pricing material exists, but pricing rules and entitlement logic still need tightening.

Still needs: We still need final EUR pricing sign-off, cleaner entitlement rules, and an approved product-maturity map for assisted beta selling.

Required now: 2 open / 2 doneHelpful in beta: 2 open / 0 doneFor broader GA: 0 open / 0 done

Offer, Product, and Pricing checklist
Done	Item	Status	Phase	Workstream
Required for warm-account private betaThe true minimum needed to share the website, sell into known customer relationships, and run a controlled beta safely.
Still to do	Approve the Research Workspace and Enterprise package rules Approve the active and dormant Research Workspace offer, Enterprise boundary, and the commercial rules required for launch. Read detail for Approve the Research Workspace and Enterprise package rules The selected direction is Research Workspace at EUR 260 per active builder per month, EUR 30 per dormant workspace per month, and Enterprise as a separate contract. Launch and legal approval still apply, and self-serve charging must wait for the commercial controls. What's still missing Approve EUR 260 per active builder per month and EUR 30 per dormant workspace per month. Confirm the Research Workspace inclusions, exclusions, usage boundaries, and separate respondent or sample-cost treatment. Approve the Enterprise boundary and the Founder Research Cohort eligibility, feedback expectations, and manual conversion offer. Set the remaining dormant policy choices and make self-serve purchase conditional on delivered entitlement, metering, and billing controls.	Blocked	Foundation	Pricing and commercial model
Still to do	Show what customers can actually buy in beta Approve an explicit product-maturity map rather than offering every planned product as one undifferentiated beta set. Read detail for Show what customers can actually buy in beta The refreshed map separates the live core from products in test, controlled beta, in build, and directional preview. Access must be agreed account by account and matched to what can actually be delivered. Live core: Quantitative Surveys, Discussion Groups, Guided Interviews, and Trust Centre. In test: Discussion Groups V2 improvements. Controlled beta: Insight Navigator. In build: Segment Lens beta underway, with full release targeted for October. Selected preview / directional: Research Guard beta targeted for September; Research Architect remains a later release.	In progress	Foundation	Platform and SKU architecture
Done	Create simple pricing material for conversations Review the current EUR pricing explainer so the founder can handle beta commercial conversations consistently. Read detail for Create simple pricing material for conversations The pricing sheet now reflects the current public figures, assisted-beta boundaries, and open package decisions. Once approved, it becomes the source for the website, deck, proposals, and FAQ.	Ready for beta	Private preview	Pricing and commercial model
Done	Platform story scoped to current maturity The platform story already stays ambitious without implying every tool is equally mature today. Read detail for Platform story scoped to current maturity This is effectively in place already. The main job now is to keep future website, pitch, and proposal material aligned with that same honest scope.	Ready for beta	Early selling beta	Platform and SKU architecture
Helpful during betaUseful hardening work that makes the motion cleaner and more repeatable while beta is underway, but does not need to block the first warm-account launch.
Still to do	Match product scope to plans and access rules Tie the product map to real plans, access levels, and usage rules. Read detail for Match product scope to plans and access rules In simple terms, if we say there are tiers or bundles, the product and commercial setup need to behave that way too. What's still missing Decide what the real beta plans or bundles are. Define what access each plan actually unlocks. Set the usage rules or guardrails that stop the packaging from being hand-wavy. Make sure product entitlements and commercial wording match.	In progress	Private preview	Platform and SKU architecture
Still to do	Connect pricing to real commercial rules Make sure plans, limits, and contracts line up with how we say pricing works. Read detail for Connect pricing to real commercial rules Customers should not hear one pricing story and then discover the product or contract cannot actually support it. What's still missing Check that pricing tiers match the real plan structure. Check that any limits, seats, or usage assumptions can actually be supported. Make sure contracts and commercial language do not contradict the pricing sheet.	In progress	Private preview	Pricing and commercial model

Read full pillar detail

In progress14% checklist complete

Proof, Pilots, and Onboarding

We have real product proof and real pilot activity, but not yet a simple repeatable way to show that proof and onboard customers.

Still needs: We still need reusable proof, a cleaner onboarding plan, and a simple scorecard for what a successful pilot looks like.

Required now: 3 open / 1 doneHelpful in beta: 2 open / 0 doneFor broader GA: 1 open / 0 done

Proof, Pilots, and Onboarding checklist
Done	Item	Status	Phase	Workstream
Required for warm-account private betaThe true minimum needed to share the website, sell into known customer relationships, and run a controlled beta safely.
Still to do	Define the first-customer journey Write down the default steps from “yes” to first value in the beta. Read detail for Define the first-customer journey This should show what happens after a customer agrees to try the product, including setup, onboarding, support, and early milestones. What's still missing Write the step-by-step path from signed-up beta customer to first value. Define who does what during setup, onboarding, and support. Make the early milestones visible so each pilot starts the same way.	In progress	Foundation	Onboarding and pilot operations
Still to do	Choose the proof format by product Decide which products need full case studies, which need customer reviews, and which can rely on internal dogfood evidence for now. Read detail for Choose the proof format by product Some products need a proper before-and-after story because the claim is about changing a workflow or business outcome. Others only need a short quote or usability proof because the claim is about a specific delighter. This item turns that into a simple proof plan. What's still missing List the product claims that need case-study-level proof. Identify where Empathy Researchers can produce internal before-and-after case studies. Identify where customer reviews, short quotes, or usability reactions are enough. Agree which external customers need permissioned case-study outreach and who asks.	In progress	Private preview	Proof and credibility
Still to do	Define what a successful pilot looks like Agree the simple scorecard that tells us whether a pilot is going well and whether it should convert. Read detail for Define what a successful pilot looks like This keeps pilot reviews grounded in clear signals instead of gut feel and helps the team know when to extend, convert, or stop. What's still missing Choose the small set of signals that define a healthy pilot. Decide what counts as ready to convert, extend, or stop. Write those rules into a simple pilot scorecard the team can actually use.	In progress	Private preview	Onboarding and pilot operations
Done	Lead with how the product works, not big promises Make sure early materials show the mechanism clearly so people understand what the product actually does. Read detail for Lead with how the product works, not big promises For private beta, concrete workflows are more believable than sweeping outcome claims. People need to see how the product helps, not just hear that it does.	Ready for beta	Foundation	Proof and credibility
Helpful during betaUseful hardening work that makes the motion cleaner and more repeatable while beta is underway, but does not need to block the first warm-account launch.
Still to do	Turn pilot activity into reusable proof Rewrite what we have learned from early customer work into short proof snippets we can reuse. Read detail for Turn pilot activity into reusable proof This means moving from scattered notes and live conversations to portable proof that can appear in the website, deck, or one-pager. What's still missing Pull the strongest proof moments out of current pilot notes and conversations. Rewrite them into short, reusable proof snippets. Place those snippets into the website, one-pager, and deck where they help the story most.	In progress	Private preview	Proof and credibility
Still to do	Prepare the demo environment and training plan Decide what environment, sample data, and training rhythm we use for beta customers. Read detail for Prepare the demo environment and training plan This helps every pilot start from a repeatable setup instead of being reinvented from scratch each time. What's still missing Choose the default demo or pilot environment customers will see. Decide what sample data or starter material is needed. Set the training rhythm so onboarding does not have to be reinvented each time.	In progress	Private preview	Onboarding and pilot operations
Needed for broader GAWork that matters once the goal shifts from controlled relationship-led beta to broader public availability and repeatable market motion.
Still to do	Get permission to use named proof later Secure customer permission for references, quotes, or results that can support broader launch later on. Read detail for Get permission to use named proof later This is not the first blocker for private beta, but it matters once we want stronger public credibility and more formal external proof. What's still missing Identify which customers or pilot outcomes are strong enough to ask permission on. Decide what kind of proof we want: quote, logo, named reference, or result. Ask for permission in a way that feels proportionate and easy for the customer to approve.	Blocked	Early selling beta	Proof and credibility

Read full pillar detail

In progress14% checklist complete

Demand and Sales Readiness

We know the likely sales motion, and the first proof-claims, pricing, and one-pager drafts now exist. What is missing is the polished founder sales kit.

Still needs: We still need the full sales deck, the demo path, and founder validation on the proof claims and one-pager.

Required now: 2 open / 0 doneHelpful in beta: 3 open / 1 doneFor broader GA: 1 open / 0 done

Demand and Sales Readiness checklist
Done	Item	Status	Phase	Workstream
Required for warm-account private betaThe true minimum needed to share the website, sell into known customer relationships, and run a controlled beta safely.
Still to do	Build the sales deck Create the main deck the founder can use to explain the product in a clear, repeatable way. Read detail for Build the sales deck The website already contains much of the story. This item is about turning that story into a portable conversation asset for real customer meetings. What's still missing Turn the website story into a tighter slide sequence for live conversations. Choose the core proof, product, pricing, and pilot slides. Add the approved one-line and proof claims so the deck feels consistent with the rest of the GTM. Review and tighten the first founder-ready draft.	In progress	Foundation	Sales motion and demo readiness
Still to do	Write the demo path Define the exact 15 to 20 minute demo flow so every conversation follows the same strong path. Read detail for Write the demo path This is about the structure of the walkthrough itself: what opens the demo, what screens appear in what order, where proof gets reinforced, and how the conversation closes. It is separate from the ICP item above, which is about making the message and examples feel right for the chosen buyer. What's still missing Choose the opening story and setup for the walkthrough. Decide the exact screen order for the 15 to 20 minute path. Mark where the strongest proof claims should be reinforced during the demo. Define the closing step and the follow-up ask at the end of the demo.	In progress	Private preview	Sales motion and demo readiness
Helpful during betaUseful hardening work that makes the motion cleaner and more repeatable while beta is underway, but does not need to block the first warm-account launch.
Still to do	Approve the buyer follow-up one-pager copy Approve the content for a short buyer-facing follow-up asset before it becomes a designed page, PDF, or shareable link. Read detail for Approve the buyer follow-up one-pager copy The copy now uses the current speed / control / travel positioning, EUR pricing, and explicit product-maturity labels. It still needs founder approval before design or external distribution. What's still missing Review the copy draft with the founder. Tighten the wording so the buyer-facing message is sharper and easier to forward internally. Make sure the copy matches the approved positioning, proof claims, pricing posture, and beta CTA. Choose the final delivery format: designed page, PDF, email follow-up, or shareable link.	In progress	Foundation	Sales motion and demo readiness
Still to do	Pick the first two ways we will find beta customers Decide the main channels for private beta instead of trying lots of things at once. Read detail for Pick the first two ways we will find beta customers In practice this is likely founder outreach and warm introductions, but it should be written down and treated as the actual plan. What's still missing Choose the first two acquisition paths for private beta. Write down why those two paths come first and what is being deprioritized. Turn that choice into a simple working outreach plan.	In progress	Foundation	Demand channels
Still to do	Turn the ICP into outreach language Convert the customer profile into clear outreach messages and a simple sequence of proof. Read detail for Turn the ICP into outreach language Each contact should quickly understand why this matters to them and what evidence we have so far, without reading a strategy document. What's still missing Write the first outreach opener for the chosen buyer. Choose the order in which proof should appear in outreach and follow-up. Create the simple follow-up sequence that turns interest into a meeting.	In progress	Private preview	Demand channels
Done	Prepare answers to common questions The FAQ now reflects current positioning, EUR pricing, assisted beta, and product maturity; its competitor claims still need an August recheck. Read detail for Prepare answers to common questions The internal answer set is materially current again, but it is not approved for sales use until the founder signs off the commercial and product answers and the April competitor review is revalidated. Internal-first format for founder, sales lead, and outreach owners. Includes short answers, longer answers, proof hooks, and watch-outs. Covers both direct objections and qualifying questions that should be asked before answering. Competitor descriptions were last checked on 18 April 2026 and need revalidation.	Ready for beta	Private preview	Sales motion and demo readiness
Needed for broader GAWork that matters once the goal shifts from controlled relationship-led beta to broader public availability and repeatable market motion.
Still to do	Decide what content supports beta selling Choose what lightweight content we will create to support outreach, credibility, and follow-up. Read detail for Decide what content supports beta selling This is not a full content machine. It is just enough material to help founder-led selling work more smoothly. What's still missing Choose the minimum content set that actually helps beta selling. Decide what is needed now versus what can wait until later. Tie each content asset to a real sales use, not just a marketing wish list.	In progress	Private preview	Demand channels

Read full pillar detail

Blocked33% checklist complete

Trust, Legal, and Launch Operations

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

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

Required now: 2 open / 1 doneHelpful in beta: 1 open / 1 doneFor broader GA: 1 open / 0 done

Trust, Legal, and Launch Operations checklist
Done	Item	Status	Phase	Workstream
Required for warm-account private betaThe true minimum needed to share the website, sell into known customer relationships, and run a controlled beta safely.
Still to do	Publish the minimum legal and trust basics Put the basic company, privacy, and legal details in place so the product looks safe enough for beta conversations. Read detail for Publish the minimum legal and trust basics This is the minimum layer that helps a warm customer feel they are talking to a real business rather than an internal experiment. What's still missing Finalize the minimum company and legal wording buyers should see. Make sure privacy, terms, and company details no longer read as provisional. Add the trust basics needed for warm beta conversations on the live site.	Blocked	Foundation	Trust, legal, and procurement
Still to do	Prepare the DPA and procurement answers Create the standard documents and answers enterprise buyers ask for once interest becomes serious. Read detail for Prepare the DPA and procurement answers This includes a DPA path and a short FAQ on how data is handled, who the contract is with, and what buyers should expect. What's still missing Draft the DPA route or template buyers can be pointed to. Write the short procurement FAQ covering contracting, data handling, and buyer expectations. Make sure the founder can answer the first round of diligence questions without improvising.	Not started	Private preview	Trust, legal, and procurement
Done	Lean launch stages are now defined The warm-account beta checklist is now split into what is required now, what is helpful during beta, and what can wait for broader GA. Read detail for Lean launch stages are now defined This is now the working operating model for the GTM board. The important thing is to keep future checklist work mapped back to these three launch stages so the list stays honest about what truly blocks warm-account beta versus what is later hardening work.	Ready for beta	Foundation	Launch governance and measurement
Helpful during betaUseful hardening work that makes the motion cleaner and more repeatable while beta is underway, but does not need to block the first warm-account launch.
Still to do	Create the baseline metrics view Set up a simple place to track the numbers and signals that show whether launch prep and beta activity are progressing. Read detail for Create the baseline metrics view This can start small. The point is to track progress consistently, not to build a giant dashboard on day one. What's still missing Choose the small set of metrics and signals worth tracking now. Create the first working baseline sheet or view. Populate it with the current starting numbers so progress can be judged over time.	In progress	Private preview	Launch governance and measurement
Done	Set a weekly GTM review rhythm The weekly GTM review cadence is now defined through a reusable template and agreed operating rules. Read detail for Set a weekly GTM review rhythm The meeting now has a default 30-minute structure, named attendees, standard account and metrics fields, separate artifact versus product gap tracking, and a transcript-plus-AI workflow for turning the conversation into a reusable operating record. Default attendees: founder, Desmond, CTO, and head of sales / sales lead. Default agenda: metrics, accounts with movement or blockers, objections and gaps, then decisions and actions. Capture method: meeting transcript plus AI-generated draft, then Desmond review and cleanup. Template path: reporting/founder-gtm/reviews/weekly-gtm-review-template.md	Ready for beta	Private preview	Launch governance and measurement
Needed for broader GAWork that matters once the goal shifts from controlled relationship-led beta to broader public availability and repeatable market motion.
Still to do	Explain security and governance in buyer language Turn internal trust thinking into a simple external story buyers can understand quickly. Read detail for Explain security and governance in buyer language The goal is not a huge trust centre yet. It is a clear explanation of data handling, controls, and accountability in plain language. What's still missing Choose the simple buyer-facing trust story we want to tell. Translate internal governance and security thinking into plain language. Package that story in a lightweight format the founder can share in conversations.	In progress	Early selling beta	Trust, legal, and procurement

Read full pillar detail