We build all of it, or just the hard parts.
Cerebro is software and a team of data engineers. We connect your systems, make the numbers agree, build the dashboards, tools and custom applications your team works from, and keep them right. Some customers have us do all of it. Others build alongside us, or on their own with us on call.
Three ways to work with us
Same product and the same team either way. You choose how much of the work is ours.
We build it
For teams with no data person, or whose data person left
You tell us what you watch and what you decide. We connect the systems, model the data, build the dashboards and tools, and fix what you flag on review calls. Your team explains the business and checks the numbers.
We build it with you
For teams that want to learn it as it takes shape
We build the base and take the hard parts: the sources with no API, the data models, the first dashboards. Your people ask for changes on regular calls and learn to make their own.
You build, we back you up
For teams with someone who likes data
Sign up free and build with the assistant, the CLI or MCP. Bring us in for a source nobody has an API for, a migration, a model that needs checking or a second pair of eyes.
The work is broader than dashboards
What our team has taken on for customers this year. Examples are described, not named.
The whole data foundation
A consumer brand's data engineer had left. We reviewed their warehouse, modeled the data inside it, and built sales, customer profitability and production cost dashboards their team now reviews every week.
Systems with no API
An on-premise ERP and an older CRM at a manufacturer. A property system that only sends a daily report. Point-of-sale and restaurant accounting feeds. We build the pipeline and check the numbers against the source before anyone relies on them.
Moves off the old reporting tool
We have rebuilt reporting that lived in Zoho Analytics, Tableau and Omni, and we are midway through a move off Looker. Show us the old dashboards on a recorded call and we rebuild what your team actually uses.
Data that doesn't agree
Engagements in the CRM that don't match invoices in the books. Duplicate and half-filled records. We find the gaps, map the systems to each other and give your team a queue to clean up the rest.
Tools people work from
A weekly sales review that replaced a folder of screenshots. A call list for reps with buttons that log the call. A staff planning model. A queue where one click runs the CRM function you already wrote.
Custom applications
When a dashboard isn't enough, we build the application around it: client and partner portals, intake and approval workflows, and internal tools shaped around how your team works and what it's trying to hit.
Reports and alerts that arrive on their own
A daily Slack post with the charts and a short read for a media-buying team. Scheduled emails for the people who never open the app. An alert when a number crosses the line you set.
An analyst on call
Weekly check-ins or open office hours. Bring a question, a new report or a number that looks wrong. We work through it together and agree what needs follow-up. Some teams have kept this going for months.
Training and handoff
We train the people who open the dashboards, the ones who ask in Slack, and the analyst or consultant who wants to build in the terminal with the same tools our team uses.
How a build usually runs
- 01
Data sync call
30 minutes
We connect a tool or two, look at a slice of your real data and agree what done looks like: which systems, which dashboards or tools, who uses them.
- 02
The build
Usually two to four weeks
A first version often shows up in the first week or two. A focused setup reaches a stable base in about three weeks. More systems, more locations or a migration take longer, and we say so on the first call.
- 03
Review and fine tuning
Weekly, sometimes more
You react on short calls. We make the quick changes on the call and the rest soon after, then train the people who will use it.
- 04
Keeping it right
As long as you need
A monthly plan runs the syncs, questions and automations. New builds are scoped to a spec. Ongoing changes and check-ins are hourly or agreed up front.
How we price the work
Some work is easiest to agree up front. Some is easier to run by the hour. We pick with you on the first call, and you always know which one you're on before we start.
Scoped to a spec
When the outcome is clear
We write down what gets built and agree a fixed price for it.
- A setup build and the first dashboards
- A new data source or a migration
- A custom application or workflow tool
Hourly
When the work is ongoing or still taking shape
We track the time and you see what it went to.
- Changes and new reports after launch
- Analyst time on questions and odd numbers
- Exploratory work before a spec makes sense
Your Cerebro plan
Always, once you're running
The monthly plan runs the syncs, questions, dashboards and automations.
- Self-serve building with the assistant
- Scheduled reports, alerts and embeds
- Plans and credits on the pricing page
You react. We fix it while you watch.
A review call is a few people from your side, each with an ask or two. Margin by product line. Budget next to actual. A view of the next thirteen weeks. We triage live, make the quick changes during the call and finish the rest soon after.
Between calls your team can edit dashboards themselves, by asking. Every change is saved as a version, so a bad edit can be rolled back.
- Every change is saved as a version
- The SQL behind each tile stays visible
- Your people learn the tool while we build
Dashboard assistant
- Read the sales lines and the budget sheet
- New tile · margin by product line, trailing 4 weeks
- Budget column added to 3 tiles
- Totals checked against the source
Version history
- Current
Added margin by product line and budget columns
Cerebro · Just now
- Restore
Moved the 13-week view to the top
Ops lead · Yesterday
- Restore
Review call: 4 tiles changed
Cerebro · Tue
Working with a consultant or agency?
Zoho partners, CRM consultancies and sales-ops firms run their client work on Cerebro. They keep the relationship and whatever part of the build they want. We take the data work, a first version or a defined piece of the project, and their consultants build next to us with the same CLI and MCP access our own team uses.
The client gets live dashboards with no login. The consultant gets the hard data work off their plate.
What it's like to work with us
“The way you guys think about things has been worth every penny I've paid you, even if your app wasn't so cool.”
“Cerebro has been super helpful. The data engineering work they've done for a lot of our biggest customers has given them the dashboards of their dreams.”
Peter FullerFounder, The Workflow Academy“We've made more progress with you in the last 30 days than in the last several months.”
“It's more than a solution, it's almost a service. If you take care of the data ingestion and ETL, or work hand in hand with us on some of it, it's more about a relationship than a solution.”
“Not only does Chase come back with it resolved, he says, hey, I added this new feature to the dashboard too.”
“Everything in there is what we've been screenshotting for our weekly one-on-ones. It's going to drastically improve the meeting and cut the time spent putting it together.”
Questions before you start
Can you just do all of it?
Yes. Some customers have us build and maintain everything, from the pipelines to the dashboards to the weekly review. We still need someone on your side who can explain the business and check the numbers.
Do we need a data person on staff?
No. That is often why teams call us. If you do have one, we take the parts they don't have time for and they own the rest.
Do we have to start with a build?
No. Sign up free, connect a source and build with the assistant yourself. Bring us in later for a hard source, a migration or a dashboard for a whole department.
How long does it take?
A first version usually shows up within a couple of weeks. A focused setup takes about three weeks to reach a stable base. Several systems, many locations or a migration take longer. We give you a timeline after the data sync call.
What if our system has no API?
We have connected on-premise ERPs, older CRMs and systems that only email a report or export files. If it is a database behind an app you own, we can read it in place. We confirm what's possible before we scope it.
Who owns the dashboards and the data?
You do. Everything lives in your organization, and the SQL behind every tile is visible. Larger rollouts can keep the warehouse in your own cloud account.
We already have a consultant or agency. Does that work?
Yes. Zoho partners, CRM consultancies and sales-ops firms run client work on Cerebro. They keep the relationship and whatever part of the build they want. We take the data work, or a defined piece of the project.
How is it priced?
It depends on the work. When the outcome is clear, like a setup build, a new data source, a migration or a custom application, we write a spec and agree a fixed price. Ongoing changes, analyst time and exploratory work are billed hourly. Either way you're on a monthly plan for the platform, and we agree which applies before we start.
Start with a 30-minute data sync call
We connect a tool or two, look at your real data and agree what you want built and who does what. You decide from there.
Prefer to try it first? Sign up free and build your first dashboard today.