A year ago, I couldn't have built any of this.
Not because of lack of coding skills. Not because the ideas were missing. I've spent decades in systems and manufacturing. My wife's career is in healthcare strategy. We've always understood the problems. We just couldn't build the solutions. Not at the speed or scope that mattered. The gap between seeing a problem clearly and shipping software to solve it required teams, timelines, and capital we didn't have.
That gap is closing.
AI tooling didn't make me a better thinker. It made me a faster builder. The domain knowledge was already there — years on shop floors, in compliance reviews, in conversations with operators who know exactly what's broken but can't get anyone to fix it. What changed is that the distance between understanding a problem and shipping a working system collapsed. Dramatically.
So I started building.
The work
JAWS runs production at a real bindery in Kent, WA — job tracking, estimation, scheduling. Not a demo. The system that runs the shop. LedgerOps made sense of messy financial exports until JAWS grew enough to absorb it. That's not a failure — that's how real tools evolve when the builder is also the operator.
WeavePulse came from watching healthcare nonprofits drown in federal reporting. I'm not running a nonprofit, but I understand the compliance burden well enough to know that the tools available to them are either inadequate or unaffordable. So we built the thing that should exist.
LumenHealth maps how AI is reshaping clinical careers — because someone needs to, and the people closest to the problem are too busy living it to build the resource. AeroEd started as a collaboration with a high school student who wanted to work in aerospace and couldn't find a straight answer about how to get there. It's now 741 pages of career guidance, company intelligence, and flight school data. A teenager saw the gap. We had the tools to fill it.
Appeal Packet Builder turns health plan denials into submission-ready appeal packets. DropCert creates proof-of-mailing certification for regulated print. csvops is an open-source CLI for inspecting CSV files because every operational workflow eventually produces one that someone needs to make sense of.
None of these required a team of twenty. None required venture funding. None required permission.
What I've learned
The constraint was never ideas. People who work inside a domain — any domain — see dozens of problems worth solving. The constraint was the build. And for millions of people right now, that constraint is evaporating.
This isn't about AI replacing expertise. It's the opposite. AI is useless without someone who knows what to build and why. The person who's stood on the shop floor, sat through the compliance review, fought the claims denial — that person now has the tools to ship a solution. Not a slide deck. Not a requirements doc. Working software.
That's what Plyworks is. Not an agency. Not a consultancy. A builder's workshop where domain knowledge meets modern tooling. Some of what we build, we operate ourselves. Some of it we're pushing toward product. All of it comes from standing close enough to the problem that we can't look away.
I'm one of millions of people undergoing this transformation. Some are further along. Some are just starting. The ones who will build things that matter are the ones with judgment — who understand not just what's possible, but what's worth building. Who can tell the difference between a tool that solves a real problem and a demo that impresses at a conference.
If that's you, we should talk. Not because I have answers. Because this is more interesting done together.