I’m testing a service before building another course or SaaS feature
I have spent a lot of time doing outreach for my own small web design business. One lesson kept coming up: Personalized outreach can still feel completely generic.
“I looked at your website.”
“I noticed some SEO problems.”
“Would you like a free audit?”
The business name and website findings might be accurate, but the owner still sees the pitch coming. I started getting more normal replies when I opened with one specific observation and one genuine question about the business. The goal was not to hide a pitch. It was to stop assuming every business had the same problem.
Sometimes the conversation revealed a real need. Sometimes it revealed that the business was already booked, did not want more leads, or was not a fit. I have now packaged that process into a small custom service for freelance web designers.
I review their current outreach, offer, pricing, target businesses, natural writing style, common prospect replies, and sales process. Then I build them a conversation-first outreach system with openers, follow-up questions, pitch transitions, objection responses, and custom AI instructions.
I decided to test it as a $149 service before turning it into a workshop, course, or larger Webvidence feature.
The immediate goal is five beta clients and enough real feedback to see whether people will pay for the method itself.
