How long does client onboarding take? Count it before you quote
· 6 min read
Longer than most freelancers price for, because onboarding is made of many short tasks that each feel too minor to count: the contract, the kickoff call, the questionnaire, access to a dozen accounts, the first round of questions. Measure the next one from signed contract to the first hour of real work, and you will have a figure to build into every quote that follows.
What counts as onboarding
Onboarding starts when the client says yes and ends when you begin the work you were hired to do. In between is a set of jobs that nobody bills for by default:
- Paperwork. The contract, a deposit invoice, perhaps a supplier form from the client’s finance team.
- The kickoff call. Plus the preparation before it and the notes after it.
- Gathering information. A questionnaire or brief, brand files, previous work, logins.
- Access. Accounts, shared folders, chat channels, permissions that do not quite work the first time.
- Setting up your own side. A project folder, a schedule, reminders, a place for notes.
- The first questions. The back and forth of the first week, as you find out what the brief left out.
Each one takes anywhere from a few minutes to an hour. Together they can add up to a meaningful part of a short project, and they rarely appear in the quote.
Why it gets missed
Onboarding is easy to overlook for three reasons. It happens before the real work, so it does not feel like part of the project. It is scattered across several days and apps, so no single piece looks large. And it is different for every client, so last time’s total is hard to remember.
The result is predictable. Your quote covers the deliverables, onboarding comes out of your margin, and on a short project the margin was thin to begin with.
Measure the next one
Treat your next new client as a measurement.
- Mark the start. The day the contract is signed or the client confirms in writing.
- Mark the end. The first session of real project work: the first draft, the first design, the first line of code.
- Count everything in between. Calls, mail, forms, setup. If it is for this client and it is not the deliverable, it is onboarding.
- Note the waits separately. Days spent waiting for access or files do not cost hours, but they push the timeline, and the client should know about them.
- Repeat for the next two clients. Three onboardings give you a range.
Here is how the arithmetic works, with made-up numbers. If onboarding took four hours on a project quoted at forty, a tenth of the job went unpriced. On a project quoted at ten hours, the same four hours is a far bigger slice.
Let the Mac count the scattered hours
The trouble with measuring onboarding by hand is that it arrives in pieces: ten minutes on a form, half an hour on a call, twenty minutes fighting with a shared folder. Those are exactly the pieces you forget to write down.
Punchcard catches them without a timer. It notices which app is in front through the day and, at the closing time you set, prints a receipt: the top five apps with the time on each, the rest as MISC, and a day total. During onboarding the receipt tends to be heavy on Mail, Calendar, chat, the video call app and the browser, and light on the app where your real work happens. When that work app becomes the top line, onboarding is over.
The CSV export gives the detail: one row per session, with start, end, app, idle and seconds. Open it in Numbers and add up the sessions between your start and end dates. Tracking is free and never expires, and the CSV export works without a license; printing receipts after the first two needs the license, $9 once.
Be clear about one limit. Punchcard has no projects, no clients and no tags, so it does not know which client a session was for. If you onboard one client while working for another, write one line at the end of each day: “Thursday, about 1h 15m onboarding the new client.” The receipt keeps that line honest, because the day total is already counted. It also has no rates or invoicing; the hours go into your quote by hand.
Put the hours in the quote
Once you know what onboarding costs you, there are a few fair ways to charge for it:
- A line in the quote. “Project setup and kickoff, 4 hours.” A line the client can understand is easier to accept than a fee that seems to come from nowhere.
- A minimum project size. If onboarding is roughly fixed, very short projects are the ones that lose money. A minimum makes them worth taking.
- A faster onboarding. A standard questionnaire, a checklist of the access you need, a template project folder. Each one cuts time from every future client.
Whichever you choose, it should be a decision rather than a default. How to estimate hours for a quote when you never tracked the last job covers the rest of the quote, and How much time you spend on proposals that never get paid looks at the hours that come before the yes. Once the project is running, How to spot scope creep in your hours before the project ends helps keep it on budget.
Questions
Should onboarding be billed separately?
That is a choice about how you present your price. Some freelancers show it as its own line; others fold it into the project fee. Either works, as long as the hours are counted somewhere.
Does onboarding get faster with repeat clients?
Usually, because the access, files and paperwork already exist. That is one reason repeat work can earn more per hour than the same rate on a new client.
What if the client is slow to send what I need?
Note the waiting days separately and share the dates. A start date that depends on receiving access is a reasonable thing to put in the contract.