Good questions.
Clear answers.

Bunya is a complete, AI-powered operating system for Australian advice firms. Command Centre manages the practice, Broadcast HQ supports marketing, and Bunya Voice connects calls and meetings to client context. Your Blueprint defines the products, connections and workflows included for your firm. See how the system fits together ↗

Client records are part of the foundation. Bunya also brings advice work, reviews, reporting, campaigns and conversations into an agreed operating workflow, with AI helping prepare work for review. The difference is the scope of the system and how it is built around your firm.

The products form the wider Bunya system, but your build is scoped around your requirements. We agree which capabilities, connections and rollout stages you need in the Blueprint. There is no assumption that every capability shown on the website is included in every build.

Bunya is built on a Microsoft foundation, including Power Platform, Dataverse, SharePoint and Teams as required by your scope. Command Centre supports day-to-day operations; Power BI provides reporting. The connected services, data sources and licensing are agreed for your setup.

Client and relationship records, advice work, review cycles, tasks, handovers and reporting. Its AI layer can help your team prepare drafts and carry out agreed actions with approval points. Explore Command Centre ↗

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, while connected engagement and performance can inform the next campaign. Explore Broadcast HQ ↗

Available publishing, inbox and analytics functions depend on platform APIs, 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.

Business calling and Teams meetings to SharePoint records and Power Platform account context. 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. Explore Bunya Voice ↗

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.

No. Broadcast HQ is the campaign and content product. Grow is a separate service for brand, website and marketing setup, including help getting your marketing approach running. Explore Grow ↗

It uses connected context to help prepare work such as meeting notes, campaign drafts and client preparation. Agreed actions can include preparing jobs or record updates. Available tools, permissions and approval rules are defined in your build.

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. They do not guarantee that every AI output is correct, so people still check the result.

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.

No. AI prepares and supports the work. Your authorised team remains responsible for reviewing outputs and making professional decisions. Configured checks do not establish compliance or guarantee that an output is free from errors.

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. We confirm those requirements alongside your governance needs.

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.

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.

The agreed setup uses your Microsoft environment, with Dataverse for relevant structured records and SharePoint for supporting documents and conversation artefacts. Data location, retention and any connected AI or third-party processing are reviewed as part of the solution design.

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.

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.

We map the work, explore a clickable model and agree the products, workflows, integrations and delivery scope. You keep the Blueprint either way; its cost is credited if you proceed with the build. See the delivery process ↗

Timing and cost depend on your product 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.

The rollout plan covers testing with your team, relevant training and guidance, a supported run-in and the transition into daily use. We agree the approach around your firm’s requirements.

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.

The test drive lets you explore the Command Centre using example data at your own pace. A booked demo is a guided conversation about your firm and the wider Bunya system. Using your own data requires a separately agreed setup; it is not assumed for an introductory demo.