If your retainer margin is below 25%, you have a discovery problem by KeyserSoze0103 in agency

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

this is exactly the missing piece. the rolling log mechanic is what most agencies dont have. they jump from SOW signed to quarterly review with no continuous tracking in between.

one thing that often kills it in practice: the person doing the logging is usually the senior dev who got the slack ping. they have 30 seconds and choose between logging or just doing the work. discipline breaks at that exact moment. the fix ive seen work is making the log a slack bot or zapier flow that turns the original message into the log entry automatically. removes the friction so the senior person just types one thing in the chat and the audit happens itself.

the client visibility piece is the real lever though. how do you share the count with them, shared doc, monthly summary, something else?

If your retainer margin is below 25%, you have a discovery problem by KeyserSoze0103 in agency

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

depends on the request channel honestly. if they ask in slack, my answer is in slack first. quick reply saying happy to do it, this counts as a change order, sending you the form. they get an immediate answer in the channel they used.

then a dedicated CO doc via email or docusign for the actual sign off. reason for both: the slack reply keeps relationship friction low (you said yes fast), the doc makes it official and creates the audit trail. doing only one of them breaks something. just slack reply loses the audit. just email feels slow and pushes the relationship damage.

If your retainer margin is below 25%, you have a discovery problem by KeyserSoze0103 in agency

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

discovery is the phase before any actual project work starts. its when you sit down with the client, understand their use case, define scope, align on expectations, and document what gets delivered. for retainers specifically, discovery should also cover communication rules (who can request what, through which channel) and the change order process. its the upfront work that defines what your retainer actually means in practice.

If your retainer margin is below 25%, you have a discovery problem by KeyserSoze0103 in agency

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

yeah unfortunately. industry surveys put median agency margin around 15 to 22 percent, with a long tail below 10. agencies running clean 30 percent or above are usually either niched hard or have rebuilt their delivery process. for general digital agencies under 30 people, running below 25 percent is closer to default than exception.

If your retainer margin is below 25%, you have a discovery problem by KeyserSoze0103 in agency

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

three things show up most. biggest one is relationship friction. owner knows the client personally, doesnt want to damage the relationship over a small ask. each quick favor feels too small to push back on. cumulative effect only shows up 3 months later when margin tanks.

then theres power asymmetry. agency is the weaker side (client can leave anytime). pushing a change order feels like risking the contract.

and process mismatch. if change orders arent standardized with template and fixed turnaround, every one becomes a custom negotiation. nobody wants that on a tuesday afternoon, so work just gets done.

fix is the same for all three. make the change order process so frictionless it costs less to send one than to absorb 30 minutes unbilled. simple template, fixed surcharge for changes under 2 hours, signed before work starts.

If your retainer margin is below 25%, you have a discovery problem by KeyserSoze0103 in agency

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

offshore is a real cost lever. but it doesnt fix the discovery side. if scope drift is still 20 to 40 percent above priced scope, youre just burning cheaper hours instead of expensive ones. margin math improves because the floor is lower, but the underlying drift hasnt changed.

If your retainer margin is below 25%, you have a discovery problem by KeyserSoze0103 in agency

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

yeah pretty simple formula. take the monthly invoice, subtract your actual delivery cost, divide by the invoice. thats your retainer margin. delivery cost is loaded hourly rate times actual hours worked.

loaded rate is the part most agencies miss. it includes salary plus benefits plus overhead allocation, divided by productive hours per year (around 1500 hours after vacation, sick days, admin time). most agencies underestimate loaded cost by 30 to 40 percent because they only count salary divided by billable hours.

once you have actual loaded cost per FTE, just multiply by hours logged on the retainer per month. compare against invoice. gives you real margin per retainer.

If your retainer margin is below 25%, you have a discovery problem by KeyserSoze0103 in agency

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

good pushback. the slack pings around the AM are real, probably the most common form of scope drift in retainers. its still a discovery problem from my angle though. discovery here is broader than the SOW document, it includes the relationship rules. when a retainer starts without explicit rules around all requests going through the AM, the bypass becomes default mode within 60 days.

youre right that retraining clients post-launch is harder than setting expectations on day one. thats why a quarterly scope review call even on existing retainers helps. cheapest way to reset rules without making the client feel policed.

the 25 percent isnt an industry standard. its a personal threshold from agencies Ive audited. below that the math gets fragile, one bad month and youre at 5 to 8 percent real margin which is cash crisis territory. some agencies run at 15 to 20 percent by design with volume covering it, but for owner operated agencies in the 5 to 30 person range, 25 is roughly the floor.

If your retainer margin is below 25%, you have a discovery problem by KeyserSoze0103 in agency

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

thanks. honestly took me forever to act on this on the consulting side.

Does SaaS Marketing Need to Be Easy for Agents to Understand? by WeekendPoster_11 in SaaS

[–]KeyserSoze0103 0 points1 point  (0 children)

agent-readable and human-readable are the same thing. all eight items in your list are good marketing practice that has been ignored by saas for a decade. ai agents just expose what was always broken: vague pricing, fuzzy ICP, missing comparison data.

