How we help

You're the new CFO of a scaling life sciences company.

What to look at first, what to leave alone, and how to tell the difference — from someone who has been inside a lot of these finance functions.

The moment

Everyone is being helpful and nobody is being precise.

You are somewhere in the first sixty days. You were hired because the company is about to become something it currently is not — commercial, public, acquisitive, international, or all four — and everyone is being helpful and nobody is being precise.

You have inherited a finance function built by good people under pressure, which means it works and it is not documented. You are being asked for a view on systems in a meeting next month, and you do not yet know enough to have one you would defend.

What usually goes wrong

Move too fast, move not at all, or miss the seam.

The system decision gets made before the process is understood. A new CFO arrives, finds the ERP inadequate, and starts a selection. Nine months later the company has a better system running the same undiagnosed processes, and the problems that prompted the search are still there.

Or the opposite — nothing is touched for a year. The new CFO does not want to be the person who broke the close, so nothing changes until something breaks on its own. That is usually the quarter with the most at stake.

The regulated part is treated as somebody else's problem. Quality owns GxP, finance owns finance, and nobody owns the places they meet — inventory valuation on quarantined stock, the contract that carries both a payment term and a quality agreement, the batch that is on hold and on the balance sheet.

What good looks like

Evidence, not the person who has been there longest.

Operations. You know which processes are load-bearing and which are habit, and you know it from evidence rather than from the person who has been there longest.

Regulatory. You can say which finance-adjacent processes carry regulatory weight and which do not. You do not need to become a quality expert; you need to stop being surprised.

Capital. Whatever is coming — a filing, a raise, an audit, a sponsor — the control environment is being built toward it deliberately rather than discovered in diligence.

Global. If a second country is anywhere in the plan, the finance architecture anticipates it.

The first two weeks

The naive question you cannot ask yourself.

Honestly, this is the engagement where a fresh outside read is worth the most, because you are the one person in the building who cannot yet ask a naive question without it being interpreted.

We read the close, the systems, the org, and the last audit. We talk to the people who will tell an outsider what they would not tell their new boss in month two. You get a written baseline: what works, what is fragile, what is a genuine risk, and what the sequence should be. Yours to use however you like, including disagreeing with it.

A self-check

Five questions worth answering before the meeting.

  1. Can you describe your close in a sequence, with owners, without asking anyone?
  2. Do you know which of your processes would fail if their most experienced person left?
  3. Has anyone told you what the system actually cannot do, as opposed to what it does badly?
  4. Are you being asked for a systems decision before you have a process baseline?
  5. Do you know where finance and quality touch, and who owns those seams?
Where to start

One question, ten business days, in writing.

Most of these begin as a targeted analysis — one question, ten business days, in writing.

Sometimes the question is simply what should I be worried about that nobody has told me. That is a legitimate question and a good use of ten days. We can have an NDA signed the day you ask.

Start here

Tell us what you have walked into.

Start a conversation