Why Matterbeam

2 min read
Why Matterbeam
A way out

Data can be magical.

I've built companies on data. I've seen truly counter-intuitive results that changed everything with people empowered by evidence instead of gut feel or force of personality. I've seen what's considered "possible" change when you have the right insight. At Smarterer, my favorite moments were having conversations with people (often times with PhD's) that started with "what your talking about is impossible" progressing to "I never really thought about it that way" and followed by a complete change in what that person considered immutable or foundational.

But I've also seen the other side. The grind.

I've watched brilliant and creative people blocked, ignored, and wasted. Crazy ideas, cross-pollination across domains, genuinely new approaches all of them abandoned because getting the data was just too hard. I've watched the scar tissue form. People stop trying. They stay in their lane. They work with the wrong data because getting the right data was too painful. KPIs freeze. Models go stale. The ambition evaporates.

It's not your people. You're not doing it wrong. That next database, catalog or processing framework isn't going to fix it either.

I worked with remarkable people, using the latest tools, working incredibly hard but something was still wrong. I started calling it the splinter in my mind (from the Morpheus speech in the Matrix). Something always slightly out of phase. Islands of value, moments where it works, but the real promise of data always just out of reach. Like a mirage.

I've had a few big flashes of insight in my life. The root of Matterbeam was one of them.

We've been iterating on data infrastructure built around patterns and assumptions from the 1980s. We assume data lives in a place. We make choices about what it's useful for, lock those choices into rigid shapes and systems, and build everything else around them. The "nightly dump" to run analytics was a 1980s solution to a 1980s constraint. We now build entire companies around tens, hundreds or thousands of "nightly dumps". Each one a set of frozen choices made for a specific purpose, at a specific moment in time.

So every new business reality, every new technique, every new idea becomes weeks or months. Or a year. Or, most often, never.

The data space is noisy. Everyone promises the one system to finally reach the promised land. But that promise doesn't engage with reality. There's a law of "data physics", any system must make tradeoffs in how it represents information to optimize for some uses over others. There is no one system. There never will be.

The insight behind Matterbeam is simpler and more radical than another system: data should be a utility. A resource. Something you transform into information as reality changes, as needs change, as techniques change. Not locked into a shape chosen years ago for a purpose that no longer fits.

When you make that easy, genuinely easy, the shape of what's possible changes. People with hunches get to test them. New ideas don't die in a backlog. Migrations stop being death marches. The brilliant people you hired become empowered to do the brilliant things you hired them for.

That's why Matterbeam exists. Not pipelines. Not infrastructure. To unleash what becomes possible when the people in your business can finally, actually, use the data.

Want to try it out? Give us some feedback? Create an account today.

Share This Post