Internal case study

WaySky on WaySky.

Before asking anyone else to trust the process, we ran it on ourselves — using the WaySky system to track where we were being skipped, strengthen our public proof surface, and test how Fix Pack and Source Sprint work in practice.

MA
Michael AttarFounder, WaySky
01The problem

Why we ran it on ourselves first.

WaySky helps B2B SaaS vendors get recommended in AI-driven buying conversations. Before asking other companies to buy into that, we applied it to ourselves: tracking our own visibility, understanding why we were skipped, strengthening positioning and proof, and testing the full execution path before using it with clients.

This isn't a victory lap — it's a transparent look at how the process works. Like many early companies, we had a clear point of view but the public proof was still incomplete:

  • limited service-page depth
  • a thin trust and proof surface
  • incomplete comparison and category pages
  • inconsistent public support for our positioning

Good products still get skipped when the proof surface is weak.

02The approach

What we tracked.

We used WaySky's own portal to monitor the prompts that matter most for our category — not just whether we appeared, but the gaps behind the misses.

Where we were being skipped

Which buyer prompts surfaced other vendors and not us.

Who showed up instead

The competitors AI named in our category.

Which prompts mattered most

The questions that actually shape shortlist decisions.

What our surface didn't support

The proof and positioning gaps behind the misses.

03The work

What we changed first.

Before pushing for more outside visibility, we focused on the parts of the public surface that needed to be stronger. That Fix Pack work included:

  • rewriting and restructuring the pricing page
  • separating About and Trust into clearer standalone pages
  • building dedicated service pages for Reality Check, Fix Pack, Source Sprint, and Visibility Retainer
  • clarifying the homepage ladder
  • improving category clarity for B2B SaaS
  • adding comparison and educational pages

More visibility only helps when the public surface is ready to support it. So Source Sprint came after the fixes — only once positioning was clearer, trust was stronger, and the company was easier to place. That's exactly how WaySky uses the process with clients.

04The outcome

What changed.

The point isn't to claim instant dominance — it's to show the process honestly. What changed first wasn't magic. It was clarity. WaySky became easier to understand: what the company does, who it's for, how the ladder works, why done-for-you execution is the core, and how trust, proof, and category positioning fit together.

That stronger foundation is what gives later visibility work a better chance of compounding.

This is an active internal case study. We'll keep updating this page as results develop.

05What we learned

What we learned.

Diagnosis is not enough

A dashboard alone does not change outcomes.

Proof assets matter more than expected

Service pages, pricing clarity, trust pages, and comparison surfaces all influence recommendation readiness.

Outside proof works after the fundamentals

Source Sprint is stronger when the company is already easier to understand and trust.

Recommendation readiness is ongoing

This is not a one-time project. It compounds when maintained.

06For clients

What this means for clients.

WaySky isn't asking clients to trust a process we haven't used ourselves. We apply the same system internally:

  • track the problem
  • diagnose what is blocking you
  • fix the missing proof and clarity
  • strengthen the outside signals
  • keep improving over time

We don't just sell the process. We operate under it.

Case study

Start with the same first step we did.

Track where you're being skipped. Then fix what matters.