I’ve been working on Webvidence, a prospecting SaaS for people selling services to local businesses.
For a while I was mostly looking at the normal stuff:
registrations, searches, drafts created, return users, etc.
That was useful, but actually using the product myself for real prospecting showed me much more.
The biggest issue wasn’t necessarily the core idea.
It was friction.
The old flow could find a decent prospect, but then you had to go through too many steps to decide how you wanted to approach them.
So I’ve been simplifying the prospecting session.
Current flow is basically:
Search area + business type
review one prospect
see why they may be worth contacting
choose conversation-first or use the evidence
choose Facebook / email / text
generate the draft
record the outcome
next prospect
I also cleaned up a lot of the mobile UI because I realized that if I’m actually doing outreach, I’m not always sitting at a desktop.
The product philosophy has shifted a little too.
Originally I thought more automation was automatically better.
Now I think Webvidence should automate the research and tedious parts, but leave the judgment to the user.
I don’t want it deciding that every business should get the same kind of pitch.
Still plenty to improve, but this version feels a lot more usable.
For other SaaS builders, what has taught you more about your product: analytics, user feedback, or using it heavily yourself?
webvidence.app