Every buyer comes to you with a history. Some of them have tried to solve this problem before and failed. Some have succeeded with a different provider and are looking for something the previous relationship no longer delivers. The Process Past Question makes that history visible, and turns it into your most specific proposal advantage.
Why Vendor History Is Your Sharpest Competitive Edge
Most freelancers treat vendor history as background, something that doesn’t really affect the brief or the proposal. This is wrong. A buyer who hired an agency that produced great strategy but poor execution is not the same buyer as one who hired a freelancer who disappeared after week two. Their fears, their checkboxes, their definition of “this is going well” are completely different.
The Process Past Question surfaces that history directly. “What have you tried before, and what did or didn’t work about it?” is a simple ask that positions every future section of your proposal around the specific gap between what they received before and what they actually needed.
Gap Selling defines the sales problem as the distance between the buyer’s current state and desired state. The Process Past Question tells you about the current state not as a snapshot but as a sequence, they’ve tried things, some worked partially, and you’re the next attempt. Knowing what the previous attempts looked like tells you exactly what gap you’re being hired to close.
The Exact Wording That Opens the Door
Three common variants, in order of effectiveness:
Best: “What have you tried to solve this in the past, whether in-house, with a vendor, or on your own, and what did or didn’t work about those approaches?”
Good: “Before we talk about what I can do, I’d love to understand what you’ve already tried. What’s the recent history here?”
Acceptable: “Who else have you worked with on this kind of project, and what was that experience like?”
The first version is strongest because it’s explicitly non-judgmental (“whether in-house, with a vendor, or on your own”), removes the competitive frame (“I’d love to understand” vs. “who else”), and builds in the evaluative question (“what did or didn’t work”) rather than leaving it implicit.
The Process Past Question is a form of competitive intelligence that the buyer is actively willing to give you, because they want the next engagement to succeed. Frame it as learning from their experience, not mapping their vendor landscape, and you’ll get remarkably candid answers.
The 4-Second Silence Rule
After the buyer gives their first answer to the process past question, stop. Don’t follow up immediately. Count to four in your head.
This is uncomfortable. Your instinct will be to respond, to say “interesting” or “got it” or to ask a clarifying question. Resist it.
The reason: the buyer’s first answer is almost always a compressed headline. “We tried an agency last year, it didn’t work out.” That’s not the answer. The answer is what comes after four seconds of silence: “They were honestly pretty good at the concept work, but they kept bringing in junior people to do the actual execution and the quality suffered. We spent a lot of time fixing things.”
That elaboration is worth more than the headline. It tells you:
- The quality of strategic thinking is not the buyer’s primary concern (they said the agency was “pretty good at concept work”)
- The buyer cares about seniority and personal involvement, they don’t want to pay for an expert and get a junior
- They’ve experienced rework and wasted time, which means timeline reliability will matter
You got all of that from four seconds of silence. Fill that pause and you would have gotten the headline.
Four Categories of “What Didn’t Work”
Buyer answers to the process past question cluster into four failure types. Each maps to a specific proposal response.
Quality failure: “The work wasn’t good enough.” Your response: provide evidence of comparable quality up front, a sample, a case study with outcomes, a brief audit of their current situation that demonstrates your standard.
Process failure: “It was chaotic and we never knew what was happening.” Your response: include a specific communication and project management protocol in your proposal. Not vague promises, a named system with explicit touchpoints.
Fit failure: “The approach was fine but it wasn’t right for our industry / scale / audience.” Your response: demonstrate domain-specific knowledge in the proposal. Reference their sector, their constraints, their competitive environment by name.
Relationship failure: “It just wasn’t a good working relationship, we felt like a small client and didn’t get the attention we needed.” Your response: address client access directly. Name how you structure your client relationships, what the buyer can expect in terms of availability, and how you handle situations where priorities conflict.
What “What Almost Worked” Reveals
The most underused follow-up to the process past question is: “What about it was almost right, what was working before it fell apart?”
This question extracts the part of the prior solution that was valuable, which tells you what to preserve and protect in your own approach. If the buyer says “the reporting cadence was actually great, we loved the visibility, but the work itself was inconsistent,” you know that reporting cadence is a feature, not a burden. Put it in your proposal as a featured element, not a footnote.
Buyers are rarely unhappy about everything in a prior engagement. Finding the part that worked and explicitly continuing it in your approach signals that you’re building on what they value, not replacing it wholesale.
Using the Answer to Frame Your Pitch
Once you have the buyer’s vendor history, you have the frame for your entire proposal.
If the previous agency was slow to start: “We have a 3-day onboarding sprint that gets us from kickoff to first deliverable without a 4-week setup phase.”
If the previous freelancer communicated poorly: “Every Friday you’ll have a status note in your inbox, three bullets, what’s done, what’s in progress, what I need from you.”
If the previous team produced work the buyer couldn’t use: “Everything I deliver comes with a brief explanation of how to use it and why it’s structured the way it is.”
None of these lines are generic. Each is a direct address to a specific prior failure the buyer named. That specificity is the difference between a proposal that sounds like it was written for everyone and one that sounds like it was written for this client, right now, this week, based on what they just told you.
The Process Past Question is how you get the raw material for that specificity. Four words, “what have you tried before?”, and then four seconds of silence.
