About
It started as somebody's spreadsheet
MaverStudio was built for a five location academy network that was already doing this work by hand, once a month, from exports. The software is that job, done properly and done daily.
Why it exists
The question nobody could answer
An operator with five gyms can tell you what they spent on ads last month, and can tell you how many members they have. What no system would tell them is whether the campaign that produced the most leads produced any members who were still training a year later.
The data existed. It was in two places, in five accounts, behind five logins, and joining it meant a morning with a spreadsheet and a tolerance for approximation. So the answer arrived late, arrived rough, and mostly did not arrive.
MaverStudio does that join continuously, keeps the grain fine enough to act on, and then carries on past the sale into whether those members actually stay. That is the whole idea, and everything in the product is downstream of it.
How we build it
Four rules we do not bend
These are the reasons the product looks the way it does, including the parts that would be easier to sell if we broke them.
A number you cannot audit is not an answer
Every figure in the product can be opened until you reach the rows underneath it: the touchpoints, the check-ins, the cost entries, the sync that brought them in and when it last ran.
The thresholds belong to the operator
What counts as at risk, what counts as a stale lead, what counts as enough spend to judge a campaign. These are your calls about your business, so they are settings rather than constants we chose.
No metric that only flatters
If a channel has costs we cannot see, we say so rather than showing it as free. If a lead cannot be traced, it is reported as untraced rather than assigned to whatever campaign was running.
One product, not a tier ladder
Everyone runs the same code. Charging more for a checkbox creates a maintenance burden for us and a worse product for you.
How we work
Small, and direct about it
This is a small operation. The person who answers your email is the person who changes the software, which is the main reason a threshold you need can be a settings row rather than a roadmap item.
It also means we are careful about who we take on. A network we cannot set up properly is worse for both of us than a network we turned down.
Where your data lives
Your organization’s data sits in its own tenant, on infrastructure we operate, and is never pooled with another customer’s for reporting or for anything else.
Provider credentials are encrypted at rest and never displayed back, to you or to us. Anything a member of our team does that touches a customer account is written to an audit log that cannot be edited from inside the product.
Everything in your account exports as CSV, from inside the product, without asking us for it.
Come and ask us something hard
We would rather answer a sceptical question now than a disappointed one after setup.