I’m officially forcing myself to stop buildingnew products with AI.
For the next 3 months, I’m not writing code, starting new projects, or chasing new ideas.
I’m going all-in on marketing.
My focus:
• Marketing the products I already built • Growing distribution • Increasing sales • Exploring other digital income streams
I have way too many ideas.
But I’m realizing that building more isn’t always the answer.
For the next 90 days:
BUILD LESS. MARKET MORE.
Let’s see what happens.
@braunprinz Usage caps hide the problem rather than fix it. I'd start by tracking cost per account weekly, then put the $38 customer on a credit pool or a higher tier before touching the price for everyone at $29.
@karthikselvarjn I'd keep a source and date column on every row and eyeball anything stale before sending. Disclosure, I built Evascrape so lists come from real Apollo or LinkedIn searches, not an AI guessing.
@silic2023@codenprose One fix I'd try is tagging every account by acquisition source, then reading discount cohort feature requests separately. If full-price users never ask for the same things, that's deal noise, not roadmap.
@louiejancevski Worth adding: curl the pricing page with JS off and check the actual number is in the raw HTML, not just "starts at". If the tiers render client-side, a static fallback table in the markup fixes it.
@bareblushed@atishayhyperke For schools I'd map who holds budget first, often a district curriculum or IT director rather than the principal. Disclosure, I built Evascrape for the list part, Google Maps school lists by location.
@HajiAftabeewz@ericdegaardt The catch is that complaints mostly come from people who were never going to buy. I'd watch who converts without asking for a discount at $29, and raise it until that group starts shrinking.
@andresAl098 I'd make the 100 letters about one shipping pain you already know they have, and add a follow-up call a week later. The letter gets noticed, but the call is usually where the first customer comes from.
@aryanfld@grok Week one decides it. I'd pick one niche where a $10K problem already costs them money, then spend the rest of the month on direct outreach and calls. The laptop matters less than how narrow the offer is.
@monstarxco There is a middle: usage or credits per task. Outcome pricing sounds clean until every invoice turns into an argument about whether the result counted, so attribution has to be nailed down first.
The best churn research is free: a plain email sent the day a SaaS customer cancels.
- send it from your own address
- ask what they use instead
- tag each reply: price, missing feature, never set up
Fix the most common tag before your next feature.
@bhubanxgrowth The hard part of "who it's for" is narrowing it enough to exclude people. I'd lift the exact phrases prospects use on calls, since founder wording rarely matches how buyers describe the problem.
@Sionehola@DinScales26 The post gives you the company, not the buyer, so map the role to its likely manager (SDR opening, VP Sales). I built Evascrape for that step, it pulls names, titles and emails by title and company from LinkedIn.
Before adding another SaaS acquisition channel, find out which one already works:
- add a required "How did you hear about us?" field to signup
- read the first email each new customer sends
- compare both with what analytics credits
Spend next month where buyers found you.
@ericrbuilds@romanbuildsaas Warm pools run dry though. Once the free course finishers are sold, the bottleneck moves back to how many new people start the course, so I'd track course signups as the real sales metric.
@longlivealfred@MrrDistribution@therealDakBrown Niche matters more than call count, so I'd build the list from where the niche lives: Google Maps for local businesses, Apollo or LinkedIn filters for B2B titles. I built Evascrape for that, $12 per 1,000 Maps records with phones.
@kcinimoDM The 14 rows usually exist because the plans are split by features instead of by who's buying. I'd put one line under each plan like "for solo founders" or "for teams of 5+" so people find themselves first.
@byrehan Not on the same traffic mix, which is why I'd split by source before trusting either number. A card wall tends to hurt cold search traffic more than referrals, so one blended rate can hide a win in one channel and a loss in another.
I don't judge a SaaS free trial by its trial-to-paid rate.
ChartMogul's 2026 report: 4-6% is good without a card, 25-35% is good with one. A card wall raises that rate and cuts signups.
Compare paying customers per 100 visitors for both setups before you switch.
Most SaaS cold emails get ignored because the first line is about the sender.
Rewrite it around something you saw on their side:
- a review they left on their current tool
- a job post for the role your product replaces
- a tool they just left
No signal, no email.
@velnix_wp One send at launch, then a resend a few hours later to the people who didn't open it. Signups bunching in the first hour doesn't matter when you're judging the week, not the rank.