Demo tenant data

Everything the demo tenant holds is invented. This page lists it — every company, person, customer requirement, project and commercial number a client sees during a walkthrough — so anyone presenting the demo, or reviewing it, can read the world without opening the code.

The world is Orrery Software: a fictional mid-market B2B SaaS vendor. Orrery sells its own software to mid-market customers across Northern Europe, and its services organisation handles the implementation, integration, migration, optimisation, training and specialist product work around that software. The demo is designed to feel like a SaaS vendor with a growing installed base, a lean internal services team, and more customer demand than it wants to fulfil entirely with permanent headcount. That is the same customer profile the marketing site  addresses, so the demo argues for the pitch rather than against it.

Two rules hold for everything below, and both are enforced in code:

• Fictional only. No real prospect or client name appears anywhere in the demo tenant.
• Fully authored. Nothing is randomised. Every company, person, title, value and score is written down, so a reset reproduces exactly the world described here.

The source of truth is the storyline module — packages/services/src/db/services/demo-data/storyline/saas-vendor.ts, exported as demoStoryline. It is the only storyline; there is no second world to switch to. This page describes what that module produces; the Demo environment guide covers how it is seeded, reset and presented.

Demo terminology

The walkthrough uses one vocabulary throughout, and this page follows it.

The journey reads: Customer requirement → Qualification → Project → Bid → Quote → Delivery → Completion → Revenue.

At a glance

Orrery uses EUR as its tenant reporting currency, and all service values are normalised into EUR regardless of the customer’s local currency.

Sales regions covered: Benelux, DACH, Nordics, UK & Ireland. Languages: Danish, Dutch, English, French, German, Swedish.

The scale is deliberate. Individual pieces of work run €22k–€48k, and the completed projects behind them €20k–€39k. That is enough workload to create a real capacity, revenue and customer-success problem without turning Orrery into an enterprise systems integrator.

The people

The demo has 20 sign-in seats — four internal, ten customer contacts, six delivery experts. Every one is a real login, so any of them can be signed in as or viewed as; none of them is a real person.

The Orrery team

Customer contacts

One named contact per customer company. Each signs in to their own company’s workspace.

Delivery experts

Language is not decoration: matching treats it as a hard filter, so an expert only ever appears against a customer whose language they speak.

Sign-in addresses

Addresses and credentials are not published here. Every seat follows one convention, jamie.nisbet+<lastname>.<role>@sustentus.com, and the twenty are derived from the storyline rather than kept as a second list. Passwords live as environment variables on the Vercel project. See Login credentials.

Customer companies

Ten fictional Northern-European companies, deliberately mid-market — none of them should feel like a global enterprise transformation account. They spread across sectors, countries, regions and languages so every filter and grouping in the platform has something to show. Sofia Almeida owns the whole portfolio.

Three of them carry a story the walkthrough points at.

Havenbrook Retail Group — the anchor account

An eighteen-store specialty retailer, and the seat a demo is usually presented from. It has the most history of any account: a completed phase 1, a live and blocked phase 2, a supplier onboarding integration in quoting, a store-rollout requirement awaiting qualification, and five more completed projects behind it. It is the account that shows how an established SaaS customer keeps generating paid services demand long after implementation.

Thornhill Utilities — the customer experience risk

A regional utility whose satisfaction responses run 6, 7 and 6 — well below Orrery’s target and below the platform’s low-CSAT cutoff, so it surfaces as a genuine failing-CSAT row rather than one more green line. It shows up naturally in customer health, renewal risk and delivery-quality views, and it also carries one qualified-out requirement.

Merrivale Legal — the contraction risk

A 140-lawyer firm whose completed project values decline as time runs forward — €28k, then €22k, then €21k — and which has closed nothing in four months, so it lands on renewals and revenue-at-risk. Its new €24k matter billing requirement is the realistic opportunity to reverse the decline.

The executive account read

