CAT Consultores
For eleven years we have been building dashboards, integrations and custom systems. And in eleven years nobody ever called us because they wanted a dashboard: they called because they needed to know something in time, to stop losing money or to stop doing something by hand. That is what we deliver, and we call it Results as a Service: the tool is the means, not the product.
The day a dashboard is handed over, the client has not gained anything yet. They gain on Monday morning, when someone looks at a number that did not exist before and changes a decision. That Monday is the product. Everything else, the data model, the measures, the integration, the server, the maintenance, is the factory: necessary, invisible and ours.
A model where what you contract is not a tool or a project with a closing date, but a concrete business result, sustained over time. Choosing the technology, building it, running it and keeping it alive stays on our side.
In Spanish we call it Resultados como Servicio. The acronym was coined by analogy with SaaS, PaaS and IaaS, the “as a service” family of the software world, and it moves the point of sale one step up: from the program to the effect of the program.
SaaS rents you the car. Classic consulting builds it to measure and hands you the keys. RaaS drives you to the destination.
Between raw data and the number you can use there are six stretches of work. The only thing that changes from one model to the next is how many the provider does and how many you end up doing.
We take on the whole chain and on keeping it working next month. What reaches you is the number ready to use, not the task of producing it.
| SaaSSoftware as a service | Classic consultingProject with a date | RaaSResults as a service | |
|---|---|---|---|
| What you contract | Access to software that already exists | Hours of a specialist | A concrete business result |
| What reaches you | A username and a password | A deliverable and a report | A number that moves, not a deliverable that gets filed |
| Who does the work | You and your team, every day | The consultant, while the project lasts | We do, continuously |
| When it ends | When you stop paying the licence | On delivery day | It does not end: it holds and adjusts |
| If it does not work | It is “an adoption problem”. Yours. | It was delivered and closed. You hire again. | Nobody calls it closed |
| What gets measured | Active users, licence usage | That the project ships on time | That the original question has an answer without you asking for it |
| What it is like | Renting the machine | Commissioning the build | Contracting the outcome of the build |
The industry changes, the size changes, the technology changes. The result being sought, almost never.
One number per question, the same for everyone, updated without anyone building it by hand.
Work that one person does every day today and nobody does tomorrow, because it is already done.
Commercial decisions made with the margin in sight, and your own channels that do not depend on somebody else’s platform.
It runs in your browser, on sample data. Move a filter and the numbers, the series and the alerts recalculate. That is how a result arrives when it is done well: you do not have to ask for it, or wait for someone to build it.
Period
Region
Segment
RaaS does not remove the technical work: it moves it. Not seeing it does not mean it is not there, so here it is in writing. It does not matter where your numbers live today, a spreadsheet on OneDrive, a legacy ERP, the ecommerce API or last week’s campaign: they get ordered, related and turned into a single truth.
Data sources we integrate
Custom development stack
In a project, the last phase is delivery. Here the last phase is the one that never ends: it is the one that turns a delivered tool into a result that holds.
What the business needs to be able to answer, and who will use that answer to decide.
Where that number comes from today. Quality, frequency, access, cleanliness.
The model, the dashboard, the integration, the screen. Whatever it takes.
In the hands of whoever decides, with the team trained to read it alone.
The business changes and the tool changes with it. There is no final handover here.
A new category is useful if it clarifies. If it also over-promises, it stops being useful.
If the product was already built and the only new thing is the brochure, that is SaaS with marketing. Here the result is defined first and only then is the tool chosen. Sometimes the tool already exists and nothing needs building: that is a valid answer too.
The decision still belongs to the people who know the business. We take on giving them something to decide with, and training them so they do not depend on us to read it.
Some jobs are a closed project and it is perfectly fine that they are: a website, a migration, a one-off development. When that is the case we say so and work it as a project, without dressing it up as something else.
You do not need to know which tool solves it, or whether one is needed at all. That part is ours.