Jared Lukes. Start here

04 · Monthly · Fractional CTO

Someone on your side of the table for the technology.

I take the CTO seat part time. I decide what gets built, pick the dev shop and the software, manage them, and answer for the result. $3,500 a month for about two days a month, $6,500 for about a day a week, or $11,000 for about two days a week. Three months minimum, two years maximum. I hold two of these seats right now.

Sounds like you

“We pay a dev shop every month and nobody here can tell if the work is any good.”

“Every software decision lands on my desk and I am not a technology person.”

“A big customer sent a security questionnaire and I do not know how to answer it.”

“We need a CTO, but not a full-time one, and not yet.”

The problem

Your vendors are grading their own homework.

Without a technical lead, the dev shop decides what to build, the software vendor decides what you need, and you find out what it cost at the end. A full-time CTO in Minneapolis runs a median base near $324,000. A fractional seat puts someone on your side of every one of those decisions, for a fraction of that.

Who it is for

Companies with no CTO yet Owners managing a dev shop Founders before the first tech hire Teams after a CTO leaves

What you get

Decisions you can stand behind, and someone who answers for them.

In the seat now

Two CTO seats, running today. At Quartz Importers MN I designed and built a 49-workflow automation platform that has run 39,645 times at a 0.2 percent failure rate, and in about 30 days mapped the whole market the company sells into (case study). At U.S. Asset Appraisals I run the marketing technology and the AI rollout for a firm working in 35+ states. I picked every vendor in both.

The Quartz Importers knowledge graph
The Quartz Importers knowledge graph.
Workflows in production at Quartz Importers
Workflows in production at Quartz Importers.

How it works

Step 01

Talk it through

A 30-minute call. What you have, what it costs, and what keeps breaking.

Step 02

Read what you have

The first month is mostly listening: the code, the contracts, the vendors, the bills.

Step 03

Run the technology

The roadmap, the vendor calls, the build or buy decisions, the security basics.

Step 04

Hand it over

By two years at the latest, I help you hire a full-time owner and hand over a system they can run.

Questions

What does a fractional CTO seat cost?
$3,500 a month for about two days a month, $6,500 for about a day a week, or $11,000 for about two days a week. Cash, equity, or a mix on longer work. Nonprofits, co-ops, and arts groups can use the sliding scale.
Do you write the code yourself?
Sometimes, on a fixed-price build. The monthly seat is for deciding, choosing, and managing. Paying a CTO rate for routine development is a bad deal for you, so part of the job is finding people who do that work for less. Fixed-price builds are on the build page.
Can a fractional CTO replace our IT company?
No. The IT company keeps the computers, the network, and the accounts running. The CTO decides what the business should build or buy and makes sure every vendor, the IT company included, delivers what it owes you.
Is the CTO seat remote or on site?
I come to you anywhere in the Twin Cities for the kickoff, vendor reviews, and anything that goes better in a room. Remote works for everyone else.
What do we have when the engagement ends?
A written roadmap, vendor contracts in your name, the passwords and accounts in your hands, and a description of how everything fits together. Nothing should depend on me after I leave.
Do you also take AI or marketing seats?
Yes, same structure and same prices. I hold a Chief AI Officer seat today as well, and take CMO seats for the right brand. The title depends on what is missing.
How long does a fractional CTO seat last?
Three months at least, two years at most. Three months to read what you have and see whether the plan works; two years to get it running and hand it to a full-time owner. Why the two-year limit.
Can you save a software project that has run for years?
Sometimes, but usually I would rather wind it down. A system that has burned money for a decade is rarely worth bringing back. I find what still works, move the data somewhere it can live, end the contracts, and start the replacement on a two-year clock.

Before you hire this, people ask

Tell me what you pay for and what you get.

Bring the dev shop invoices. We will read them together.