How to brief a fractional CFO

A fractional CFO cannot read your mind, and they should not have to reverse-engineer your company from a dump of files. The first thirty days produce a close calendar and a cash view only if the briefing packet is complete enough to work from on day one.

Send a packet, not a scavenger hunt. The goal is shared context before the first working session, not a performance of how busy everyone is. The founders who get the most from a fractional seat treat the brief like onboarding a senior hire: clear access, honest history, and a written definition of “good” for the next ninety days.

Speed without context looks like productivity and feels like waste. Every missing bank login, unnamed revenue owner, or buried covenant turns week one into discovery billables instead of a published calendar. The brief is how you choose which of those weeks you want to buy.

The packet itself

Build one folder (or shared drive) with a short index at the top. Label folders so a stranger can navigate without Slack. Prefer exports that can be refreshed over screenshots that go stale by Friday. Date-stamp the index so the pair knows what is current versus what was dumped in a hurry the night before kickoff.

• Legal entities, jurisdictions, and which entity holds cash.
• Last twelve months of financials, even if messy, plus current year to date.
• Bank list with who has access and which feeds are automated.
• Billing system, payroll system, and AP process owners by name.
• Debt, convertible notes, and any covenants that can surprise cash.
• Cap table summary and recent financing documents.
• Top ten customers by revenue and top ten vendors by spend.
• Board calendar and any reporting commitments already promised.
• Known landmines: disputes, tax notices, stalled audits, broken integrations.
• What “good” means for you in ninety days, in one page of plain language.

If you cannot name the owner of revenue data, the close will not save you. Fix ownership first.

Access before kickoff

Access list the accounts on day one: banks, ledger, billing, payroll, drive folders for contracts, and the board deck archive. Pending access is the most common reason the first close slips. Approve access before the kickoff call when you can. If legal review is required for bank or payroll access, start that review the week before the engagement begins—not the morning of the first working session.

Write which tools are source of truth. If billing lives in Stripe and the ledger sometimes disagrees, say which one wins for which question. Ambiguous sources of truth turn every flux conversation into archaeology. The same clarity belongs to inventory, deferred revenue, and any subsidiary ledger that leadership treats as “close enough.”

1. Day minus seven. Packet shared, access requested, ninety-day outcomes drafted by the founder.

2. Day zero kickoff. Walk the packet live. Name landmines out loud. Confirm who unblocks systems when the pair is stuck.

3. Week one. Close calendar draft, bank inventory complete, first cash trough visible from real accounts.

4. Week two to four. First full close cycle under the new calendar, anomaly queue public, monthly pack shape agreed.

What the first thirty days should produce

Incomplete packets create expensive discovery. Complete packets create a calendar and a forecast. Tarient would rather spend week one building the close than hunting for bank logins. Hold the engagement to concrete outputs, not vibes about “getting oriented.” If an output slips, name the missing input from the packet—do not absorb silence as normal.

1. A published close calendar with owners.
2. A thirteen-week cash view tied to real bank accounts.
3. A materiality threshold and a short list of judgments that need policy.
4. A visible anomaly queue instead of private worry.
5. Agreement on what the monthly pack contains and when it arrives.

Politics, history, and handoffs

Tell the truth about politics. If two co-founders disagree about runway math, say so. Fractional leaders can navigate conflict they can see. They cannot navigate conflict that appears as contradictory files with no explanation.

Share the last three board decks even if you are embarrassed by them. Patterns in what was promised versus what was delivered are part of the job. Hiding them slows trust. The same rule applies to prior auditor comments, tax notices, and abandoned ERP migrations—surface them once so the pair does not rediscover them mid-close.

If you use multiple bookkeepers or a prior CFO on a taper, write the handoff boundaries. Parallel authority without a written split produces duplicate entries and mutual blame. Name who posts, who reviews, and who may speak for numbers externally during the overlap window. Put that split in writing before the first close week, not after the first conflict.

• Do not wait for “clean books” before briefing—messy books with owners beat tidy silence.
• Do not bury covenants in a legal folder nobody opens until a repayment surprise.
• Do not treat the brief as optional reading; treat it as the working set for week one.
• Do not redefine success every Monday; lock a ninety-day page and revise deliberately.
• Do not leave payroll and equity events undocumented—those are the landmines that blow calendars.

How Tarient uses the brief: we map your packet into Oversight, assign the pair, and schedule the first close against a realistic calendar. If the packet shows the fifth business day is impossible this month, we say so on day one and show the path to a credible fifth by cycle three. Related reading: monthly close, close calendar. To send a packet, contact Tarient.

A good brief shortens the path to a boring fifth-business-day close. A bad brief buys you billable archaeology. Choose on purpose. The packet is not bureaucracy—it is how you buy a calendar instead of a scavenger hunt, and how you give a fractional seat a fair shot at earning trust in thirty days.