I start from the business model, not the tech stack. Then I build the smallest thing that moves it forward — and grow it from there.
Test an idea or fix one painful process — fast.
Replace spreadsheets, email chains and manual steps.
Connect the whole operation — web, mobile and the tools you already use.
Pull the point toward what matters most — quality, speed or complexity. Then nudge the budget and see what gets added or stripped away.
Drag the point, use the arrow keys, or tick what it needs to do.
In the estimate Added by budget Removed by budget
A playful estimator, not a quote. Real numbers follow the intake form.
Sites that bring people in, systems that run the operation, and products people choose to use every day.
A calm, dignified presence for the hardest week of someone's life — clear services, transparent pricing and a contact path that works at 3 a.m.
Read the caseThe beers, the taproom and what's pouring this week. Built so the brewers can update it between batches.
Read the caseClass levels, the weekly schedule and sign-ups — with the energy of a Saturday social.
Read the caseProduction batches, inventory, orders and customer relationships in one place — replacing a patchwork of spreadsheets.
Read the caseSomewhere between Airbnb and Couchsurfing: paid hosting with the warmth of staying with a local. Listings, bookings, payments and reviews.
Read the caseA day-planning tool I built to solve my own workflow problem — capture everything, then decide what actually gets done today.
Read the casePersonal development as a whole-life practice — habits, reflection and energy, tracked together instead of in five separate apps.
Read the caseWorking software every 1–2 weeks. Early builds have rough edges — on purpose. Your feedback shapes the next one.
Pick the quick 5-minute form or the deep 30-minute one. Your configurator result comes along.
One of three answers: let's talk, tell me more — or a referral to someone better suited.
Scope, milestones and a fixed price. The smallest version worth shipping, and what waits for Phase 2.
A working build every 1–2 weeks. You test for 48 hours, I iterate. No big reveal at the end.
Code, documentation and a walkthrough — or ongoing care, if you'd rather I keep it running.
I've worked on the business side — as an entrepreneur, and as a consultant helping small and mid-sized companies rethink how they work. At some point I stopped writing recommendations and started building the tools myself.
That's the difference. Before any code, I model how your business creates value — processes, people, data — and design the software around it. Then I ship it in small steps, with you, until it fits.
— full story & credentials coming soon