Nobody can say how many customers you have
The count comes out different depending on which system you ask and who last tidied it. Both answers have a defensible story behind them.
Decisions made on a number nobody in the room will defend.Systems build: CRM, data and automation
One system of record, and the work running on it
A CRM or business operating software configured against how your work actually runs, everything you already hold migrated into it and validated, the repeating steps automated, your tools connected, and the reporting built on top. Handed over to an administrator on your side who can change it without us.
What this is fixing
Every team works from the version of the customer they can see
All six symptoms below come from that one cause. There is no record to correct, so each team maintains its own, and every one of them is right about part of it.
The same client gets contacted twice
Two people work the same account in the same week, because neither could see that the other already had.
The client concludes you are not organized, and tells someone.Reporting is a person, not a system
Somebody spends the last two days of every month building the report out of exports, by hand, from memory of how they did it last time.
The number arrives too late to act on, and cannot be checked.The process lives in whoever has been here longest
There is a right way to do it and it was never written down, so each new hire learns a slightly different version of it.
Quality depends on who happened to pick up the work.You bought the tool and went back to the spreadsheet
A system was purchased, configured to the vendor default, and quietly abandoned because it did not match how the work actually runs.
A licence you still pay for and a process you still do by hand.Nothing connects, so everything is retyped
The order is entered in one place, the invoice in another, the delivery in a third, each time by a person reading off the last screen.
Three chances to get it wrong, and no way to tell which one did.What gets built
Six parts, and what you hold at the end of each
The first four are what most people mean by a systems build. The last two are what decide whether it is still being used a year later, which is why they are in the scope rather than in a follow-on quote.
- Part 01
The system of record
A CRM, or business operating software such as Zoho One, configured against the way your work actually runs. Not a default template with your logo on it.
- Objects, fields and stages that match your process, not the vendor demo
- A pipeline for each distinct way you actually sell or deliver
- Roles, profiles and record-level access rules
- The platform decision made on evidence, and written down with the reasons
- Part 02
Your data, migrated and proven
Everything you already hold, moved in and reconciled. This is the part that decides whether anyone trusts the system in week one.
- Every source inventoried, including the spreadsheets doing a system job
- Duplicates found and merged against rules you approve first
- Records cleaned, standardized and mapped field by field
- A validation report you sign off before go-live, not after it
- Part 03
The repeating work automated
The steps your team does by hand every week, running on their own, with the exceptions going to a named person rather than failing quietly.
- Assignment, routing and follow-up on a rule rather than a memory
- Approvals and notifications wired to the step that triggers them
- Documents and quotes generated from the record instead of retyped
- An exception path and an owner for every automation
- Part 04
Your tools connected
Data moving between the systems you already run, so a change in one is a change everywhere, without anybody keying it twice.
- Integrations built and documented, both directions where both are needed
- What happens when one system is unavailable, decided in advance
- Existing tools kept where they work, replaced only where they do not
- A map of what data lives where, and which system is authoritative
- Part 05
Reporting people trust
Dashboards built on one set of numbers, so the meeting can argue about the decision instead of about the figures.
- The measures agreed before anything is built
- Role-based views: an operator sees their work, a director sees the function
- Live from the system rather than assembled from exports
- A baseline taken before go-live, so you can show what changed
- Part 06
Ownership handed over
Your administrator can change the system without calling us. That is the exit condition, and it is the one most rollouts skip.
- A written procedure for every process, in the language your team uses
- Training by role, plus separate administrator training, recorded
- A permissions matrix and a named owner for each set of data
- A stabilization period after go-live, scoped rather than assumed
The migration
Six steps, and you approve the rules before anything moves
This is the part of a build that decides whether people trust the system in the first week, and it is the part most quotes describe in one line. Here is the whole of it.
- Inventory
- Every place a record currently lives, including the exports, the shared drive and the spreadsheet somebody maintains privately. You see the list before anything moves.
- Deduplicate
- Matching rules proposed, reviewed and approved by you, then applied. Which record wins a merge is your decision, not a default.
- Clean
- Formats standardized, dead records flagged rather than deleted, and the gaps that only a person can fill sent back to you as a list.
- Map
- Field by field, source to destination, written down. Anything with nowhere to go is raised before migration rather than discovered after it.
- Migrate
- Loaded into the configured system in a test pass first, checked, then in the real one. History comes with it, not just the current state.
- Validate
- Counts reconciled source against destination, samples checked by your own people, and a report you sign. Go-live waits for that signature.
Nothing in your existing systems is deleted by us, and you keep them running until you say otherwise. If the validation report does not reconcile, go-live moves. That has happened, and it is cheaper than the alternative.
Price and duration
Two bands, split where the scope stops being fixed
One team on a settled process is a defined package, so it carries a fixed price. Anything with several departments, integrations or reporting that has to be designed is scoped after the design, because quoting it before that would be a guess with your money in it.
Fixed scope
$2,500 to $4,500
5 weeks
One team, one settled process, one system. The scope and the price are agreed before we start and neither moves.
- One system of record configured to your process
- Existing data migrated and validated
- Core automations and training by role
- Fixed price, paid half at start and half at training
Scoped build
$4,500 to $12,000
10 to 19 weeks
Several teams or departments, more than one system, integrations, or reporting that has to be built rather than switched on. Scoped once the design is agreed.
- Multiple systems on one architecture
- Integrations built and documented
- Reporting and dashboards designed with you
- Stabilization period after go-live
Licences are yours and are billed separately by the vendor. Running the system after go-live is a separate decision, not an assumption. Two things sit outside these bands: agents and AI inside the workflow, which is the other half of FusionBuild, and a whole department rebuilt as a single environment, which is the AI Operating System. Where nobody has agreed what the work should look like yet, FusionMap comes first and makes this build shorter.
Platform
The platform is a finding, not a preference
It gets decided during the design, on evidence, and you get it in writing with the reasons. Three routes come out of that decision, and the third is the most common one.
Zoho
For Organizations who would rather licensing, build and support came from one place, and who want the operating software and the CRM to be the same decision.
You receive A Zoho CRM or Zoho One build, with the licences under one agreement in your own account and one support path when something breaks.
Microsoft, or a mix
For Organizations already standardized on Microsoft, or running a set of tools they have no intention of replacing and no reason to.
You receive The same build on the platforms you already have, plus the integration work that makes them behave as one system rather than four.
What you already own
For Businesses running template adoption: the system went in configured to the vendor demo, and the team was back on the spreadsheet inside a quarter.
You receive The system you are already paying for, reconfigured against how the work runs, with your data cleaned into it. No new licence.
Zoho Authorized Partner. Where Zoho is the right answer, licensing, build and support come from one place. Where it is not, the design says so, and clients have finished on Microsoft, on a mix of platforms, and on tools they already owned.
Fit
What the build needs from you before it starts
Five things, and the fifth is the one that gets skipped. A build with no named administrator is a system that becomes ours to run by default.
Ready to build if
- One system of record is the goal, and somebody senior owns that decision
- You can name the processes that have to run inside it
- The data exists somewhere, even if that somewhere is a spreadsheet
- Somebody will be the administrator afterwards, and you can say who
- That person can be freed for training, not only for the kickoff call
Start somewhere else if
- Nobody has agreed what the work should look like yet. Go to FusionMap.
- What you need is AI inside a workflow rather than the system under it. Go to FusionBuild.
- A whole department has to run as one environment. Go to the AI Operating System.
- The system already exists and nobody has time to run it. See Managed Operations.
Questions
The seven we get asked before every build
What happens to the data we already have?
It is inventoried, deduplicated, cleaned, mapped and migrated, and you sign off a validation report before go-live. We do not delete anything in your source systems. You keep them running until you are satisfied.
We already have a CRM nobody uses. Does it have to be replaced?
Usually not. That is template adoption: the system went in configured to the vendor demo rather than to how the work runs, which makes it a configuration problem sitting on a capable platform. Rebuilding on what you already own is cheaper, and it is what we recommend wherever the platform can do the job.
Do you only build on Zoho?
No. We are a Zoho Authorized Partner, which means licensing, build and support can come from one place when Zoho is the right answer. Clients have finished on Microsoft, on a mix of platforms, and on tools they already owned. The platform decision is made during the design, on evidence, and you get it in writing with the reasons.
How long before people are actually using it?
Five weeks for one team on one settled process. Ten to nineteen where several departments, integrations or custom reporting are in scope. Training and go-live are inside those figures rather than after them.
Who owns the licences?
You do, in your own account, whether we resell them to you or you buy them direct. Nothing is held in an account you cannot get into without us.
What happens after go-live?
A stabilization period is inside the scope: issues resolved, workflows corrected against how people actually use it, and data quality monitored. After that your administrator runs it. Managed Operations exists if you would rather that was us, and you are not obliged to buy it.
Do we need AI for any of this?
No. The systems build stands on its own and most clients stop here for a while. Where both are wanted this comes first, because AI over scattered data produces confident wrong answers and no amount of model quality fixes it.
After go-live
Where a finished system usually leads
A system people trust changes what the next constraint is. Most clients stop here for a while, and that is a legitimate place to stop.
Bring the system you already tried to fix
The spreadsheet, the half-configured CRM, the tool nobody opens. We will tell you whether it can be rebuilt on what you own, what the data is going to take, and which band it falls in.