Website pages to add

1. Home

2. How It Works

3. Hidden Buyers

4. Proof Library

5. Use Cases

6. Case Studies

7. Pricing

8. Resources

9. Book a Call

To support an outcome led, strategy first approach (and stop people mentally filing you under “video production”), you want pages that do three things:

1. prove you understand the proposal buying reality

2. show a clear, repeatable system

3. make it easy to self qualify and take the next step

Here’s the most useful site structure.

Core pages you should have

1) How It Works

This is your system page - the operating loop, not the deliverables.

Include:

• the steps (diagnose - build proof - deploy - measure - improve)

• what happens in the first 30 days

• what inputs you need from the client

• what outputs they get (non video and video)

• what “done” looks like

Why it matters: it moves you from “vendor” to “method.”

2) Outcomes

A page that frames your offer around outcomes, not services. For example:

• Win rate uplift / higher conversion

• Shorter approval cycles

• Fewer no decision stalls

• Higher confidence for hidden buyers

• Less time wasted writing bespoke proposals

Even before you have hard numbers, you can position outcomes as targets and talk about the mechanisms.

3) Proof Library

Make the “library of proof” tangible here - without calling it a DAM or pretending you have a platform.

Include:

• what a proof module is

• example module categories (security pack, onboarding pack, ROI proof, customer proof)

• how it’s stored in BetterProposals Content Library

• how it compounds over time

This page is key to making your claim feel real.

4) Hidden Buyers

A dedicated page that shows you understand the internal decision dynamic.

Include:

• who the hidden buyers typically are (Procurement, Finance, Security, Legal, Ops, Leadership)

• what each one needs to say yes

• how you create “lens pages” inside proposals

• how you reduce perceived risk without bloating the proposal

This directly supports your new positioning.

5) Use Cases

This is where you show scenarios, not industries:

• Enterprise SaaS security review heavy deals

• Cybersecurity competitive bake offs

• Public sector procurement

• Regulated industry compliance requirements

• High ACV services with long evaluation cycles

Keep it “problem based” rather than “we serve everyone.”

6) Packages or Pricing Approach

You don’t need to publish exact pricing, but you do need a page that answers:

• how you charge (retainer, per proposal, proof sprint)

• typical ranges

• what changes the price

• what’s included

This reduces tyre kickers and builds trust.

7) Case Studies

Even if you’re early, start with:

• 1 to 3 “micro case studies” (before / after, what changed, what assets were created)

• or “internal pilot” case study using your own pipeline and proposal process

This is where your credibility lands.

8) Resource Hub

You want one “evidence led” hub that reinforces the strategy first stance.

Start with:

• Proposal Win Review checklist

• Hidden Buyer Approval checklist

• Proof Library starter template (lead magnet)

• “What to include in a security pack” guide

This page becomes your inbound engine.

Optional pages that add serious weight

9) The Proposal Win Review

A productised diagnostic page. This is the best wedge for trust.

It should explain:

• what you review

• what you deliver (risk map, messaging gaps, proof gaps, quick wins)

• turnaround time

• fixed price

This makes you feel consultative and outcome led immediately.

10) FAQ

Answer the objections people will have:

• “Is this just video production?”

• “We already have case studies - why isn’t that enough?”

• “Will this work for our industry?”

• “How do you avoid creating more work for us?”

• “Can you work with our existing proposal tool?”

If you want, tell me your current menu items and I’ll recommend the tightest version for launch (no fluff), plus the “Phase 2” pages to add once you have 2 to 3 case studies and clearer packages.