Every account opens on one card at /vendor/customers/[id], in three parts: the licence they hold, the services work in play, and how the account is tracking. Only the first is stored; the rest is computed from the seeded projects, requirements, invoices and satisfaction responses, which is why a reset reproduces it exactly.

Licence — authored. ARR, renewal date and licensed platforms are the one part of the account the platform cannot derive: this tenant’s money is services money, so no invoice or quote in it is licence revenue. The storyline authors all three. ARR is held in thousands and the renewal as an offset in months rather than a calendar date, so a reset next year still opens on renewals ahead instead of a page of lapsed contracts. Licensed platforms, not products — a customer buys the suite, and each account licences the platforms whose modules its projects actually touch.

Services — derived. Services pipeline is every requirement and project on the account that has not been qualified out, valued at its accepted quote where one exists and its budget midpoint where none does. Active projects, new requirements, qualified out and the engagement count are counts over the same leads. The budget the seeder writes brackets each authored value symmetrically, so the midpoint is that value exactly and an account’s pipeline adds up to the figures listed further down this page.

Tracking — derived, and shared with the metrics surface. Account health is metric M5: a 0–100 score from satisfaction (40 points), engagement recency (25), delivery reliability (20) and commercial trend (15), banding Green at 70 and above, Amber 45 to 69, Red below 45. Revenue at risk is metric M10 — the contracted value of in-flight work carrying a risk flag — built tenant-wide and then filtered to this account. Both are read rather than recomputed, so this page and /vendor/metrics can never band the same customer differently on the same day.

Descriptive scale — eighteen stores, a 140-lawyer firm, eleven renewable sites — stays prose, and lives in the requirement text where it belongs.

Licences by account

Ten accounts, €3,100k of ARR between them, each €190k–€450k. The two accounts carrying a risk story renew soonest, which is what makes them urgent rather than merely unhappy.

Renewal is an offset from the seed run, not a fixed date — storyline.test.ts holds every account inside the coming twelve months and pins Merrivale and Thornhill as the two soonest.

Delivery experts

Six consultants, between them covering every product module, skill and language combination the seeded projects need.

Elin Bergqvist

Implementation lead, Orrery Core

Leads Orrery Core implementations end to end — discovery, configuration, migration and cutover. Twelve years in enterprise software delivery, the last six on Orrery, across retail, logistics and manufacturing rollouts in the Nordics and Benelux.

• Skills: Implementation management, Platform configuration, Change enablement
• Products: Ledger, Billing, Workflow Studio, Scheduler, Mobile Field
• Languages: English, Dutch, Swedish
• Projects: 3 current, 4 completed
• Evidence on file: 2 items (see Expert evidence)

Chidi Okafor

Data migration and analytics

Moves data onto Orrery and makes it answer questions once it is there. Specialises in high-volume migrations from legacy ERP, reconciliation of historical records, and standing up the reporting layer customers actually use in their first quarter.

• Skills: Data engineering, Reporting and analytics
• Products: Data Hub, Insight, Forecast
• Languages: English, Dutch, Danish
• Projects: 3 current, 9 completed
• Evidence on file: 2 items (see Expert evidence)

Anders Lindberg

Integration and API engineering

Builds the connections between Orrery and everything around it — ERP, CRM, warehouse and finance systems. Works API-first, and is usually the person called in when an integration built by somebody else has stopped behaving.

• Skills: API integration, Solution architecture
• Products: Integration Hub, API Gateway, Partner Portal
• Languages: English, Dutch, Swedish, Danish
• Projects: 4 current, 2 completed
• Evidence on file: 1 item (see Expert evidence)

Margot Duval

Security and compliance

Takes Orrery deployments through security and compliance review. Handles access models, audit trails, data residency and the evidence packs regulated customers need before they will sign off on a go-live.

• Skills: Security and compliance, Platform configuration
• Products: Ledger, Partner Portal
• Languages: English, French
• Projects: 2 current, 6 completed
• Evidence on file: 2 items (see Expert evidence)

