Reduce headache? — A bit of context.
Guided by core missions, founders are constantly solving problems. Once funding hits, those core missions become susceptible to shiny object syndrome. Suddenly, every new tool looks like a solution to optimize operations just a bit more.
A new CRM, a bit more automation, perfectly-designed dashboards. You blink, and suddenly your life's mission is being run by a Rube Goldberg machine nobody actually knows how to use.
The cost isn't the monthly software bill.
It's the hours your team spends navigating overlapping systems. The friction in your workflows. The momentum lost in maintenance.
It's the quiet defeat, this is just how startups are.
What if it doesn't have to be this way?
I design underengineered systems—lean, intuitive frameworks that grow with you, not against you.
We start by stripping your operations down to their essentials. Then, we rebuild with intention, using only what drives clarity, speed, and alignment across your team.
Your company starts moving again.
Freed from the shackles of the Rube Goldberg machine, your team spends time building towards the mission, not endlessly wrangling their tools back into place.
Your systems finally feel like they were built for you, not forced on you.
It's time to cut the noise.
If your workspace feels bloated, confusing, just plain overcomplicated, or your team feels bogged down, it's time to find the signal hiding in the static.
I'll help you re-engineer your setup around what actually matters: the mission that brought you here in the first place.
Reach out
Let's simplify your systems before they slow you down.
FAQs
What do you mean by underengineered systems?
It means stripping away unnecessary tools and automations to lean, intuitive systems that serve your core business functions—nothing more, nothing less.
What kinds of tools do you work with?
The ones you're using: Airtable, Notion, Zapier, Google Workspace, and other modern SaaS platforms. That said, the focus isn't on specific software, it's on how your systems work together.
Are you just cleaning things up, or rebuilding from scratch?
Usually, it's both. I work with your team to audit what you have, decide what's worth keeping, and rebuild the rest around simpler, more functional frameworks.
How do you decide what to keep and what to cut?
Working directly with your team to understand what's actually used, what's ignored, and what's slowing people down. Data, workflows, and real habits drive the decisions, not assumptions.
My company is still small, do I need this yet?
Absolutely. Early-stage is the best time. Building lean, scalable systems before things have a chance to get messy saves time and money down the road.
Do you handle implementation, or just strategy?
Both. I design the framework, document the logic, and help your team implement it so it becomes part of your daily workflow—not another plan that sits on a shelf.
How long does a typical re-engineering take?
Depends on complexity and team size. For larger teams, I prefer working with you for a full quarter, but smaller teams can be as little as 6 weeks.
How do you measure success?
Less friction, fewer tools, faster workflows, and teams who actually enjoy the system. I often track time saved per task or reduction in redundant tools as benchmarks.
We just bought a ton of software. Can you work with that?
Absolutely. The goal isn’t to throw everything out—it's to make sure every tool you keep has a clear purpose and earns its place in your stack.
What's the first step?
Start with a short consult. We'll talk through your current setup, identify immediate friction points, and outline what a simplified system could look like for your team.