Advisory & fractional CTO
Most of this site is things I built. This page is the other half of the job — the architecture call, the build-vs-buy answer, the strategy that has to hold up in the room where it gets funded.
I spent nearly thirteen years as a CIO buying and defending enterprise technology, and the last decade inside vendors architecting and selling it. So I know how the case gets built — and which parts of it you should push on.
What I’m hired for
You need an architecture decision owned — and defended to people who don’t write code.
Architecture ownership, technology roadmap, build-vs-buy calls, and technical due diligence. Plus the translation layer: putting engineering reality in front of a board or an executive team in language that survives the follow-up questions.
The security strategy has to hold up in the room where it gets funded.
Zero Trust, SASE, CNAPP, and deception technology — architecture and strategy pitched at whatever altitude the room needs, CISO included. A decade spent as the bridge between security architecture and the executives who pay for it.
Your team is adopting AI coding tools and nobody owns the guardrails.
Multi-agent AI coding workflows running in production here, not in theory. Guardrails, review gates, and an adoption plan that lets a team move faster without giving up quality, review discipline, or control of its own IP. I have also watched a platform bet go wrong from the inside, which is the other half of what I bring to the conversation.
Sometimes the answer isn’t advice — someone just has to build the thing.
Production build capacity on Fastify, React, and Postgres, with working fluency in Python, PHP, and SQL. Self-hosted, documented, and handed over — the same way everything else in this workshop gets built.
How it’s structured
Every engagement is anchored to a real decision or a real deliverable — and it’s fine to start small and see whether the fit is right.
A standing architecture sounding board, quarterly planning, and someone on call for the decisions that matter.
Embedded technical leadership — architecture ownership, roadmap, hiring input, and AI-adoption governance.
Architecture review, security-posture review, and second-opinion calls when a decision is already on the table.
Full-stack development scoped by the hour or bid by deliverable, whichever fits the work better.
Your team in one room — an AI-governance briefing or a security architecture working session.
Board- or CISO-level, one topic, no ramp-up required. Built for the room it’s delivered in.
Rates are set per engagement based on scope, timeline, and travel. A detailed rate sheet goes out with the first conversation — ask for it here.
Background
I’ve also watched platforms die. I was inside a company built on the Apple ecosystem when that ecosystem contracted, through the pivot into Windows and healthcare, through the years multimedia and VR were going to change everything, and through the dot-com collapse that ended it. That’s the other thing I bring to an AI conversation: I know what being early and wrong actually costs.
Matt DisherFounder, Disher Solutions
How it starts
Thirty minutes, no charge. What’s the decision actually in front of you?
What “done” looks like, what it costs, and how long it takes — in writing.
Small first, if that’s the right fit. The work should earn the next month.
Tell me what’s in front of you and I’ll tell you how I’d approach it — and whether I’m the right person for it.