Fractional CTO who works forward-deployed: embedded in your team, on the tools, shipping with you.

The no-nonsense CTO who gets software shipped and products made real.

The no-nonsense CTO who gets software shipped and products made real.

I'm Norman Holz. I take messy ideas, stalled projects, and AI prototypes and drive them to production, with architecture, hands-on code, and shipping discipline in one seat. Part fractional CTO, part forward-deployed engineer: I turn vision into a technical plan and stay on the tools until it crosses the final mile.

Clear decisions, solid systems, teams that deliver.

Request an intro call
Warrior in the Garden

Warrior in the Garden

Astronaut in the Ocean

Astronaut in the Ocean

Caveman in a Modern City

Caveman in a Modern City

Fractional Realities generated by Nano Banana Pro 2

You know the pain.

The prototype got you 80% there

AI tools, no-code platforms, or a fast freelancer proved the shape of the idea. But it's not ready for real customers, and the last 20% is the hard part.

The handoff is messy

The agency, contractor, or internal team left behind unclear architecture, brittle code, missing context, and a roadmap nobody fully trusts.

Vendor Proposals are hard to judge

Agencies and freelancers promise a lot. Some proposals are worth it. Some bundle in work you pay for but do not need yet.

Dev teams have no direction

Your developers are talented, but nobody's connecting their work to actual business outcomes. Features ship. Value doesn't. And nobody's asking why morale is tanking.

Tech debt is eating you alive

Every new feature takes twice as long as the last. Your codebase is a house of cards and everyone's afraid to touch it.

The questions are getting expensive

Investors, customers, and your own team are asking technical questions that need real product, architecture, and delivery judgment, not a guess.

Easy to work with.

01
30-minute call
We talk
You tell me what's broken, what's ambitious, what keeps you up at night. I listen. Then I ask the questions you haven't thought to answer.
02
Day one
I embed
I join your team's tools, meetings, and channels. Slack, GitHub, Jira, whatever you use. No onboarding theater. I work when you work.
03
Weeks, not quarters
We ship
Decisions get made. Architecture gets built. Your team moves faster. You see real results in weeks, not slides in quarterly reviews.

Two ways to start.

Low-commitment ways in before any retainer. Get value fast, then decide if you want me around longer.

~2 days

Product Rescue Check

A direct diagnosis of what is stuck and what is worth saving. You walk away with a clear recommendation: repair, rebuild, or a sharper product cut.

2-6 weeks

Release Sprint

A focused push to turn a stuck project, AI prototype, or urgent product release into something demoable, fundable, sellable, or production-ready. Paid and scoped up front.

One retainer, full coverage.

The Forward-Deployed CTO Retainer: weekly CTO leadership across product direction, architecture, vendor decisions, team cadence, and the work it takes to get software shipped. Flat monthly, scoped to your situation, easy to stop if it stops being useful.

~2 days/week

Advisory

Steady technical judgment without full immersion. Product calls, architecture reviews, vendor decisions, and a filter on the expensive questions.

~4 days/week

Embedded

I work inside your team. Hands-on architecture, code reviews, sprint cadence, and direct execution. For when the build is stuck and someone has to get software out the door.

Monthly retainer. Cancel anytime. No notice period.

Who I work best with.

  • You're early-stage, scaling, or building software in a company where tech is not the core business
  • You need CTO-level expertise and judgement without adding a permanent role
  • Your dev team is small, new, or held together with agency contracts
  • You're hiring senior engineers and the cost of a bad hire is high
  • You've got a promising prototype or demo that needs to become software real customers can actually use

Recent writing.

Notes on AI strategy, technical leadership, and the human side of software teams.

Read all articles

Your move.

Send the facts as they are: what exists, where it hurts, which constraints matter, and what you want to use an intro call for.