Stefan Reinhart

Platform performance

Performance and scale. Profiles slow Orrery deployments, tunes the workloads behind them, and sizes environments for customers whose volumes are about to change — usually before the customer has noticed there is a problem.

• Skills: Performance tuning, Solution architecture
• Products: Scheduler, Asset Register, Forecast, Mobile Field
• Languages: English, German, Swedish
• Projects: 3 current, 7 completed
• Evidence on file: 1 item (see Expert evidence)

Nina Whitlock

Training and change enablement

Gets people to actually use what has been implemented. Designs the training, the champion networks and the floor-walking plan for the first weeks after go-live, for audiences from finance teams to field engineers.

• Skills: Technical training, Change enablement
• Products: Mobile Field, Workflow Studio, Scheduler
• Languages: English, Dutch, Danish
• Projects: 2 current, 8 completed
• Evidence on file: 1 item (see Expert evidence)

Service catalogue

Orrery sells services around its own software rather than third-party platforms, which is what makes the demo read as a software vendor selling services around its own product. The hierarchy is four tiers: platform → product → service → skill.

Platforms and product modules

Services

Core services, attached to every product — Rapid implementation, Team training, Premium support.

Specialist services, rotated across the products — Ongoing optimization, Data migration, Integration build, Custom extension, Compliance review.

Skills

Each skill is linked to the services it delivers, so every product → service path resolves to at least one expert who can do the work.

Services pipeline

Orrery currently holds €794k of services pipeline across twenty-five records: 3 new customer requirements, 20 active or recently completed projects, and 2 qualified-out requirements. The individual pieces of work run €22k–€48k, which is deliberate — they should feel meaningful to a mid-market SaaS vendor without looking like enterprise transformation programmes.

The spread is chosen so every one of the nine journey stages has something in it and every dashboard opens on a populated queue.

Values are in thousands, as the storyline authors them. Seeded quotes carry EUR.

What each stage carries

A record’s stage decides which supporting documents the seed writes with it, so the demo never shows a quote with no bid behind it or an invoice with no milestone.

Every record — including the ones that never reach a bid — carries its own authored proposal title and summary, four milestone names, blocker labels, customer actions, scope changes and both sides of the project conversation. The stage decides how much of that becomes a document.

Pending customer requirements — 3 records · €104k

Customer needs identified but not yet qualified. Nothing has gone to the expert pool, so the proposed project and milestones below are authored content rather than records anyone can open.

Rollout to remaining 17 stores

Havenbrook Retail Group · €48k · No expert assigned yet

Customer requirement — Head office and one pilot store are live on Orrery Core. We want the remaining seventeen stores moved onto the platform without disrupting trading.

Requirements — Rollout in controlled groups. Each store needs a rollback plan and an overnight cutover.

Proposed project — Complete the Core rollout across the remaining estate. Seventeen stores in controlled groups, each group proven before the next, with an overnight cutover per store.

Milestones

1. Two-store proving wave
2. First five stores
3. Remaining ten stores
4. Estate hand-over

Asset records migration

Nordstral Energy · €32k · No expert assigned yet

Customer requirement — Asset records across our eleven renewable sites sit in legacy exports and spreadsheets. We want them in Asset Register with the history intact.

Requirements — Move the history into Asset Register with an exception report for anything that fails to map.

Proposed project — Asset Register migration and reconciliation. Profile first, map second, load third — with every unmappable record surfaced rather than quietly discarded.

Milestones

1. Source profiling
2. Mapping
3. Trial load
4. Production load

Matter billing migration

Merrivale Legal · €24k · No expert assigned yet

Customer requirement — Matter billing still sits in a legacy practice system that no longer fits how the firm works. We want it on Ledger, with the history intact.

Requirements — Move active matters and seven years of billing history into Ledger with appropriate confidentiality controls.

Proposed project — Ledger implementation for matter billing. Billing on Ledger with a migrated history that stands up to a regulatory inspection.

