Build the Boring Stuff First. That’s How You Scale.
- May 6
- 2 min read
By Rick Elmore
Most founders chase growth before they build the foundation to support it. I did the same thing early on—and it almost broke my business.
I’m the founder of Simply Noted, a handwritten mail company powered by custom-built robotics and software. Today, we’ve processed millions of pieces of mail and built one of the largest fleets of handwriting robots in the world. But none of that happened because we got great at sales first. It happened because we got serious about infrastructure.
In the early days, like most founders, I focused on revenue. Close more deals. Bring in more customers. Say yes to everything. But as demand increased, cracks started to show. Orders got messy. Fulfillment slowed down. Quality became inconsistent. I found myself manually checking work just to maintain standards.
That’s when I realized something most founders learn too late: growth doesn’t expose your strengths—it exposes your weaknesses.
We didn’t need more customers. We needed better systems.
So we stopped chasing growth and started building what I now call “the boring stuff”—the operational backbone that actually makes scale possible.
First, we rebuilt our production systems from the ground up. Instead of hiring more people to keep up with demand, we focused on increasing throughput. We engineered workflows and machines that could handle 10x the volume without requiring 10x the headcount. That meant designing processes that ran consistently, predictably, and without constant human intervention.
Second, we implemented quality control that didn’t rely on me. If your business depends on the founder to maintain standards, it’s not scalable. We introduced automated checks, camera systems, and redundancies so quality became part of the system—not a manual task.
Third, we focused heavily on data. Most businesses operate reactively. They fix problems after they happen. We wanted to see problems before they hit. By tracking production, delivery, and engagement data, we could identify bottlenecks early and fix them before they impacted customers.
None of this was exciting. None of it felt like “growth.”
But it was the reason we were able to grow.
The biggest mistake I see founders make is trying to scale output without understanding throughput. Output is how much you can produce today. Throughput is how much you can produce consistently, at scale, without breaking your systems or your team.
If your operations can’t handle growth, growth becomes the problem.
Looking back, there are a few principles I’d share with any founder trying to scale:
Build your business as if you won’t be there to run it. If something only works because you’re involved, it’s a liability.
Document everything. What feels obvious in your head becomes chaos when you try to delegate it.
Automate what repeats. If you do something more than a few times, it should become a system.
And most importantly, fix small problems early. Messy data, manual workflows, unclear ownership—these seem minor at first. But at scale, they become the things that stall or kill your growth.
Scaling isn’t about doing more. It’s about building systems that allow more to happen without you.
That’s the boring part.
And that’s the part that actually works.
Connect With Rick
Comments