Contracts, revenue recognition and documents, in finance software you own.
Each contract and line is registered once. Every line gets a revenue schedule, and revenue counts only after the accountant approves that version. It runs alongside your ledger, linked to the same clients and deals as sales.
One contract with its terms and lines. Each line says how its revenue is recognised and to which accounts.
How we run our own finance on it
Our own contracts, revenue recognition and signed documents run on it across two legal entities, in the UK and the US, alongside Xero.
How we run SegmentStream on SegmentStream →- Contracts and their lines are registered once, linked to the client and the deal that won them.
- Each line gets a revenue schedule. It counts only after the accountant approves that version; a new version supersedes the old one.
- Recognised revenue shows by client and month, per legal entity and currency.
- Signed documents are filed by legal entity, client and year under consistent names.
- Opening balances are rebuilt from Xero through a read-only connection. Nothing here writes to Xero.
- Sales and account managers read contract terms for renewals, and nothing else of finance.
What it covers
Contracts and contract lines
Each contract and line registered once, linked to the client and the deal that won it, per legal entity and currency.
Revenue recognition with approval
Every line gets a revenue schedule from its amount, pattern and dates. It counts only once the accountant approves that version.
Documents
Signed documents filed by legal entity, client and year under consistent names, linked to their contracts.
Opening balances
Rebuilt from Xero through read-only connections. Nothing here writes to Xero.
Approvals
Expense and invoice approvals, with rules such as "nobody approves their own" and "over a threshold, a second approver" inside the action.
Subscription revenue from Stripe
MRR, expansion and churn from Stripe, modelled by a pipeline over the read-only connection.
Built from typed blocks
No new product to buy: the blocks below, written by an agent into your workspace's repository and deployed with one command.
None required.
None required.
$ segmentstream deploy
Every block ships together from one git repository your company owns. SegmentStream runs it.
- revenue-recognition spreadsheets
- contract folders in shared drives
- contract revenue tools such as ChartMogul or Baremetrics, for this use
Your ledger keeps running. Existing contracts and documents load through the ontology API, opening balances are rebuilt from the ledger through a read-only connection, and the accountant approves each schedule before it counts.
Enterprise, with our engineers
Our engineers model your contracts and recognition rules with your accountant, load your existing contracts and documents, rebuild opening balances from your ledger, and show the schedules match before anyone relies on them.
Self-serve, with your own agent
Tell your agent how you recognise revenue. It writes the contract, schedule and approval actions, and the accountant role that alone can approve.
Related solutions
Read more
- 8 October 2026Agent sprawl: how to run a company on one AI agent instead of 3,000Companies are building AI agents by the thousand, each with its own instructions, its own keys and its own copy of the rules. Vercel went the other way and moved hundreds of internal agents behind one. Here is how a company runs on a single agent, and what has to sit behind it.
- 7 October 2026Read this before you cancel HubSpot or SalesforceCompanies are cancelling CRM contracts and having AI agents write their own. Writing the CRM is now the easy part. What decides whether it survives is the layer underneath it: objects, permissions, actions, history and safe access for agents. That layer is called an ontology.
- 3 October 2026SaaS becomes company contextAgents are now how people ask questions and get work done. The CRM, the BI tool and the warehouse stop being separate products and become one thing a company owns: its context. Here is what that is made of, and why we're building it.
Questions
How does it work with Xero or QuickBooks?
It works beside them. Your ledger keeps the books; contracts, revenue recognition, approvals and documents run on SegmentStream, linked to the same clients as sales. Xero is a ready-made read-only connection, and QuickBooks connects through OAuth 2.0.
Who can change what revenue counts?
Only the accountant role can approve a schedule, and a schedule counts only after it is approved. A new version supersedes the old one, and every change is kept with who made it and when.
What do other teams see?
Sales and account managers read contract terms, dates and status for renewals. They see no schedules, balances or documents. The accountant reads CRM records to link contracts but cannot change them.
Rather have it built for you? Start a pilot.
Our engineers model your contracts and recognition rules with your accountant, load your existing contracts and documents, rebuild opening balances from your ledger, and show the schedules match before anyone relies on them.
- 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 worksYour company’s software, built by agents, owned by you.
$ segmentstream workspace create acme --region eu --subdomain acme
▸ Created workspace acme · database, warehouse and a private git repository
$ segmentstream workspace WORKSPACE-ID clone acme && cd acme
▸ your agent writes the five folders and runs the checks
$ git add -A && git commit -m "First version"
$ segmentstream deploy
▸ app, ontology API and MCP tools live for your invited members
Our engineers build the first version on your data in two weeks, at a fixed price.
Or join the waitlist for self-serve:
Self-serve opens to the waitlist first.