SegmentStream
Our own company

How we run SegmentStream on SegmentStream.

SegmentStream HQ is the software our company runs on: a CRM from lead to client, contracts and revenue recognition, signed documents and social listening, in one workspace. Agents built it on the platform in its first week, from the same blocks any customer gets, and our team works in it every day.

14
entities, plus the built-in user
10
roles, for members and API keys
12
connections, from Xero and Stripe to Telegram
1 week
from the first commit to CRM, finance and social listening

What the team opens.

The app our team opens every day, built in the workspace's app/ folder and signed in through it.

Deals by stage, per product, with owners and close dates. Only sales and growth see amounts.

hq.segmentstream.app
SegmentStream HQ, the deals pipeline: Lead, Qualification and Opportunity columns with each deal's company, contact, owner, amount and close date

Three parts of the company, one workspace.

Sales and CRM

The website's forms submit leads through an API key that can submit and do nothing else. Each new lead is posted to the team's Telegram group, where someone claims it. A deal changes stage only through move_stage, only sales and growth see amounts, and every change is kept with who made it and when.

Entities
companycontactleaddealclientsubscription
Actions
lead.submitlead.notifylead.claimlead.qualifylead.disqualifydeal.move_stage
Roles
admingrowthsalesaccount_managerintake (API key)
Connections
resendtelegramapollosupabase_crm
Sales and CRM →

Finance and accounting

Each contract and its lines are registered once. Every line gets a revenue schedule, and it counts only after the accountant approves that version. Recognised revenue shows by client and month, per legal entity and currency, and signed documents are filed by legal entity, client and year. Xero and Stripe are read-only connections: Xero stays the ledger.

Entities
contractcontract_linescheduleschedule_lineopening_balancedocument
Actions
contract.registercontract_line.generate_scheduleschedule.approveopening_balance.recorddocument.uploaddocument.move
Roles
accountantadmin
Connections
xero_ukxero_usstripe_ukstripe_us
Finance and accounting →

Marketing and social listening

A monitoring agent, connected over MCP with an API key that can only bring posts in, searches X and LinkedIn and writes each post into the workspace with the reason it picked it. Each member marks a post replied, skipped or dismissed, and the agent reads those verdicts before its next search. Contacts carry subscription and email status synced from Resend.

Entities
social_postsocial_post_reviewcontact
Actions
social_post.ingest_postsocial_post.dismisssocial_post_review.reviewcontact.subscribecontact.set_email_status
Roles
social_monitor (API key)social_reviewermarketingemail_sync (API key)
Connections
apifylinkedin_communitylinkedin_adsresend
Marketing →

In the console.

The same workspace in the SegmentStream console, where it is managed: the ontology an agent wrote, and who may do what.

The CRM part of HQ's ontology, as deployed: a deal, the keys that link it to its neighbours, and the actions on each. Written by an agent.

cloud.segmentstream.com
The console's ontology map of HQ's CRM focused on Deal, showing keys: Deal with its company, primary contact, lead and owner and its move_stage action, surrounded by Client, Lead, Contact and User with their keys and actions, and every relationship named

Built by agents in a week.

Every step was an agent writing code in the workspace's five folders, the checks passing, and one deploy. Dates are from the repository's history in 2026.

  1. 7 Oct

    Lead intake

    The workspace is created and the website's lead form starts writing leads through an API key.

  2. 8 to 9 Oct

    Connections

    Connections declared in code: Resend, Xero, Stripe, Apollo and Supabase, then LinkedIn. The credentials stay with the platform.

  3. 10 Oct

    The CRM

    Companies, contacts, leads, deals, clients and their roles, deployed in two steps. New leads are posted to Telegram, where the team claims them.

  4. 11 Oct

    Finance and social listening

    Contracts, recognition schedules, opening balances and signed documents for finance. Social posts with a review per member for marketing.

  5. 12 Oct

    One set of records

    Contracts linked to CRM clients, and a client's status derived from its contracts.

Built from

Next: Lead scoring, graded within hours →
Enterprise pilot

Start a pilot.

Our engineers build the first version of your software in your own workspace, on your data, as code you own. Tell us what you run today and what you want to replace.

  • One solution, on your data, in your own workspace
  • First version live in two weeks
  • Parity proven before anything is switched off
  • Fixed scope and price, credited to your contract if you continue

Not ready for a pilot? Send the form anyway with your question. An engineer will reply, not a sales rep.

How the pilot works

Goes to our founder’s inbox. No sales queue, no newsletter.

Prefer to build it yourself? Join the waitlist.

Join the waitlist for self-serve:

We’ll email you product updates, tips and onboarding help. Unsubscribe anytime.

Self-serve opens to the waitlist first.