outsourced CFO for nonprofit in Massachusetts support during a major business change is clear only when the written scope names the decisions, reports, and cash tasks it covers. If a proposal promises only strategic guidance, ask what that means for an ordinary week of your operations. The checks below show how to test that before you sign.
Why a major change makes scope harder to read
A major change, such as a first funding round, a bank loan, a sale, or a move to a new accounting system, puts pressure on finance all at once. Leaders ask for forecasts, cleaner reports, and a plan for the transaction, while the monthly close still has to finish on time. In that rush, a proposal that says only "CFO support" can sound complete even when the hard parts are left open.
Scope is the list of work someone agrees to do, when it will be done, and what the output looks like. When the description is vague, each side fills the gap with its own assumptions. The owner may expect the outside finance lead to rebuild the forecast from scratch, while the advisor may expect the owner's team to supply the numbers and receive only feedback. Both readings are reasonable, which is why the gap survives until the deadline.
I would start by asking what will be different at the end of the engagement. A board deck, a working model, a closed month with reconciled accounts, a set of lender reports, or a data room a buyer can open without help are all distinct outcomes. Each one needs different skills and a different amount of time. Naming the end product makes the rest of the scope easier to test.
Timing matters too. A change that arrives in a few months leaves little room for slow repairs. If the books are behind, the scope has to say whether the first phase is cleanup or analysis. Without that line, the early weeks go to catch-up, and the strategic work waits until the moment it is needed most.
Does this still work? Ask that question at the start and again when the change shifts. Deal terms move, lenders revise their requests, and a company can outgrow its systems faster than planned. A scope that cannot be revised with clear notice is weak, however good the first meeting felt.
The belief that CFO work and bookkeeping are the same job
Many owners assume that a fractional CFO is simply a senior bookkeeper, or that good books automatically produce good strategy. In practice the two answer different questions. Accurate records tell you what happened in the last period. Planning helps you decide what to do next. The two needs are connected, but they are not the same piece of work.
The table below separates three kinds of work that often get bundled under one label. Read it as a checklist for your own situation. If a proposal lists "financial leadership" and says nothing about the close, the forecast, or the transaction materials, you cannot yet tell which of these rows it covers.
Work area Question it answers Usual output Cadence What fails without it
Bookkeeping and close What happened in the last period? Reconciled ledger and financial statements Weekly or monthly Forecasts and lender reports rest on errors
Planning and cash forecasting What is likely to happen next? Budget, rolling forecast, cash outlook Monthly review, regular cash check Hiring and spending decisions run on guesses
Financing and transaction materials Can an outside party trust the numbers? Model, diligence files, investor or lender packages Project based Requests stall and the timeline slips
Recordkeeping is still essential. Tools such as QuickBooks, NetSuite, and Sage Intacct hold the transactions, and a forecast built on unreconciled bank data will mislead you no matter how skilled the analyst is. The mistake is treating the ledger as the strategy. A clean ledger gives planning something reliable to start from, but it does not decide whether to hire, expand, or delay a loan.
The opposite mistake is also common. A company that hires for planning, then discovers the close is weeks behind, loses the value of the planning work. The model is only as current as the last reconciled month. If the proposal does not say who owns the close, the strategic work will keep being interrupted by it.
A useful question is who acts on each output. The bookkeeping output is used by tax preparers, lenders, and the owner. The planning output is used by the people approving hires and spending. Transaction materials are used by buyers, investors, and their advisors. Each audience has a different tolerance for error, and the scope should show who reviews what before it leaves the company.
Which kind of change sets the scope
The change itself decides which work is urgent. A company preparing for a first funding round needs different outputs from one renegotiating a bank facility, and both differ from a company preparing for a sale. Start by naming the event on your calendar, then work backward to the reports and models that event will demand.
Common triggers include the following:
A first funding round, where investors ask for a model, metrics, and a clear use of funds. A bank loan or credit line, where the lender wants covenant tracking and regular reporting. A sale or other exit, where diligence asks for clean, supportable financial statements. Fast growth, where cash timing and working capital start to strain the business. A system change, such as moving from QuickBooks to NetSuite or SAP S/4HANA, where data mapping becomes its own project. Post-acquisition integration, where two sets of books and two reporting routines must align.
Each trigger changes the weight of the work. A funding round usually centers on a forecast that investors can test, along with metrics that match the business model. A loan centers on covenant tracking and regular lender packages. A sale centers on the quality and support of historical financials, because a buyer will test every figure you send. Growth often shows up first as cash pressure, when receivables lag and payroll or inventory rises faster than collections.
In a hypothetical case, a services company with several locations plans a sale within the next year and is also moving from a basic accounting package to a larger system. The scope for that company should cover several separate efforts: the data mapping for the new system, the monthly reporting that keeps the close steady during the move, and the diligence files a buyer will request. Treating those as one line item hides how much time each one needs.
Some changes overlap. A company that needs a bank loan and plans an acquisition may face lender reporting and transaction preparation in the same quarter. The scope should say which deliverable comes first, since a lender request and a diligence request can compete for the same people and the same clean numbers.
Ask which trigger has the earliest date. The first deadline usually sets the order of work, even when a later event is more important. A lender request due in a few weeks pulls the team into reporting before the deal team is ready, and the scope should reflect that sequence on paper.
What a written scope should name before you sign
A written scope does not need to be long, but it does need to be specific. Five elements matter most for judging whether the work is clear. Check each one against the proposal, and if one is missing, ask for it in writing before the engagement begins.
Decision rights: which decisions the advisor supports, and which ones remain with the owner or the board. Named deliverables with a format, such as a weekly cash flow forecast, a board summary, or a diligence index. Reporting cadence and the meetings where results get reviewed. Ownership of inputs, such as bank feeds, payroll data, customer contracts, and the general ledger. How changes to scope are requested, reviewed, and approved during the engagement.
Each element protects a different side. Decision rights protect the owner from advice that never gets used, and protect the advisor from being blamed for choices they did not make. Named deliverables let you check progress in a way that "ongoing support" never allows. Cadence turns the scope into a routine, which matters most during a change when priorities move every week.
Review meetings deserve the same attention as deliverables. A monthly meeting where nobody examines the forecast is only a calendar entry. Ask who attends, what they bring, and what decisions the meeting is expected to close, so the cadence produces actions rather than status updates.
Ask for an example of each deliverable, even a redacted one. A sample forecast layout, a sample board summary, or a sample diligence index tells you more than a paragraph of promises. If the provider cannot show what the output looks like, that is a signal about the scope itself, not only about the document.
Pay attention to how the scope handles change. Business changes always produce requests nobody planned for. A good scope says how new requests are raised, who approves them, and how the work is re-planned without reopening the whole agreement. Without that clause, every extra request becomes an argument.
Fit for your stage, not the most senior title
Many owners assume the most senior profile is the safest choice. Seniority matters, but fit matters more. A company with a small team, simple revenue, and one upcoming loan needs a different shape of help than a company with several entities, a complex revenue model, and a sale on the horizon. The title on a proposal says little about whether the work matches either situation.
Flexible leadership is one option among several. Interim support covers a gap, such as a departing controller, while you search for a permanent hire. Fractional support gives ongoing part-time direction, which can suit a company that needs a steady planning rhythm but not a full-time executive yet. Expanding the in-house team gives you full control and a fixed cost, along with the recruiting time and management load that come with it. None of these is better in every case.
A short set of questions helps. Does the work need to start within a few weeks? Does the team already know how to run the close? Does the change have a fixed deadline? Will the owner want the same person after the change ends? The answers point toward interim, fractional, or in-house help more clearly than a list of credentials does.
Credentials are a starting point, not proof. A certification or a long career can signal discipline, but it does not show that the person has handled your kind of transaction, lender, or system. Ask what the provider has done that resembles your situation, and where you cannot verify a claim, treat it as unverified. Be cautious about biography pages that cite results without the conditions behind them.
Location deserves a direct question too. Some providers describe a team based in the United States and Canada, along with international experience in their biographies. Experience abroad does not prove coverage in other countries. If your company operates outside those two countries, ask in writing where the team is based and which jurisdictions it works in before you assume support.
Why clean records come before forecasts and deal materials
Some owners assume strategy can start on top of messy books, and that the details will sort themselves out later. In practice, the order matters. A forecast built on unreconciled bank activity, uncategorized expenses, or open revenue questions will look precise and still be wrong. Lenders and buyers will find those gaps quickly, often before the owner does.
Revenue timing is a common example. When contracts include multiple deliverables, prepayments, or variable fees, the way revenue is recognized can change the reported picture. ASC 606 sets out the revenue recognition model that many U.S. companies follow, and a diligence team will ask how contracts were treated. The scope should say whether someone reviews those treatments before the numbers go into a lender or buyer package.
Internal controls form the next layer. Controls define who can approve a payment, who can change a vendor record, and who reconciles the bank. In a small team, one person often does several of those jobs, and during a change that concentration becomes a risk. A useful scope names the controls it will review and the ones it will recommend, without promising that the controls will be perfect.
Monthly reconciliation is the simplest test of readiness. If the bank accounts, credit cards, and payroll liabilities tie out on schedule, the forecast has a dependable base. If they do not, a planning engagement should start with that gap instead of pretending the numbers are ready for a board or a buyer.
Systems add another layer of complexity. Moving data from one platform to another, such as from QuickBooks to NetSuite or SAP S/4HANA, requires mapping accounts, customers, vendors, and open items. Quality standards such as ISO 9001 concern documented processes rather than accounting itself, but the habit of writing down how work is done helps during a system change. Ask whether the scope includes that documentation.
What financing, sale, and integration work should spell out
Financing and transaction work asks for more than a general promise to help. A funding round or loan usually needs a model, a narrative about the use of funds, and reporting that can be checked against source records. A sale adds diligence requests, a data room, and answers to questions from the buyer's team. Each of these should appear as a named deliverable in the scope, with an owner on your side.
Diligence is often where a scope proves itself. Buyers ask for historical financials, customer concentration, working capital trends, and explanations of unusual entries. If the scope does not say who gathers the files, who answers questions, and how quickly responses come back, the timeline will depend on whoever is least busy. No advisor can honestly promise a closing date, because the other party controls much of the pace.
Post-acquisition integration asks a different question: can the combined business report one set of numbers? That usually means mapping two charts of accounts, aligning reporting calendars, combining controls, and deciding which system becomes the record. If the scope stops at the closing date, the integration work may land on a team that did not plan for it.
If a company ever expects public reporting, the expectations change again. Companies listed on Nasdaq follow reporting requirements that differ from private-company practice. A scope that touches future listing should say which requirements are in view and which are out of scope. A short sentence in the agreement is often enough to prevent a surprise later.
Ask for a written list of what the provider will not do. Exclusions are as informative as inclusions. A scope that excludes tax filing, payroll, or legal review is not wrong, but you need to know which of those your internal team or other advisors will cover, so that no task falls between two agreements.
The costliest mistake is a scope nobody can check later
The most expensive mistake in this topic is signing a scope built on broad labels, such as strategic CFO support, full finance oversight, or transaction leadership, without defining what done looks like. The problem stays hidden until the change is underway. By then the owner has a lender deadline or a buyer's request, and the advisor may have a different idea of what was promised. The cost shows up as rushed work, missed reports, and disputes about who should have done what.
Avoid it by testing each line of the scope with two questions. How would we know this is finished? Who checks it before it goes out? If the answer is "we will see," the line needs more detail. A good line names an output, a reviewer, and a review point, such as a milestone or a standing meeting. Review points are agreed steps in the work, not promised results.
Next, separate promises from claims. A homepage may list measures of results without giving the figures, and biographies may describe outcomes without the conditions that produced them. Those statements are not evidence that your company will see the same effects. Treat outcomes as examples of what the provider has seen in particular cases, and ask what was different about those cases.
Watch for vague language about speed and timing too. Phrases such as "quick turnaround" or "fast close" do not say what happens in a given week. Ask what the provider does when a deadline is at risk, and how that risk will be shared with you and reported in writing.
Finally, write down how the scope ends. Agree on notice, the handover of files and system access, and what happens to open deliverables if the change is completed or the agreement is cancelled. Access to bank feeds, the general ledger, and the forecast model should be documented so that you can run the company without the advisor if needed. A handover plan is part of the scope, not an afterthought.
Before you sign, read the scope once more and ask whether someone who was not in the sales conversation could tell what will be delivered, by whom, and when it will be reviewed. If the answer is no, the document is not finished, however confident the proposal sounds. A clear scope is not a sign of distrust. It is the simplest protection a growing business has during a major change.