
Agency Growth
How I Structure an Early Client Offer When I Have No Case Studies Yet
· Updated
When a prospect asks for proof, I hear a question about the risk of buying from someone they do not yet know. If I have no client case studies, I cannot solve that by pretending I do. The offer needs to explain what I will do, what the buyer pays for and how the risk is shared.
The three approaches I discussed were performance pricing, a retainer with an outcome guarantee and a free deliverable made before the sales conversation. They do different jobs. The work sample can open a conversation, while the payment structure determines the terms of an actual client relationship.
Performance pricing connects the fee to an agreed event
Instead of only charging a recurring retainer, I described charging as a result occurs. For lead generation, that might be a fee per booked call or a fee per call that actually takes place. Those are distinct billing events; neither is the same as charging for a signed customer.
I also described a small technology fee to cover such things as domains, inboxes and leads. My recommendation was not to start an ongoing client relationship with no money changing hands at all. That is different from making a limited sample for a prospect before they become a client.
The client still needs a business and offer that can benefit from the service. Changing the payment terms does not make an unsuitable client capable of getting results. That was an important condition in my discussion of performance pricing.
Client Ascension related reading: the LTV screening guide examines the client’s customer value, delivery margin, acquisition cost and cash timing. It gives more context for checking whether the buyer’s economics can support an agency service.
A retainer guarantee needs an outcome and a time window
The second structure was a normal retainer or upfront payment with specific outcome benchmarks. In the example, if the agreed result did not occur in the agreed period, the client received a refund or a proportional refund. That allocates risk differently from simply asking someone to pay and hope.
I treated that as a different arrangement from billing only as performance occurs. It requires the business to be prepared to honor the refund terms it describes. The label guarantee does not substitute for explaining the result and what happens when it is not delivered.
Client Ascension terms note: these are historical offer structures from Daniel’s lesson, not current program guarantees or a claim that a guarantee removes every risk to either party.
A useful sample gets the prospect closer to evaluating the work
The third approach was creating something before being asked: for example, a funnel, email flows, ad scripts or a VSL script. The prospect could assess the quality of actual work instead of only hearing a claim about the service.
I explicitly distinguished this from the final paid offer. Giving someone a sample may help get them on a call, but a beginner can still face the proof question when the conversation turns to working together. The sample does not automatically settle the payment model or the outcome terms.
Client Ascension related reading: Ayman’s content-agency case study describes free-sample outreach, his own content, one-off projects and hiring. It is a separate operator example of using actual work to start business conversations.
Tell the truth when the buyer asks what you have done before
The response I suggested was direct: explain that the formal agency is new, say that there are no client case studies yet, and show the process and risk terms that are actually being offered. The purpose is to acknowledge reality, not invent a work history or bury the answer in an apology.
I also wanted the person selling the service to have examples of the actual deliverable. An email-flow service should be able to show what its email flows look like. A sample demonstrates what the work is; it should not be presented as a measured client result it has not produced.
A process another person has used can be discussed as an example, but it must stay their example. I specifically said not to pass it off as my own case study. Showing a similar method is different from claiming I personally achieved another operator’s result.
Turn the work into a documented case, then put it where it helps
A case study needs more than a compliment. I asked for the actual result, how it was achieved, the time taken, money invested and returned, and the challenges along the way. A testimonial and a study of what happened are not interchangeable.
I described documenting a case in a Gamma presentation and recording a Loom walkthrough. The material could be used on a landing page, in relevant outreach replies, during follow-up and around a sales call. Creating the evidence and putting it in front of a prospect are separate tasks.
The first client may not produce a usable result immediately. My case-study flywheel was the process of delivering, documenting and using that evidence in later conversations, not a promise that every first project becomes a success story.
Client Ascension related reading: the acquisition guide discusses matching the offer to a channel, available resources and the sales cycle. It addresses the outreach work that sits alongside choosing an early-client payment structure.
Adapted by Client Ascension with AI assistance from Daniel Fazio's lesson. The first-person narrative follows the source speaker’s account. Watch the original video





