Your Fractional CFO Remembers Last Quarter Better Than Your Team Does

Eight months in, the contractor is the one who remembers

A company brings in a fractional CFO for two days a month. The arrangement is meant to be light. She sits in the pricing conversation, the vendor review, the board prep, and the two calls with the bank, and then she leaves and works somewhere else for the rest of the week.

Eight months later somebody asks why the pricing tiers changed in March. Three people were in that meeting. One has left. One remembers the outcome but not the reasoning. The third remembers a version of the reasoning that turns out to be the argument that lost. The person with the clean answer is the fractional CFO, and she has it because her notes are how she bills, how she picks up a thread after two weeks away, and how she defends a recommendation to a client she sees six times a quarter.

That happens because of how the role works. A part time senior operator lives inside decisions and very little else. They do not absorb context by being around, since they are not around, so they write it down. The full time team sat in the same meeting and wrote nothing, because they assumed they would remember, and because they had four other things happening that afternoon.

The consequence is easy to miss while the engagement is running and impossible to miss once it ends. The company's clearest record of its own reasoning sits in an account belonging to somebody else.

Everybody guards the leak, nobody guards the gap

Ask a founder what worries them about a fractional hire or an embedded contractor and you will get the leak. This person works with four companies, two of them adjacent to ours, and they are sitting in our roadmap meeting. Does our thinking end up somewhere it should not.

The worry is legitimate, and it is also the easier of the two, because everyone in the room is already alert to it. It has a clear shape, it gets written into the agreement, and the person on the other side has more to lose from a breach than anybody. Reputation is the whole business for someone who works this way.

The other exposure has nobody watching it. Nothing about it trips an alarm or looks like a violation. The engagement goes well, the deliverables land, the invoice clears, and the reasoning behind eight months of decisions quietly leaves with the person who is leaving. There is no moment where anyone says a rule was broken, because none was.

This is how a growing share of senior work gets staffed

The US Bureau of Labor Statistics ran its Contingent Work Supplement in July 2023 and published the results in November 2024, the first time the survey had run since May 2017. In July 2023 there were 11.9 million independent contractors on their sole or main job, 7.4 percent of total employment, up from 6.9 percent in 2017. BLS counts independent consultants and freelance workers inside that category.

Two details in the release matter more than the headline number. The arrangement is chosen: 80.3 percent of independent contractors said they preferred it, and 8.3 percent would have preferred a traditional job. And it is mostly durable rather than temporary: only 4.1 percent of independent contractors on their sole or main job were also contingent, meaning in a job they did not expect to last.

What the statistics do not measure is the variable that creates the problem here. BLS records the arrangement on a person's sole or main job. It publishes no count of fractional executives, and it does not ask how many companies one person sits inside at the same time. How many rooms someone is in is exactly what decides where a company's context ends up, and nobody counts it.

Treat it as a standing feature of how senior roles get staffed. A CFO two days a month, a head of ops for a quarter, a security advisor through the fundraise, a designer through the rebrand. Plan the memory around that shape rather than around the org chart.

A work made for hire clause probably does not cover the notes

Most contractor agreements carry a work made for hire clause, and most people who sign one assume it settles ownership of everything the contractor produces. Under US copyright law it does less than that. The Copyright Office lays it out in Circular 30, revised August 2024.

A work becomes made for hire in one of two situations. Either an employee created it within the scope of employment, or it was specially ordered or commissioned and meets four requirements: a written agreement, an express statement in that agreement that the work is a work made for hire, signatures from all parties, and the work falling inside one of nine listed categories. The circular is blunt about the arithmetic. If a work fails to satisfy any of these requirements, it is not a work made for hire.

The nine categories are a contribution to a collective work, part of a motion picture or other audiovisual work, a translation, a supplementary work, a compilation, an instructional text, a test, answer material for a test, and an atlas. Notes about your pricing decision are none of those. And a contractor is not your employee, which is usually the entire point of the arrangement, so the first route is closed as well.

That leaves assignment. If you want to own what a contractor writes about your company, the agreement has to assign it, and somebody has to have put that in writing. The Copyright Office states that it cannot give legal advice about whether a particular work qualifies, and neither can an article like this one. The useful action is narrow: ask whoever drafted your contractor template whether it assigns work product, or only recites work made for hire language. Those are different clauses, and plenty of templates carry only the second.

Owning the file and being able to open it are different problems

Suppose the assignment language is there and ownership is clean. You may still not have the record.

The notes were taken in a personal account. A notes app tied to somebody's personal Apple ID, a personal workspace in a note tool, a folder on a laptop your company never issued. Ownership on paper gives you a claim you could enforce. It does not put the notes in front of the person who needs them on a Tuesday afternoon, and nobody wants to reopen an engagement that went well by sending a legal request for a folder.

Custody has to be arranged while the work is happening and while everybody is friendly. Extracting a record after the fact turns a filing question into a negotiation, and that always arrives at the worst possible moment.

Three gaps, and only one of them gets talked about