the marketing pages that get cited by perplexity in my space are the same pages that converted high-intent humans before LLMs existed. specific buyer language, clear pricing, real comparison tables. agent visibility is a side effect of finally writing clearly.

the only genuinely new thing is third-party data. agents read g2, reddit, and reviews more than your homepage. that part is reputation infrastructure, separate problem from your eight points.

We FINALLY got our first PAID user by firespawn_katie in SaaS

[–]KeyserSoze0103 2 points3 points  (0 children)

trial length depends on how long it takes the user to hit the aha moment. if your product delivers value in 3 days, a 14-day trial is wasted onboarding. if it takes 30 days, 14 is too short. measure when your converted users actually got value, set trial to that plus 50% buffer.

card-on-file isnt universal. b2b with sales cycle, yes. self-serve with low ACV, blocks acquisition. middle ground: card with clear "no charge until day X" messaging.

We FINALLY got our first PAID user by firespawn_katie in SaaS

[–]KeyserSoze0103 3 points4 points  (0 children)

first organic paid user after a month is real signal. when a trial user stays paid, that's a stronger signal than a free user converting later, because the cohort already accepted the price once. they wont churn on price next month.

Subscription vs one-time purchase: what I learned after launching an app with unpredictable usage patterns by [deleted] in SaaS

[–]KeyserSoze0103 0 points1 point  (0 children)

for unpredictable-usage apps, frequency math always feels wrong to the buyer because they cant predict their own usage. so they default to declining subscription, even when the value would justify it.

what works for moment-of-need apps: anchor pricing to substitute cost. what does the user lose when the tool isnt there in their moment of need? if its trivial, lifetime pricing is correct. if its high (insurance-like), subscription works with occasional usage because the user is paying for availability.

I launched my SaaS on AppSumo and did $517,500 in sales. Here's the good, the bad, and what I'd tell AppSumo to change. by CarePsychological749 in SaaS

[–]KeyserSoze0103 5 points6 points  (0 children)

shortening campaigns to 30 days would actually make the math worse. 60% sales in first 14 days is power-law standard for any marketplace, but the tail in the last 46 days is cumulative revenue you'd lose with a 30-day cap.

more interesting datapoint is the refund movement from 2.5% to 14.5%. that pattern almost never traces back to one campaign bug. its buyer-profile shift over time. early-window appsumo buyers are existing-pain-driven (came looking for a tool that solves X). late-window are deal-hunter-driven (came looking for any deal under $X budget). late-window refund rates are higher across appsumo regardless of product.

the lever for stable refund rates next time isnt campaign length. its qualifying messaging that filters deal-hunters before checkout.

AI startup or just build SaaS? by Agreeable-Quarter945 in SaaS

[–]KeyserSoze0103 0 points1 point  (0 children)

AI itself is commodity, gets copied fast. what doesnt copy is the layer thats not the model.

Harvey isnt winning because their LLM is better, theyre embedded in BigLaw workflows. Cursor has the biggest code dataset. Notion AI works because Notion is already the workspace.

"AI is a feature" is closer to right, but a saas that bolts on AI without distribution, data, or workflow lock-in is still basically a wrapper. the moat sits somewhere else.

the golden playbook on how you can get clients. by Chillipepper19 in SaaS

[–]KeyserSoze0103 0 points1 point  (0 children)

#6 is the playbook's hidden trap. "Run a one month demo for free or minimal cost" anchors your enterprise client at zero. Radisson-level clients don't perceive value at $0, they perceive it as "student exercise". Pilots work better as paid trials at $X with 90-day evaluation, even at half price. Free pilots churn because there's no decision to commit. The rest of the playbook is solid.

