The question always comes at the same point in the conversation, just when things seemed to be going well.
“Do you have any case similar to mine that you can show me?”
That’s where many first meetings end. Not because the answer is no, but because of what comes next: the awkward silence, the half-hearted excuse, the “well, I’ve worked on several projects but I can’t name names.” The client notices, and it’s over.
The cycle is well-known. No one hires you without demonstrable results, and there are no demonstrable results without someone hiring you first. What almost no one explains is that this cycle isn’t broken by achieving a success story, but by changing what you bring to the table when asked.
This article is about that specific conversation. Where to find those first clients is discussed elsewhere, and much better: it’s covered in the guide on how to make a living from SEO, which dedicates an entire chapter to channels, word-of-mouth, and communities. Here, we pick up right after, when you already have someone in front of you.
What They Ask You and What They’re Really Asking
It’s important to understand where that question comes from, because it’s neither random nor in bad faith.
Google’s own guide for hiring an SEO specialist recommends that companies ask for examples of previous work and speak with past clients. It’s one of the first things mentioned. Any company that has done its homework will ask you, so stop taking it as a personal attack.
But that same guide says something else that almost no one has read, and which completely changes the position from which one responds.
Google points out that you should check if the professional is genuinely interested in the company, and that a good specialist should ask what makes that company unique, who its competitors are, and how its customers find it today. If they don’t, the recommendation is to look for someone else.
Read that again, because there lies the door.
What is evaluated in that meeting is judgment, not history. A success story is a shortcut to demonstrate judgment, and it’s a convenient shortcut, but it’s not the only way. When you don’t have one, you have to demonstrate it the long way: live, in front of the client, and on their own business.
Those who understand this stop trying to appear experienced and start asking better questions than their competition. Which, by the way, is usually an agency that arrives with a dossier of logos and hasn’t even looked at the client’s website for five minutes.
What You Already Have Even If You Think You Have Nothing
Before the meeting, it’s wise to take an honest inventory. Most people who say they have nothing, actually have something.
Your own project, however small. A non-profit’s website. The experiment you set up to test a hypothesis. Work done at an agency, explaining the approach and learning without breaking confidentiality or naming names. A public analysis of a sector you know well.
None of that is a success story with revenue figures. But all of that shows you’ve gotten your hands dirty, and getting your hands dirty is exactly what separates someone who knows SEO from someone who has watched a lot of SEO videos.
A rule that admits no exception: don’t inflate anything. Not a percentage, not a client who was actually a favor, nor a responsibility that wasn’t yours. Anyone who exaggerates in the first meeting pays for it in the third month, when the client asks about something you were supposed to master. And the industry is smaller than it seems.
Replace the Success Story with a Diagnosis
This is the move that changes the conversation, and it’s simpler than it seems: arrive with an analysis of their website already done.
Not a fifty-page report or a complete audit given away for free. Two or three concrete findings, well-explained, with the why and what they imply for their business. Something that can be told in ten minutes and that the client didn’t know.
It works for two reasons.
The first is that it demonstrates the judgment we talked about earlier, and it demonstrates it on the only project the client cares about: theirs. An external success story always requires an act of faith: “This worked for them, trust that it will work for you.” A finding about their own website needs no faith.
The second is that Google’s own guide is recommending that company request a technical and search audit to find out what needs to be done, why, and what results to expect. It even warns them that they will probably have to pay for that service and that it’s advisable to give read-only access to Search Console, never write access, at that stage.
So, the client who has done their research already expects this step. Arriving with part of the work done isn’t giving anything away: it’s anticipating what they were going to ask for anyway.
If the problem they bring is a traffic drop, there’s a specific order to diagnose it that avoids the three most common errors, and it’s explained in the article “organic traffic drop.” Arriving at that meeting knowing how to distinguish a measurement problem from an algorithm problem is worth more than any logo in a presentation.
What Exactly to Answer When Asked
The answer has three parts, and none of them is an excuse.
First, say it directly. You don’t have a case identical to theirs. One sentence, without apologizing and without dragging it out, because the more it’s stretched, the bigger the problem seems.
Second, show what you do have. Your own project, previous work, whatever is from the inventory you made earlier.
And third, move the conversation to the ground where you can win: what you’ve seen on their website. This is where the diagnosis comes in handy.
What you should never do is compensate for a lack of history with a promise. Guaranteeing positions is the most expensive mistake of all, and not just because it’s obvious that it can’t be fulfilled: Google’s guide literally tells that company that if someone guarantees them the top spot, they should look for someone else.
You are competing for a position of trust. Telling the uncomfortable truth in the first meeting is, in itself, a demonstration of professional judgment. And it’s the only thing that someone inflating their portfolio cannot imitate.
Charge from the First Project
Working for free “to build a portfolio” seems like the obvious solution when you have nothing to show. It almost never is.
A price of zero is not a low price: it is the absence of price, and it places the work in the category of a favor. Projects that start as favors are managed as favors, they are postponed, expanded without negotiation, and end badly more often than not.
And when it’s time to start charging, the conversation is extremely awkward, because you have to justify why something that was free last week is now worth money.
Low prices at the beginning; it depends on the value you are providing. It’s normal to decide to charge low prices; everyone does it, and it’s fine. But set a price.
There’s an intermediate version that works well, which is the diagnosis from the previous section: part of the analysis is delivered in the meeting, the full audit is charged for, and that audit becomes the gateway to the long-term project. The client takes a small risk, you get paid from the beginning, and both check if they understand each other working together before signing anything bigger.
Set Expectations Before Signing, Not After
Here’s another piece of information from Google’s guide that’s useful to have on hand: it warns companies that the benefits of changes usually take between four months and a year to be seen.
That information is a gift for someone just starting out.
Those without a history are often tempted to accelerate timelines to compensate. They promise movement in two months, the client believes them, and in month three, a tense relationship begins that ends in cancellation and a review no one wants.
Losing a client by over-promising at the beginning is the silliest way to prolong this stage, because it also leaves you without the testimonial you needed.
Stating a realistic timeline makes you seem less brilliant in the meeting and much more professional in month four. And month four is what decides if there’s a renewal, a recommendation, and a case to tell.
The Goal Isn’t the First Client, It’s the Third
One client can be a small step. Three start to be a repeatable pattern, and repeating is what turns this into a business instead of a streak.
So, from the very first project, it’s wise to do two things that almost everyone postpones and then finds difficult to claim later.
Ask for written permission, even if it’s in an email, to share the case. What can be published, what figures, whether the company can be named or if you should refer to “an e-commerce in sector X.” Asking at the beginning, when the relationship is fresh, is much easier than asking a year later.
And ask for the review at the right moment, which isn’t at the end but precisely when the first result that makes the client’s day arrives. That’s when people write genuine things.
With two or three documented projects, this conversation ceases to exist. There’s no need to substitute anything: you show what you’ve done and move on.
The Four Mistakes That Prolong This Stage
- Waiting to be ready. There’s no moment when you feel prepared. You learn by charging and with a client in front of you, not by accumulating courses.
- Offering everything to everyone. When you have no history, specialization is the only thing that distinguishes you. It’s more credible to be the one who understands a specific sector than the one who does general SEO.
- Quoting without having looked at the website. It’s the shortcut that ruins the first year’s margin and also conveys the exact opposite of the judgment you’re trying to demonstrate.
- Not qualifying. Accepting anyone because you need to bill is understandable but costly. The client who haggles before knowing what you do will haggle every month.
And After This, What?
All of the above addresses a specific stage: getting someone to pay you for SEO when you can’t yet demonstrate it with your own results.
What comes next is a different and much less technical problem. How much to charge and how to raise prices without losing clients. What services to sell and which to reject. How to organize yourself so that the third client doesn’t cost three times the effort of the first. How not to depend on just two invoices.
None of that is learned by doing better SEO, which is the trap almost all of us fall into: thinking that if we improve technically, business will come naturally. It doesn’t. They are two distinct disciplines, and the second one is almost never taught.
That’s what the SEO consultant course is about: not learning SEO, which is presumed, but building the business around it.
Frequently Asked Questions
Can I use my own projects as a success story?
Yes, and they are better than they seem, because you can show complete data without asking anyone for permission. What is not advisable is to present them as client work.
Is it a good idea to work for free to get the first case?
It’s the fastest route to a project that is managed as a favor. Low prices at the beginning, yes; free, unless it’s a cause you genuinely care about, no.
What do I do if the client insists on guaranteed results?
Explain that no one can guarantee them and why. Google says the same in its own documentation. If they still insist, that client will be a problem by month three.
How long does this stage last?
It depends on commercial activity, not technical knowledge. With two or three closed and documented projects, the question about success stories stops appearing.
