Shape the product
Turn messy operating needs into a clear path through the software, with enough detail that the team can make confident decisions.
About Ben
I’m Ben Miller: a husband, dad, and technical director shaped by a lifetime in customer service. I help turn complicated operating realities into software that people can understand, trust, and keep improving.
Why I make room for the hard work
Building dependable software is meaningful because it supports a life I care deeply about: the people I love, the time we have together, and the kind of example I want to set for my kids.
How I show up
That can mean defining a product workflow with the people who use it, shaping the interface so it has a clear point of view, or working through the technical architecture that makes it durable in production.
At Modern McGuire Productions, I lead work across a multi-tenant platform: customer-facing tools, operational systems, integrations, content publishing, and the data that helps teams understand what happened. It is one place I get to stay close enough to the details to make good decisions without losing sight of the person on the other side of the screen.
My favorite problems have a little ambiguity in them. The constraints are real, the workflow has exceptions, and the answer is not just “add another screen.” Those are the moments where careful product thinking and practical engineering make each other better.
The long way into software
Before I worked in software, I spent years in customer-facing jobs: making smoothies and training new people at Jamba Juice, working reception at H&R Block, and taking temporary work wherever it was available. Those jobs taught me that people rarely arrive with a clean, well-formed problem. They arrive busy, frustrated, and hoping someone can make the next step feel possible.
I took an unconventional route through school too: public school, independent study, and community college while I was still in high school. Afterward, I attended the California Regional Fire Academy and graduated at the top of my class. I decided firefighting was not the path for me because I was not interested in becoming a paramedic. I just wanted to fight fires.
In a strange way, that is still what I do. My first development-adjacent job was manually entering 200 business cards from faxed conference scans into a CRM for a life-insurance company.
I was handed 200 faxed business cards to enter into a CRM. I reached for automation instead.
I started with browser automation and iMacros. That small experiment led to internal tools, then six years growing into an IT Manager role.
Later, I left a comfortable job—and took a pay cut—to become a junior web developer at a Sacramento agency. It was a hard year, but it gave me the foundation to grow quickly. When my wife and I found out we were expecting our first child, I got much clearer about the kind of work and life I wanted to build. Starting a business was scary, but it was the right answer: solve difficult problems for business owners in a way that genuinely helps them. Solve the problem; worry about the money later.
Where that shows up
Turn messy operating needs into a clear path through the software, with enough detail that the team can make confident decisions.
Design the application boundaries, integrations, data flows, and delivery paths that let new capability hold up in production.
Make the place people actually work feel clear, approachable, and honest about what is happening behind the scenes.
Currently
Get in touch
I occasionally take on carefully scoped contract work when there’s a strong fit.
GitHub