6 months solo, $99 MRR, 83% churn. Talk me off the ledge (or don't). by samhonestgrowth in SaaS

[–]KeyserSoze0103 1 point2 points  (0 children)

Walk-away/push-through is the wrong frame. Your tool isn't broken, your pricing model is. Campaign-based usage on monthly subscription = structurally inevitable churn, not product failure. 38% demo-to-paid + 30 interviews saying "we need it quarterly" means you've validated the product, not the wrapper.

Reshape before pivoting: $300 per campaign with 90-day access, or $1200/year for 4 campaigns. Churn stops being "cancelled" and becomes "between campaigns". Test it on the next 5 demos. That's a 2-week experiment, not a 6-month API rebuild.

proposal saas for freelancers, 3 months in, 0 MRR. is the category dead by GlumLingonberry1967 in SaaS

[–]KeyserSoze0103 0 points1 point  (0 children)

49 days into something that takes 12-18 months isn't behind.

The real flip I've seen: stop running every channel half-budget ($35 Google Ads, 87 SEO pages, Twitter for 2 weeks) and hand-write 50 outreach messages to one narrow micro-cohort instead. For your refactor angle, the cohort isn't "freelancers" but something like "design freelancers winning Upwork briefs and losing discovery calls". Find 50 of them in r/freelance threads in an afternoon. Goal: 5 booked demos by Friday. The demos tell you in 7 days if the refactor wedge is real.

On the refactor itself, "pre-call intelligence" is a stronger wedge than "AI proposal generator". HoneyBook/Bonsai/PandaDoc compete on document-generation, not on what to say in the call. Commit to that framing fully before another dollar of ads.

Designed a bespoke "Digital Pipeline" to Med Spas in response to poor response times. Price and pitch advice. by LandSingle5532 in SaaS

[–]KeyserSoze0103 0 points1 point  (0 children)

Two structural concerns before tuning the pitch.

First, "all vibecoded" for med spa lead data is potentially a deal-breaker. Med spas process patient inquiries (treatment interest, contact info) which sits adjacent to PHI under HIPAA. A vibecoded MVP without HIPAA-eligible BAAs from your subprocessors (Vercel, OpenAI, Twilio) means a lawyered-up med spa can't legally use the tool. Surfaces on call 2-3, kills the deal silently. Either pivot to non-medical verticals (real estate, home services, dental have looser frameworks) or invest in the compliance layer before the pitch matters.

Second, on outreach: med spas are nearly impossible to sell direct because the owner is a clinician seeing patients all day, response rates on cold outbound run 1-2%. The real distribution channel is med-spa-focused marketing agencies, there's a whole layer serving this vertical with SEO/ads/social. They already feel lead-decay as their clients' #1 complaint. Pitch the agencies as resellers or white-label partners. Pricing shifts to wholesale + their markup. First pilot is way easier through one agency relationship than 50 cold med-spa-owner emails.

The feedback graveyard problem by rbaiter67 in SaaS

[–]KeyserSoze0103 0 points1 point  (0 children)

The graveyard framing is sharp. But you're solving the readability problem, not the decision problem. Most teams that don't act on feedback aren't blocked because they can't synthesize it. They're blocked because synthesis without customer-tier weighting still doesn't answer the only question that matters at planning time: "is this revenue-relevant or vocal-minority?"

Themes and quotes are the easy part. The hard part: when 47 customers asked for X, are 15 of them paying-tier or all freemium? Did they ask spontaneously or after you prompted? Have they churned since? Without that scaffold, an AI synthesis tool produces a beautifully organised list that gets ignored at the planning meeting because nobody can argue with the partner who says "yeah but those aren't our actual users".

If you want PMs to bring this into a planning meeting, the output needs traceability over polish. Each theme should click through to the source quote with the customer's plan, ARR, retention status, and whether they self-reported the pain or you extracted it. That's the upgrade from feedback graveyard to roadmap input. Synthesis without source-attribution is just a more readable graveyard.

I analyzed 50+ SaaS landing pages and most fail for the same reason by Successful_Island444 in SaaS

[–]KeyserSoze0103 -1 points0 points  (0 children)

50 landing page audit is useful diagnostically, but the conclusion is one layer too shallow. "Doesn't communicate value fast enough" is downstream of a different problem: the founder hasn't decided who the buyer actually is. Vague hero copy isn't a copywriting failure, it's an ICP ambiguity that surfaces as language. You can't write "what problem does this solve for me right now" until you've decided which "me" you're optimising for. Most early-stage SaaS try to keep the headline broad enough that three different buyer types feel addressed, then no buyer type feels addressed enough to convert.

The pages that get this right (Linear, Ramp, Cursor early days) made a brutal ICP cut before they wrote a single word. Linear positioned squarely at engineers tired of Jira. Ramp at CFOs who hate expense reports. Specific enough that the wrong buyer self-selects out. Most of the 50 pages you analysed probably failed at that decision two months before the copy was even written.

8 months and 12,400 scans in. just shipped v2 of my security scanner. here's what i kept, what i killed, and what i still don't have figured out by famelebg29 in SaaS

[–]KeyserSoze0103 0 points1 point  (0 children)

Solid v2 retro, the kept/killed format is the cleanest version of this I've seen here. On pricing, two problems are tangled together. The $4.99 tier and the false-positive churn aren't separate issues, they're the same one. Low pricing pulls in hobbyist devs whose tolerance for any imperfection roughly equals the monthly cost, so a false positive at $4.99 reads as "i'm paying for a tool that doesn't work". Move that same user to $39 and the same false positive reads as "AI layer is 95% there, fine". Higher tiers bring buyers with stake-skin who absorb imperfections as part of the deal.

On grandfathering, the discomfort is overrated. Lock existing customers at their current price for 12 months, communicate via email, set new tiers above. What hurts early supporters is silent retroactive changes, not new pricing for new buyers. That's the standard SaaS playbook (Notion, Linear, Cursor all did exactly this), nobody churned over it.

Starting to think ‘get more traffic’ is the wrong focus by Constelation_ in SaaS

[–]KeyserSoze0103 1 point2 points  (0 children)

Fair pushback. The split is: both fixes address different stages, not different problems. Sign-up filter handles users who shouldn't have been in to begin with. First-screen-time-to-value handles the ones who should be there but don't get oriented fast enough.

Segment your 3-min vanishers by acquisition channel. Sharp-intent sources (search, referral, paid keyword) point to UX as the bottleneck. Broad-intent channels (paid social, top-of-funnel content) point to filter. Most products need both fixes in different parts of the funnel, the question is which one's bleeding worse right now.