Why does the first project with a new client always take longer?

Because it carries hours that are not the work: the kickoff call, getting access to their systems, reading their brand files, and learning how they give feedback. Those hours are real, they happen once per client, and they are almost never in the quote. On a 3,000 fee quoted at 30 hours, ten hours of onboarding turn 100 an hour into 75.

Should I charge for onboarding a new client?

If there is a realistic second project, the second project pays the onboarding back, because it has none of those hours in it. If this is a one-off, nobody else will ever pay for them, so they belong in the first fee. Either way, log them on the project so you know what they were.

How do I know if a new client is worth it?

Do not judge the first project alone. It is structurally the worst-paying one. Divide the client's total fees by every hour the client has cost you across all their projects and compare that to your floor. In the example, 75 on the first project and 100 on the second is 85.71 over both, which clears a floor of 85. If the second project never arrives, the first number was the real one.

Why the first project with a new client pays the worst

Not because of scope. The kickoff, the access, their files and learning how they give feedback are hours nobody quoted, and they only exist because the client is new. Divide the fee by all of them, then read the client over two projects, not the first one alone.

Not because of scope. The first project with a new client carries hours that are not the work: the kickoff call, the access, their brand files, and learning how they give feedback. Nobody quoted them, they only exist because the client is new, and they land on the first fee. On a 3,000 project quoted at 30 hours, ten of those hours turn 100 an hour into 75. The second project has none of them. That is why the number to read is the client over two projects, not the first project on its own.

The hours nobody quoted

Think about what the first week with a new client actually contains.

The kickoff call that was booked for thirty minutes and ran to ninety, because that is where you found out what they meant. The access: accounts created, invites accepted, the CMS login that took three emails and a password reset. Their files: the brand guide, the previous agency’s work, the folder with fourteen versions of the logo. Their process: who signs off, how feedback arrives, how many people are copied on it, and the first round of “we do it like this here”.

None of that is the deliverable. All of it is on the clock before the deliverable starts.

Two things make these hours different from an ordinary overrun. They are not scope: the client did not add anything, and nobody changed their mind. And they happen once. A returning client’s second project starts on Monday with the access already working and the feedback loop already known. The onboarding is a one-time cost, and the first project is where it gets booked.

Quoted 100, paid 75

The arithmetic is the same division as always: fee over every hour the job took.

	Fee	Hours	Effective rate
As quoted	3,000	30	100
With onboarding	3,000	40	75

Against a floor of 85, the project you quoted at 100 pays 75. Nothing went wrong. The work took the thirty hours you said it would. The ten hours on top are the cost of the client being new, and they arrived before the work did.

This is worth separating from a fixed-price overrun, because the fix is different. Scope creep is the client adding work, and the answer is a change request. Onboarding is you learning the client, and there is no change request for that. The answer is to know it is coming and decide in advance who pays for it.

Same client, same fee, two projects

Here is what the same client looks like when the second project arrives.

	Fee	Hours	Effective rate
Quoted	3,000	30	100
First project	3,000	40	75
Second project	3,000	30	100

Same fee, same client. The dip in the middle is the onboarding, and the second project is where it comes back.

Over both projects the client has paid 6,000 for 70 hours, which is 85.71 an hour. That clears the floor, just. A third project at the same fee takes the client to 9,000 over 100 hours, which is 90, and from there the onboarding is a rounding error.

The second project has no onboarding in it. That is not a bonus, it is the structure: the first project made a loan, and the second one is where the client pays it back.

Why this is a client number, not a project number

Judge the first project on its own and every new client looks like a bad one. That is not a sign you are pricing badly. It is what a first project is.

The number that answers whether a client is worth having is the effective rate per client, across every project they have given you. Ranked that way, a client at 75 and then 100 is a client at 85.71, and the ranking tells you the truth about the relationship rather than the truth about one invoice.

The same number turns the one-off into a decision. If there is no second project, because the client wanted one landing page or one audit and nothing more, then 75 was not a loan. It was the final rate. The onboarding you absorbed will never come back, and a loan nobody repays is a gift. Gifts are fine when you meant to give one.

What to do before the first quote

Log the onboarding on the project, not on admin. Kickoff, access, their files, their process. Those hours belong to this client, and the moment they land in a general admin bucket they stop being attributable to anyone. Keep them on the project and the 75 shows up where you can see it.

Ask whether there is a second project. Not as a sales question, as a pricing one. “Is this a one-off, or the first of a few?” changes the quote. A client with a roadmap can be quoted at 100 with the onboarding as an investment. A client with one deliverable cannot.

If it is a one-off, put the onboarding in the fee. Ten hours at your quoted rate is 1,000. A 4,000 fee over 40 hours is the 100 you meant to charge in the first place. Say what it covers, because it is true: getting set up in their systems and learning how they work is real work that only they benefit from.

Read the client after the second project, not the first. One project at 75 is a number. Two at 75 and 100 are a client at 85.71, and that is the one to compare against the floor. If the second project has not arrived after a reasonable while, the first number was the real one, and the client belongs in the under-the-floor list with everyone else who is there.

Do the onboarding once. A kickoff agenda, an access checklist, a standard file request. The repeatable parts get shorter every time you run them, which does not help with this client but does shrink the loan you make to the next one.

Where CronLoom comes in

CronLoom has no onboarding category and does not send invoices. What it has is the division, kept per project and per client.

Set the first project up with its fixed fee, log the kickoff and the access against it like any other hour, and the project’s effective rate is fee over every hour that landed on it. At 40 hours it reads 75, and it is flagged as under the floor you set. Then the second project lands, at 100, and the client view shows what the two of them add up to: 85.71, above the line. That is the number the first project could never show you on its own.

The budget alert helps in the middle. Set the project’s hours to the 30 you quoted, and the 80% alert arrives at hour 24, which with a new client is often while you are still finding your way around their CMS. That is the right moment to know the work has not started yet and the hours have.

The effective hourly rate calculator does the single division if you want to check one project by hand. If you want it running per client while the hours happen, join the waiting list.

Try it on your newest client

Take the most recent client you started with. Add up the hours from the first email to the first hour of real work: the call, the access, the files, the reading. Add them to the project’s hours and divide the fee by the total.

Then ask the only question that matters about that number: is there a second project, and did you price the first one as if there would be?