Three ways to work with me.

• You've outgrown the patchwork — tools, contractors, spreadsheets — and you need someone to own the lane.
• You have multiple things going on — or you don't yet know what you don't know — and you need someone who can figure it out and go build it.
• You want technical leadership that's in the work, not on top of it.

• Embed in your team — leadership meetings, Slack, tools, day-to-day decisions.
• Own the tech roadmap and prioritize what actually gets built.
• Build the highest-priority work myself, end-to-end — not just plan it.
• Pull in people across the org (sales, ops, support, the people doing the actual work) to ground my judgment in what's true.
• Evaluate vendors, CRMs, and AI implementations.
• Make hiring calls on technical roles.
• Translate between you and outside engineers, contractors, or agencies.

Monthly retainer. Most engagements run 6–12 months minimum — embedding takes time to compound, and a contractor-at-arm's-length relationship doesn't get me close enough to the org to do the work well. We start with a 2-week diagnostic to align on priorities before signing the retainer.

This isn't a board advisor role, and it isn't strategy-only. I'm in the code as much as I'm in the meetings — that's the whole point. If you want someone to nod at quarterly reviews and hand you a deck, hire someone else.

• You'd rather work with one person who owns it end-to-end than coordinate an agency.
• You have one specific thing that needs to ship, with a clear start and a clear end.
• The problem is defined enough that we can scope it, price it, and finish it on a timeline you can plan around.
• You need a partner who understands product, GTM, and change management — not just a developer who'll ship what you ask for.

• Build MVPs and client-facing web/mobile apps from zero.
• Build internal platforms — admin tools, automation pipelines, integrations.
• Connect the tools you already use — CRMs, e-commerce platforms, APIs — into something that actually works together.
• Implement AI workflows that actually do something useful (not chatbot theater).
• Run discovery, scope the work, and quote a fixed fee before we start.

Fixed-fee, fixed-scope. Most builds land between 1 and 6 months. Starts with a paid discovery sprint to scope the work — we both walk away from that with a real estimate and a real plan, or you take the discovery output and hire someone else.

This isn't ongoing leadership and it isn't staff augmentation. If your problem is bigger than a single project — multiple initiatives, moving targets, unknowns you can't yet name, or a tech function that needs an owner — that's Fractional CTO, not Build.

• You have a tech decision in front of you and want a second set of eyes before you commit.
• You're evaluating a CRM, a vendor, or a major platform migration.
• You're considering an AI initiative and want to know what's real and what's vendor pitch.
• You're doing tech due diligence on an acquisition or partnership.

• CRM and platform evaluations.
• AI strategy and implementation roadmaps.
• Tech due diligence for M&A or major partnerships.
• One-off architecture reviews.
• Strategic working sessions on specific decisions.

Hourly or sprint-based. A typical engagement is a single 60-minute call, a 1-week sprint with a written deliverable, or a 2-week deep-dive. No retainers, no commitment past the engagement.

This isn't ongoing fractional leadership. If you find yourself wanting me back every week, we should talk about converting to Fractional CTO.