Milestones

1. Discovery
2. Ledger configuration
3. History migration
4. Parallel run

Backlog — 3 records · €91k

Qualified and accepted, waiting on requirements sign-off before the pool sees them. As with pending, the proposal below is authored but not yet a record.

Customer shipment portal

Dalmore Logistics · €29k · No expert assigned yet

Customer requirement — Our customers contact depot staff for basic shipment status because they cannot look it up themselves.

Requirements — Provide self-service shipment status through a branded, mobile-friendly portal.

Project — Partner Portal for customer shipment visibility. A branded shipment-status portal built on Partner Portal, designed for a phone in a yard rather than a desk.

Milestones

1. Status model
2. Portal configuration
3. Customer pilot
4. Release

Production scheduling rollout

Kaltbach Manufacturing · €27k · No expert assigned yet

Customer requirement — Scheduling across our four production lines is managed through spreadsheets that only two people understand.

Requirements — Prove Scheduler on one line, against the spreadsheet, before extending to the remaining three.

Project — Scheduler implementation across four lines. Prove Scheduler against the incumbent spreadsheet on one line, then extend to the remaining three.

Milestones

1. Line analysis
2. Configuration
3. Parallel scheduling
4. Rollout

Regulatory reporting automation

Stellan Bank · €35k · No expert assigned yet

Customer requirement — Our small finance team assembles the quarterly regulatory reporting by hand, and the assembly is where our errors come from.

Requirements — Automate the main submission pack through Insight, with every figure traceable to its source data.

Project — Regulatory reporting automation. Insight generates the submission pack end to end, with lineage from every figure back to its source record.

Milestones

1. Measure definitions
2. Data lineage
3. Report generation
4. Dry run

Bidding — 3 records · €111k

Open to the expert pool. Each carries a shortlist of four matched experts and three bids — two submitted, one still in draft, which is what a bid pool mid-flight looks like.

Claims intake automation

Bellweather Insurance · €42k · Leading match: Anders Lindberg

Customer requirement — Our claims teams re-key first-notice information by hand from email and web forms, and it is the slowest part of our claims journey.

Requirements — Automate intake and integrate it with the existing claims platform. Must pass our security review.

Project — Automated first notice of loss. Workflow Studio takes intake from email and web, with a clean exception path for anything it cannot parse.

Milestones

1. Intake analysis
2. Workflow build
3. Claims integration
4. Security review

GxP validation pack refresh

Aubrec Pharma · €38k · Leading match: Margot Duval

Customer requirement — We need the Orrery validation pack refreshed for the current software release. Study start-up is being held up by it.

Requirements — Update the controlled documentation and audit evidence without rebuilding the existing operating model.

Project — Current-release GxP validation refresh. A validation package for the release you actually run, written to survive an inspection.

Milestones

1. Gap assessment
2. Protocol update
3. Evidence collection
4. Pack hand-over

Mobile Field rollout for 85 engineers

Thornhill Utilities · €31k · Leading match: Elin Bergqvist

Customer requirement — Around eighty-five field engineers still work from printed job sheets for part of their work and re-key everything at the depot.

Requirements — Deploy Mobile Field with offline working, and prove the process with one regional team before going wider.

Project — Mobile Field rollout. Mobile Field on the handsets your engineers already carry, with offline working proven on one regional team before rollout.

Milestones

1. Device and coverage review
2. Configuration
3. 15-user pilot
4. Wider rollout

Quoting — 3 records · €103k

A bid has been accepted and the commercial quote is with the customer. The losing bids are on the record as rejected.

Patient scheduling integration

Vireo Health Group · €26k · Preferred expert: Anders Lindberg

Customer requirement — Appointment changes in the clinic scheduling system do not always reach the customer portal quickly enough, so patients arrive for appointments that have moved.

Requirements — One authoritative appointment feed across our fourteen clinics. Changes must reach patients within minutes, not overnight.

