Latest
You Don’t Own Anything AnymoreThe Budget Decided How My Department Was ShapedWhy Your Competitor’s Book Is Working and Yours Would NotWhy Are These Guys Smiling? A Business Book That Became a Wrestling MemoirPangram Wants to Decide Who Gets PublishedWhat You Have Enough Material For Right NowWhen a Book Is the Wrong ToolThe Woke VirusGalactic InvasionChatGPT Turns Four: From a Free Research Preview to GPT-6What’s New at The Writing King: Week of November 1, 2026Diwali: The Festival of Lights and the Story Behind the LampsHow Much Water and Power Does Heavy AI Use Take? I Ran My Own NumbersBad Boys: Ride or Die (2024)Anti-Communism Week: Remembering the Writers Communism SilencedVesuvius Day: The Teenager Who Wrote Down Pompeii’s Last DayVoyager 1 One Light-Day: Fifty Years to Travel One Day of LightVellum Added an Optional AI Feature. A Pile-On Killed It in a Day.Are AI Subscriptions Losing Money? The Gym Membership Math Says NoAI Terms Every Writer Should Know, and Why Each One MattersWorking While Sick: What 24/7 On Call Cost MeHe Banned AI From His Writing Group. His Own Cover Got Called AI Slop.Who Writes the Fake Fan Mail Authors Get? Inside the Scam CompoundsSMS Appointment RemindersJoe Rockey: Ghostwriting His BookFree BooksDarrell Stern: Stop Being Invisible, Become UnmissableHow to Turn Your Expertise Into a Book People Want to Read | The Expert MethodWhat’s New at The Writing King: Week of October 25, 2026Challenger Remembrance Day: The Engineer Who Wouldn’t SignJoel Salomon: The Truth About MoneyReddit Is Putting Up a Login Wall. Wikipedia Won’t Be Far Behind.Victoria Chemko: The Body Is the First TechnologySir Patrick Stewart: A TributeA Year in the Bank: ADHD, Face Blindness and the Freedom to Walk Out | The Impossible Puzzles Show, Episode 326A Yale Economist Says We Won’t Be Missed. He Forgot the Bread Line.Walter Koenig: A TributeAI Has Paid Off Outside Tech. Apollo Is Reading the Wrong Scoreboard.I Don’t Post Bad ARC Reviews. I Send the Author a Note.The Little Red Book of Stuff That Works!Your Kids Are Your Own FaultGrow a PairYou’re Broke Because You Want to BeIt’s Called Work for a Reason!No Time for TactShut Up, Stop Whining, and Get a LifeWilliam Bessette: AI Enablement and Child Welfare TechnologyFree Book Planning ToolsWhat’s New at The Writing King: Week of October 18, 2026Ghostwriting by the Numbers: Timelines, Word Counts and the First Call
The Writing King Your Ethical Ghostwriter. Your Story, Done Right.

Working for Yourself

Build a Profitable Consulting Practice

The Part of Consulting Nobody Teaches

Expertise does not pay the bills. Contracts do.

My first consulting job came from a college professor almost seven feet tall named Fred, near the end of the semester where I first touched a computer. Fixing bugs in general ledger programs on a TRS-80 with sixteen kilobytes of memory and two floppy drives.

I was overconfident, underprepared and completely naive. I had my eye on the six hundred dollars and didn’t realize I had no idea how to fix the programs until I was in too deep to get out.

Looking back I did everything wrong that was available to do wrong. I didn’t validate my assumptions. I didn’t write a statement of work. I didn’t terminate the contract when it became obvious I was over my head.

Forty years later, most consultants I meet are still making some version of those mistakes, and for the same reason: they’re good at their craft, and nobody taught them the other half. Knowing your field cold doesn’t get you paid. Contracts do. Clients who pay on time do. Walking away from the wrong engagement before it eats a year does.

Free work: what was promised and what came backA comparison drawn from the free work story in the sample chapter. A nonprofit promised referrals from wealthy board members in exchange for an unpaid database project. Richard spent three weeks on it and delivered a working system, and what came back was a thank-you letter and no further work.Free work: what was promised and what came backThe nonprofit story from the sample chapterPromisedReferrals from wealthy board membersA retail chain ownerA manufacturing companyA venture capitalistFuture paid workDeliveredThree weeks of unpaid workA new system that worked wellA nice thank-you letterNo referralsNo further work
Free work: what was promised and what came backA comparison drawn from the free work story in the sample chapter. A nonprofit promised referrals from wealthy board members in exchange for an unpaid database project. Richard spent three weeks on it and delivered a working system, and what came back was a thank-you letter and no further work.Free work: what was promised andwhat came backThe nonprofit story from the sample chapterPromisedReferrals from wealthy board membersA retail chain ownerA manufacturing companyA venture capitalistFuture paid workDeliveredThree weeks of unpaid workA new system that worked wellA nice thank-you letterNo referralsNo further work

Why the book says never work for free: the promised referrals almost never materialize.

What is inside Build a Profitable Consulting Practice?

What do readers say about Build a Profitable Consulting Practice?

Amazon reviews of the previous edition. 2 of them, averaging 5.00 out of 5.

⭐⭐⭐⭐⭐ Richard Makadok, Purdue University Krannert School of Management

Great textbook for any college course that includes a field-study project for a client. Last year, this book helped my students to avoid many subtle pitfalls in their client relationships for a field-study project in my course, so I’ve assigned it again this year. Also, the author generously made time to give my class a Q&A session via Skype.

⭐⭐⭐⭐⭐ Author from South Africa

