Discovery, product decisions, specifications, reusable services and runtime evidence form a delivery ecosystem. Product and service relationships are visible without claiming that every repository is already consolidated.
CONNECTED ACROSS LSSM
Shared direction. Many connections.
Select an entry to explore its neighbours. Move between ownership, specifications, areas, products, data and infrastructure without leaving this page.
Arrow keys navigate entries. Enter selects. Alt + arrows rearranges. F fits the view; Shift + F fits the selection. + and − zoom. Shift + F10 opens actions.
Drag to pan · Ctrl/⌘ + scroll to zoom
Accessible entry list (14)
Families & ecosystems
Products & experiences
Products & experiences
Products & experiences
Products & experiences
Products & experiences
Products & experiences
Products & experiences
Products & experiences
Products & experiences
Products & experiences
Shared foundations
Shared foundations
Shared foundations
01 / We have market evidence and need to choose the next experiment.
GTM Learning Loop
Choose the next useful market experiment
Use campaign, conversation and deal evidence to refine an ICP, inspect a small cohort and prepare a reviewed message experiment.
Turn GTM evidence into sharper ICP hypotheses, reviewed experiments, approved messages, and better next iterations.
Explore GTM Learning Loop
GTM Learning Loop
GTM Learning Loop learns from campaigns, replies, sales calls, objections, and deal outcomes to sharpen your ICP, improve your messages, recommend proof assets, and create approved next actions.
02 / We need to turn meetings, feedback and product evidence into a decision and an approved handoff.
ContractSpec Studio
Turn meetings and product signals into approved work
A review-first product decision and delivery workspace. ContractSpec Studio connects meetings and product signals to briefs, priorities, issues and approved handoffs, with the evidence and review history kept close to the work.
Turn meetings and product signals into approved work
Start with one meeting or product signal. Review the work, approve the handoff, and export it into the tools your team already uses.
Source stays attachedReview stays visibleKeep your stack
Marketing component excerpt
03 / Quotes, invoices, payments, usage and review decisions need to agree without losing their history.
BillingOS
Keep quote-to-cash connected and reviewable
Country-neutral billing contracts and reusable workspaces for quotes, invoices, credit notes, payments and reconciliation. Optional France-specific readiness and provider adapters sit around the core, while CompanyOS supplies operator review composition.
Reusable BillingOS components · synthetic France-SME fixture · no live invoice, payment or compliance qualification
04 / Usage records, costs and business metrics should be traceable without treating every analytics event as a billable fact.
Usage & metering
Usage evidence that adds up
Shared metering records feature and operation usage with allocation dimensions, exact quantities, idempotency and superseding corrections. PostHog metering and company-metrics adapters provide related reads; business aggregates remain distinct from the usage evidence that BillingOS rates.
The separate read-only adapter layer returns scoped aggregates and evidence from PostHog, Stripe, named PostgreSQL queries, GitHub, Linear, Vercel, Search Console and approved MCP/HTTP/Runtime Node sources.
These business and product aggregates remain distinct from the billable usage ledger.
Source contract and adapter documentation · no fabricated analytics dashboard or live metrics
05 / Conversations and channels need one clear workspace with explicit boundaries.
CommunicationOS
Conversations with clear context and boundaries
A reusable communication application kit with inbox, spaces, rooms, official channel connections, search, meetings, governed work and forms. The same canonical route and authority model supports standalone and embedded hosts.
Return to the active conversation or move deliberately between rooms.
1 room
ACTIVE ROOM
Leadership
A persisted message
Open conversation
CommunicationInbox component · source test fixture · hCircle is a product projection of this platform
06 / Our product needs the emails for one workflow without access to the user’s whole personal inbox.
MailPatio
Email inboxes for your app
Embedded email infrastructure for dedicated addresses, workflow-linked messages and explicit application access. Its public website explains the proposed model with a fictional interactive example; live mailbox service and production intake remain disabled.
One tenant, mailbox and document-review purpose. Draft preparation does not send email.
ContractSpec supplies the cited building blocks. This end-to-end recipe is a proposed Patio composition; its fixture decisions do not run those services.
A local simulation. No account is connected and no message, publication or deployment is sent.
07 / Our app needs a reachable phone identity and the calls or messages for one workflow, without taking over a person’s whole phone.
PhonePatio
Phone identity, calls and messages for your app
A proposed channel product for dedicated numbers, inbound and outbound voice, SMS, MMS and RCS. PhonePatio and TelPatio remain alternative names for this one telephony scope; carrier support and service implementation are to establish.
Concept schematic · service implementation and provider setup to establish.
08 / A proposed boundary for physical letters, print-and-post workflows and delivery evidence, with formal digital correspondence connected to its own governed services.
LetterPatio
Postal correspondence for your workflows
A proposed boundary for physical letters, print-and-post workflows and delivery evidence, with formal digital correspondence connected to its own governed services.
Physical correspondence connected to a digital workflow.
↗
THE PLANNED ENTRY POINTA document and its delivery address
↗PrepareDocuments & address checks
≡DispatchPrint, envelope & post
⌘TrackDelivery events & evidence
Concept schematic · service implementation and provider setup to establish.
09 / A proposed service boundary for social accounts, publishing, comments, permission-dependent direct messages and evidence-aware listening. Shared source building blocks exist; the branded service remains to establish.
SocialPatio
Social channels with clear permissions
A proposed service boundary for social accounts, publishing, comments, permission-dependent direct messages and evidence-aware listening. Shared source building blocks exist; the branded service remains to establish.
Social channel work with explicit identities and platform permissions.
↗
THE PLANNED ENTRY POINTAn authorised social account
↗PublishPosts, media & schedules
≡EngageComments & permitted replies
⌘UnderstandListening, signals & measures
Concept schematic · service implementation and provider setup to establish.
10 / A proposed experience for transcription, speech generation and voice-agent conversations, composed from bounded shared voice capabilities rather than a phone-number or carrier service.
VoicePatio
Speech and voice interaction for your app
A proposed experience for transcription, speech generation and voice-agent conversations, composed from bounded shared voice capabilities rather than a phone-number or carrier service.
This ecosystem groups products around related outcomes. Each product keeps its own audience, interface and implementation. Follow a capability to inspect the scope and evidence for each connection.
An editorial grouping requested by the founder on 29 October 2026. Membership reflects the recorded product scope; it does not establish common product lineage, legal ownership, a live integration or shared customer data.
Membership groups products by the work they address. Product pages and capability coverage record the inspected implementations, proposed connections and availability separately.