Project — Clinic-to-portal scheduling integration. Integration Hub makes the clinic system authoritative and pushes changes to the portal in near real time.

Milestones

1. Data model
2. Integration build
3. Sync testing
4. Clinic rollout

What this one demonstrates — a second quote sits in draft, waiting on a decision.

Supplier onboarding integration

Havenbrook Retail Group · €36k · Preferred expert: Anders Lindberg

Customer requirement — Supplier details are entered separately into three internal systems, which is most of why onboarding a supplier takes six weeks.

Requirements — Enter supplier details once and distribute them automatically. Target onboarding under one week, evidenced on real suppliers.

Project — Supplier onboarding integration. Integration Hub becomes the single entry point, fanning supplier details out to the three downstream systems.

Milestones

1. Process mapping
2. Hub configuration
3. Downstream integrations
4. Live supplier proving

Payments settlement extension

Stellan Bank · €41k · Preferred expert: Chidi Okafor

Customer requirement — Card settlement files are reconciled by hand every month by our finance operations team, and the errors are expensive.

Requirements — Automate the bulk of reconciliation while preserving a clear adjustment trail back to source.

Project — Settlement reconciliation extension. A custom extension that reconciles partner settlement files daily, with a traceable adjustment trail.

Milestones

1. File analysis
2. Reconciliation logic
3. Adjustment workflow
4. Month-end proving

What this one demonstrates — a rejected quote sent the requirement back round to another bid.

In progress — 4 records · €153k

Work under way. Four milestones each — two done, one running, one upcoming — with invoices raised against the completed ones, plus live blockers, customer actions and a project conversation.

Phase 2, stock and replenishment

Havenbrook Retail Group · €47k · Lead expert: Elin Bergqvist

Customer requirement — Finance is already live on Core. Phase 2 moves stock and replenishment, which is where the operational risk sits.

Requirements — Complete the work without disrupting store deliveries. Phased delivery with clear milestones and weekly check-ins.

Project — Phase 2, stock and replenishment. Stock and replenishment onto Core in three controlled steps, each reversible.

Milestones

1. Stock data mapping
2. Replenishment rules
3. Despatch integration
4. Go-live

What this one demonstrates — the live milestone is blocked; one invoice is in draft, awaiting finance approval.

Policy reporting data hub

Bellweather Insurance · €39k · Lead expert: Chidi Okafor

Customer requirement — Pricing and reserving both rely on policy data that lives in several systems, and the two teams use different definitions.

Requirements — A small governed reporting layer with agreed measures, signed off by actuarial before build, and a daily refresh.

Project — Policy reporting Data Hub. Data Hub consolidates four policy systems behind one set of actuarially signed-off definitions.

Milestones

1. Definition workshops
2. Source ingestion
3. Measure build
4. Daily refresh

What this one demonstrates — one invoice is disputed.

Customs API integration

Dalmore Logistics · €34k · Lead expert: Anders Lindberg

Customer requirement — Growing declaration volumes make manual customs submission through the authority’s portal inefficient.

Requirements — Submit declarations directly through the customs API, with retry and exception handling. Must survive the customs service being down.

Project — Customs API integration. API Gateway submits declarations directly, retries transparently, and queues what it cannot resolve.

Milestones

1. API accreditation
2. Submission build
3. Exception handling
4. Production cutover

What this one demonstrates — the project has sat in this stage for 70 days, breaching its SLA band; 2 overdue customer actions; one invoice was rejected.

Telemetry ingestion tuning

Nordstral Energy · €33k · Lead expert: Stefan Reinhart

Customer requirement — Telemetry from several sites drops occasional readings during high-volume periods, so availability figures are disputed internally.

Requirements — Stabilise ingestion — no dropped readings at peak load, demonstrated by test — and backfill the recoverable historic gaps.

Project — Telemetry ingestion tuning. Find where the pipeline sheds load, fix it, and prove it with a repeatable peak-load test.

Milestones

