Which engagement you actually need
The three options above are not tiers of the same thing. They answer different questions, and picking the wrong one wastes money in both directions — a retainer where a two-hour review would have done, or a review where the real problem is that nobody owns the technical direction at all.
Fractional CTO for startups
The case for a fractional CTO is simple: the decisions that determine whether a data or AI product survives contact with scale are made in the first few months, usually by whoever is available rather than whoever is qualified. Which parts of the stack you buy instead of build, what the data model has to support two years out, whether an LLM feature can be run at a unit cost that works — these are expensive to revisit and cheap to get right early.
I take that ownership on a monthly retainer: in the leadership conversations, accountable for architecture and spend, running the technical screens for your first engineering hires, and available to your investors during diligence. It is the right call when you have product-market signal and a technical risk you cannot name precisely, and the wrong call when you already have a strong senior engineer who just needs a sounding board — that is the consulting engagement below, at a fraction of the commitment.
Consulting for enterprise teams
Enterprise work arrives as a decision with a deadline attached. A cloud bill that grew faster than the data behind it. A migration that turned out to be larger than the tool promised. A pipeline failing quietly and surfacing three dashboards downstream. A warehouse nobody trusts the numbers in. An AI pilot that works in a notebook and nowhere else.
These engagements are bounded on purpose, and they scale from a single call to a multi-month advisory relationship. On cloud and pipeline cost, I work the levers in order of what they return — how much data each run touches before how many workers it has — and you can size your own exposure first with the AWS Glue cost calculator or read the reasoning in the Glue cost optimization guide. On migrations, the risk is almost never the rows: AWS DMS moves those, but not stored procedures, triggers, secondary indexes, foreign keys or sequences, and not a table without a primary key. That second list is usually most of the project and is usually found late — the DMS pre-flight check sizes it before you commit to a date. Redshift, Snowflake and BigQuery moves, and the legacy Sybase and SQL Server estates behind them, are covered across the case studies at tier-1 bank scale.
Technical team lead for one-off projects
Funded project, capable engineers, and no one senior enough to hold the whole thing. This is the gap that turns a three-month build into a nine-month one, and it rarely shows up in a status report until the date is already gone.
I embed for the life of the project: scope broken into milestones with real dependencies, day-to-day coordination across engineers, vendors and stakeholders, and hands-on work on the parts that are genuinely hard. Dagster, dbt and Airflow orchestration, Python ingestion at volume, Docker and CI/CD so a deploy stops being an event — the unglamorous parts are what decide whether it holds up, and my approach to each is in the ETL pipeline guide. The engagement ends with a documented handover, because the objective is your team owning it, not a dependency on me.
How an engagement usually starts
Almost always with a call and something concrete you already have — a bill, a deadline, a board question, or a pipeline that failed last week. I will tell you on that call which of the three above fits, whether it is a three-day job or a three-month one, and if it is something your team can handle without me I will say so. Scope, milestones and price are then fixed in writing before any work begins.
What does an engagement cost?
It depends entirely on scope, and I would rather quote accurately than publish a number that is wrong for your situation. A one-off architecture review, a fractional CTO retainer and a three-month embedded delivery lead are three different commitments with three different price structures. Tell me what you are trying to decide or ship and I will come back with a fixed scope, milestones and a figure in writing — usually within two business days, at no cost.
What is the difference between the fractional CTO and consulting engagements?
A fractional CTO engagement is ongoing ownership: I am accountable for technical direction, I am in your leadership conversations, and I carry the decisions forward month over month. A consulting engagement is bounded: you have a specific question or project, I answer or deliver it, and it ends. Founders without a senior technical owner usually want the first. Teams that already have engineering leadership and need an independent read on one problem usually want the second.
Can we start with something small?
Yes, and most clients do. A single paid consultation or one contained deliverable lets you assess the quality of the thinking before committing to a retainer or a larger build. Several long-running engagements started as a two-hour architecture review.
How do you contract and invoice?
As an independent B2B supplier on a straightforward services agreement: fixed scope with milestones, invoiced per deliverable, stage or month depending on the engagement type. I work with companies in any jurisdiction and bill in your preferred major currency by bank transfer.
Who owns the code and the IP?
You do. On delivery and final payment, all code, pipelines, infrastructure and documentation are yours, with a clean handover so your team can run and extend them without me.
How much of your time does a retainer actually get?
Fractional does not mean occasional. A retainer is a committed block of days per month with agreed availability for calls and escalations, set so that decisions are not waiting on me. I deliberately keep the number of concurrent retainers low — if I cannot give an engagement the attention it needs, I will say so rather than take it.
What kind of work do you turn down?
Staff-augmentation seats where the work is interchangeable with a job req, projects where the technical decision has already been made and the brief is really for validation, and anything where there is no path to my team-side counterpart owning the result. Clear scope and a real decision to influence are what make these engagements worth both our time.