Questions, answered

For commodity work such as payroll or general ledger accounting, you often should, and we connect to those systems rather than replace them. Building around your process pays off where the way you work is part of your advantage, or where you're paying people to bridge the gaps between tools.

No. Every platform starts from a proven foundation: multi-tenant data, database-enforced permissions, an audit trail, shared records, and apps like the ones in the showroom. What's specific to you is the process on top: your stages, rules, roles, fields, forms and reports.

Only where you want to. Discovery captures how work actually flows today, including the exceptions. We'll point out steps worth simplifying, but the platform is shaped to your process, not the other way round.

Where it helps a defined step, such as drafting a reply, classifying a request or summarising a record. A person stays in control of decisions. In the showroom the assistant only reads, and only what the person asking is allowed to see.

We deliver in short increments, starting with the process that matters most, so your team is using something early and the rest follows. Timing depends on scope and integrations; you'll have a plan with dates after discovery.

Each engagement is scoped after a short discovery, starting with the processes you want first. You'll have a clear estimate before any build begins, and later increments are scoped the same way.

Yes, and we recommend it. One process, such as approvals or service requests, running well is a better start than eight apps half-adopted. The platform grows from there without starting again.

In most cases, where the system offers an API and grants the access needed. Accounting, payroll, email, calendars and identity providers are connected rather than replaced, so information flows without rekeying. We confirm each integration, and what it can do, in discovery.

It's migrated as part of the rollout: mapped, cleaned where needed, loaded and reconciled with your team before anyone relies on it.

You do. Your data stays yours and is held in an environment set up for your organisation, and a full export in a standard format is available on request. Export terms, and ownership and licensing of what we build, are set out in your agreement.

Access is enforced by the database itself, so the same permission rules apply to every screen and report a signed-in person uses. Data is encrypted in transit and at rest, platform administrators sign in with two-step verification, and every change is recorded with who made it and when.

The hosting region is agreed with you, including Australian regions for organisations that need their data held onshore.

Yes. Creates, edits, stage moves, assignments and decisions are recorded with the person, the time and what changed. Your administrators can search and filter that history, as you can in the showroom's audit log.

We support the platform and keep improving it in small increments as your business changes. Everyday changes, such as fields, roles, labels and which apps are on, are in your administrators' hands.

That's the point of building around your process. Rules, steps and approvers are configuration; new capabilities are increments on the same platform, not a migration to a new product.

No. The demo company, its people, customers and figures are fictional. Your demo is private to you, you can change anything in it, and it's deleted automatically after a few days.

The pages you read, the tours and tools you use, and the changes you make in your demo, so we can follow up on what interested you. We see which records you changed, not what you typed into them. The privacy notice explains what's kept and for how long.

Yes. With the same account you can set up a team workspace, choose the apps, start blank or with example data, and invite colleagues with the right roles.