Liquid Lock
An operating partner practice for venture and private equity backed companies

Most portfolio companies do not have a marketing problem.

They have a machine problem, and marketing is where it shows first. Liquid Lock reads the whole operating engine, then fixes the one part that is actually capping the multiple.

7
departments read in every diagnostic, not the one that called
4wks
to a written read the board can act on, priced to scope before day one
1
binding constraint at a time. Plans that attack five things move none of them
Where the reading happens

Every function that touches the exit.

A pipeline number is downstream of pricing, territory design, onboarding and whether the product does what sales says it does. Liquid Lock does not start where the org chart says the problem is. It starts with the documents, department by department, and follows the money to where it is actually leaking.

See the full lens
The argument

Hiring against a symptom is the most expensive habit in a portfolio.

Three things Liquid Lock believes about growth in an institutionally backed company, each one earned the slow way.

The symptom is not the system

Marketing gets blamed because it is the last link in the chain and the easiest to see. By the time pipeline is soft, the cause is usually three departments upstream and eighteen months old.

A function can only fix its own function

A chief marketing officer cannot fix a comp plan. A chief revenue officer cannot fix a product gap. Someone has to be allowed to read all of it, and that person cannot report into one of the functions being read.

Diagnosis is the cheap part

Four weeks to name the real constraint costs a fraction of a year spent hiring against the wrong one, and a great deal less than the year after that when the hire does not work.

The entry point

It starts with four weeks.

The Diagnostic is the product. Scoped to the company, one department or all seven, priced before day one, up to forty conversations, every source system read against the board pack, and one page at the end that names what is capping value and what it would take to remove it.

Week one
Read everything

The board packs, the model, the source systems, the org chart and whatever the last consultant left behind. No opinions yet.

Week two
Talk to everyone

Up to forty conversations, top to bottom. The reps and the support team know where it breaks and nobody has asked them.

Week three
Try to kill the theory

The hypothesis goes back to the data. What survives is the finding. What does not gets written down anyway.

Week four
One page to the board

Ranked by what it costs, with what Liquid Lock would do about each item and what it would take. Then you argue with it.

Selected work

From two million to seven, then acquired.

Company names withheld. Every figure came from the company’s own reporting, and references from both the sponsor side and the founder side are available at the second conversation.

SituationVenture backed cybersecurity software at roughly one to two million in revenue, in a category buyers did not yet have a name for.
What was foundThe company was selling a capability its buyers did not yet have a budget line for. Every deal was an education cycle, pipeline was being read as demand, and marketing spend was scaling the confusion faster than the category.
What changedThe go to market was built from the ground up, positioning through pipeline, with the sales motion and the marketing engine designed as one system rather than two departments.
Read both engagements
Revenue, eighteen monthscompany reporting
What it was worth
Six to seven million in revenue inside eighteen months, and an acquisition.

If you are about to approve a hire, get a read first.

Four weeks, a price agreed before day one, and a written answer you can take to the board.

Start with a diagnostic