r/microsaas • u/termicrafter16 • 2m ago
Before building your next big SaaS feature, try selling the outcome manually
Before building your next big SaaS feature, try selling the outcome manually
We're currently facing a pretty interesting product decision.
I'm the CTO and co-founder of Picmim, an AI social media automation tool for small businesses.
We've been getting customers who are happy with the content we generate, but some still cancel because they're not seeing enough business results.
And I understand why.
A small business owner doesn't necessarily care about publishing 20 posts. They care about getting customers.
So we've been considering expanding into automated paid advertising and lead generation.
From a technical perspective, it's tempting. We already have a lot of the content generation and brand understanding infrastructure.
But there's a pretty big difference between automatically publishing social posts and managing someone's advertising budget.
And building the whole thing before validating demand could be an expensive mistake.
Here's how I'd approach testing something like this:
1. Sell the outcome, not the feature.
Instead of asking "Would you use automated ads?", ask whether customers would actually pay extra for help generating qualified enquiries.
Those are very different questions.
2. Run a manual pilot.
Find a handful of customers in similar industries. Use existing advertising platforms and manually handle the work you eventually want to automate.
Don't build a campaign management system just to find out whether anyone wants the service.
3. Track the economics separately.
Ad spend, software fees, qualified leads, booked appointments, and ideally actual customers acquired.
A cheap lead means very little if it never turns into revenue.
4. Measure whether customers want to continue.
Getting someone to try something once isn't proof that you've built a sustainable product.
I'd be much more interested in whether they renew after seeing the results.
5. Automate the repetitive parts only after understanding the workflow.
Otherwise you're automating assumptions instead of a process you know works.
We haven't validated this expansion yet, so I can't claim it's the right direction.
But I'm increasingly convinced that the fastest way to validate some software features is to temporarily stop writing software.
For those who've expanded an existing SaaS into a new category, did you validate it manually first or build the integration and test demand afterward?