Good questions. Clear answers.

Answers about Bunya Command Centre, AI with human approval, security and your data, the optional add-ons and getting started. Each answer says plainly what is agreed for your firm and what is not assumed.

01 · 6 questions

Command Centre & the advice journey.

01What is Bunya?
Bunya AI builds Bunya Command Centre, the practice operating system for Australian financial advice firms. Command Centre is financial advice software that helps take clients from first meeting to implemented advice, with AI preparing the work and advisers approving every step, inside the firm’s own Microsoft 365 environment. Bunya Voice and Broadcast HQ are optional add-ons. See Command Centre ↗
02Which parts of the advice journey does it cover?
Four stages, in order: client onboarding, SoA preparation, advice implementation and reviews and fee consent. At each one, Bunya prepares the prework and your team checks it before anything moves on. Compliance and evidence run across every stage. The steps, tools and AI preparation included are agreed for your firm in its Blueprint. The advice process guide explains each stage.
03How is it different from a CRM?
Client records are part of the foundation. Command Centre is built around the work between the first meeting and implemented advice: fact finds, file notes, SoA requests, handovers and approvals, with AI helping prepare that work for your team to review. The difference is that focus, and that it is built around your firm in your own Microsoft 365 environment.
04Do we have to stop using Xplan?
No. Command Centre focuses on the advice delivery journey, from first meeting to implemented advice, and does not set out to replicate specialist modelling, research or portfolio tools. Your Blueprint looks at the tools your firm uses now and identifies what to keep, connect or replace.
05Does Bunya write the Statement of Advice?
Bunya’s focus is the prework. The strategy discussion, fact find, documents and modelling notes come together in an AI-assisted SoA request pack, which the adviser checks before it goes to paraplanning. Your paraplanners and advisers produce, review and present the advice. See SoA preparation ↗
06Will it work with how our firm already does things?
That is the starting point. Command Centre is shaped around how your team already works, not a template you bend your firm to fit. The Blueprint maps your current process and agrees the stages, roles, approval points and connections before anything is built.

02 · 6 questions

AI workflows & human approval.

01What does the AI actually do?
It uses the client’s own information to help prepare the work between steps: file notes, fact-find inputs, request packs and follow-up drafts. Agreed actions can include preparing tasks or record updates. Available tools, permissions and approval rules are defined in your build. See AI workflows & integrations ↗
02Can AI make changes or send things without us reviewing them?
AI-assisted record changes are presented for confirmation before saving. Advice drafts, marketing content and eligible meeting follow-up require human review before use or sending. Separately agreed automations, such as publishing already-approved content at a scheduled time, follow the rules configured for that workflow.
03Does AI replace our professional judgement?
No. AI prepares and supports the work. Your authorised team remains responsible for reviewing outputs and making professional decisions. Advisers keep strategy and product judgement, and a clickthrough is not advice approval. Configured checks don’t establish compliance, and they don’t make an output error-free.
04What are AI skills?
Skills are reusable instructions and steps for a particular task, with defined inputs and review points. They help make the process and output structure more consistent, but they don’t make every AI output correct, so people still check the result.
05Can we see where AI was used, and who approved it?
AI-usage recording can form part of the workflow and its evidence trail. Your scope defines which events and outputs are recorded, who can access them and how they are retained. What was prepared, who approved it and what happened next stay with the client record. See compliance & evidence ↗
06Does Bunya connect to our platforms and modelling tools?
Command Centre is built in Microsoft 365, including SharePoint and Teams where scoped. Connections to other platforms, modelling or research tools are assessed and agreed for your firm; none should be assumed. Your existing tools can stay where they are. See how integrations are agreed ↗

03 · 6 questions

Security, ownership & your data.

