Use case page offer walkthrough for Scope & Sequence (Oct 2025)

Hey, this is Zach, and let's talk about how we would work together.

And before we do that, I want to tell you more about why we are focusing on use cases and specifically use case webpages.

It starts with our sales process today.

You've already done it already.

You've done the hard work, you've sold the product, you found product market fit.

But for whatever reason, right now, when you look at the middle of your sales funnel, deals aren't moving.

It's not because your product has gotten hard to sell.

It's just harder to explain when it reaches that stage because this is what's going on behind the scenes.

What is happening behind the scenes is this belief that our audience is going to figure out our product.

If we take them to the demo and we show them all the features, they're going to know it and it's going to click.

While that is going to resonate with a small subset of your audience, you've seen those numbers.

As you guys expand to different audiences, as you build new features, it's going to add a little bit more complexity that creates sense of burnout within your sales process.

Your teams, if your teams are feeling that and trying to explain that energy is contagious.

And it's going to your best audience as well.

Wow.

You're creating features that, a large subset are going unused in facing a wider set of competition.

No fault of your own again.

But when you build these new features, it's going to reach different people and it's going to open up to different conversations of what other tools are using, which is more so than it was 10 years ago.

And when that happens, your buyer is dealt with figuring it out.

They've got to figure out does this replace?

Like, how would our team use this?

How is this different from what we are doing before elongating the sales process, making it harder to decide which vendor is the right fit.

And as we dig deeper here before, is that just our, a single pitch that's worked before, our audience has outgrown it.

what has worked with that same audience as you guys expand within that same subset?

The issue still remains, we've got to figure it out.

And that is just becoming harder and harder today.

And it's not to say the pitch is wrong.

What is, what we're trying to say is we need to think of ways how we can explain how your product wins across different workflows.

Not recreating the pitch, not adding more slides, but shifting the conversation into different avenues, that our Buyers already know their day to day workflows and how we work together to translate use cases into a tangible asset that your sales teams can use on calls that your marketing teams can point to in campaigns and lastly that buyers can then use to sell.

The solution internally and build support is through this three phase approach.

Building from what you've done before.

Phase one, analyzing the nature of your product and how it wins across different workflows, to organizing to taking all that information and packaging it up, into a clear framework.

And three, translating all that information into a clear use case page wireframe with production ready copy.

Let's talk more about each phase here.

And as you look through all this, all this work is done in figma.

So when we are working together, we're working directly within the canvas.

We are going through each phase per a, 90 minute workshop at most.

And our objectives in this first phase here is to understand the nature of our product.

We know why it wins, but how do we communicate it?

Who is our target audience?

What are the competitive alternatives that might be coming up within this specific use case?

What, what are the use cases that we want to tackle first?

This is what we are challenging, we're tackling in the first phase.

When we move to the second phase, we are now looking at how we organize all of this information that we have gathered from the prior phase into a clear framework.

And if this looks familiar, this is in partnership with Fletch.

They have built an amazing framework to help us organize and see, see and contextualize it and building upon this framework, adding in, what is the industry trends that we're seeing that might influence this use case?

What are the reputational costs that our target buyer or the target user is facing when they're trying to accomplish this workflow?

And how can our product help to solve that?

And this is what phase three answers.

Once we build out the use case workflow, once we understand how the nature of the product fits within it, let's translate that information into a use case page.

Because you've already have the homepage, it shows why your product wins.

You want to go a level deeper and show different ways of how it works across different workflows.

That speaks to different audiences, that goes deeper, that becomes your 24,7AE.

Because the homepage gets the job done.

Our homepage is like a BDR, but our BDRs cannot sell the full cycle.

It's not because they can't do the job.

It's because this serves a different purpose of getting to show why your product wins, getting people excited enough to take them along to the full sales cycle.

And this is what we are achieving within phase three.

Because at the end of the day, it's not about recreating the wheel.

You've already found your position, it's been working.

Our next phase here is of growth is to show how it went in different ways.

We could do this in our first call deck, but always seen what's been happening before it becomes this large behemoth of an asset that in our sales team has to sift and pick through.

It gets lost in translation because we are just used to grabbing at what we know.

Why not put it in the website?

Why not make it accessible not only to your sellers, but make it accessible to your marketing team.

Make it accessible to your champion buyers so that you all are operating from the same level of expertise, showing the different ways of how your product weighs.

Because when we can do that, it makes selling a whole lot easier.

And this is what it would look like if we were to partner together.

It's $3,500, for our use case wireframe.

Up to two wireframes per use case page.

Everything you've seen before in the prior slides covered in the process.

All this work is done at Figma across three 90 minute workshops.

It takes up to three to four weeks to deliver depending on your gut under scheduling and how we partner together.

You get one use case wireframe, with production ready copy.

And you will be working with me directly from start to finish async between each session too.

Because I've been there with you guys.

I.

Before product marketing I was in sales.

I was trying to help sell the platform.

Few people understand it, but what made the job easier was showing the different ways of how a platform would fit within their workflow.

Not selling the features, but giving context as to how the features fit within what they're trying to do and what they know.

Because with a clear use case, it's easier to show how your product wins across different workflows.

This is it for the session right now.

excited about the potential partnership of working with you and thank you for hearing me out.

Take care.

Bye bye.