A solo bespoke-software practice with 25+ years in the field.
My dad brought home a Sanyo computer when I was ten. Two five-and-a-quarter-inch floppy drives: DOS booted from one, BASIC ran from the other, everything in shades of green. I'd type a few lines of code and watch the screen draw back, and I made a game for my brother, my sister, and me. It clicked then, and it hasn't let go since.
Since that first program I've built software for public and private organizations of every size: 25+ years of professional development experience, across the medical, automotive, meetings, fintech, and edtech industries, and for the Departments of the Interior, Justice, and Energy.
Bespoke used to mean expensive, because the labor was. With AI in my workflow the math changes. I can deliver custom software at prices that, before, only bought off-the-shelf platforms, and finish in weeks where the old way took months.
I'm a maker at heart. Carpentry is my hobby, and the love of building with my hands is a big part of why I became a developer too. The rest of my time goes to board games and computer games with my family, and getting outside whenever I can.
Software should serve the person using it, not the other way around. Clarity beats cleverness, every time. Solopreneurs, small businesses, and medium businesses are the backbone of this country, and too often they're the last to get new technology. I want to change that.
I'm active in the local groups around here, and those relationships pay off for the people I work with. When a client needs help I can't provide myself, I can often introduce them to someone local I trust to deliver. Working with me reaches further than the code I write.
Simple code lasts longer. Simple screens get used. Simple explanations build trust. If I can solve your problem with a plainer approach, that is the approach I will recommend, even when something flashier would be more fun to build.
Bespoke means the software lives long after the build is done. I write code, choose tools, and shape data with the years after launch in mind, so the next person who touches it (often future me, sometimes future you) is not stuck untangling clever shortcuts from a sprint that ended ages ago.
I will tell you what you actually need, which is sometimes "do not hire me." If an off-the-shelf tool fits your problem, I will point you at it and shake your hand. The engagements that go well are the ones where the fit is real, so I would rather lose a project early than build something that does not earn its keep.
Tell you what you need to hear.
Bespoke work is a relationship, not a transaction. When the fit is right, I can shape an engagement around revenue share, payments over time, or other arrangements that match what the work is worth to you. The same posture that lets me say "you do not need a custom build" on a discovery call is the posture that lets me say "I will build this with you, and we will share in what it earns." Partnership is the lead frame, not a payment trick. Learn how I partner →
Book a call. I'll listen to what you're building, and tell you what I actually think.
Book a call