1. Load profiling
2. Pipeline tuning
3. Peak-load testing
4. Historic backfill

What this one demonstrates — 1 overdue customer action.

Delivered — 3 records · €110k

Work finished and invoiced in full. The satisfaction survey has not come back yet.

Shop-floor terminal rollout

Kaltbach Manufacturing · €45k · Lead expert: Stefan Reinhart

Customer requirement — Production data from our four lines is still captured on paper and keyed in later, so our live view of the plant is hours old.

Requirements — Fixed terminals on every line, usable with gloves on, making production data available within minutes of being recorded.

Project — Shop-floor terminal rollout. Mobile Field on fixed terminals, designed for gloved hands and a noisy plant.

Milestones

1. Terminal siting
2. Interface configuration
3. Four-line rollout
4. Operator training

Access review automation

Aubrec Pharma · €37k · Lead expert: Margot Duval

Customer requirement — Quarterly access reviews take three weeks of our internal operations team’s time and still leave leavers with active accounts.

Requirements — Automate joiner, mover and leaver controls, and generate audit evidence that satisfies our auditors.

Project — Access review automation. Access lifecycle driven from HR events, with review evidence generated rather than assembled.

Milestones

1. Role model
2. HR integration
3. Review automation
4. Auditor walkthrough

Billing exception automation

Thornhill Utilities · €28k · Lead expert: Chidi Okafor

Customer requirement — Our small billing team manages recurring exceptions through spreadsheets, and the backlog grows faster than they clear it.

Requirements — Automate the common exception types and reduce the standing backlog as part of delivery.

Project — Billing exception automation. Automate the exception types that make up most of the volume, and reduce the standing backlog on the way through.

Milestones

1. Exception taxonomy
2. Automation
3. Backlog reduction
4. Hand-over

Survey — 2 records · €74k

Delivered, and the customer has answered the satisfaction survey.

Clinic scheduling optimisation

Vireo Health Group · €44k · Lead expert: Stefan Reinhart

Customer requirement — Utilisation varies across our fourteen clinics and we do not know why. We want the scheduling rules tuned against real demand.

Requirements — Tune the scheduling rules using actual demand, without increasing patient wait times.

Project — Clinic scheduling optimisation. Analyse actual demand patterns per clinic and tune Scheduler’s rules to match them.

Milestones

1. Demand analysis
2. Rule tuning
3. Four-clinic pilot
4. Wider rollout

Satisfaction — 9/10.

Onboarding journey optimisation

Stellan Bank · €30k · Lead expert: Nina Whitlock

Customer requirement — We see material customer drop-off during digital onboarding — a fifth of applicants leave partway through — and we cannot see where.

Requirements — Identify the main abandonment points and improve completion measurably within the quarter.

Project — Customer onboarding optimisation. Instrument the onboarding journey, find where applicants leave, and change the steps that cause it.

Milestones

1. Journey instrumentation
2. Drop-off analysis
3. Step redesign
4. Measurement

Satisfaction — 8/10.

Completed — 2 records · €48k

Signed off end to end — delivered, surveyed, expert rated, paid in full.

Phase 1, finance

Havenbrook Retail Group · €26k · Lead expert: Elin Bergqvist

Customer requirement — We wanted finance moved onto Core before expanding use into the operational teams.

Requirements — Finance live with a clean first month-end close. Hand-over session for the internal team.

Project — Phase 1, finance implementation. Finance implemented first, with a clean close as the acceptance test for the whole approach.

Milestones

1. Chart of accounts migration
2. Ledger configuration
3. Parallel close
4. Go-live

Satisfaction — 9/10.

E-signature rollout

Merrivale Legal · €22k · Lead expert: Nina Whitlock

Customer requirement — Engagement letters still require too much manual handling — printed, signed and scanned — which loses us work to faster firms.

Requirements — Introduce e-signature with an evidential audit trail our regulator accepts.

Project — E-signature workflow rollout. Workflow Studio handles engagement letters end to end, with an audit trail built for the regulator.

