Snapshot + self-serve kit
The launch release screens one workflow and provides a definition checklist. It creates no order, charge, subscription or customer-system connection.
SecureFlow / exception-only operations
Start with a free rules-based screen for one repetitive SME workflow. The public launch release stops at the Snapshot result and self-serve definition kit; paid implementation, connections and monitoring are not yet open.
The launch release screens one workflow and provides a definition checklist. It creates no order, charge, subscription or customer-system connection.
Paid service waits for an independent merchant account and KYC, signature-verified payment webhooks, and an operating fulfilment executor.
Before any future connection: terms, minimum OAuth scope, mapping and messages, UAT, then go-live. The system cannot approve itself.
Transparent planned catalogue · no checkout
Only Snapshot and the self-serve Workflow Definition Kit are public at launch. Paid prices are proposed pilot parameters, not market averages or order offers. No paid order, charge, subscription or intake can be created.
A$0 ex GST
A$0 incl GST · available at launch
Free opportunity score, data-risk route and a machine recommendation: proceed, narrow, prepare or decline.
A$290 ex GST
A$319 incl GST · planned pilot
Planned process and data map, value baseline, guardrails, acceptance tests and implementation specification.
A$390 ex GST
A$429 incl GST · planned pilot
Planned guided access, MFA, data-minimisation and approval controls with automatic re-checking.
A$1,490 ex GST
A$1,639 incl GST · planned pilot
Planned standard website-enquiry workflow, two supported connectors, customer UAT and 30-day monitoring.
A$149/mo ex GST
A$163.90/mo incl GST
A$1,490/yr ex GST · A$1,639/yr incl GST
Planned monitoring, retries, monthly evidence report, quarterly re-scan and permission-change alerts.
Launch boundary
Snapshot and the self-serve kit are the complete launch slice. The paid lifecycle below remains disabled until its legal, payment-security and fulfilment gates are operating.
An attributed free Snapshot measures workflow value, feasibility and data guardrails.
The result may recommend a planned product, narrow the scope, provide preparation guidance or decline. It is not an order.
The self-serve Kit helps the customer document triggers, fields, approvals, exceptions and tests.
No payment is accepted until independent merchant/KYC, signature-verified webhooks and fulfilment controls pass.
The launch release creates no intake. Any future intake must follow verified payment and explicit customer approvals.
Connections, tests, UAT, go-live, monitoring, renewal and referral remain outside the public launch release.
Planned paid acceptance · not active
Snapshot hard stops
Free · rules-based · 5–8 minutes
The snapshot measures workflow value, remote feasibility and data guardrails. It returns, narrows or declines a route automatically. It does not collect passwords, tokens or files.
Self-reported screening only — not an audit, certification, penetration test or legal opinion. Active or suspected cyber incidents are routed out of the sales funnel.
Questions before the snapshot
No. The launch release contains only the free Snapshot and the self-serve Workflow Definition Kit. Paid products are not open for order, no payment is accepted, and no order, subscription or intake is created.
The free launch release needs no sales call or project-manager hand-off. If paid delivery later opens, your team would approve terms, minimum OAuth access, field mapping, outbound wording, UAT and go-live. Internal people would enter only for a genuine legal, security or engineering exception.
The planned template covers one standard website enquiry: validate, deduplicate, summarise, route by deterministic rules, write to one supported CRM or business table, acknowledge with approved wording, retry safe failures and produce an outcome report. It is not available to order at launch.
Payments, contracts, credit, hiring or dismissal, regulated advice, legal, medical, financial or migration judgement, regulatory submissions, covert monitoring, spam, incident response, penetration testing or unapproved asset scanning.
No. The public Snapshot collects neither and the launch release does not connect to customer systems. If paid delivery later opens, supported connections would require customer-approved OAuth with the minimum allowlisted permissions. Identity, health and financial documents remain outside the planned template.
The Snapshot can recommend preparation or a narrower planned product, but it cannot create an order. If paid delivery later opens, unsupported connectors, permissions or data must stop or downgrade the scope before any accepted implementation; a salesperson cannot override the safety boundary.