Virtual CFO Onboarding: The First 30 Days (2026)
What a well-run virtual CFO onboarding looks like: the access needed before day one, the first fortnight's outputs, and the founder's actual time cost (4…
The biggest unspoken worry about starting a virtual CFO engagement is not the fee; it is the disruption. Founders imagine weeks of their time lost to onboarding, endless meetings, and a slow ramp before anything useful appears. A well-run 90-Day Number engagement is designed to be the opposite: light on your time, fast to a first output, and clear about exactly what is needed and when. This page sets out what the first thirty days actually look like, so the switching cost is visible rather than feared.
Published: July 2026
A fast start depends on access being sorted before the engagement begins, and the list is short and specific. The core items are read access to your accounting file (so the numbers can be pulled directly), read-only access to your bank feeds (so the cash position is real, not reconstructed), any prior models or forecasts you have built (so existing work is used rather than duplicated), and recent board or management materials (so the context is understood from the start). That is essentially it for a fast start.
Getting this ready before day one is what lets the work begin immediately rather than after a week of chasing logins. On access discipline, one plain line is enough: access is read-only where possible, granted through your systems’ standard sharing, and removed at the end of the engagement, no drama, no theatre. The point of the access list is speed: with it sorted up front, day one is spent on the work, not on setup.
The first week is a data audit and a focused set of questions, and it is where most of the founder’s limited time is spent. The data audit is the CFO working through your accounting file and recent numbers to understand how the business is actually recorded: how revenue is booked, how costs are categorised, where the data is clean and where it needs care. This is analytical work done largely without you, from the access granted before day one.
The questions are the part that needs the founder, and they are focused rather than open-ended. A good operator arrives with specific questions the data raises, why a cost line jumped in March, how a particular revenue stream is recognised, what a lumpy set of transactions represents, rather than a vague request to “walk me through the business.” Answering focused questions is a far lighter demand on your time than open-ended discovery, and it is the main call on your attention in week one. This is the same discipline as briefing the engagement well; the difference is that by now the deliverable is chosen and the work is underway.
By the second week, a skeleton of the deliverable exists. If the chosen deliverable is the 13-week cashflow, week two produces a working draft of the forecast structure populated with your real data; if it is a model or unit economics build, the framework is built and populated. It is a skeleton, not the finished artefact, but it is real and specific to your business, and it appears fast enough that you see tangible progress within the first fortnight rather than waiting most of the engagement for the first output.
The early skeleton matters for two reasons. It gives the founder something concrete to react to, which sharpens the work, because reacting to a real draft surfaces corrections and insights that abstract discussion never does. And it demonstrates, early, that the engagement is producing something rather than disappearing into analysis, which is the reassurance a founder starting a new engagement most wants. Progress is visible fast by design.
The back half of the first month is spent testing the artefact’s assumptions with the founder and refining it toward the finished deliverable. The skeleton built in week two rests on assumptions, about how revenue behaves, how costs scale, what the forward picture looks like, and days 15 to 30 are where those assumptions are checked against the founder’s knowledge of the business and adjusted. This is a collaborative phase, but still a light one for the founder: reacting to and correcting a draft, not building it.
By day 30, the deliverable has moved from skeleton to a substantially working artefact with tested assumptions, well on the way to the finished version that lands by day 90. The first thirty days, in other words, take the engagement from access to a real, assumption-tested draft, which is exactly the pace a founder should expect from a well-run engagement: fast to first output, collaborative on the assumptions, and light on the founder’s time throughout.
The honest number is the reassuring one. A well-designed 30-day onboarding is built to cost the founder in the region of four to six hours of their time across the whole month, concentrated in week one’s questions and the days 15 to 30 assumption-testing, with the analytical work happening without them in between. That is the design intent: the engagement is structured so the CFO does the heavy lifting from the access provided, and the founder’s involvement is focused on the few things only they can answer.
Four to six hours across a month is a deliberately modest demand, and it is what makes the switching cost low. A founder worried about losing weeks to onboarding can see, from this, that the actual cost is a handful of focused hours, most of it in the first week. The engagement is designed around the founder’s time being scarce, which is why the onboarding front-loads the questions, produces an early skeleton to react to, and otherwise gets on with the work independently.
What access does a virtual CFO need before starting?
A short, specific list: read access to your accounting file, read-only access to your bank feeds, any prior models or forecasts, and recent board or management materials. Having these ready before day one is what lets the work begin immediately rather than after a week of chasing logins. Access is read-only where possible and removed at the end of the engagement.
How much of my time will onboarding take?
In the region of four to six hours across the first thirty days, concentrated in week one’s focused questions and the days 15 to 30 assumption-testing, with the analytical work happening without you in between. The engagement is deliberately designed around your time being scarce, so the CFO does the heavy lifting from the access provided and your involvement is focused on what only you can answer.
When will I see the first output?
Within the first fortnight. By week two a skeleton of your chosen deliverable exists, a working draft of the forecast structure, model framework, or unit economics build, populated with your real data. It is a skeleton rather than the finished artefact, but it is real and specific to your business, so you see tangible progress early rather than waiting most of the engagement.
What happens in the first week?
A data audit and a focused set of questions. The CFO works through your accounting file and recent numbers to understand how the business is recorded (largely without you), then asks specific questions the data raises, why a cost jumped, how a revenue stream is recognised, rather than open-ended discovery. Answering focused questions is a light demand on your time and is the main call on your attention in week one.
Is my financial data secure?
Access is read-only where possible, granted through your systems’ standard sharing, and removed at the end of the engagement. That is the plain discipline, no more theatre than that. The point of the access list is a fast, clean start with the minimum access needed to do the work, revoked when the work is done.
What does the second half of the first month involve?
Testing the skeleton’s assumptions with you and refining toward the finished deliverable. The draft built in week two rests on assumptions about how revenue behaves and costs scale; days 15 to 30 check those against your knowledge of the business and adjust them. It is collaborative but light, reacting to and correcting a draft rather than building it, and by day 30 the deliverable is a substantially working, assumption-tested artefact.
Why does the switching cost feel higher than it is?
Because founders imagine weeks lost to onboarding and a slow ramp, when a well-run engagement is designed for the opposite: access sorted before day one, questions focused rather than open-ended, a first skeleton within a fortnight, and four to six hours of founder time across the month. Seeing the actual shape of the first thirty days is what makes the switching cost visible rather than feared.
Sydney Virtual CFO is a Sydney-based virtual CFO service for founders running $2M to $15M businesses across SaaS, ecommerce, professional services, construction, and other low-volume, high-value industries. We deliver fixed-scope CFO engagements with a named deliverable on day 90: a 13-week cashflow forecast, a fundraise-ready financial model, a unit economics build, or a board reporting pack you can run on your own.
Our front-door product, the 90-Day Number, is fixed scope at $17,850 plus GST. We are one of the few project-based virtual CFOs in Australia, in a market built almost entirely on monthly retainers. No retainers without a deliverable. No 80-page reports. No theatre.
Visit Sydney Virtual CFO | The 90-Day Number | Book a Call
This content is general information only, written for Australian founders running businesses in the $2M to $15M revenue range. It does not constitute tax, financial product, investment, or legal advice and should not be relied on as such. The work referenced is led by a Chartered Accountant (CA ANZ), but Sydney Virtual CFO is not a licensed tax agent, not a licensed financial adviser, and not authorised to provide personal financial advice. Tax obligations, accounting treatments, fundraise terms, and statutory requirements depend on your individual circumstances. For advice specific to your business, contact the team directly or consult a registered tax agent, licensed financial adviser, or qualified lawyer. Information was current at the time of publication and may change without notice. We review and update guides periodically.
