ls case-studies/

Real results, with the caveats.

Every case study states exactly how its numbers were verified — whether that is the client's own dashboard reproduced on the page, or figures they reported to me. Each also says what the result doesn't prove, because a number without its starting conditions is close to meaningless.

Short answer

Bin Bash Computing publishes two client case studies, both anonymised HVAC contractors. One went from 238 to 698 Google Search Console clicks in three months, evidenced by the client's own screenshot. The other, in the Austin metro, went from about 35 to 90 Google Business Profile calls a month over six months, from figures the client reported. Each case study states how its numbers were verified and what the result does not prove.

./how-i-report

How these are written

What you'll always see

  • The starting point, including what was broken
  • Numbers from Search Console or an equivalent, with the source named
  • A stated grade of evidence — reproduced export, or client-reported
  • An honest split of what actually drove the result
  • A section on what the case study does not prove

What you won't

  • Percentages without the absolute numbers behind them
  • Results borrowed from someone else's work
  • Clients named without their written permission
  • A claim that your business will do the same