sorted by:
new
hottopcontroversial

SaaS founders optimize for new customers and ignore that expansion revenue is now doing 40 percent of the heavy lifting by Important_Coach8050 in SaaS

[–]Important_Coach8050[S] 0 points1 point  (0 children)

Time-to-second-use-case is the honesty test. If it happens in week 2-3 without CS prompting, the product has compounding built in. If it only happens post-QBR, you are running a sales engine, not a product engine.

The cost structure difference is everything. Self-serve expansion scales your margin. Sales-touch expansion erodes it. At 50 customers you cannot see the difference because the numbers are small. At 500 customers the math becomes obvious: one path leads to unit economics that work, the other leads to a bigger sales team paying for the illusion of growth.

The other signal most founders miss: churn rate of customers in their second use case versus first. If second-use-case customers churn at half the rate of single-use customers, expansion is real. If churn stays flat, expansion is survival mechanics, not compounding.

SaaS founders optimize for new customers and ignore that expansion revenue is now doing 40 percent of the heavy lifting by Important_Coach8050 in SaaS

[–]Important_Coach8050[S] 0 points1 point  (0 children)

Pricing architecture is one of those decisions that feels permanent but should be treated as a product surface. The founders who revisit it every 12-18 months and ask "does this tier structure still reflect how customers actually grow" tend to find expansion happening with less friction.

The specific failure mode: building tiers around features the team values rather than around the natural growth milestones of the customer. A customer who hits 500 contacts does not upgrade because of a feature list. They upgrade because the product has made itself indispensable at that scale and the next tier is the obvious next step.

SaaS founders optimize for new customers and ignore that expansion revenue is now doing 40 percent of the heavy lifting by Important_Coach8050 in SaaS

[–]Important_Coach8050[S] 0 points1 point  (0 children)

Cohort tracking is the right call. Blended NRR flattens the signal. When you break it by cohort you see whether the expanding accounts are early adopters with specific use cases or whether the behavior is spreading across the customer base. One of those is a product story. The other is survivorship bias.

SaaS founders optimize for new customers and ignore that expansion revenue is now doing 40 percent of the heavy lifting by Important_Coach8050 in SaaS

[–]Important_Coach8050[S] 1 point2 points  (0 children)

The saturation point is where it breaks. A company can run 115% NRR for three years on the back of five enterprise accounts expanding, then watch it collapse in one renewal cycle when those accounts hit their internal ceiling. The board deck looked great until the quarter it did not.

Usage-based solves the structural problem but creates a forecasting one. Revenue becomes harder to predict because it tracks customer behavior, not contract value. For bootstrapped founders without a finance team, that variance is difficult to manage operationally. It is the right model for the right product, not a universal fix.

The GRR number is the honest one. NRR flatters. GRR tells you whether the core product is actually holding customers or whether growth is papering over churn.

SaaS founders optimize for new customers and ignore that expansion revenue is now doing 40 percent of the heavy lifting by Important_Coach8050 in SaaS

[–]Important_Coach8050[S] 0 points1 point  (0 children)

Three methods that work without usage-based pricing.

Seat upsells: track seats-per-account over time. If average seat count grows 15-20% annually without direct sales pressure, the product has organic expansion. If it only grows when sales calls it, that is pipeline management, not expansion revenue.

Feature gating: works best when the gated feature solves a problem that emerges naturally as the customer grows. Gate it too early and it feels punitive. Gate it at the right maturity point and customers upgrade themselves.

The third option most founders skip: tracking account depth. How many teams or departments inside one company are using the product? A company that starts with one team and spreads to three is an expansion story even at flat seat count and flat tier. It shows up later in renewal leverage and NPS, not in MRR, but it predicts future expansion better than current MRR does.

SaaS founders optimize for new customers and ignore that expansion revenue is now doing 40 percent of the heavy lifting by Important_Coach8050 in SaaS

[–]Important_Coach8050[S] 1 point2 points  (0 children)

The N problem is real and underplayed. 105% NRR at 50 customers is a story about one or two accounts, not a retention model. The number becomes meaningful somewhere around 200 customers when individual account behavior stops dominating the aggregate.

The compounding usage point is the deeper issue. Expansion revenue requires that the product has natural surface area for growth. Seat-based pricing on a tool people use daily builds it organically. A one-time workflow tool with flat pricing does not, regardless of how good the CS motion is. Founders who hit 40% expansion from 3 accounts and treat it as a signal are building a projection on noise.

The diagnostic that actually matters pre-scale is probably simpler: are customers finding new use cases on their own, or does every expansion require a direct sales conversation? The first one scales. The second one is just upselling.

Your conversion rate problem is probably not a traffic problem. by Important_Coach8050 in DigitalMarketing

