Drawing the Line: What a Consultant Bills For — and What Belongs to the Commons

The most common email I receive isn't a project inquiry. It's a question — usually a thoughtful one — about an architecture decision, a tooling choice, or a migration gone sideways. For years, I agonized over each one. Answer it and am I working for free? Ignore it and am I burning goodwill in a profession built on reputation?

It took me longer than it should have to realize the question was malformed. The line between what I charge for and what I give away isn't a wall. It's a ledger, and like any good ledger, it balances.

What Goes on the Billable Side

The rule I've settled on is simple: I charge for outcomes, context, and accountability. If a client needs me to understand their specific constraints, sit in their meetings, absorb their institutional history, and then stand behind a recommendation, that's consulting. It cannot be given away because it doesn't exist until a client and I build it together.

Concretely, this includes:

• Architecture and system design work, where the value is the synthesis of their particular situation
• Due diligence and technical assessment, where my judgment is the product
• Implementation with ownership — code shipped under my name carries my accountability, and accountability is never free
• Sustained advisory relationships, where continuity itself is the deliverable

Notice what's absent: answers to discrete technical questions. That's deliberate.

What Goes on the Free Side

Here is where most consultants get nervous, and where I've come to be generous on purpose. I answer public questions. I publish the scripts and small tools I build for myself. I write, in detail, about projects that failed.

The reasoning is not altruism — or rather, it isn't only altruism. Three things happen when you give away knowledge that is genuinely free to give.

First, the answers were already commoditized. If someone can get the full value of my expertise from a paragraph on a forum, that paragraph was never going to sustain a consulting engagement. The client who hires me isn't paying for the answer; they're paying to have the right question found, the answer adapted, and the consequences owned.

Second, public answers are a portfolio that sells while you sleep. A detailed Stack Overflow response or a well-documented GitHub repository does more credible marketing than any landing page. Prospective clients read them and think: this person explains things clearly. That's the entire pitch for a consultant, demonstrated rather than claimed.

Third, and least appreciated: teaching forces precision. Every time I've written up a failure — the time I underestimated a data migration, the quarter I misread a client's actual priorities — the act of explaining it publicly sharpened my own understanding. Writing about what went wrong is cheaper than a certification and more honest than a case study.

The Failure Write-Up as Strategy

Let me linger on failure posts, because they're the most counterintuitive item in the ledger. American professional culture, particularly in consulting, rewards the appearance of an unbroken winning streak. But clients are sophisticated. They know every technologist has shipped disasters. What they're actually screening for is whether you can diagnose a failure without flinching.

A candid post-mortem — what I got wrong, what it cost, what I changed — signals the exact trait clients are buying: judgment under uncertainty. I've had more inbound inquiries reference a failure write-up than any success story on my site.

Where the Line Actually Sits

So here's the working ledger, stated plainly:

Free	Billable
General answers to general questions	Answers adapted to your context
Open-source tools I built for myself	Tools built for your requirements
Post-mortems on my own failures	Risk assessment on your project
Public writing and talks	Private counsel and continuity

The dividing line, in every case, is the same: your specifics. The moment value depends on your codebase, your team, your deadlines, and my accountability for the result, it's work, and it's invoiced.

Some consultants worry this generosity cannibalizes the practice. In ten years, I can count on one hand the times someone took a free answer and used it to avoid hiring me — and in every one of those cases, they weren't a client I wanted anyway. The far more common outcome is the opposite: the free material is what brought them through the door.

A Closing Entry

A ledger, done honestly, tells you who you are. Mine says I sell judgment and accountability, and I give away knowledge that wants to be free. That trade has made me a better writer, a sharper engineer, and — not incidentally — a busier consultant.

If you're building a practice, I'd suggest drafting your own version of this ledger early. The line is easier to hold when you've drawn it deliberately, before the first awkward email arrives asking for just a quick favor.