The handback gap. An engagement ends with deliverables: a model, a hiring plan, a vendor shortlist, a set of policies. What does not come across is why each one looks the way it does, which alternatives were rejected, and what constraint made the obvious answer unworkable. The next person to touch that model either rediscovers the constraint or walks straight into it.

The rotation gap. Fractional roles turn over faster than full time ones by design. When the second fractional CFO arrives, the internal team spends the first month answering questions the first one already answered, and the new arrival forms opinions from a starting point that has lost the earlier reasoning. The second engagement repeats the first instead of building on it.

The asymmetry gap. Somebody working across five companies accumulates real pattern knowledge, and most of it they can never cite. They cannot say they watched this exact vendor negotiation go badly at another client last year, because saying it would be a breach. So the most valuable thing they know arrives as an unexplained preference, which is the form of advice that carries the least weight and gets overridden the most often.

A seat in the workspace solves the wrong half of it

The standard response is to hand the contractor a company email address and a seat in the shared tools. That is a reasonable first move, and it solves the file location problem. Their notes land in your archive rather than theirs.

It opens a second problem pointing the other way. A person under a different employer's roof now has search access across everything, including conversations that concerned them least and were meant for the fewest people. The leakage worry from earlier arrives through the door you opened to fix the memory worry.

The shape that works is narrower than a full seat and wider than a shared folder. The record of the meetings they actually attended for you should land in your archive as it is made. The rest of your archive should stay closed to them. And their own working file, the one holding their billing notes, their read on your org, their case for the recommendation they are about to make, should stay theirs. All of that is compatible with a tool whose default is private with explicit sharing, and awkward with a tool whose default is a shared team space.

Make it a setup step for every engagement

The instinct is to make this a question about the individual. Do we trust this person. That framing produces a fresh judgement call every time somebody new starts, and no policy at all. Handle it at the level of the engagement and it becomes a setup step you do once and reuse, with five slots filled in differently each time.

Which meetings. Name the meetings where this person's record belongs in your archive. For a fractional CFO that is pricing, board prep, bank and audit calls, vendor negotiations. It is not their internal planning call, and it is obviously not their weekly with another client.

Which account. Decide before the first meeting whether they capture into a seat you provide or into their own tool under a sharing obligation. Either can work. The failure mode is not deciding, because then it defaults to their own account and nobody notices for eight months.

Who else is in the room. Name one full time person who attends the decision meetings. That person is there so the reasoning has a second holder who will still be around in a year, which is a different job from taking minutes and a different job again from supervising the contractor.

What the agreement says about work product. Assignment language, checked by whoever drafts your contracts. It costs an hour, once, and it is the only item on this list you cannot fix later by being organised.

What happens the day after the last day. Access ends and the archive of what they captured stays. Write down which of those two is true for each system while nobody needs it to be true yet.

The record has to come out of the work, not out of the wrap up

The common plan is a knowledge transfer session in the final week. It fails for reasons that have nothing to do with goodwill. The last week of an engagement is the worst week on offer. It is billed, or it is unbilled and therefore rushed. The person is already staffing their next client. And a summary written at the end is written from memory, eight months after the meeting that actually mattered.

The version that works costs nothing extra during the engagement, because the notes were being taken anyway. That is the whole opportunity here. A fractional operator already writes things down for their own reasons. The only open question is which side of the boundary the writing lands on, and that gets answered by where capture is set up on day one.

Treat the archive as a running deliverable and the final week turns into a formality: a walk through what is already there, instead of a reconstruction of what nobody wrote down.

Where Driffle fits, and what it leaves to you

Driffle captures meetings without a bot joining the call, so a contractor attending your meeting does not add a visible third party participant to a room whose guest list is already slightly complicated. There is no auto join, no auto record, and nothing running in the background. Audio is transcribed in real time and discarded, and what is kept is the text and the notes.

Notes are visible only to their author until explicitly shared, and workspace admins see what has been shared into shared folders rather than private notes. That default is the mechanism this whole piece needs. A person can hold their own working file and still put the record of your meeting into your archive, deliberately, meeting by meeting.

Past meetings stay searchable and you can ask questions across them, which is what makes a handback useful rather than ceremonial. Action items come out with owners attached, which matters more than usual when the owner is somebody who will be back in eleven days.

What Driffle does not do is decide which of a person's meetings belong to which company. That call needs a human who knows the engagement, and it has to be made before the meeting rather than after it. Driffle also does not replace contract language, and nothing here is a compliance position or a legal guarantee. It is a description of how the product behaves.

One measurement worth taking

Wait a month after a fractional engagement ends, then ask the internal counterpart three questions beginning with why, about decisions made during it. Why this vendor. Why the tiering came out this way. Why the plan was staged across two quarters instead of one.

If they answer from the record, the memory transferred. If they answer from their own recollection, you got lucky and that person happened to be paying close attention. If the honest answer is that they would have to email the former contractor, then the engagement produced deliverables and left the reasoning at the door, and the next one will start from the same place unless something changes before it begins.