A fabulous book for anyone setting about managing a project, whether large or small, business or personal. The author clearly has tons of valuable experience in this area and has ‘been there, done that.’ One isn’t reading a bunch of theory that’s not backed up with real, live, hands-on production. A very worthwhile read.

Who should read Build a Profitable Consulting Practice?

Why consultants fail, and what the book covers
Where consultants fail What the book covers
They price too low Pricing strategies that generate profit
They struggle with cash flow Payment structures that protect cash flow
Clients don’t respect their boundaries Professional boundaries and demanding professional respect
They get pulled into free work Avoiding free work traps
They treat the business side as someone else’s problem Client management, contracts, stakeholders and online presence

Why did I write Build a Profitable Consulting Practice?

Richard Lowe, the Writing King

Forty years of consulting engagements, beginning with a six hundred dollar job I was unqualified to take. Twenty of those years were spent as Director of Computer Operations and Technical Services at Trader Joe’s, managing budgets, vendors and complexity at scale, which is the other side of the table from the consultant. I’ve hired them and I’ve been them.

► Behind the Book: Build a Profitable Consulting Practice
How this one got written, what went wrong, and what got cut.

► My First Consulting Job Paid $600. I’d No Idea What I Was Doing.
One story from behind this book.

What do people ask about Build a Profitable Consulting Practice?

Who is Build a Profitable Consulting Practice for?
Consultants at any stage: those transitioning from corporate employment, struggling with problems in an existing practice, or looking to scale to higher-value clients. The first edition, How to Manage a Consulting Project, was the course textbook at Purdue University’s Krannert School of Management (now the Mitch Daniels School of Business) four years in a row, for students doing field-study projects with real clients.
What makes Build a Profitable Consulting Practice different from other consulting books?
Practical guidance from the 40+ years since the author’s first consulting job, including two decades as Director of Computer Operations and Technical Services at Trader Joe’s and years of direct consulting experience. Every problem covered is one the author has watched play out repeatedly across real clients and real engagements. No theory. No frameworks. War stories with the lessons still attached.
What topics does Build a Profitable Consulting Practice cover?
Pricing strategies that generate profit, payment structures that protect cash flow, client management, professional boundaries, contract negotiations, stakeholder relationships, international consulting, online presence, managing testimonials and referrals, and using AI as a billable service offering.
Is Build a Profitable Consulting Practice a revised edition?
Yes. This revised edition adds new chapters on demanding professional respect, avoiding free work traps, and building the online presence modern consulting requires. Twenty-nine chapters total.
Why do most consultants fail?
Not because they lack technical skills. Because they never learn the business side. They price too low, work for clients who don’t respect boundaries, struggle with cash flow, and treat the business fundamentals as someone else’s problem. They aren’t. They’re your problem, and this book shows you how to handle them.

Also in Working for Yourself

The contract is the part that protects you

The craft is what you already have.

BUY FROM INGRAMSPARKAMAZONKOBOREAD A CHAPTERTABLE OF CONTENTS

Paperback and ebook.

A chapter

Build a Profitable Consulting Practice

Working for free is the fastest way to destroy your consulting practice. Free work devalues your expertise, attracts the wrong clients, and wastes time you could spend on activities that generate revenue. The exceptions are few and deliberate: a real school internship, a capped amount of pro bono work, and a short discovery call.

Most consultants fall into the free work trap because they think it will lead to paid opportunities. Potential clients promise future projects, referrals, or long-term relationships in exchange for free consulting. These promises almost never materialize, and you end up doing real work for imaginary compensation.

I learned about free work the expensive way during my second year of consulting. A local nonprofit organization contacted me about upgrading their donor management system. They explained that their budget was limited, but they had connections with several wealthy board members who might need consulting services for their businesses.

The nonprofit director painted a compelling picture of future opportunities. She claimed that one board member owned a chain of retail stores, another ran a manufacturing company, and a third was a venture capitalist who funded tech startups. If I could help them with their database project, she was sure they would recommend me for lucrative paid work.

I spent three weeks analyzing their existing system, designing a new database structure, and implementing the migration. The work was complex because their data was messy and their requirements kept changing. I treated it like a paid project, delivering the same quality I would provide to any client.

The project was successful. The new system worked well, and the nonprofit was thrilled with the results. They sent a nice thank-you letter praising my expertise and professionalism. But none of the promised referrals materialized. The board members never contacted me, and the nonprofit never hired me for additional work.

Those three weeks of free work could have been spent marketing to paying clients, improving my skills, or developing new service offerings. Instead, I gave away my expertise and got nothing in return except a warm feeling about helping a good cause.

The problem with free work is that it attracts people who don’t value consulting services. Clients who expect free work rarely become clients who pay market rates. They’re looking for cheap solutions, not professional expertise, and they’ll continue seeking free alternatives instead of paying for quality.

Table of contents

Build a Profitable Consulting Practice

  • What is a consulting project?
  • Statement of work
  • Pricing and contracts
  • Pricing models and payment arrangements
  • Never work for free
  • Red flags
  • Reading your client
  • Controlling change
  • Controlling chaos
  • Communicating with the client
  • Meetings
  • Managing executives and stakeholders
  • Building and managing teams
  • Remote work
  • International and cross-cultural work
  • Record everything
  • Errors and omissions insurance
  • Demand respect and give it
  • When it goes south
  • The end of the project
  • Marketing yourself between projects
  • Testimonials, referrals, and recommendations
  • Your website and online presence
  • Outsourcing
  • Using virtual assistants
  • Project management tools
  • CRM and business tools
  • Using AI on your projects
  • AI consulting as a service offering
  • Conclusion
  • Index
0 comments

No comments yet. Yours can be the first.

Was this useful?