Appendix brief
The repo already supports a platform brand with multiple SKUs. What remains is turning that product architecture into a crisp commercial story that shows what is sold now, what is bundled capability, and what remains directional proof of the broader business unit.
Key takeaways
Related workstreams
What the repo already proves
The product is not being invented as a single point solution. The strategy docs, launch posture, site IA, and portfolio structure all describe a suite posture with distinct products and capability layers inside one system.
This matters because the founder does not want the company pigeonholed as only a survey tool, and the repo already contains enough structure to defend that broader posture without resorting to vague future-state claims.
What still needs a founder call
The open question is the beta-visible product map. Which tools are saleable today, which trust capabilities are included rather than sold separately, and whether Research Architect is public beta product, bundled workflow component, or near-term proof of the roadmap all still need explicit treatment.
The founder site should make that distinction visible because it is the bridge between suite ambition and launch honesty.
Why shared services belong in a GTM conversation
This is where BU basics meet GTM. Shared services, entitlements, governance, and usage logic are not just engineering concerns; they determine whether the multi-SKU story can be sold and supported credibly.
The founder site should therefore treat platform architecture as both product truth and commercial readiness truth. Billing and entitlements are still incomplete, which may constrain how sophisticated early pilot agreements and plan structures can be.
Source evidence