Tell me the idea, rough is fine. Within a week you're using a working prototype, built by the person you talked to. You find out what it should be before you've paid for what it shouldn't.
The person you talk to is the person who builds it.
You see it in week one, and again after every block.
Stop at the end of any block with something real in your hands.
Most software starts with a specification: pages of text describing the thing. But you're not picturing pages. You're picturing the thing itself, and the text never quite matches it. The gap shows up later, as another round of discovery or a build that misses, and you pay for it.
You'll know what you want when you see it. Almost everyone does. So we start with a prototype you can click, question, and change. It isn't the product yet. It's how we agree on what the product will be, after 28 years of watching the other way fail.
If a picture is worth a thousand words, a prototype is worth a thousand meetings.
Marketing, sales, operations, or just chaos: if it keeps you inside the business, it's worth a conversation.
The weekly report, the emails that follow the same five rules. That work runs on its own, and you read the result on Monday.
Or software that almost fits. You get a tool shaped like how your team actually works, and nobody asks who has the latest copy.
Click a working prototype in a week and change it until it's right, before you commit to anything. Something you can use in weeks, not months.
The figures you actually ask about, on one screen instead of in five tabs.
Different problems, different owners, different tools. Some are live, some are still in progress. The tools follow the problem, never the other way round.
Managing diabetes means juggling readings, meals, and doses across too many places, with no single clear picture.
One simple daily app, with its own brand and website, now in early beta testing.
Amateur pool is a big community with no home of its own. Players, pool rooms, cue makers and coaches are scattered across paper score sheets and separate apps.
A social site dedicated to amateur players, the broader pool community, and the people and businesses that serve it. Players get a page of their own, a practice log, and a league record read from a photo of the score sheet.
bartablebilliards.com ↗Bank and kick shots rely on diamond systems that are hard to picture and harder to practice.
Pick a system, place the balls, and get a clear aiming diagram with the predicted path and a plain-language explanation. Shareable by link, no account needed.
bartablebilliards.com/table ↗Stacks of scanned paper that nobody can search, sort, or act on in time.
A system that reads every document, files it correctly, makes it findable, and flags what needs action and when. It runs privately on local hardware.
AI coding agents move fast, but they can say they're done when they're not, and nothing holds them accountable.
A governance layer that makes agents trustworthy inside a real codebase: they must prove the work is finished, know what they may do without asking, and the process only ever gets stricter.
A website for an independent distributor that has stocked bearings, hydraulics and power transmission parts since 1989. Product lines, the manufacturer line card, and both branches one phone call away.
torkproducts.com ↗The site you're reading, plus the branding kit behind it: logo, color palette, and type system, built to work together on screen and in print.
autonomicllc.com ↗A website for a fiduciary wealth management firm. Services for families and business owners, plain answers to common questions, and a direct path to booking a consultation.
davimanfinancial.com ↗A website for a third-party administrator that designs and manages retirement plans for employers in all 50 states. Plan types explained plainly, with portal access for clients and participants.
front9admin.com ↗Bring the idea as messy as it is. We find the one problem worth solving first, then put what we agreed in writing before any work begins.
Within a week, a prototype you can click, react to, and change until it matches what you pictured. For automations, a flow diagram we walk through together.
The real thing gets built in the open, in short blocks, so you see progress, not status reports. Then it's tested, documented, handed over, and running, and it keeps improving from real feedback.
Focused sprints with a clear start and finish. Momentum is how good software gets built, so I protect it.
Week one asks something of you: an hour or two a day, so feedback is fast and decisions get made while they're still cheap. In return, you never wonder where your project is. You saw it yesterday. A shared picture, a steady rhythm, no scramble.
The work is based on the prototype, and each block stands on its own. You can stop at the end of any block with something real in your hands.
You're busy running the business, so you shouldn't have to manage a project too. I've built software for 28 years, and I'm the one who hears the problem, joins the calls, and writes the code.
Sweetwater Sound · Acquia · Vera Bradley · Cooper-Standard Automotive · Traction AG · RCA / Thomson Consumer Electronics · Eli Lilly · NCAA
More than half my career was as a consultant, so many of these clients won't appear on my LinkedIn profile. The consultancies I worked through will. Happy to talk through any of it on a call.
Describe your idea, as best you can, and the budget you're working with. We'll talk it through: the real problem, what it needs to do, and whether it fits. If it does, we sign a short agreement and I start your prototype. If it doesn't, I'll say so, and show you what the budget does buy.
I reply within a day.