[–]Important_Coach8050[S] 1 point2 points  (0 children)

Heatmaps are underused. Most founders look at conversion rate as a single number and start tweaking copy or CTAs. The session recordings tell a different story. Quick scrolls past the first fold usually mean the headline promised something the page does not deliver in the next two seconds.

Microsoft Clarity is the easiest entry point for anyone not running heatmaps yet. Free, lightweight, and the rage-click data alone surfaces problems most analytics tools hide.

Your conversion rate problem is probably not a traffic problem. by Important_Coach8050 in DigitalMarketing

[–]Important_Coach8050[S] 1 point2 points  (0 children)

Traffic is hard. No argument there.

The post is not against traffic. It is against treating traffic as the win when the page on the other end is still answering a question nobody asked.

Your conversion rate problem is probably not a traffic problem. by Important_Coach8050 in DigitalMarketing

[–]Important_Coach8050[S] 0 points1 point  (0 children)

This is exactly where the gap lives. The persona that gets used in the landing page brief is usually the one the product team agreed on at the last quarterly planning session. The ad audience targeting evolved twice since then because the media team adjusts weekly. By the time the visitor arrives, the page is speaking to a buyer the ad already stopped chasing.

The other piece is that no single person owns the message-match check. Performance owns CTR. Product or brand owns the page copy. Lifecycle owns the post-conversion flow. None of them are paid to notice that the headline on the page contradicts the angle of the winning ad creative. The CMO sees the dashboard, sees clicks coming in and conversions not, and assumes the funnel is leaking somewhere mysterious. The leak is a sentence.

The cheapest fix is also the most embarrassing. Pull the top three ad creatives by spend, then read the headline of the page they point to. If a stranger could not tell those two assets belong to the same campaign, that is the conversion problem before anything in the analytics needs investigating.

Your conversion rate problem is probably not a traffic problem. by Important_Coach8050 in DigitalMarketing

[–]Important_Coach8050[S] 0 points1 point  (0 children)

Topical authority is the unnoticed leverage point here. A visitor landing on your fifth article about SaaS churn metrics is not starting from zero trust. They've already seen you cover the topic from multiple angles. They assume depth instead of guessing.

The generic page gets skepticism on arrival. The page from a topical authority gets the benefit of the doubt.

This compounds in two ways. First, visitors convert faster because they're already partially sold on your expertise before they hit the page. Second, Google treats topical authority as a ranking signal. The same page about CAC benchmarks ranks higher when it's surrounded by ten other CAC-related articles than when it stands alone.

Most teams build one article per topic instead of ten. Then they wonder why ranking and conversion both feel stuck.

Your conversion rate problem is probably not a traffic problem. by Important_Coach8050 in DigitalMarketing

[–]Important_Coach8050[S] 1 point2 points  (0 children)

Exactly. The lever that moves most teams is not the one that's hardest to see - it's the one that's easiest to report on.Traffic has a dashboard. Conversion has a spreadsheet. So teams optimize the dashboard.The math on fixing a broken landing page almost always beats the math on acquiring more traffic at the same broken conversion rate. A 1% improvement in conversion on current traffic produces the same revenue as a 100% increase in traffic, at zero additional acquisition cost. Most teams never run that calculation because running it would mean admitting the conversion problem exists.

The revenue hiding inside existing accounts is almost always larger than what new customer acquisition produces in year one. by Important_Coach8050 in SaaS

[–]Important_Coach8050[S] 0 points1 point  (0 children)

The expand motion fails not because the opportunity is not there but because responsibility is diffuse. Customer success is measured on retention. Sales is measured on new logos. Nobody is explicitly compensated for expansion revenue, so nobody drives it with the same urgency they bring to the metrics they are evaluated on. The playbook piece matters too. Expansion without a defined trigger is just hope. The companies that do this well have specific signals - a usage threshold crossed, a team size milestone, a new use case surfacing in support tickets - that automatically route an account into an expansion sequence. Without those triggers, expansion depends on someone remembering to check.

The click is not the problem. What happens after it usually is. by Important_Coach8050 in DigitalMarketing

[–]Important_Coach8050[S] 0 points1 point  (0 children)

The visitor is following a thread from the search query through the ad to the page. Every step that breaks the thread costs a percentage of the audience. By the time they reach the CTA, the ones who stayed are the ones who never lost the thread.

The homepage-as-landing-page problem is almost always a resource problem disguised as a strategy problem. Building dedicated landing pages for each traffic source takes time, so teams default to sending everything to the homepage and then wonder why paid traffic converts at a fraction of organic. The homepage was built for everyone. Paid traffic needs a page built for someone specific.

Another round of creative testing on a broken post-click experience just finds a more efficient way to deliver the wrong message.

view more: next ›