See it work

Try a prepared job before you set anything up.

Choose a task close to your work and follow the evidence, review and next decision. The examples use fictional data and require no account.

Example data · no customer records · no account required
Example data

Start with one useful task.

Choose the work closest to yours. These are prepared synthetic examples: no customer records, no external messages and no claim that an acceptance-gated feature is already production-complete.

1 · Finding

A material issue needs an owner

Example finding: a fire-door defect is recorded against the building with a fictional responsible manager and a clear next action.

What this proves today

The public experience can route a visitor into a relevant, clearly synthetic task without an account and without exposing prospect or customer data. Real product processing and private workspace persistence are separate acceptance gates.

Live product logic · synthetic input

Run one real Assentra decision.

Pick a fictional recommendation and run the same deterministic ownership resolver used by Assentra's report compiler. The input is synthetic, but the routing result is produced live by the current product logic.

This proof performs no database write, sends no message and does not represent an AI-generated professional conclusion.

Choose a synthetic finding

Ready

Selected: Fire door defect. Nothing is pre-timed or pre-rendered; press the button to run the server-side resolver.

Prepared proof, not invented customer results.

The public examples explain the intended workflow using synthetic information. They do not stand in for acceptance evidence, measured customer savings or a production integration.

See the full buyer journey modeloptional detail
This retains the existing C4/C5 synthetic journey contract while the task-first sandbox is built out.
Choose your journey

See Assentra through the job you are trying to do.

Each route uses the same fictional Northstar environment but tells a different buyer story: before Assentra, what changes inside Assentra, the first useful outcome, and how the loop closes.

Before Assentra

Compliance information is scattered

Property records, surveys, evidence, actions and resident communication sit across disconnected systems and inboxes.

No single live view of portfolio attention

Ownership is difficult to prove

Evidence and remediation drift apart

Synthetic demo data only. This illustrates Assentra workflow logic and does not represent a customer case study, measured outcome or production integration.

See the original property lifecycle storyoptional detail
Synthetic demo data

Explore a complete property story.

Choose a fictional property and follow the lifecycle from the first signal through ownership, evidence and resolution. Nothing in this experience is customer or resident data.

Northstar Property Partners

Fictional organisation and representative property data created solely to demonstrate Assentra workflows. It is not customer, resident, client or real-property data.

Version demo-portfolio-v1

Property story

Harbour Court

A material fire-door issue moves from inspection finding to accepted completion evidence.

Attention requiredOwner: Property managerEvidence: Partial

Step 1 of 4

Issue identified

A communal fire-door defect is recorded during a structured inspection and routed into Compliance attention.

Lifecycle

Attention required

Responsible role

Property manager

Evidence state

Partial