Bring me the hard GTM problem

I work with founders and revenue leaders on hard GTM problems. I get in the details, figure out what to do, and help make it stick.

01 The work

I solve hard GTM problems.

A new sales motion. Positioning that is not landing. A platform with too many use cases. A solutions or forward-deployed motion that needs to be built. A team scaling faster than its systems.

I get into the calls, data, customer language, and decisions. Then I help the team figure out what to do and get it moving.

The work can be a focused build or ongoing advisory. We decide that after we understand the problem.

02 Ways to work

The engagement follows the problem.

System Build· Focused

Make the system explicit.

The raw material already exists in your calls, customer data, and best people. I pull it together, find the patterns, add what is missing, and build a system the team can run.

Shape Focused scope Usually 45 to 90 days Finished system and rollout plan
Advisory· Ongoing

Bring me the hard problem.

We set the deliverable after we understand the problem. I work directly with the founder, CRO, or leadership team to figure out what to do and get it moving.

Shape Regular working sessions Hands-on when useful Retainer, equity, or both
03 Track record

Operator experience. Applied to your problem.

Exit value $100B+ Across IPOs, acquisitions, and private equity.
GTM builds 50+ Seed through Series E. Two decades in enterprise software.
Most recent $3.35B Chronosphere to Palo Alto Networks.
A partial list of GTMs I have worked with
MongoDB· Datadog· Okta· Chronosphere· Qualtrics· Sprinklr· Medallia· Cloudera· Roboflow· Gretel· Yext· FireMon· Fiserv· BladeLogic·
04 How I work

I do the homework. A lot of it.

I go into the field and learn. Customers. Reps. Leadership vision. I use 20 years of inspecting GTM teams and pattern matching, plus my own tools and a deterministic framework, to get fluent fast and form an initial hypothesis.

01Learn

Go into the field.

I learn from customers, reps, data, and leadership vision. Calls, CRM, customer language, existing material, and direct conversations.

Get fluent fast
02Point of view

Build the hypothesis.

I turn the evidence into an initial view of the problem and the best path forward. The goal is about 70 percent accuracy before we get in a room, so we can use the session to make decisions.

Aim for 70 percent accuracy
03Co-creation

IRL working session.

We make key decisions and collaborate on the content, process, and rollout. This is the remaining 20 to 30 percent.

Make the key decisions
04Deliverable

Build the evergreen system.

The team leaves with an evergreen system it can keep improving as the company, customers, and market change. I build the source, tools, operating rhythm, and ownership that keep it current.

Keep it growing

Two systems I build often.

Common Build · One

Deal Architecture

Make the selling motion explicit.

  • 01Deal types and plays
  • 02First-call qualification
  • 03Discovery, proof, and pricing
  • 04Rollout and evergreen source
Focused build Usually 45 to 90 days
Common Build · Two

Sales Leadership System

Make great management repeatable.

  • 01Role and success profiles
  • 02Interview system
  • 03Manager operating rhythm
  • 04Development and reinforcement
Focused build Usually 45 to 90 days
05 Start

Have something hard to figure out?

Intake SF · 001

Email me. I will tell you if I think I can help.

Write to jeremy@stageforward.ai