Software people work in
The system stores the records; people, or an outsourcing provider, key in bills, match the bank, chase customers and close the month, screen by screen, paid by the seat and the hour.
Stabiso · coming out of stealthOne unified Enterprise System of Record, with the intelligence built in
Every organization will run its back office as software. This is the system it runs on.
The market is busy adding AI agents to the software companies already have. Stabiso skips that step: the intelligence is built into the system of record itself, the one place that holds the ledger, customers, orders, bills and bank. The system keeps the outcomes true, like an outsourced back office, and people are needed only for the approvals and the real questions. It is running today, from the first lead to the closed month, and anyone can talk to it from their own ChatGPT or Claude.
- 12 outcomes the system keeps true by itself, lead to closed month
- 27 modules on one ledger and one audit trail
- 230+ tools for Claude and ChatGPT
- 690+ documented API operations
01The step we skip
Not AI added to software. Intelligence inside the record.
Most of the market is adding agents on top of the software companies already use. We think that is a detour. The work of a back office is mostly rules, and rules belong where the records are.
AI agents bolted on
Agents outside the system imitate the clerks: they read screens and call APIs, pay per action, and work on data they do not hold. Every answer has to be fetched, and checked again, from someone else’s system.
Intelligence in the system of record
The system knows what should be true and keeps it true: rules settle most of the work the same way every time, AI judges only what is left, the system checks the result, and people decide.
Our view
The company’s records and the work done on them belong in one place. Code does what is deterministic, a model is called only for judgement, one item at a time, and nothing it does counts until the system’s own check says so. People stay where they matter: the second pair of eyes, and the decisions about money and identity.
02Why now
The systems of record have started charging for the way out.
In September 2026 Salesforce announced that each call an outside AI agent makes to its platform, over MCP or the API, will count as a “Headless Platform Interaction” and use up paid Flex Credits. The rate is not set yet and nothing is metered so far; after objections from its partners, Salesforce opened talks with them in October. In 2025 it had already closed Slack’s API to other companies’ apps that store or index customers’ messages.
The direction is clear: a vendor whose software becomes the system of record can charge for every agent that works from the outside. A company that plans to put AI agents on top of such a system pays a toll on its own data, set by someone else.
With the intelligence inside, there is no toll to pay.
In Stabiso the work is done where the records are, so it needs no outside agent to reach them. And the door stays open: the company’s people, its own assistants (Claude, ChatGPT) and any provider it hires use the same API and the same MCP tools, under the same permissions, controls and audit trail. The complete archive of the books and documents is the company’s to export at any time.
Sources: Salesforce Ben on Flex Credits for agentic calls, Salesforce Ben on the partner talks, Reworked on the Slack API change.
03The future for every organization
Every organization has a back office. Most of it is rules.
A bakery, a hotel, a software company, a holding with forty subsidiaries: each one books its bills, matches its bank, chases its customers, files its VAT and closes its month. Today it pays for that work three times: for the software, for the people who work in it, and often for an outsourcing provider or an accounting firm on top. When the system of record does the work itself, those three bills become one, and what is bought is the result.
How a back office runs today
“We bought the software. Now we hire people, or an outsourcing provider, to do the work in it.”
Paid by the seat and by the hour. The knowledge of how it works sits in people’s heads, and every new company, country or month-end adds headcount.
How it runs on Stabiso
“The bank is matched, the bills are booked, the month is closed on the agreed day. We approve; the rest is done.”
The work is done where the records are and recorded with them. A new company is a new set of books on the same system, not a new team.
Julien Bek, Sequoia Capital, in “Services: The New Software” (2026)
“The next $1T company will be a software company masquerading as a services firm.”
04How it works
One unified system of record. Four ways to run it.
Stabiso is an Enterprise System of Record, an ESoR: the one place where an organization’s records live, each defined once, with its rules, its history and who changed it. One ledger for every company, currency and country, and one set of customers, vendors, products, people and documents that sales, purchasing, finance and the close all share. Every way in reaches those same records, under the same rules, with the same audit trail: nothing goes around the controls, whoever or whatever is asking.
We think every organization will run on an ESoR. Classic ERP grew as modules for departments, with people moving the work between them and AI now added on top. An ESoR starts from the records and their rules, so the work itself can run in the system of record, with people deciding only what needs a person.
The app
A fast web app for finance and sales teams on desktop, tablet and phone, in English, German, French, Italian and Swedish. An assistant is built in: ask a question, get the figures and a link to every step, or ask for a list in a sentence and keep it as a report on Home or in your inbox each week. Each company chooses its industry, and the app puts that industry's screens first.
Your AI assistant
Connect Claude or ChatGPT in a minute. The assistant works the books with 230+ tools, from reports to drafting bills, quotes and the month-end close.
The API
Headless from day one. Every screen is built on a public REST API with idempotent writes and Standard Webhooks across 19 domain events, so other systems can do anything a person can.
Autopilot
The system keeps business outcomes true by itself, like an outsourced back office, and leaves a person only the steps that are theirs. Switched on per company and per outcome.
Rules for everyoneRoles, approval policy, AI reviewer, posting limits, closed periods
System of recordLedger, sales, purchasing, bank, tax, close, CRM, support
05Autopilot
Outcomes, not tasks.
Nobody tells the system what to do next. Each outcome is a test it checks from its own records, such as “every bank line is matched”. Switched on, Autopilot keeps it true, and each pass follows the same five steps: code first, AI only where judgement is needed, people last.
-
1code
Check
The system finds what is not yet true, from its own records.
-
2code
Rules
Code settles everything it can, the same way every time, at no AI cost.
-
3model
AI on what is left
Each leftover item, one at a time, with its own records and a few tools. It may ask one question instead of guessing.
-
4code
Check again
An item counts as settled only when the system’s own check says so.
-
5person
People
A short list of one-click steps and real questions, each a link to where it is done.
A pass runs when something happens (a bank statement arrives, a delivery is posted, a deal is won), once a day, and whenever someone presses Run now. The AI works on at most 50 items a company a day; the rest waits for the next day or a person.
Twelve outcomes a service can promise, running today
- SellNew leads are followed upEvery lead has an owner and a first step planned.
- SellWon deals are billedEvery won deal has its quote, order or subscription.
- CollectCustomers are invoicedEverything delivered or due is invoiced.
- CollectCustomers pay on timeReminders at the right level, direct debits collected.
- CollectThe bank is matchedEvery bank line matched, booked or set aside.
- PayBills are in and codedEvery incoming bill read, coded and matched to its order.
- PayVendors are paid on timeBills due soon are in a payment ready to release.
- BookRecurring bookings are madeRent, allocations and accruals booked when due.
- BookAssets are depreciatedEvery ended month has its depreciation booked.
- CloseThe month is closed on timeThe close runs done and the checklist passing by the agreed working day.
- CloseThe VAT return is readyEvery ended VAT period prepared from the books, nothing blocking it.
- CloseGroup and reports are readyIntercompany agreed, the group consolidated, the close memo written.
06Talk to your data
Your own ChatGPT or Claude, connected straight to the books.
Stabiso has its own MCP server today, with 230+ tools. A company connects the ChatGPT or Claude it already uses in a minute: the person signs in and allows it, and from then on they ask in their own words. The assistant works under that person’s rights, so it sees what they may see and nothing more, and every call is in the audit trail.
Sales knows who to call, and when
“Which deals should I call about this week?” The pipeline, the open leads, the follow-ups due and each customer’s history come back in one answer, and the call can be logged straight after.
Leaders see the cash at once
“Show me the cash of every company as a chart.” The assistant reads each company’s cash and its 13-week forecast and draws them side by side; for a group, the consolidated balance sheet and cash flow.
Accounting just asks
“The VAT report for last quarter.” The report comes back with every box opening the bookings behind it; the trial balance, the aging and the close checklist the same way.
Auditors serve themselves
External auditors get read-only access with an end date and may connect their own AI. They pull the reports and files they need without taking the team’s time, and every page and tool call they open is logged.
07What it covers
Not a slide. A complete system of record, running today.
Intelligence is only as good as the records under it, so we built the whole system, not a layer on top of someone else’s. It runs today on demonstration companies, with every function below live.
- Sales and CRM
- Leads and website forms, HubSpot sync, contacts, deals and pipeline, forecasts against quota, teams, quotes customers accept online, Salesforce import.
- Order to cash
- Sales orders, deliveries, invoices as PDF, Swiss QR-bill and e-invoice (ZUGFeRD, Factur-X), reminders, direct debits, statements, aging, and a Shopify shop’s products, orders, refunds and payouts with their fees.
- Subscriptions and revenue
- Recurring billing, seats and plan changes, renewals, recurring revenue reporting, revenue recognised over time as it is earned.
- Purchase to pay
- Purchase orders, goods received, bills read by AI and matched to orders, duplicate checks, payment runs with cash discount.
- Expenses
- A photo of the receipt on the phone fills in the expense by itself; the AI reviewer checks it against the expense policy, so a manager sees only what it flags, and the money goes back in the next payment run. Company card payments are matched to their receipts.
- Bank and currency
- Bank files and statements, automatic matching, reconciliation, daily exchange rates, revaluation of foreign balances.
- Tax
- VAT returns where every box opens its bookings, reverse charge, VAT number checks against official registers, withholding tax.
- Close and reporting
- A month-end checklist and close calendar (counting statutory public holidays) that blocks the close until every check passes, year-end close, P&L, balance sheet, cash flow, budgets, a rolling 12-month forecast every company has from the start, reports anyone builds and keeps: pinned, shared, e-mailed on a schedule, and a 13-week cash forecast from each customer's real payment habit, its lowest point on Home.
- Groups
- Intercompany invoices mirrored on both sides, group loans and dividends, consolidation with eliminations and minority interests.
- Assets, leases, stock and capacity
- Fixed assets with book and tax depreciation, leases, warehouses, goods received on purchase orders into stock through the GR/IR account, stock counts and stock valuation, rooms, seats and people’s time sold by the night, day or hour, never booked twice, and a hotel’s front desk: room types with seasonal rates, check-in and check-out, the stay invoiced at check-out. Each company chooses its industry (hotel, services, wholesale, retail, online shop, manufacturing) and the app puts that industry’s screens first.
- Support desk
- Customer cases and queues with SLA clocks and statutory public holidays, right next to the customer’s open invoices, subscriptions, deals and history, with AI-drafted replies a person sends.
- Open by design
- A public REST API with 690+ documented operations, Standard Webhooks, and an MCP server with 230+ tools, so Claude, ChatGPT and any other system work in the same books under the same rules; the complete archive is the company’s to export.
- Built from modules
- 27 modules beyond the core, each with its own version, tests and release notes, so a new industry or country is a new module on the same books: a hotel’s front desk and an online shop already are.
08Countries
Built for companies across borders.
Tax rules and charts of accounts for each country are part of the product, not a consulting project. Returns are prepared and checked in the system; you submit them.
- Switzerland
- Liechtenstein
- Germany
- France
- Italy
- Spain
- Sweden
- Finland
- Denmark
- Norway
- United Kingdom
- EU one-stop shop
- United States sales tax
- Canada
Charts of accounts: Swiss SME, German HGB, French PCG, Italian, Spanish PGC, Swedish BAS, Finnish, Danish, Norwegian NS 4102, IFRS, UK, US GAAP, Canada. App and documents in English, German, French, Italian and Swedish.
09Controls
Fixed checks decide. People step in when needed.
Autonomy is only useful if you can trust it. The AI reviewer runs fixed checks on a new customer or vendor—duplicates, VAT register, own bank accounts—on the entries of the period-end runs and on expenses, and clears what passes. What it holds waits for another person; an owner who runs the company alone releases it with a passkey touch, so a company of one is never blocked. An administrator switches to four-eyes mode when the law or auditor requires a second person.
Autopilot and assistants may
- Read the books and answer with the entries behind each figure
- Match bank lines, read and code bills
- Prepare entries, bills, quotes and reminders
- Prepare the close and the VAT return
Only a person may
- Approve
- Close a period
- Send an invoice or release a payment
- File a return
AI reviewer (default) or a second person
- New customers and vendors, depreciation, revaluation and deferred tax entries, expenses: cleared when every check passes
- Bank details, payment reversals, posting limits and whatever the reviewer holds: another person, or the sole owner with a passkey
- Every review, each check and its evidence in the audit trail
- Every sign-in needs the person's passkey: a stolen password or a fake sign-in page opens nothing.
- People sign in with their company account (Okta, Microsoft Entra ID), then their passkey; leavers switched off at the provider are switched off here.
- Roles say in plain words what each person can do, open only their part of the app, and lose rights nobody used for 90 days.
- Posted entries are never changed, only reversed. Every entry is chained and checked for tampering.
- Every number opens the entries behind it. Every action names who did it, person or agent.
- Test copies of the live books in one click. They never send e-mails, payments or filings.
10Audit
Built for the audit, from the first entry.
A new system of record has to earn an auditor’s trust. Stabiso was designed for the audit from the start, not fitted for it later, so an audit can take days instead of weeks.
Evidence that cannot be rewritten
Posted entries are never edited, only reversed. Every entry is chained to the one before it, and anyone can recompute the chain to prove nothing was changed.
Every number traces to its source
Each figure in a report or a tax return opens the entries behind it, and each entry the document, bank line or file it came from.
Who did what, and who approved it
Every change records the person or agent, the values before and after, and the second person who approved it. Autopilot records what each pass saw, did and which tools it used.
Controls enforced, not described
Segregation of duties, posting limits and closed periods are rules the system refuses to break, so the auditor tests one rule instead of sampling thousands of postings for it.
The files auditors ask for
The French FEC, the German GoBD data carrier and the OECD SAF-T in one click, an audit evidence pack after the AICPA Audit Data Standards in every country, and a complete archive of a company’s books and documents.
Read-only access for the auditor
Invite an auditor with the date their access ends. They, and the AI assistant they connect, can read everything and change nothing, and every page and tool call they open is in an access log.
11Safe on Google Cloud
Born in the hyperscaler, not moved there.
Stabiso was born on Google Cloud as an event-driven transactional engine with the intelligence embedded: every posting is one transaction in its database, and every change is an event that Autopilot, webhooks and the assistants act on. The services every system of record depends on, its hosting, database, backups, encryption and storage, are Google’s own, run in Google’s Zurich region, so we put our work into the system of record and not into running data centres.
For the infrastructure we rely on Google’s certifications and audit reports, not on our own: Google Cloud publishes its ISO/IEC 27001, 27017 and 27018 certificates and its SOC 1, 2 and 3 reports, and the application runs on Cloud Run under Google’s published 99.95% monthly availability.
What we add on top
- Data, backups and documents stay in one region: today Google’s Zurich region, and the whole system is set up by region, so it can be delivered from any Google Cloud region.
- A backup every day, kept 30 days, and a restore to any second of the last seven.
- High availability, with a standby database in a second data centre of the same region, is part of each customer’s service setup.
- Once a month a scheduled drill restores the books to a copy and checks them, to prove the backups work.
- Sign-in with passkeys, or the company’s own identity provider and then a passkey.
- Every change is in the audit trail, and posted entries are chained so tampering shows.
- Auditors read with their own access that ends; the company exports its complete archive at any time.
12A look inside
13Be part of it
Run your own firms on it. Or build a service on it.
The best way to see what this changes is to run a company on it. The same system serves an owner with one company, an investor or a holding with many, and a provider that runs the back office for its clients: the outcomes, the controls and the evidence are the same whoever approves.
Investors and holdings
Put your own companies on one system of record. Each company keeps its own books, the group is consolidated with its intercompany, and one person can belong to several organizations and choose one at sign-in.
Founders and owners
Skip the outsourcing step. The processes run inside your own system of record, your own people approve, and there is nothing to hand over to a new team.
Outsourcing providers and accounting firms
Sell finished work instead of hours. The system prepares, your accountants approve and answer the questions, and every promise, such as “closed by working day 5”, is measured from the records.
How a firm starts
One company, a few outcomes
Set up the company, bring its opening balances, and switch on the outcomes where most of the hours go today, often the bank and the bills.
Try it on a copy first
A test copy of the live books takes one click and never sends e-mails, payments or filings.
Measure, then add the next
Every pass is recorded: what the rules settled, what the AI did, what was left for a person. The minutes a person spends per company per month come from the records, not from a promise.
Not there yet
One screen across all of a provider’s clients is still to be built: today each organization’s Processes page shows its own. Payroll is not part of Stabiso.
Every back office will be software. Help build it.
Stabiso is coming out of stealth, and runs today on demonstration companies. We are looking for investors who want to be part of it, and who could run their own firms on it, for owners who want their company to run on it, and for outsourcing providers and accounting firms who want to sell finished work instead of hours.