A company that keeps moving after you generate it.
Static fixtures test one frozen moment. Real software handles a business that changes — month-end, renewals, churn, a fraud pattern that emerges over six weeks. Advance the clock whenever you want fresh activity.
The simulation clock
Every company has a clock you control. Advance it and the business generates the events a real one would — new invoices, payments, hires, deals closing, churn — with books still tying out across the seven correlated systems.
# move the clock 30 days (send X-API-Key: <project key>)
POST https://api.fictix.ai/api/v1/orgs/{slug}/simulation/advance
{ "days": 30 }Advance by days or hours, step a set number of events, or pause. Save a checkpoint and restore it to rerun from the same point. Do it in the console or over the REST API; a packaged CLI is coming.
The seven dials
Company behaviour is shaped by seven controls:
| Dial | Governs |
|---|---|
| Growth | Revenue and customer acquisition trajectory |
| Churn | Customer loss rate and contraction |
| Chaos | Operational messiness — late entries, corrections |
| Fraud | Intensity of fraud-shaped patterns |
| Seasonality | Cyclical revenue/expense swings |
| Maturity | Process discipline of the finance org |
| Trickle rate | How many new events each stretch of simulated time produces |
Events you can subscribe to
As the clock advances, Fictix sends webhooks signed with X-Fictix-Signature: sha256=<hex> (HMAC-SHA256) and retries each delivery up to 3 times with backoff — so you can test event-driven flows (reconciliation triggers, alerting, sync) against events, not a one-shot fixture. Webhooks are on the Developer plan and above.
Why it matters for detection
The hardest anomalies aren't present at t=0; they emerge. Turn up the fraud dial and fraud-weighted activity keeps arriving as you advance the clock, so you test detection on a business that moves, not just a snapshot.
Questions
Can I control how fast data arrives?
Yes. You decide when the clock moves: advance it by days or hours, step a set number of events, or pause it. The trickle-rate dial sets how many events each stretch of time produces.
Does the data stay consistent as time advances?
Yes. New events keep the books tying out across the seven correlated systems (QuickBooks, Stripe, Plaid, Ramp, BILL, Gusto and NetSuite) as the clock moves.
Can I test webhook-driven flows?
Yes, on the Developer plan and above. Advancing the clock sends webhooks signed with X-Fictix-Signature (HMAC-SHA256), retried up to 3 times with backoff.