Skip to main content

Why VivoAI

What you can prove with VivoAI
that you can’t with a CRM.

A CRM tells you who you spoke to. VivoAI keeps what was said, what was promised and which condition it satisfies, linked, so you can answer whoever asks.
  • Flat plans, no per-seat charges
  • Hosted in AWS Sydney
  • Onshore AI inference

Three audiences

The difference shows up when someone asks you to prove it.

A CRM is built to manage relationships. Engagement on a regulated project also has to stand up as evidence.
  1. 01 · The regulator

    “Show us the evidence for conditions 9 to 16.”

    A CRM gives you
    A history of contacts and notes. Proving a condition was met means searching notes, inboxes and spreadsheets, then hoping nothing is missing.
    VivoAI gives you
    Each approval condition with its evidence already linked: the notices, calls and field visits that satisfy it. Gaps are visible, and the pack exports when it is asked for.
  2. 02 · The community

    “What actually changed after the consultation?”

    A CRM gives you
    Activity counts: how many meetings were held, surveys sent and calls logged. Nothing about whether anyone’s view moved.
    VivoAI gives you
    Outcomes: a baseline of trust and understanding, how it shifts over the project, and where, linked to the engagement that preceded it.
  3. 03 · The decision

    “Who told the landholder access would be restored by June?”

    A CRM gives you
    A note against a person, written by whoever was there. When they move on, so does the context.
    VivoAI gives you
    Every commitment tied to who made it, when, to whom and for which property, with contradictions between commitments flagged for review.

Ask any vendor

Ten questions to put to every platform you evaluate.

Storage location and processing location are different questions. Ask each vendor for the evidence behind its answers. These are ours.
  1. 01Where is data stored?

    In the AWS Sydney region (ap-southeast-2), with the region enforced in code.

  2. 02Where does AI processing happen?

    Onshore, in the AWS Sydney region. Offshore processing paths are disabled by default.

  3. 03What can they evidence, and whose attestation is it?

    No independent certifications of our own. AWS holds SOC 2 and ISO 27001 attestations for the infrastructure. Not IRAP-assessed. The AWS Sydney infrastructure we run on is IRAP-assessed; that covers our infrastructure.

  4. 04What does the AI actually analyse, and how is it reviewed?

    Calls, emails, survey responses, submissions and social media. Outputs carry a confidence level, ambiguous suggestions wait for a person, and AI-assisted decisions keep an audit trail.

  5. 05How are risk scores explained to your team?

    Each risk score comes with a stated rationale and a confidence level.

  6. 06Is every interaction kept in one record?

    Yes. Interactions link to the stakeholders, properties, projects, issues and conditions they concern.

  7. 07How are commitments tracked to closure?

    Each commitment is recorded against who made it, when and to whom, and tracked until it is closed.

  8. 08Can submissions be grouped by theme automatically?

    Yes. Submissions are clustered into themes, and form-letter campaigns are grouped while unique concerns are kept.

  9. 09Can sentiment and issues be mapped by location?

    Yes. Sentiment and issues can be overlaid on project maps by area and property.

  10. 10Is pricing per seat or a flat plan?

    Flat, published plans with no per-seat charges.

These answers describe VivoAI only. Put the same questions to any vendor you are evaluating and ask for evidence behind the answers.

Data and AI

Where your data lives, and where the AI runs.

Sensitive stakeholder data, including the names, addresses and views of community members, deserves a clear, evidenced answer on each of these.

Australian data residency was a foundational decision for VivoAI, not a setting added later. It affects every layer, from where data is stored to where the AI models that process it run.

Storage
All data stored in the AWS Sydney region (ap-southeast-2), with the region enforced in code. AWS is US-headquartered, and we are upfront that Australian hosting does not by itself place data beyond the reach of foreign law.
AI inference
Runs onshore in the AWS Sydney region. Offshore processing paths are disabled by default.
Security baseline
Built against the Australian Government Information Security Manual (ISM), ISO/IEC 27001 controls and the ASD Essential Eight.
IRAP
Not IRAP-assessed. The AWS Sydney infrastructure we run on is IRAP-assessed; that covers our infrastructure.
Privacy
Designed to support your obligations under the Privacy Act 1988 and the Australian Privacy Principles. NSW agencies assess their own AI use cases under the NSW AI Assessment Framework; VivoAI supplies the evidence those assessments need.
Language
Transformer-based language understanding that handles Australian English, place names, regional colloquialisms and government terminology, not keyword matching.

Pricing

Flat plans. No per-seat charges.

Per-seat licensing creates a perverse choice: restrict access and lose visibility, or pay for every officer, project manager and executive who needs to see the record.

VivoAI publishes flat plan pricing. Each plan includes a set number of users, from 3 on Essentials to 50 on Enterprise, and adding a team member within your plan’s limit costs nothing extra. Procurement, legal and executive users can share the allowance, which suits joint venture and alliance delivery where several organisations need the same project data.

Users included per plan

  • Essentials3 users
  • Professional8 users
  • Professional Plus15 users
  • Enterprise50 users

One published price per plan. No surprise costs when someone joins within your plan’s limit.

Next step

Put us to the test with your own questions.

Bring the audit request, the councillor’s question or the solicitor’s letter you’re worried about. We’ll show you how VivoAI would answer it.