The invoice says: Technical leadership services, September. $15,000. Due on receipt.
That is the whole document. There is no breakdown, no days, no list of what happened. And you are not sure whether to be annoyed, because the work has been good and asking for detail feels like you are accusing someone of something.
You are not. Ask. But ask for the right thing, because the wrong version of this request makes the engagement worse, and there is a specific kind of detail that is worth having and a specific kind that quietly destroys what you are paying for.
Why the one-line invoice is normal, and why it is still not enough
A retainer is priced on availability and judgment, not on units of work. That is the point of it. The fractional CTO has reserved capacity for you, taken fewer other clients because of it, and will answer the phone on a Thursday when your database falls over. You are buying a standing claim on senior attention. A one-line invoice reflects that honestly, and a lot of good operators genuinely believe that itemising undermines the model.
They are half right. The invoice can stay simple. What cannot stay missing is the record of what the month contained, because without it three things happen.
You cannot tell whether the retainer is sized correctly, so you either quietly overpay for capacity you are not using or quietly consume capacity you are not paying for. You cannot defend the spend to a board or an investor who asks what $180,000 a year bought. And when the engagement ends, there is no trail of decisions and reasoning, which is exactly the asset you thought you were accumulating.
The fix is not a detailed invoice. It is a monthly note that sits alongside a simple invoice.
What a good monthly record contains
Five things. It should take the person twenty minutes to write, and if it takes longer than that, the month was disorganised in a way worth knowing about.
Days used against days contracted. Eight contracted, nine and a half used. One number, not a timesheet. This is the single most useful line because it tells you whether the arrangement is calibrated. Two or three months of consistent overage means you need a bigger retainer, not a bigger argument. Consistent underuse means you are paying for availability you are not converting, which is your problem to fix, not theirs.
The decisions made, with the reasoning in one line each. Chose Postgres over DynamoDB because the access patterns are relational and the team knows SQL. Deferred the Kubernetes migration another two quarters. Rejected the vendor's proposed architecture on the grounds that it locks us in at the data layer. Three to six of these in a normal month. This is the actual product you are buying, and it is the part that compounds.
What is in flight and what is blocked. Short. Two lines.
Anything that got worse. The honest operators put this in without being asked. Test coverage dropped, the on-call rotation is one person deep, the staging environment has diverged from production again. If a monthly note has been sent nine times and has never contained bad news, the note is marketing rather than reporting.
What next month should go to. So you can redirect it before it happens rather than reading about it after.
That is the document. It is not a timesheet and it is not a status report. It is a decision log, and it happens to also function as an invoice backup. I have written about what a retainer is meant to cover more fully in what a fractional CTO retainer actually buys each month; the monthly note is how you check you are getting it.
The detail that does damage
Here is where founders go wrong. Frustrated by a one-line invoice, they ask for an hourly breakdown. Sometimes they ask for time tracking against tasks.
Do not do this. You will get it, and it will cost you.
The moment a senior person is accounting for their time in fifteen-minute blocks, their behaviour changes. Thinking time becomes unbillable-looking, so it gets compressed or hidden. The half hour spent reading your competitor's engineering blog, which is where a genuinely useful insight comes from, does not go on a timesheet because it looks like nothing. The conversation with your engineer that had no agenda and surfaced the thing everyone had been avoiding does not have a task code.
What you get instead is visible activity. Tickets closed, documents written, meetings attended. All of it countable, most of it not the reason you hired a technical leader. This is the same failure as judging an agency by the length of its status report, which I wrote about in agency status reports that describe motion instead of progress. Timesheets manufacture the same illusion, just with your own contractor.
Days used against days contracted gives you ninety percent of the accountability with none of the distortion. Take that and stop there.
How to ask without making it weird
If you have been receiving one-line invoices for four months, the request is easy to make badly and easy to make well.
Badly: "Can you break down what I'm actually paying for?" That reads as a challenge to the value of the work, and you will get a defensive timesheet.
Well: "Two things would help me. Can the invoice show days used against days contracted, and can you send a short monthly note with the main decisions and what is blocked? I need it for the board pack and it will help me tell whether the retainer is the right size."
That framing does three things. It gives a reason that is not suspicion. It asks for decisions rather than hours. And it opens the door to resizing the retainer, which is usually the conversation that actually needs to happen and which both sides have been avoiding.
I have never seen a good operator refuse that request. Most of them are relieved, because the monthly note is also how they demonstrate value in a role where the best outcomes are invisible things that did not happen.
If you do get resistance, that is information. Not proof of anything, but worth a follow-up question about why.
What to do with it once you have it
Read three months of notes together, not one at a time. The pattern is what matters.
If days used runs consistently over, raise the retainer or cut the scope, and do it deliberately rather than letting it resolve as overage. If it runs consistently under, ask what else they could be pointed at, because unused senior capacity is the most wasteful line in an early-stage budget. If the decision list is thin but the day count is full, the person is being consumed by delivery work rather than leadership, which is a scoping failure and usually yours rather than theirs.
And keep the notes. Twelve of them is your technical decision history, which is the document you will want when an investor asks why the architecture is the way it is, and the one thing that survives when the engagement ends.
If you want a second read on whether your current retainer is sized right, bring three months of invoices. Our structure is on the Fraction pricing page, and you can book a call to talk it through.
Common questions
Is a one-line invoice from a fractional CTO a red flag?
On its own, no. It is standard for retainer work and reflects that you are buying availability rather than units. It becomes a problem when there is also no monthly record of decisions, because then you have no way to tell whether the retainer is sized correctly or what you are accumulating.
Should I ask a fractional CTO to use time tracking software?
No. It changes behaviour in the wrong direction, pushing a senior person toward visible activity and away from thinking, reading, and the unstructured conversations where most of the value is. Days used against days contracted is the right granularity. If you genuinely need hour-level detail, you probably want an hourly contractor rather than a retained technical leader.
What if the monthly note shows fewer days than I am paying for?
Do not immediately cut the retainer. First check whether you are the constraint: unused capacity is often a founder who is not bringing decisions to the person they hired to make decisions with. If two more months confirm genuine underuse, resize it. A retainer that is too big erodes the relationship almost as fast as one that is too small.
Can I ask for the monthly note retroactively for months already invoiced?
You can ask, and most people will reconstruct one or two months from their own notes. Asking for six months of backfill is a bigger request than it sounds and will feel like an audit. Better to start it from the current month and treat the past as a gap you are closing rather than a debt you are collecting.
Does the same standard apply to an agency invoice?
The principle does, but agencies bill differently and you should expect more line-item detail from them, because you are buying delivery volume rather than judgment. The decisions-and-blockers note is still the thing worth asking for, and it is far rarer from agencies than from individual operators.