Start with one meeting. Decide with the details in front of you.
Getting started with Bunya begins with a free demo: one meeting to see Command Centre and talk through how your firm works. From there, each step is a choice you make with the scope, timeline and costs in front of you.
You only commit to a paid step after you have seen a written proposal, and you only commit to the build after you have clicked through your own Blueprint.
Book a demo- 01 · Demo & discoveryOne meeting with example dataFree
- 02 · ProposalScope options and pricing, in writingBefore you pay
- 03 · BlueprintA working model of your firm, clicked through by your teamYou decide: build, change or stop
- 04 · Setup & migrationIn your firm’s own Microsoft 365Built for you
- 05 · Testing & trainingProven on your own workYou accept it
- 06 · Go live & improveLive is the beginningOngoing
Six steps
What happens at each step. And what you decide.
Choose a step to see what happens, the decision that is yours, what you get and the time it asks of your team.
Every firm’s timeline is set in its proposal and Blueprint.
One meeting: see Command Centre with example data, and talk through how your firm works.
- What happens
- We show you the advice journey in Command Centre. You tell us where work waits in your firm today.
- What you decide
- Whether you would like a proposal.
- What you get
- A clear view of whether Bunya fits your firm.
- Your team’s time
- One meeting with the principal, and anyone else you would like there.
A written proposal with scope options and pricing for your firm.
- What happens
- We turn what we heard into options: what is included, what is not, and what each costs.
- What you decide
- Whether to start a Blueprint, and which option suits you.
- What you get
- A written proposal with prices, before any paid commitment.
- Your team’s time
- A follow-up call to walk through it.
A paid, low-risk next step: a working model of your firm’s workflows that your team clicks through before anything is built.
- What happens
- Workshops with the people who do the work. We map stages, approval points, documents and tools, then build the clickable model.
- What you decide
- Go ahead with the build, change the scope, or stop here.
- What you get
- A clickable Blueprint, the release plan, agreed scope and running-cost scenarios.
- Your team’s time
- A handful of workshops, plus time to click through the model.
Command Centre configured in your Microsoft 365, and your data brought across to the depth you chose.
- What happens
- The core journey is built in your environment. Data is migrated with a trial run before the real one.
- What you decide
- How much history moves, and when to cut over.
- What you get
- Your Command Centre, set up and holding your clients.
- Your team’s time
- A nominated person to answer questions and check the trial migration.
Your people prove it on real work, then every role is trained.
- What happens
- Representative users run agreed scenarios on real clients. Role-based training follows.
- What you decide
- Accept the release against the tests agreed in the Blueprint, or send it back.
- What you get
- A release proven on your own work, and a trained team.
- Your team’s time
- A few testers alongside their normal work, then a training session per role.
Your team works in Command Centre, and the rest of your scope arrives in releases.
- What happens
- Close support in the first weeks, then regular sessions to choose the next improvement.
- What you decide
- What to improve next, and in what order.
- What you get
- A system that keeps up with how your firm works.
- Your team’s time
- A short regular review with your nominated owner.
How costs are determined
No guesswork. You see the price before you commit.
Your proposal sets out the price, based on four things. Nothing is built until you have agreed it.
Your teams, your advisers and the way your client work is organised.
Which solutions, AI workflows and integrations are in scope.
Start clean, bring active clients across, or bring the full history.
The level of help and improvement you want after go-live.
Running costs: Microsoft licences, usage and agreed support are part of the cost picture, and they are set out before you approve the build.
The Blueprint
The questions that surface halfway through. Settled before anything is built.
A paid, low-risk next step after your proposal: a working model of your firm’s workflows, clicked through by your team before you commit to the build.
How advice moves through your firm today, and where a person must sign off.
Which of your current tools stay, which connect, and which go.
Your SharePoint structure, templates and where client files live.
What moves across, with a trial run before the real one.
The person who looks after templates, triggers and AI workflows once you are live.
Set out before you approve the build.
You decide whether to build, change the scope or stop.
After go-live
Live is the beginning. Not the handover.
How questions, maintenance and improvements are handled after rollout is agreed for your firm.
Video tutorials for each role, and a team to ask when something is unclear.
The integrations agreed in your Blueprint are covered by your support arrangement.
A regular session to choose what to improve next, so the system keeps up with how your firm works.
“The attraction was a practical approach tailored to financial advice, rather than automation for its own sake.”
Questions
Getting started questions. Straight answers.
01How do we get started with Bunya?
02What happens in the demo?
03What is a Blueprint?
04How long does it take to go live?
05What if we decide not to go ahead?
06How much of our team’s time does it need?
Start with one meeting.
Bring the part of your advice process that slows you down most.
NextCustomer stories →