Meet the Harpers

The partnership review was in a glass room overlooking Paddington station, for a heavily funded satellite internet startup I will not name in this essay. Overpriced espresso, a wall of displays still warm from the work I had shipped overnight: wireframes for sign-up, booking an installer, and the screen that tells you you are online. My rainmaker, Charlie, sat beside the client's CTO. The last funding round still glowed on the screen in nine figures. Charlie pointed at the journey map I had drawn and asked the CTO whether we could cut the steps and rebuild the flow on new cloud software before the runway chart turned red. Charlie said we had designed the answer that morning. He had not looked at me once. I nodded. The room heard efficiency. I heard my own work leaving under someone else's breath.

That nod was not surprise. It was a design choice. I had learned that conflict on a live account costs more than credit on a slide. I removed the friction the way I have removed friction elsewhere when the fee was large enough and the relationship fragile enough. Two and a Half Men mapped the geometry for laughs: Charlie lives on royalties and relationships, Alan pays the bills with expertise nobody prices correctly, Jake learns that satisfactory output is cheaper than excellence. The labour market files it under transformation. I have billed from inside all three costumes. Call it the Harper Effect once you have felt the nod land.

Your utilisation report measures the wrong relationship

Consulting firms do not pay for the best answer. They pay for the person who already holds the relationship when the answer lands. Partnership dashboards track relationship health, deal registration, and billable hours. They do not track who designed the journey that makes a transformation slide look credible. That is measuring credit assignment, not capability. The instrument is not broken. It is aimed at the wrong coordinate.

When a client promises AI will deliver a leaner operation, the translation is often specialist labour cut while the transformation narrative stays on the slide. The Paddington account is one instance, off the record. Investors and boards are not wrong to want efficiency. They are wrong to imagine it lands on the people who designed the journey or wrote the code underneath. The savings line is real. The distribution line is missing. That gap is where profit lives.

Deal registration is where value is captured

Org charts hide a quieter map. Wins are captured at deal registration, committee seats, and shared-vision slides. Value is built in design files and delivery rooms where nobody from the Global Executive Committee wants to stand. Charlie types hold the P&L keys: the joke in the hallway, the name on the steering slide, the nod that unlocks budget without anyone opening the journey map. Designer types map the flow, remove the friction, and invoice hours that vanish into someone else's utilisation target. Builder types write the code that keeps customers connected. The firm quotes the designer's rate to the client and attributes the win to the rainmaker. Margin expands. Nobody calls it extraction because the deck says digital transformation.

After we won a multi-million-pound satellite programme pitch, Charlie used the victory for a committee seat. My partnership track did not close loudly. I was quietly removed from the building. Marcus, a lead solution architect on the same account, was rewarded with implementation lead in a windowless room in Slough, patching legacy code at midnight while the savings narrative moved upstairs. I gained the knowledge that the system is extractive. Marcus did not gain autonomy over his own time. When AI arrives on the earnings slide, it is often his midnight work being described as an efficiency gain for someone who was not in the basement.

The savings get booked upstream. Vendors hold the slide.

Institutional Charlies do not need a Malibu beach house. They need a vendor partnership and a board narrative. When a large operator announces an AI-led transformation, savings get booked upstream in restructuring charges and margin guidance. Specialist labour gets liquidated downstream in headcount targets the market still applauds. The executive layer signs the programme. The vendor layer sells the operating model. The designer and engineer become the line items the slide replaces.

Titles help here the way they always help when proof would be inconvenient. A SVP or managing director on the slide excuses absence of the journey map. A partnership director on the account excuses absence of design authorship. Immunity is not diplomatic. It is operational: a ready-made exit from the moment someone asks who actually kept the service running. Charlie did not need to understand the flow. He needed my nod and a flight to Verbier once the signature landed. Large operators do not need every redundant role named on the org chart. They need applause for efficiency while the people who designed and built the thing being automated are steered out of the credit line.

The domestique burns their legs so the leader gets the jersey

In professional cycling, a domestique rides in the wind so the team leader can sprint. They fetch water, close gaps, and sacrifice their own standings so someone else's name reaches the podium. The leader gets the yellow jersey. The domestique gets sore quads and a line on the team sheet most fans never read.

You feel this before you can explain it. Your lungs burn while someone else's quote is printed. Your thighs shake on the climb you paced for another rider. You know the effort was real even when the credit was allocated elsewhere. Contribution and recognition are different currencies. Grab for one mid-race and you often lose both.

I chose the nod because the fee was larger than the fight

One spring afternoon in 2021 I handed Charlie a design-led digital transformation framework without securing lead partner designation on the account. I convinced myself that being the brain was enough. In consulting, the relationship holder holds the P&L keys. I traded intellectual property for approval on the next phase. That is the same trade I made in the Paddington boardroom when I stayed silent rather than correct a client-facing claim I knew was wrong. Conflict threatened the account. The account was paying.

I am not telling this as a victim story. I priced the nod. I knew what silence bought: continued billing, a seat at the next workshop, no awkward partner conversation about who actually designed the journey. Marcus did not get that choice. He got the basement, the midnight patches, and a utilisation target that treated his excellence as a cost centre. That household runs on the bargain. So does a transformation programme when savings are announced before autonomy is offered to the people who built the thing being automated.

The comfortable case for giving without counting

Adam Grant argues in Give and Take (2013) that generous contributors who help without immediate return often build the highest-trust networks and end up among the most successful. Givers, matchers, and takers populate every firm. Grant's evidence suggests the most effective givers are strategic rather than self-sacrificing: they contribute widely but protect their time and credit when it matters. Read generously, the case is comforting for builders: keep delivering excellence, keep handing over the hard intellectual work, and reputation will eventually convert into power. It requires believing that consulting is a high-trust marketplace where social capital compounds fairly and transformation programmes reward the people who made them possible.

That paragraph deserves its full strength because many builders want it to be true. It would mean the nod in Paddington was an investment, not a theft. It would mean Marcus's midnight patches were compounding into partnership rather than subsidising someone else's committee seat. The Trades Union Congress report on algorithmic management, published in May 2026, finds that digital transformation paths tend to deskill specialist labour and centralise decision-making power in fewer hands. tuc Robert Greene's The 48 Laws of Power (1998), Law 7, states the quieter rule: get others to do the work, then take the credit. Reputation compounds for extractors when the org chart is designed to capture wins upstream. Transformation compounds savings for vendors and executives when specialist labour is priced as replaceable. Charlie did not need a high-trust network. He needed my winning slide and my silence while he booked the flight.

The gap between the person who builds value and the person who captures it is where profit lives in this industry.

Over-delivering for systems that measure relationship credit instead of network survival is not being a giver. It is being farmed.

Marcus is still in Slough at midnight, patching the code that keeps customers online, while the person who took the credit plans the next transformation off his labour.