Milestones

1. Evidential requirements
2. Workflow build
3. Two-team pilot
4. Firm-wide rollout

Satisfaction — 7/10.

Qualified out — 2 records

Requirements closed without going to the pool, with the reason on the record. Neither became a project, so the proposals below exist only as authored content.

AR work-instruction pilot

Kaltbach Manufacturing · No expert — closed before the pool saw it

Customer requirement — We explored augmented-reality work instructions on one production line.

Requirements — Pilot on one production line, with a view to wider rollout.

Why it was qualified out — No budget in the current financial year.

Proposed project — Augmented-reality work instructions pilot. A single-line pilot to establish whether AR instructions reduce assembly errors enough to justify a rollout.

Milestones

1. Line selection
2. Content build
3. Pilot and measure

Drone inspection trial

Thornhill Utilities · No expert — closed before the pool saw it

Customer requirement — We explored drone inspection for several remote assets, to reduce manual site visits.

Requirements — Trial across three remote asset sites.

Why it was qualified out — Outside Orrery’s current service catalogue.

Proposed project — Remote asset drone inspection trial. A three-site trial to establish whether drone inspection data can replace routine manual inspection visits.

Milestones

1. Site selection
2. Trial flights
3. Data assessment

Completed project history

Thirty-six projects sit behind the current tenant, all delivered and paid during the previous 18 months, dated backwards in 30-day windows — window 1 is the last thirty days. They exist so the analytics have a past: without them every “vs prior period” comparison reads flat and the retention cohorts have nothing to retain. Together they represent €1,012k of completed services revenue, each project €20k–€39k, which keeps the historic services business consistent with the current mid-market project profile.

The last thirty days completed €125k against €116k in the thirty before, so the vendor analytics open on a positive movement. Thirty-two projects have a customer satisfaction response and average 8.2/10; four completed and were paid without one, which is what makes “revenue awaiting CSAT” a real number rather than zero.

Completed services revenue by window

Expert evidence

Nine items uploaded by experts against their profiles, deliberately spread across all four verification states so the review queues, the expert’s own knowledge page and the evidence chips on a bid all have something in them.

Supply outreach

Four outreach dispositions, one per action state, distributed across the coverage cells the seeded requirements produce. They are what the SDM’s coverage and outreach views read.

Supporting records

Each record drags a supporting cast behind it, and it is all authored per record rather than pulled from a shared pool — so no two projects in the demo show the same blocker, the same customer action or the same conversation. One seed run writes:

Blockers, actions and scope changes only exist on projects that reached delivery, which is why the counts are small next to the invoice and message totals.

Records outside this page

The demo tenant also fills the activity feed, the audit trail and every persona’s notifications. Those are working records rather than business content — they describe what happened to the data above, they change as a walkthrough progresses, and they reset with the tenant. They are out of scope for this page; the Demo environment guide covers what the reset does with them.

The shape of the business

Taken together the tenant represents a mid-market SaaS services operation. Paid services projects sit between €20k and €50k, current services demand totals €794k, and historic completed services revenue is roughly €1m across 36 projects. The licence business behind that is €3,100k of ARR, with individual customer relationships between €190k and €450k — authored on the accounts rather than derived, because services money and licence money are different money (see The executive account read). The scale is chosen to create a real capacity, revenue and customer-success problem without turning Orrery into an enterprise systems integrator.

Keeping this page true

The world above is one module, and there is only one. If it changes, this page has to change with it — there is no generation step that keeps them in step.

• The data lives in packages/services/src/db/services/demo-data/storyline/saas-vendor.ts, exported as demoStoryline.
• There is no second storyline and no way to select one. The seeder and the reset both read that module directly; neither takes a storyline argument.
• storyline/storyline.test.ts pins the totals published here — the €794k pipeline, the €1,012k completed tail, the value bands, the window figures, the stage spread and each expert’s project counts. A value edited without this page being updated fails there.