← Back to all demos

Weekly reporting

Monday’s numbers. Can you trust them?

Bring billing, sales and support snapshots into one reviewable report. Every number has a source. Missing data stays visible.

Synthetic data. This is a deterministic reporting prototype: no live integrations or language model calls. It is not a client case study.

Explore a data condition

3 sources · one validation gate

All three are ready. If a source is missing or stale, the gate holds the draft.

Complete synthetic sample. Use the source controls to inspect missing or stale data.

Draft prepared · human review required

Source: demo-report.json · complete base data

View data table
3 sources · one validation gate
EvidenceValue / state
BillingReady
CRMReady
SupportReady

Example report

7–13 September 2026

Snapshots as of 14 Sept, 09:00 UTC. All amounts in EUR.

Download sample report (Markdown)

Source readiness

All three source snapshots passed validation.

Deterministic synthetic report. The published report shows the complete case; missing and stale conditions are produced by the same reporting code.

  • Billing

    Ready

    Snapshot:

  • CRM

    Ready

    Snapshot:

  • Support

    Ready

    Snapshot:

Validation gate

Period · amounts · freshness

3 / 3 sources ready

Passed

Report draft

Calculated metrics · source references

Prepared

Human review

Check before local export

Pending review

Source: Complete sample report (JSON).

View data table
Source status and snapshot time · report period to (end exclusive)
SourceStatusCaptured (UTC)
BillingReady14 Sept, 08:00 UTC
CRMReady14 Sept, 08:10 UTC
SupportReady14 Sept, 08:20 UTC

Draft — human review required

Sources passed validation. Check completeness, definitions and the urgent support ticket before approving. Nothing is sent automatically.

Monthly recurring revenue

+12% versus the supplied previous snapshot.

Sum of normalized monthly subscription amounts at the current snapshot; not revenue collected this week. MRR change is percentage change from the provided previous snapshot; unavailable when the baseline is zero.

Previous snapshot€10,000
Current snapshot€11,200

Common baseline: €0. Previous total sums the supplied integer-cent subscription amounts in sample billing data (JSON).

Billing· 14 Sept, 08:00 UTC

Source: Complete report (JSON)

View data table
Monthly recurring revenue
Billing snapshotMRR
Previous snapshot€10,000
Current snapshot€11,200

Open pipeline

€30,000

Unweighted value of open opportunities at the snapshot; not forecast revenue.

CRM· 14 Sept, 08:10 UTC

Open support tickets

3

Unresolved tickets at the snapshot, including carried-over tickets.

Support· 14 Sept, 08:20 UTC

Tickets resolved this week

2

Resolved timestamps within the seven-day UTC period; period end is exclusive.

Support· 14 Sept, 08:20 UTC

Items for review

  • 1 urgent support ticket remains open. Review before sharing.
  • Confirm source exports are complete and metrics mean what your team expects.

Approval belongs to a person.

The runnable example requires a reviewer name and the exact report fingerprint before creating an approved local export. Change the input and the old approval no longer works. A blocked report cannot be approved.

Technical run details

Source records

  • Billing · billing-demo-0914 · ready · 14 Sept, 08:00 UTC
  • CRM · crm-demo-0914 · ready · 14 Sept, 08:10 UTC
  • Support · support-demo-0914 · ready · 14 Sept, 08:20 UTC

Report fingerprint

6fa01ea38af3bb013d069ef624a692b70cd30aa5fc5649eaa5109ef5aa11b036

This sample makes zero external API calls (€0 in API charges). Hosting, development and human review still have costs. Client time savings, model quality and live connector reliability have not been measured.

Scope a weekly reporting pilot

We can agree your metric definitions, check an approved sample from billing, CRM and support, and define when a draft must stop for missing data. A pilot would measure the review work before any live integration.