A series a b2b saas, generated to feel real.
Recurring revenue, deferred-revenue schedules, and a burn rate someone watches weekly.
What this company looks like
A fictional series a b2b saaswith up to two years of correlated books — customers, vendors, payroll, ledger. Larger companies are a labeled sample. It's not a real company and any resemblance is coincidental; it's a profile you control. Save it and it gets a short ID, so everyone replays exactly the same data.
What's hard to test about it
- Deferred revenue and recognition over the subscription term
- MRR movements — new, expansion, contraction, churn — tying to the GL
- Stripe payments matching QuickBooks invoices and deposits in the bank feed
Compatible with the tools it runs on
Fictix exposes this company through endpoints shaped like each of these services. Change the base URL and send your Fictix project key (X-API-Key). Responses follow each vendor's shape, so most client code works with little or no change. (Fictix is independent and not affiliated with these products — the names describe compatibility only.)
The mistakes you can hide in it
Plant the failures this profile actually suffers from, then measure whether your product catches them:
Questions
Is this based on a real series a b2b saas?
No. It's a fictional company generated from a profile (industry, stage, size); any resemblance to a real business is coincidental. You own the parameters, not someone else's brand.
Does the data reconcile across systems?
Yes for QuickBooks, Stripe, Plaid and Gusto: they're among the seven correlated systems, so their books tie out. Mercury carries the same company's data but isn't reconciled.
Is it reproducible?
Yes. Save the company and it gets a short ID like fix-7kq. Fictix stores it, so your laptop, CI and the demo all replay exactly the same data. Regenerating from the same seed gets close, but not identical.