About

Built in Northeast Ohio for businesses that make and do things.

Established industrial companies may have decades of operating experience, substantial equipment and several systems generating information every day—yet a question that crosses those systems can still take hours or days of spreadsheet work.

Why RBA exists

The problem is not that these companies do not understand their business.

The people who sell, purchase, schedule, make, install, service and bill the work carry context no system export can replace. The difficulty is that the records needed to test a question often sit across several systems and years of history.

RBA was founded by Julian and Aaron in Northeast Ohio to pair that operating knowledge with disciplined financial and operational analysis.

Access to the capability

Larger companies built teams for this.

Large organizations may employ data engineers, analytics engineers, BI developers, data architects, financial analysts, operations analysts and data scientists to connect records, define measures, build models and make the result useful.

RBA gives smaller and lower-middle-market operating companies another way to obtain much of the resulting analytical capability without assembling that entire organization internally.

DATA ENGINEERINGANALYTICAL MODELINGFINANCIAL ANALYSISOPERATIONS ANALYSISBI + REPORTINGAI + NATURAL LANGUAGEManaged financial + operational analytics

Our place in the work

We like technology.
We do not think the client should have to care about all of it.

The technical work can be demanding. The client conversation should remain about the business question, the evidence, the model and what the answer means.

How we think

Respect the operator.

The analytical system should extend operating knowledge, not perform around it. RBA works with the people who understand the business, makes reasoning reviewable and stays direct about what the records can and cannot support.

01

Respect experience

The people closest to the work hold context that no field name or algorithm can replace.

02

Show the reasoning

A result is stronger when a reviewer can follow it through the definition, calculation and records.

03

Build for the next question

Useful history, definitions and models should accumulate instead of disappearing after one report.

Start with the question

What are you trying to figure out?

You do not need a formal project plan. Tell us the question and what makes it difficult to answer today.

Tell us what you're trying to figure out Already a client? Open Client Portal ↗