I am this person, and the person who will do this work.
The Golden Thread is my practice — design, systems, and the applications that run on them, from one hand. You are not being introduced to a team you’ll never meet. The person who sits in the first conversation is the person who architects it, builds it, and is still there when something breaks at an awkward hour.
Three disciplines that were never separate.
Most people who can architect a database can’t design the interface that sits on top of it. Most people who can design the interface have never carried a system through a state audit. I’ve been doing all three at once for thirty years — the design shaping the architecture, the architecture shaping what the application could become — because in the work I’ve actually done, they were never separable.
Digital design first — interfaces, web, and the production work behind them. I’m a graphic designer of both digital and physical assets: full publication production, print media, and digital production, across the complete Adobe suite. Brand development and large-format print belong to the same practice, and the standard doesn’t change when the output does.
Data and application architecture across SQL and NoSQL, and the operational discipline around them — security, compliance, migration, incident command. A case-management platform I wrote has been in production since 2004.
The platforms themselves — built, directed, and run. Cloud practice management in daily production. A multi-tenant assessment platform carried through its full lifecycle, including a wind-down done properly.
This practice sits at the intersection of everything I’m inspired by: the graphic design, the system development, and now — through the service layer — actual application development. All three, one practice. This is what I’ve been reaching for my entire career.
What’s new is the practice, not the combination. The integration has been continuous — every system I’ve built was designed as well as architected, and every design I’ve made had to survive contact with real operations. What changed is that the work now has a name, a method, and a door you can walk through.
Which is the practical argument for hiring one person instead of three vendors: the sign, the site, and the system stop disagreeing with each other. Nobody is translating between them, because nobody has to.
And that progression is the method’s own shape. Design was the first chamber. The systems work was built outward from it, using it as structure; the application practice was built on both. Nothing was torn down to make room for what came next — each discipline is still load-bearing, still in use, still informing the turn after it. That is what a nautilus does, and it is why The Nautilus Method™ is named the way it is: I had been working this way for thirty years before I gave it a name, not the other way round.
One person, and a team made of something new.
For years I wrote my own sites in the plural — we, our team, the studio — because that is what everyone does and it makes a small practice sound safe. I’ve stopped. The plural was never the reassuring part; it just moved the accountability somewhere you couldn’t see it.
The team is real, though. It’s made of AI agents that I direct — and I am unusually comfortable in that space, because I have spent the last several years building with them rather than talking about them. I’ll tell you plainly where that line falls on your project: what I specified, what the agents built, what I verified before it shipped.
I use house-built tooling for speed. You never see it. This is not a DIY experience, and there are no skins to try on — you are not going to be handed an editor and wished luck. What you buy is work made for you, delivered quickly because the workshop behind it is already well-tooled.
How I work is public. The method has a name and its own page, the reasoning behind decisions gets written down as we go, and you’re entitled to ask why anything is the way it is. A practice that hides its method is usually protecting something other than you.
Lead with truth.
This is the one that governs the rest, so it’s worth saying plainly rather than leaving you to infer it.
It isn’t a slogan I adopted for business. It comes from my faith in Christ, and it is the same principle whether I’m reading a regulation, pricing a job, or telling a client something they’d rather not hear. I’d rather you know that up front than wonder later what I was optimizing for.
What it actually looks like in the work is unglamorous:
Everything on this site traces back to something real. When I couldn’t verify a number about my own work — an uptime figure, a compliance percentage — I took it off the page rather than let it stand because it flattered me.
Everything I do to make you easier to find is something I’d be comfortable explaining to your customers. Ranked is a game; referenceable is infrastructure.
If a direction is going to cost you, I’ll say so plainly — with the reasoning, not just the verdict. Then it’s your business and your call, and I’ll build what you decide. Saying it twice is nagging; not saying it at all is cowardice dressed up as service.
The method, or the receipts.
How an engagement actually unfolds — in turns, each one built on the last — is The Nautilus Method, and it’s a short read. If you’d rather see what I’ve built before you read about how I build it, the record is there too, with dates on it.