Client Retrospective: What Went Right This Year

Every consulting practice has a bad year at some point. 2025 was not that year for me. Looking back at the client work I took on, the projects I delivered, and the invoices I collected, the patterns behind the good year are worth naming. Here is what actually went right and why.

The Work That Worked

Three project types delivered consistently:

Platform builds: backend plus frontend plus deployment, 4 to 8 week scope
Audit and fix: existing system, find what is broken, ship patches
Content automation: scraping, transcription, publishing pipelines

All three share a common shape: clear scope, technical depth, and a concrete deliverable.

The Scoping Discipline

The biggest change this year was my scoping discipline. Every project got a written scope document with three explicit sections:

What is included
What is excluded
What triggers a change order

The exclusions section was the highest-leverage addition. Most scope creep comes from unstated assumptions about what is included. Stating the exclusions upfront prevents those conversations later.

The Pricing Shift

I moved more projects to fixed fee this year. Hourly work has a ceiling. Fixed fee scales with value delivered, not hours spent. AI tools made this shift possible because my delivery speed increased without my hourly rate increasing. Clients paid for outcomes, not time.

The Communication Rhythm

Weekly written updates, monthly video calls, async Slack for everything else. That rhythm fit most of my clients. The ones who wanted daily stand-ups and synchronous everything were the ones who burned out the relationship. Structured communication wins.

The Handoff Lessons

Every project ends with a handoff. The projects that went smoothly shared three traits:

Documentation written during the build, not after
Admin UI for non-technical edits
A clear support agreement (or a clear end)

The projects that ended messily skipped one of those three.

What I Would Change

I took on one project that did not fit the shape. It produced revenue but consumed disproportionate energy. Next year I will say no faster to projects that do not match the three good shapes above.

A good consulting year is not one magic client. It is a set of repeated patterns executed with discipline.

The Referral Flywheel

Most of my 2025 clients came from prior clients. Not from cold outreach. Not from content marketing directly. From people who worked with me, shipped the project, and told someone else. That flywheel only spins if the work is good and the handoff is clean. Every project is a potential referral or a potential anti-referral. Treat them that way.

The Metrics I Actually Track

Revenue per project (not per hour)
Average project duration (watch for scope creep)
Time from inquiry to signed contract (sales cycle health)
Percentage of revenue from referrals (relationship health)

Four numbers. Reviewed monthly. More than enough to run the practice.

For a starting framework, see the statement of work templates as a structural reference.