Cold outreach to prospect list
Direct email or LinkedIn message to B2B prospects. Keep it personal, short, and specific to their situation. Claude writes the copy.
Building the product is only half the job. The other half is getting real users, real retention, and real revenue. The Traction Menu is the set of growth activities we run alongside the build to make that happen.
Every product is at a different stage with a different audience — so these are a menu, not a checklist. Your product owner picks the handful that fit where you are right now, runs them, learns from the signal, and adjusts. Pick what fits; skip what doesn't.
We match activities to where your product actually is — pre-launch, early users, or scaling — and to who your buyer is.
A dedicated Designli product owner owns each activity end to end, using AI to move fast and pulling in the pod when engineering is needed.
We measure the signal from each one, keep what works, drop what doesn't, and feed the learning straight back into the roadmap.
Finding and recruiting the right early users.
Direct email or LinkedIn message to B2B prospects. Keep it personal, short, and specific to their situation. Claude writes the copy.
Share the landing page or ask for feedback in relevant communities. Lead with value, not promotion. Getting 10 quality signups from a relevant subreddit beats 100 random clicks.
Help the founder draft a personal ask to their existing contacts. The most effective first source of users is almost always people the founder already knows.
Capture interest and qualify early users directly on the landing page or via a follow-up. Ties responses to PostHog user data.
Offer early access in exchange for an intro to their audience. Works well for niche B2C products where one trusted voice reaches hundreds of ideal users.
Building an audience through useful content.
Authentic story post from the founder. Claude drafts, founder personalizes. Performs well organically. Publish on LinkedIn or Substack — wherever the ICP is.
A page targeting a problem keyword ("best tool for X" or "how to solve Y"). Builds organic traffic over time. PO scaffolds with Claude Code and Astro — no dev needed.
One email per week: what we're building, what we're learning. Keeps the waitlist warm and filters for engaged users. High open rates because subscribers opted in early.
"The old way vs. [product name]" — pure content, no app needed, sharpens positioning and drives search traffic. Pure Claude Code task.
These require dev work from the pod. PO owns the hypothesis and spec; pod builds it.
Users move up the waitlist by referring friends. Classic pre-launch viral mechanic. Works best when the product has clear demand.
Standard refer-a-friend with incentive. Incentive design matters — discount, free month, or upgrade all perform differently depending on the product.
PostHog funnels reveal where users drop off. PO identifies the drop-off hypothesis, pod fixes the flow. Session replay is the fastest way to spot what's confusing.
B2B viral loop — one user pulls in their colleagues. Most effective B2B growth mechanic when the product has multi-user value.
Learning from early cohorts to feed the hypothesis portfolio.
The most valuable thing a PO can do early. Claude writes the script — focus on problems, not features. Don't pitch; listen. Record with consent.
5 questions max, triggered after a key action. Ties responses directly to user behavior data in PostHog.
Watch what early users actually do in the product. More honest than any survey — users say one thing and do another. Block 30 minutes per week for this.
PO writes one paragraph per week summarizing traction learnings. Feeds directly into the portfolio review — traction results are hypotheses too.
Most founders either ignore paid entirely or waste money on it too early. PO can own the learning loop.
$200–500 on Meta or Google to validate messaging and ICP targeting before spending real money. PO writes the hypothesis, Claude generates ad copy and variations, PO reads the results.
Pixel installation and a basic retargeting audience for people who visited but didn't sign up. Cheapest paid channel there is. Pod handles the pixel; PO defines the audience logic.
UTM discipline from day one. PO sets up a simple tracking convention so the founder actually knows which channel drove which signups.
Leverage other people's audiences instead of building your own from zero.
Build an integration with a complementary product, then co-promote the launch. PO identifies the partner, manages the relationship, coordinates the announcement. Both sides benefit.
Joint webinar, case study, or blog post with a non-competing product that shares your ICP. PO handles outreach and coordination, Claude drafts the content.
For products where someone else touches your buyer (consultants, agencies, adjacent SaaS). PO designs the program terms and tracking. Simple at first — even a shared discount code works.
Knowing what you're up against and how to position against it.
PO maintains a living doc: who the competitors are, what they charge, what they launched this month, where they're weak. Updated monthly. Claude summarizes competitor changelogs and review sites.
When a prospect chooses a competitor or chooses you, PO captures why. Five data points here are worth more than a hundred survey responses.
MVPs look like MVPs. At some point that becomes a liability.
Once the product has traction, PO specs a design sweep: consistent spacing, better empty states, loading states, error messages. Not a redesign — a cleanup. Pod executes.
Component library, color tokens, typography rules. Makes every future sprint faster and prevents the UI from drifting into chaos as features pile up.
Receipts, password resets, notifications. These are often the most-seen pieces of the product and they usually look terrible. Claude drafts copy, pod templates them.
When the product outgrows its first surface.
Launched on web, now need mobile (or vice versa). PO runs the discovery: what translates, what's native-only, what's the minimum viable second platform. Natural upsell into another pod engagement.
If the product has data or functionality others want, PO scopes a public API. Developer docs, rate limits, authentication. Turns a product into a platform.
Zapier/Make integration so users can connect the product to their existing stack without custom dev. Reduces churn for power users.
Testing willingness to pay and optimizing the upgrade path.
PO sets up two or three pricing tiers and tests willingness to pay with early cohorts. Claude drafts the pricing page copy.
Instrument the upgrade path, identify where people bail, test different triggers (usage limits, time-based trials, feature gates). PO owns the hypothesis; pod builds the paywall logic.
When someone cancels or goes inactive, PO runs a 15-minute call or sends a 3-question survey. Cheapest source of product truth you'll ever get.
Keeping users engaged after they sign up.
Triggered emails based on user behavior: welcome, activation nudge, "you haven't been back," milestone celebration. PO writes the logic and copy; email platform handles delivery.
Define 3–5 triggers worth interrupting someone's day. Most founders either send zero notifications or spam. PO designs the rules. Pod implements.
PO pulls a PostHog dashboard showing DAU/WAU ratio, feature adoption, and session depth. One paragraph: what's working, what's not, what we're trying next week.
Passive acquisition channels that compound over time.
Screenshots, description copy, keyword strategy, review solicitation flow. Claude drafts all the copy. PO manages the submission process.
If the product connects to other tools, get listed in their marketplaces (Zapier, HubSpot, Shopify app store, etc.). Each listing is a passive acquisition channel.
G2, Capterra, Product Hunt collection pages. PO creates the profiles, seeds with early reviews. Pure hustle, no dev work.
Packaging the product and its data for external audiences.
A one-page view of the numbers that matter: activation rate, retention curve, revenue, growth rate. PO builds this in PostHog or a simple Astro page. Updated weekly.
Architecture documentation, test coverage report, dependency audit. Pod generates this; PO packages it. Becomes critical when a Series A firm sends their technical advisor.
The boring stuff that becomes a blocker the moment a real buyer shows up.
Claude drafts, founder's lawyer reviews. Most MVPs ship without these, then a B2B prospect's procurement team asks and it becomes a blocker.
WCAG 2.1 AA baseline check. PO runs an automated scan, pod fixes the critical issues. Increasingly a legal requirement, not just nice-to-have.
For B2B SaaS, enterprise buyers ask. PO can start the evidence collection early even if formal certification comes later.
Someone has to answer when users get confused.
Claude drafts articles based on the most common user interview questions and session replay confusion points. Hosted on a simple Astro site or Notion public page.
Even if it's just a shared inbox at first, PO defines the triage process: who responds, how fast, what gets escalated to the pod as a bug vs. a feature request.
These activities are part of how Designli helps founders turn a working product into a growing one. Tell us where you are and we'll map out the right first moves.
Talk to Designli →
Social & Community
4Presence and engagement on the primary channel.
Consistent posting
3x/week minimum on the primary channel. Claude batches a week of content at a time — give it the value prop and three things that happened this week.
Community engagement
Spend 15 minutes/day answering questions in 3–5 relevant communities. Build credibility before promoting. Never post a link in the first message.
Create a community for early users
A Discord or Slack for beta users creates a direct feedback loop and makes early users feel invested in the product's success.
Product Hunt launch
Launch once there is something real to show — not a landing page. Drives a spike of early adopters and signals legitimacy to investors.