Jeremy Foreshew
A practical decision method

Theory sucks.
Proof is better.

The Proof Loop turns a messy business problem into an evidence-backed next move.
Diagnose the actual issue, find the useful pattern, adapt it, test it, then make a clean call.

Why it exists

Most teams do not have an idea problem. They have a diagnosis problem.

When the room has plenty of opinions and no shared read on reality,
the loudest theory gets mistaken for strategy.

01

The symptom gets treated as the cause

Weak conversion can be an offer issue, a trust issue, a message issue, or a traffic issue. Jumping straight to execution makes expensive theater out of the wrong answer.

02

Borrowed tactics lose the reason they worked

Copying the visible move is easy. Understanding the audience, context, timing, and mechanism underneath it is where strategy begins.

03

Teams launch, then keep the story they wanted

A test only teaches you something if the team defines what proof looks like before the results arrive and acts on the answer afterward.

The method

From messy signal to
a clean decision.

The loop gives the work a shape. No wandering brainstorm. No fuzzy experiment. No soft landing where everyone keeps their favorite opinion.

01

Diagnose the real problem.

Slow down just enough to stop solving the wrong thing. What changed? Who is affected? What else could explain it? What would prove the current theory wrong?

02

Find working patterns.

Look at competitors, adjacent categories, creators, marketplaces, sales motions, and the weird corners of the internet where a similar problem has already been solved.

03

Adapt the pattern.

Fit the mechanism to the customer, offer, timing, voice, channel, budget, team, and actual constraints. This is where borrowing turns into strategy.

04

Prove it with a clean test.

Turn the idea into a bet with an audience, condition, metric, win condition, and kill condition. The result has to tell the team something useful.

05

Close the loop.

Read the result, make the call, and decide what changes next. The learning does not count until the team has changed the behavior around it.

The output

Reality gets a vote. Then you make the call.

The goal is not to be right in the meeting. The goal is to know what to do after the work has met the market.

Call 01

Kill

The premise did not hold. Stop spending energy defending it.

Call 02

Rework

The signal is interesting, but the execution or condition needs a better shape.

Call 03

Keep

It works. Keep it in the mix and give it the operating discipline it deserves.

Call 04

Scale

The proof is there. Put more behind the move with your eyes open.

Start here

Bring one messy problem.
We will give it a better shape.

For growth, GTM, positioning, commercial performance, agentic AI opportunity, or the business question that keeps getting debated instead of solved.