Your First Finance Hire: How to Scope It
The short answer
Most first finance hires are scoped by title rather than by work, which is why they land wrong in one of two directions: too senior for the tasks, or too junior for the decisions. The fix is to list every recurring task the seat would own, estimate the hours honestly, and let the total tell you what to hire. The title comes last.
Scope by hours, not by title. The title comes last.
By Stephen Ninesling, FynScale

Your First Finance Hire: How to Scope It
Short answer: Most first finance hires are scoped by title rather than by work, which is why they land wrong in one of two directions: too senior for the tasks, or too junior for the decisions. The fix is to list every recurring task the seat would own, estimate the hours honestly, and let the total tell you what to hire. The title comes last.
Why the first one is the hardest
Every hire after the first has context. You know what the finance function does at your company because you have watched someone do it.
The first hire has none of that. You are scoping a role you have never seen operate, usually while the work is being done by a founder at 11pm and a bookkeeper who was hired for something narrower. So the role gets defined by what hurts most this month, which is rarely the same as what the seat should own.
Two failure modes, and they are equally common.
Too senior. You hire a controller or a VP of Finance and they spend most of the week on bookkeeping and reconciliations because that is what actually needs doing. They are bored within six months and gone within twelve, and you have paid a premium for work a bookkeeper could have done.
Too junior. You hire a staff accountant because the visible work looks like transaction processing. Then a judgment call arrives, revenue recognition or an entity structure question or a lender's request, and there is nobody positioned to make it. You are back to the founder at 11pm, only now with payroll on top.
Scope by hours, not by title
The exercise takes an afternoon and it is the single highest-value thing you can do before writing a job description.
Step one: list every recurring task. Not categories, tasks. "Reconcile the operating account" not "handle banking." Include the monthly close steps, the payables run, the invoicing, the payroll entry, the reporting, the ad-hoc requests that arrive from you or from a lender.
Step two: estimate hours per month, honestly. Ask whoever does it now rather than guessing. People consistently underestimate work they do not perform themselves, usually by half.
Step three: mark each task by the level it actually needs. Processing (data entry, categorisation, running the payables). Execution (reconciliations, journal entries, close mechanics). Judgment (treatment decisions, structure, what the numbers mean).
Step four: total the hours in each band.
Now the shape of the answer is visible rather than assumed. A total of 120 hours a month with 100 of them in processing is not a controller role. Twenty hours a month that are almost all judgment is not a full-time role at all.
Reading the result
Mostly processing, high volume. You need a bookkeeper or a staff accountant. This is a capacity problem, not a seniority problem.
Mostly execution, high volume. You need a senior accountant or an accounting manager. This is the most common actual answer at 20 to 50 people, and it is frequently mis-titled as controller.
Meaningful judgment, moderate volume. You need controller-level capability, but check the total hours before assuming it is full time. Judgment work is often ten to twenty hours a month, which is a fractional shape.
Meaningful judgment, high volume across all three bands. This is a genuine controller hire, and you are probably overdue.
High judgment, low volume, plus strategic questions. This is CFO-shaped work and it is almost never full time at your stage.
The thing that changes the answer
One factor moves the outcome more than headcount or revenue: how much of the work is structural rather than recurring.
If your chart of accounts does not support the reporting you need, if reconciliations have never truly tied, if revenue recognition is unresolved, then a large one-time project is sitting underneath the recurring work. That project needs seniority. The recurring work afterwards may not.
Companies that miss this hire a senior person to do a project, then keep paying senior compensation for maintenance. The alternative is to do the structural work as a defined engagement and hire for the steady state that follows, which is usually a level lower and considerably cheaper.
What to actually write in the job description
Once the scoping is done, three things make the posting land better.
Describe the work, not the title. "Own a ten-day close across two entities and three sales channels" tells a candidate more than "Controller." It also filters out people who want a different job.
Be honest about the state of the books. Good candidates are not deterred by cleanup, they are deterred by discovering it after they accept. Saying "the chart of accounts needs rework and reconciliations are behind" attracts people who want that problem.
Name what the role does not own. If you are not hiring for fundraising, say so. If FP&A stays with the founder for now, say so. Unstated scope is where expectations go wrong on both sides.
What it costs, so the decision is priced
Fully loaded, including payroll taxes, benefits and equipment, plan on roughly:
- Bookkeeper: $55,000 to $85,000
- Staff or senior accountant: $80,000 to $120,000
- Accounting manager: $110,000 to $150,000
- Controller: $150,000 to $220,000
- CFO: $250,000 and up, frequently with equity
Add the search, two to four months, and the ramp, one to three. Committing to the wrong level costs the difference in salary plus the cost of correcting it, which is usually another search.
The test before you commit
Write the two sentences the hire is meant to make true, twelve months from now.
If they read like "close finishes in eight days and I trust the balance sheet," that is an execution hire. If they read like "I know which channels make money and I can model next year," that is a judgment hire. If they read like both, check the hours again, because that is often two roles or one role plus a system that does not exist yet.
Common questions
Should my first hire be a CPA? Useful, not required, unless you are audit-bound or dealing with complex revenue recognition. Operating experience in a company your size usually matters more than the credential.
Can my bookkeeper grow into a controller? Sometimes, and it is worth taking seriously because they already know your business. The honest test is whether they make judgment calls today or escalate them. Growth is possible; the gap is bigger than most people assume.
Should I hire in-house or fractional first? If the work is under about twenty hours a week, or if a large structural project sits underneath it, fractional first is usually the better sequence. It also means the eventual hire inherits a working system rather than a mess.
What if I get it wrong? It is recoverable, and it is cheaper to correct early. The expensive version is realising at month nine and waiting until month eighteen because the conversation is uncomfortable.
How do I know the estimates are honest? Have the person doing the work track it for two weeks rather than estimating from memory. The difference between recalled and recorded hours is routinely fifty percent.
FynScale covers the controller and CFO functions for companies between $1 million and $50 million, including the structural work that makes a first hire land in the right seat. If you are scoping one now, that is usually a short conversation worth having first.