The Referral That Cost Me Six Weeks

When a Good Source Becomes a False Signal

The referral came from someone I respected. That should have been a green flag, and in terms of the client's intentions, maybe it was. But I treated the referral as a signal that I could skip the parts of my process that exist for a reason.

I did not scope the project carefully. I did not set up tracking from day one. I gave a flat quote based on a quick conversation and started working on a handshake.

Six weeks later I was deep in a project that had grown to twice its original size, billing at a rate that made sense for the original scope and nowhere near sense for the actual one.

The Scope Creep Was Slow

It always is.

The first addition felt minor. A second deliverable that seemed like a natural extension of the first. Then a round of revisions that went three rounds deeper than any of us expected. Then a new stakeholder who needed everything re-explained and several sessions to get aligned.

Each of these felt manageable in the moment. The problem was I had no running total. I was not tracking hours by phase or by original scope versus additions. I just had a pile of logged time that was growing and a fixed invoice at the end.

By week five I looked at my hours and realized I had already passed my quoted amount and still had two weeks of work left.

Why I Had Not Caught It Earlier

I was checking my hours on a roughly biweekly basis. That gap is too long.

If I had been reviewing my time against the original estimate weekly, I would have caught the overage in week three. I could have had a reasonable, non-confrontational conversation about scope before emotions or sunk costs got involved.

Instead I had it in week five, which felt accusatory even though I was not accusing anyone of anything. The client got defensive. I felt like I was asking for something unreasonable. The conversation was harder than it needed to be.

What I Track Now on Every Project

Regardless of how the client comes in or who referred them, I run the same process.

I set up the project in Time-Trak before I do a single hour of work. I define the original scope in my own notes. I set a rough hour budget for myself. And I check in on hours weekly, comparing where I am against that budget.

That weekly check takes about five minutes. It is not a formal review. I just look at the number.

If I am at fifty percent of my budget and fifty percent through the project, I keep going. If I am at seventy percent of my budget and thirty percent through the project, I send a quick note to the client that week. Not alarming. Just a heads up that we are running ahead of the original estimate and I want to flag it before we go further.

That conversation, had early, is easy. Had late, it is not.

The Referral Lesson

Referrals are not a reason to skip your intake process. They are a reason to be grateful and then still do your job properly.

The client's intentions were fine. The scope problem was not their fault any more than it was mine. It was a structure problem. We did not have a shared understanding of what the project contained because I had not done the work to establish one.

Time tracking does not fix a bad scope conversation. But it surfaces the problem early enough that you can have a better one.

Six Weeks of Learning

I billed about sixty percent of what I should have earned on that project. The referrer still sends me work, and I still take it. But I run the same process regardless of the source now.

The shortcut I took saved me maybe thirty minutes upfront. It cost me several thousand dollars and a month of resentment I had mostly aimed at myself.

Track your time, bill every minute.

Time-Trak is a native Mac and Windows time tracker with a floating timer, automatic screenshots, and one-click invoicing.

Free during beta.

macOS + Windows · Floating widget · Auto screenshots