A Year Into Consulting: What I Would Tell Myself at the Start

About a year ago I started taking on clients under my own consulting practice after two decades of working inside organizations. Communications strategy, video production, web and app builds, AV design, and AI workflow integration, which sounds like five businesses until you notice they are all the same business: helping organizations say what they mean through whatever channel the moment requires.

The jump was not a leap into the void. I had been consulting on the side for years, and two decades inside ministries and organizations meant I had sat on the client's side of the table many times, watching outside vendors serve us well or serve us badly. I thought that vantage point meant I knew what I was doing. It helped. It was not the same as knowing.

A year in, with real invoices sent and real mistakes made, here is what I would tell the version of me who was drafting that first proposal, nervous about the pricing and secretly thrilled about the letterhead.

Scope in writing is a kindness, not a formality

Every strained moment I have had with a client this year traces back to something that felt too obvious to write down.

The rhythm is always the same. In the kickoff conversation, everything is warm and aligned. Of course the project includes that. Naturally we will handle this. Both sides nod, both sides mean it, and both sides walk away with a slightly different picture in their heads. Nothing is wrong yet. The pictures are only a few degrees apart. But six weeks later those degrees have compounded, and now there is a conversation happening that neither of you enjoys: about whether the photo editing was included, whether "launch support" meant two weeks or two months, whether the second round of revisions was in the number.

Early on I resisted heavy paperwork because it felt like distrust dressed up as professionalism. I had it exactly backwards. The document does not exist because you distrust each other. It exists so that six weeks in, neither of you has to rely on memory of a phone call. Memory is a terrible archive. It edits toward what each party hoped. The written scope is the neutral referee both of you appointed back when everyone was friends, which is the only time a neutral referee can be appointed.

So now everything goes in writing: deliverables, dates, what is included, and, just as important, what is not. That last list feels awkward to write and pays for itself every single time. "This project does not include ongoing content updates after launch" is one sentence. The conversation that sentence prevents is a week of tension and a bruised relationship. A clear no in the scope is a kindness delivered early, at the cheapest possible price.

Report before you are asked

The habit that has done the most for client trust this year costs me minutes: a short weekly note. What happened this week, what is happening next, what I need from them. Three small paragraphs, sometimes three bullet points, sent whether or not anything dramatic occurred. Especially when nothing dramatic occurred.

Here is what I misunderstood at the start. I assumed clients were evaluating my output. Mostly, in between deliverables, they are evaluating their own anxiety. When a client hears nothing, they do not think "he is surely making steady progress." They think about the money going out, and the thing they cannot see, and the last vendor who went quiet before going sideways. Silence is a screen, and people project their worries onto it. I have come to believe clients rarely fire people over slow progress. They lose confidence over silence, and then the next small stumble becomes the story that confirms the fear.

The weekly note deletes the screen. Progress becomes visible, blockers surface while they are still small, and the "what I need from you" line gently keeps the client accountable for their side of the timeline, which matters, because by far the most common cause of a slipped deadline is an approval or an asset sitting on the client's desk. When the note has been reporting that dependency for three consecutive weeks, the schedule conversation is already had. Nobody is surprised, and nobody is blamed in the dark.

Nobody has ever complained about being too informed. A few clients have told me the note is the reason they came back. Minutes a week. There is no better trade on my ledger.

Productize the repeatable middle

My early proposals were all custom, which meant every one took an evening. Custom scope, custom phases, custom pricing logic, invented fresh each time, as though I had never done a website or a video project before. I told myself this was craftsmanship. It was actually a failure to notice my own patterns.

Because the truth is that every engagement has three parts. The beginning and the end are genuinely unique to the client: their goals, their audience, their particular situation, the strategy that fits them and no one else. But the middle, the process itself, repeats. Discovery follows the same arc. Website launches need the same checklist every time. Handoffs require the same documentation, the same credentials list, the same training session. I was hand-crafting the exact part of the work where hand-crafting adds nothing.

A year in, most engagements assemble from pieces I have standardized: a discovery process I run the same way every time, a launch checklist refined by every launch before it, a documented handoff that means the client is never stranded when the project ends. Proposals that took an evening now take an hour, and they are better, because each standardized piece carries the accumulated fixes from every previous project. The checklist remembers what I would forget.

Here is the part I did not expect: standardizing the middle did not make the work feel like an assembly line. It made the work better where it counts, because custom thinking now goes where it matters, into the client's actual strategy, not into re-inventing my own process weekly. The craft did not disappear into the templates. It got concentrated.

Say no earlier than feels polite

Now the expensive lesson. The engagements I regret this year were all visible in the first conversation. Every one. I can replay each kickoff call and point to the exact moment the signal appeared, and to the exact moment I talked myself past it.

The signals are not subtle. Vague goals that stay vague after two rounds of clarifying questions, which means the goal is not undiscovered, it is nonexistent. No owner on their side, nobody whose actual job is to answer questions and approve things, which means every decision will take three weeks and a committee. A budget allergic to the outcome they described, which is not a negotiation problem but an expectations problem, and expectations problems do not improve after money changes hands.

I saw each of these and proceeded anyway, for the reasons everyone proceeds anyway. The calendar had a gap. The person was likable. I believed, with the optimism of someone new to running his own shop, that professionalism could compensate for a missing foundation. It cannot. Execution cannot fix what alignment never established.

The arithmetic I finally accepted: a kind, early no costs one awkward email. A wrong yes costs a quarter. Not just the project's weeks, but the drag it puts on everything adjacent, the energy it siphons from good clients, the discount it quietly negotiates against your confidence. And declining is not even a rejection, done right. Twice this year a graceful "I am not the right fit for this" turned into a referral elsewhere and a better-fit project back from the same person later. The no was the beginning of the relationship, not the end of one.

The relationship outlasts the project

Which brings me to the thing I most misunderstood about how this business actually works.

I spent my first months thinking about pipeline the way the internet told me to: marketing, visibility, funnels, follow-up sequences. All real things. But a year of actual revenue tells a simpler story. Most of my work now arrives through people I served well the first time. Repeat engagements from clients whose first project went cleanly. Referrals from people who watched the weekly notes arrive and the handoff documentation actually get delivered. The proposal got them in the door once. The follow-through is the entire marketing budget.

This reframes everything on the list above. The written scope, the weekly note, the standardized handoff, the early no: none of those are project management tips. They are all the same act, which is treating the person across the table like someone you will still be working with in five years, because if you do the first four things, you will be.

So treat every handoff like the beginning of the next engagement, because it usually is. Leave the documentation better than anyone asked for. Make the last week of the project as attentive as the first. Twenty years inside organizations, I watched vendors reveal themselves in exactly those final weeks, when the invoice was already assured. Now that I am the vendor, that is the reputation I am spending my year building, one clean ending at a time.

That is the note I would slide across the desk to the me of a year ago, right before he sent that first proposal. He would probably nod along and then learn all five the long way anyway. Some tuition apparently has to be paid in person. But it would have been nice to know how much of this job is just keeping small promises visibly, repeatedly, in writing. That part, it turns out, was never consulting. That was the whole business.