01What does “built in your own Microsoft 365” mean?
The system is delivered into your firm’s Microsoft environment and built around your agreed processes. Your contract defines the delivered components, documentation and ownership terms. Microsoft licensing, third-party services and agreed ongoing support remain separate costs. See security & your data ↗
02Where are our records and documents kept?
The agreed setup uses your Microsoft environment, with Dataverse for relevant structured records and SharePoint for supporting documents and conversation records. Data location, retention and any connected AI or third-party processing are reviewed as part of the solution design.
03How do Microsoft 365 and Power BI fit in?
Command Centre is built inside your firm’s own Microsoft 365, using services such as Dataverse, SharePoint and Teams as your scope requires. Command Centre supports day-to-day advice work; Power BI provides reporting. The connected services, data sources and licensing are agreed for your setup.
04Can different team members have different access?
Yes. Roles and permissions are configured around the work each person needs to do. Personal task views and broader practice views can be provided to the appropriate roles. Access rules need to be agreed, configured and tested for your firm.
05Can we move data from our current system?
Migration starts with an assessment of source records, export options, duplicates, document structure and permissions. We then agree mapping, validation and the migration scope. The effort depends on the quality and accessibility of the source data.
06Could another provider maintain the system?
A suitably experienced Microsoft specialist may maintain the components in your environment, subject to the delivered documentation, permissions, licences and any third-party dependencies. We agree handover and support responsibilities so you understand what continuity would involve.

04 · 5 questions

Optional add-ons.

01Do we need Bunya Voice or Broadcast HQ?
No. Command Centre is the core product, and advice delivery does not depend on either add-on. Bunya Voice (calls, meetings and follow-up) and Broadcast HQ (marketing and client communications) are optional. Any add-ons are agreed in your Blueprint, and there is no assumption that every capability shown on the website is included in every build.
02What does Bunya Voice connect?
Bunya Voice is an optional add-on that connects business calling and Teams meetings to SharePoint records and the client’s account in Command Centre. For eligible client meetings, AI prepares notes, actions and a branded follow-up draft for authorised review. Number eligibility, call types, licensing and recording policies are confirmed during scoping. See Bunya Voice ↗
03Is every call or meeting automatically recorded?
Capture depends on the supported service, licensing, agreed recording policies and consent settings. Those requirements are established before rollout. Account matches that are not confident are surfaced for review.
04What does Broadcast HQ do?
Broadcast HQ is an optional add-on for marketing and client communications. It takes an idea, voice note, file or link through campaign planning, drafting, review and supported publishing. Brand context and configured checks support human approval, and your firm reviews everything before it is published. See Broadcast HQ ↗
05Can Broadcast HQ publish and reply on every social channel?
Available publishing, inbox and analytics functions depend on each channel’s API, account permissions and configuration. We confirm the channels and publishing accounts in your scope. Paid-media management and advanced multi-identity workflows may need a separate phase.

05 · 6 questions

Getting started & support.

01How do we get started?
Book a demo. It is one meeting that covers both the demo and discovery: you see Command Centre with example data, and we talk through how your firm works and where advice is backed up. How getting started works ↗
02Is the demo free?
Yes. The demo is one free meeting with no obligation. You only commit to a paid step after you have seen a written proposal.
03What happens in the Blueprint?
The Blueprint is a paid, low-risk next step after your proposal: see a working model of your firm’s workflows before you commit to the build. We map the work, click through a model of your firm and agree the workflows, connections, any optional add-ons and the delivery scope.
04How long does a build take, and what does it cost?
Timing and cost depend on your scope, workflows, data migration, integrations and rollout needs. These are confirmed in your Blueprint and proposal, alongside licensing, usage charges and ongoing services. We do not assume one fixed price or timeframe suits every firm. To test your own assumptions first, try the cost & capacity calculator ↗
05How do you handle training and go-live?
Go-live happens in releases. Each release is tested on your own work and accepted by your team, with training for every role, a supported run-in and the transition into daily use. We agree the approach around your firm’s requirements.
06What happens when we want changes or need help?
Your support arrangement defines how to raise issues, request changes and access guidance. Changes are scoped and tested before the agreed release process. Monitoring, maintenance and improvement allowances depend on your service agreement. Contact our team ↗
Xplan AI skills Your data Approval Blueprint Bunya Voice Broadcast HQ Go-live Migration Training

Ask us anything in a demo.

One meeting covers the demo and discovery. We’ll answer it for your firm.

NextHow getting started works →