If I Could Turn Back Time  🔗 **Source:** [If I Could Turn Back Time](https://www.youtube.com/watch?v=ar4qSVuFodQ) > [!note]+ Document Notes > > [!info] Generated analysis — not the author's words. Sections below are machine-written > > from the captured source. Only text inside `> [!quote]` blocks is verbatim from the author. > > Do not quote or attribute any other line to the named author. > > # 🏷️ Title: If I Could Turn Back Time (Agency Edition) > <!-- deep-read:sections start --> ## 🧭 Table of Contents - [[#🔗 References]] - [[#📝 Summary]] - [[#📖 Main Content]] - [[#📚 References|📚 References (Section 6)]] - [[#🗣️ Paraphrase]] - [[#📰 Newsletter]] - [[#✅ Action Items]] - [[#🧪 Hypotheses]] - [[#📊 Methodology]] - [[#❓ Questions]] - [[#🔮 Future Research]] - [[#💡 Implications]] - [[#🧠 Learning Styles Assessment]] - [[#📊 Accessibility Assessment (WCAG 2.2 AA)]] - [[#🌍 DEIB Assessment]] - [[#✅ Logical Validity]] - [[#🛡️ DARVO Analysis]] - [[#🎯 Conclusion]] - [[#🔄 Refactor Appendix — If I Could Turn Back Time (Agency Edition)]] ### 🔗 References - Kurt Vonan — co-host, principal of Mañana No Más (manananomomas.com) - Toby Cryns — co-host, principal of The Mighty Mo (themightymo.com), also referenced as "Toby Crimes" in the auto-transcript (mis-hearing of "Cryns") - John Maxwell — leadership author, cited for the "replace yourself with someone 80% as good" delegation principle - SendGrid (SenGrid in transcript) — email deliverability tool referenced as a competence litmus test for outsourced vendors - LifterLMS — LMS plugin referenced in the dual-payment-gateway support incident - WooCommerce — e-commerce plugin referenced throughout (both hosts serve WordPress/WooCommerce clients) - South Valley Economic Development Center, Albuquerque — small-business incubator referenced for the "building yourself a job" anecdote - "Meeting agendas" / EOS agenda — referenced as a callback to a prior episode in the same podcast series ## 📝 Summary - **What happened**: Two WordPress/WooCommerce agency owners (Kurt Vonan of Mañana No Más, Toby Cryns of The Mighty Mo) hold an unscripted, recurring-podcast conversation reflecting on what they would refuse to sell or do differently if rebuilding their agencies from scratch today. - **Why it matters**: The conversation surfaces recurring failure modes in service-agency economics — scope creep on legacy-site work, founder bottlenecking ("secret sauce" and "one-minute manager" syndrome), pricing/margin blindness on subcontracted work, and the emerging problem of AI-generated RFPs devaluing human sales effort. - **Stakeholders**: Agency owners/founders, agency sales and support staff, agency clients (especially those who shop around for cheaper vendors), and by extension anyone running a services business dependent on founder-delivered quality. - **Risks**: Founders who stay the "secret sauce" cap their own growth and burn out; agencies that quote site-remediation work without firm boundaries absorb open-ended scope risk; agencies that don't niche or product-ize support risk commoditization; unchecked, AI-generated RFP volume could erode the value of genuine human sales effort industry-wide. - **Bottom line**: The strongest through-line is that successful agency growth requires founders to convert themselves from doers into replaceable processes — and to draw and hold firm boundaries (on scope, on cheap work, on rescuing botched third-party work) rather than solving every problem personally. ## 📖 Main Content ### 🗒️ Notes No on-screen timestamps are visible in the Reader UI, but the transcript carries per-word `data-rw-start` offsets in seconds; approximate segment starts are given below using those offsets. - **~0:00–1:30 — Cold open: "What would you refuse to sell?"** Kurt says he'd stop selling site audits and rebuild quotes on existing sites — calls it "playing in other people's gardens," since inherited custom fields/CSS create open-ended scope risk. He'd only do fresh builds going forward. - **~1:30–4:00 — Toby's counter-answer: process over refusal.** Toby says he wouldn't refuse a category outright, but would refuse *selling without a firm process/boundaries*. He'd reposition his own process and tooling as the sales pitch itself ("you need us for our process and our tools") rather than a concession to the client. - **~4:00–6:30 — Cheap work as a relationship gateway.** Both agree cheap/discounted work for *existing* clients can be fine if there's a repeatable process behind it; the danger is pricing something too low with no process to "jam it into," which is where past pain came from. - **~5:00–9:00 — User support as an underrated profit center.** Toby recounts a live launch-week story: a customer couldn't find a lead-magnet email (landed in spam); the team proved via screen-share and SMTP logs that everything worked, resolved the customer politely, and used that proof to pre-empt any invoice dispute — "easy money" and justification for years of recurring billing. - **~9:00–12:00 — The "secret sauce" founder problem.** Kurt admits he still personally runs the first week of every launch's support because he wants to control tone/voice and be ready for escalation — and explicitly says "I realize that's wrong," since it keeps him hands-on when he should be running sales meetings and generating revenue instead. - **~12:00–17:00 — Delegation and the John Maxwell 80% rule.** Toby cites John Maxwell: if someone can do a task 80% as well as you, replace yourself with them — "bar none." Both admit falling into "one-minute manager" behavior (knocking out small tasks personally instead of delegating), at the cost of funnel work, new sales, and "networking backwards" with existing clients for referrals. - **~17:00–24:00 — Profit vs. enjoyment vs. peace of mind.** They interrogate whether agency decisions are driven by what's profitable or what the founder personally enjoys (e.g., Kurt's launch-week involvement is emotionally satisfying but not itself profit-generating once the sale is closed). Kurt frames his current life stage as optimizing for "peace of mind" over pure growth or revenue; Toby struggles to define happiness at all, floating (and doubting) the idea that happiness equals "a lack of responsibility." - **~24:00–30:00 — Growth math and subcontractor margins.** They discuss how growth changes agency economics non-obviously: hiring means you must sell 2.5x more at a 40% margin just to net the same take-home; subcontracting a $10k job for $6k nets $4k for coordination — which can be a good margin, but founders resist accepting that framing. - **~30:00–33:00 — "Building yourself a job" vs. building a company.** Kurt recounts an Albuquerque small-business-incubator phrase distinguishing founders who build a duplicable, hireable business from those who "build themselves a job." Notes that many agency owners in their circles would bankrupt themselves personally if they scaled a team, because they can't sell at a level that supports both staff and themselves. - **~33:00–43:00 — AI-generated RFPs and the asphalt/road anecdote.** Both report a rising share of RFPs are visibly AI-generated (encyclopedic bullet-point requirements, questions from people with no domain knowledge), while their own responses remain deeply human — creating an asymmetric-effort problem. Toby now sometimes replies bluntly that a request "appears to be AI generated" and offers a real conversation instead. Kurt shares a possibly-apocryphal anecdote: a government road-building RFP asked for "asphalt," a bidder delivered literal crushed rock (technically asphalt aggregate) instead of a paved road, won on price, and got away with it because "that's not what the bid was for" — used as a metaphor for exploiting literal RFP language versus genuine need. - **~43:00–52:00 — Cheap outsourcing gone wrong.** Kurt describes a long-term hosting client who balked at his (already discounted) quote for added services, hired a cheaper unverified vendor who broke the client's forms (didn't even use the site's own form tool) and didn't know what SendGrid was, then came back to Kurt with an "emergency." Kurt held a firm boundary: offered to quote the repair or hand over a full backup for migration, but declined to fix it for free, explicitly framing it as "this is the result of your decision." - **~52:00–58:00 — Product-izing boundaries: the "unlimited warranty."** In reaction, they float productizing hosting/maintenance support into an explicit "unlimited warranty" tier (all edits/maintenance/updates included) priced at roughly $4,000–$10,000/month depending on scale — as a way to make the boundary a sellable product rather than an ad hoc favor. - **~58:00–68:00 — Niching by product, not audience; e-learning/e-commerce as recurring-revenue niches.** Toby distinguishes "niching down" by product (e.g., specializing in one platform/workflow) from niching by audience/vertical (e.g., agencies that "only do web development for plumbers" or "only do advertising for roofers"). Both cite e-learning (ticketed user support with 12–24hr guaranteed response, thousands of dollars/month) and e-commerce/WooCommerce as niches with built-in recurring support demand. Toby recounts a concrete technical war story: a client's Stripe payment gateway was activated in both LifterLMS and WooCommerce simultaneously, so the two integrations' webhooks canceled each other out and silently dropped two orders — diagnosed in minutes once someone who understood the stack looked at it. - **~68:00–end — Closing CTA.** They close with a direct audience prompt — "what could you stop doing today that would strengthen everything else?" — and contact info: Toby on LinkedIn and at themightymo.com; Kurt at manananomomas.com and on LinkedIn. ## 📚 References - John Maxwell's leadership writing (specifically the 80%-replacement delegation principle) — named directly, not linked - SendGrid — named as a competence benchmark for legitimate marketing/dev vendors - LifterLMS and WooCommerce — named platforms central to the payment-gateway conflict story - South Valley Economic Development Center (Albuquerque) — named small-business incubator source of the "building yourself a job" framing - The hosts' own companies as primary sources of the anecdotes: Mañana No Más (Kurt Vonan) and The Mighty Mo (Toby Cryns) - A prior episode in the same podcast series, referenced for "meeting agendas" / EOS-style agenda structure (not independently named or linked in this transcript) ## 🗣️ Paraphrase Two working agency owners use a casual, recurring-podcast format to audit their own operating mistakes, landing on a shared diagnosis: growth stalls not from lack of demand but from founders who won't stop doing the work themselves — whether that's personally handling launch-week support because it feels good, knocking out "one-minute" tasks instead of delegating them, or under-pricing rescue work on someone else's broken site because turning down a relationship feels wrong. They trace this into concrete economics — the counterintuitive math of subcontractor margins and the doubled sales effort growth actually demands — and into a philosophical aside about whether agency decisions are optimized for profit, personal enjoyment, or peace of mind, none of which they find easy to define. From there the conversation turns outward to two structural pressures reshaping their market: cheap, unqualified outsourced labor that clients hire instead of paying full agency rates, which then boomerangs back to the agency as an unpaid "emergency," and a rising tide of AI-generated RFPs that make the sales process feel increasingly asymmetric, since the agencies still answer with real human effort while the other side may not even read the response. Their proposed fixes converge on the same idea from different angles: turn implicit expectations into explicit, priced products — a firm process sold as the offering itself, an "unlimited warranty" maintenance tier instead of ad hoc rescue work, and a platform- or workflow-based niche (e-learning support, WooCommerce) instead of trying to be everything to everyone. ## 📰 Newsletter Two agency owners get honest about what they'd refuse to sell if they started over — and it's not a client type, it's themselves as the bottleneck. This episode of the "Agency Action" show digs into the "secret sauce" trap (founders who can't let go of launch-week support), the real math behind subcontractor margins and growth-driven sales targets, and a blunt boundary story about a client who hired a cheap vendor, got burned, and came back expecting a free fix. The back half turns to two forces squeezing agencies right now: AI-generated RFPs that make sales feel one-sided, and the case for productizing support (think "unlimited warranty" hosting tiers) instead of absorbing scope creep for free. If you run — or hire — a services business, the "building yourself a job vs. building a company" distinction alone is worth the listen. ## ✅ Action Items Not applicable — WordPress-specific subteam categories (WordPress core/DevRel/OSS-governance) don't map to this source, which is a general agency-operations conversation, not WordPress project governance. Two generic action items are genuinely relevant to Courtney's own agency/consulting-adjacent work: - Audit any current engagement where you're the "secret sauce" (the person clients implicitly expect for escalation) and identify who could cover it at 80% quality. - If any current pricing includes ad hoc "we'll just fix it" support, consider whether it should become an explicit, priced maintenance/warranty tier instead. ## 🧪 Hypotheses 1. Agencies that convert founder-delivered quality into documented, delegable process retain client satisfaction scores within a small margin of founder-delivered work (testable via before/after CSAT or NPS when a founder hands off a support function). 2. Firms that quote a flat "unlimited warranty" maintenance tier see fewer disputed invoices on rescue/emergency work than firms that price emergency support ad hoc. 3. The proportion of RFPs an agency identifies as AI-generated correlates negatively with that RFP's eventual close rate. 4. Agencies that niche by product/workflow (e.g., WooCommerce-only, LMS-only) sustain higher support-ticket margins than agencies that niche by client vertical/industry alone. 5. Founders who personally handle the "first week" of every client launch show measurably lower new-business pipeline activity in that same week compared to weeks they don't. 6. Discounted work for existing clients converts to expanded scope/upsell revenue at a higher rate than equivalently discounted work for new clients. ## 📊 Methodology Not applicable — this is an unstructured, anecdote-driven conversation between two practitioners, not an empirical study. No data collection, sampling, or evidentiary method is used; all claims are personal experience, informal pattern recognition ("we've noticed"), and one explicitly unverified anecdote ("who knows if it's true or not"). ## ❓ Questions - At what revenue/team size does "secret sauce" founder involvement stop being a strength and start being a growth ceiling — and is that threshold measurable in advance? - Is there a reliable way to price "unlimited warranty" maintenance so it doesn't become the next source of unbounded scope risk the hosts are trying to escape? - How should agencies actually respond to visibly AI-generated RFPs — decline, auto-respond in kind, or force a human conversation — and which approach protects close rate best over time? - Does niching by product (platform/workflow) actually outperform niching by audience (industry vertical) in support-ticket margin, or do both work equally well with sufficient process? - What early warning signs distinguish a founder who is "building a company" from one who is "building themselves a job," before the team-hiring decision is made? - How do agencies fairly and clearly draw the boundary between "we'll rescue your botched third-party work" and "you made your bed" without damaging the client relationship? ## 🔮 Future Research - A structured survey of WordPress/WooCommerce agency owners on delegation practices and their correlation with revenue growth and founder burnout. - A comparative study of "unlimited warranty" or flat-rate maintenance pricing models against time-and-materials emergency billing, measured on dispute rate and gross margin. - Tracking of RFP response effort vs. close rate segmented by detected AI-authorship, to quantify the asymmetric-effort problem described in this conversation. - Case studies of agencies that successfully transitioned from audience-based niching to product/workflow-based niching (or vice versa). ## 💡 Implications - **Practice**: Agencies should formalize "who covers launch week" and "what counts as an emergency" into written process before they're needed, rather than relying on founder heroics in the moment. - **Policy**: None directly — this is a private-sector operations conversation with no regulatory or public-policy dimension. - **Education**: The delegation and pricing-math content (subcontractor margins, growth-driven sales targets) would work well as a case study in small-business/agency-operations training or DevRel-adjacent consulting curricula. - **Funding**: Not applicable — no funding, grant, or investment dimension is discussed. ## 🧠 Learning Styles Assessment - **Visual**: Weak — audio-only conversational format with no charts, diagrams, or visual aids; a visual learner gains nothing extra from the source itself. - **Aural**: Strong — the entire source is a spoken, conversational podcast; tone, pacing, and back-and-forth banter carry meaning that a pure transcript read loses. - **Verbal**: Strong — argument and insight are carried entirely through language and analogy (the asphalt/road story, "playing in other people's gardens," "building yourself a job"). - **Kinesthetic**: Weak — no hands-on demonstration, exercise, or physical task is modeled; all content is reflective/discursive. - **Logical**: Moderate — some structured economic reasoning appears (margin math, the 2.5x sales-growth calculation) but it's conversational and not rigorously worked through. - **Social**: Strong — the format itself is a peer dialogue modeling how two founders think out loud together; useful for anyone who learns by watching (or joining) a conversation between practitioners. - **Solitary**: Moderate — useful for solo reflection afterward (e.g., the closing prompt "what would you stop doing"), but the content itself is generated through dialogue, not solitary study. - **Naturalistic**: Weak — no environmental, biological, or classification content applies. - **Reading level estimate**: Roughly 8th–10th grade equivalent (Flesch-Kincaid range) — casual, conversational spoken English with business jargon (RFP, SMTP, webhook, margin) but simple sentence structure typical of unscripted speech. ## 📊 Accessibility Assessment (WCAG 2.2 AA) - **Text alternatives**: A full transcript is present in Reader (this is itself the text alternative for the audio/video), which satisfies the core requirement; the source YouTube video should also carry captions, though caption accuracy wasn't independently verified here. - **Adaptable/reflow**: The Reader-captured transcript reflows as plain paragraph text, which is accessible; the original YouTube player's caption/transcript reflow was not evaluated directly. - **Distinguishable**: Not directly assessable from a text transcript — no color contrast or visual distinguishability claims apply to this audio-first source. - **Predictable navigation**: N/A at the source level (a single continuous conversation, no internal navigation structure); the Reader document itself navigates predictably (linear paragraphs). - **Input assistance**: N/A — no forms or interactive input exist in this content. - **Time-based media**: This is the most relevant category for a video source — a transcript is available and was captured for this analysis, which meets the base captioning/transcript expectation; whether the live YouTube video has synchronized closed captions (vs. only auto-captions) was not independently confirmed. - **Compatible/parsing**: The Reader HTML transcript is well-formed paragraph markup and parses cleanly with standard tooling (verified while extracting quotes for this analysis). ## 🌍 DEIB Assessment - **Cultural breadth**: Narrow — the conversation reflects a single cultural/professional context (US small-agency web-services entrepreneurship); no international, cross-cultural, or non-Western business perspectives are represented. - **Inclusive language**: Generally neutral; no exclusionary or discriminatory language observed. Casual references (e.g., "she" for an unnamed outsourced vendor, "he" for an unnamed peer) are incidental and not evaluative of identity. - **Neurodiversity support**: Not addressed — the conversation doesn't discuss neurodivergent working styles, though the confessional tone about personal compulsions (e.g., Kurt's comment about needing the dishwasher loaded "more efficiently") is offered candidly and without stigma. - **Representation**: Both speakers are male agency founders; no other genders, roles, or seniority levels are represented in the dialogue itself (client and staff voices are only paraphrased, not heard directly). - **Psychological safety**: High between the two hosts — they openly admit personal flaws, business mistakes, and unresolved struggles (e.g., "I realize that's wrong," uncertainty about defining happiness) in a low-stakes, peer-supportive tone, modeling vulnerable professional self-disclosure. ## ✅ Logical Validity - **Strong reasoning present**: The subcontractor-margin math (a $10k job at $6k cost nets $4k, which may or may not be a bad margin depending on framing) and the growth/sales-multiplier math (selling 2.5x more at 40% margin to net the same money) are both sound, testable arithmetic used to challenge an intuitive but flawed assumption ("I should have just done the work myself and kept it all"). - **Named fallacies**: - *Hasty generalization* — "what is one thing every successful agency stops doing" is answered with a single anecdotal marker (no longer advertising/running paid ads), which Toby himself immediately partially rebuts (Target and Walmart still advertise and are clearly successful) without fully resolving the contradiction. **Fix**: reframe as a correlational tendency observed in some successful agencies, not a universal marker. - *Appeal to authority (unqualified)* — the John Maxwell "80%" delegation rule is invoked as a settled principle without evidence, context of where it applies, or acknowledgment that "80% as good" is subjective and hard to measure in service work. **Fix**: treat it as a useful heuristic and pair it with a concrete measurement (e.g., CSAT delta) before treating it as decisive. - *Unverified anecdote presented as illustrative fact* — the asphalt/road government-bid story is explicitly flagged by the teller as possibly untrue ("who knows if it's true or not") but is still used rhetorically as though it demonstrates a real negotiating principle. **Fix**: label it clearly as a parable/illustration rather than a case example when reusing it (which this analysis already does by framing it as "possibly apocryphal"). - **Tone of voice**: Casual, self-deprecating, exploratory rather than declarative — both speakers frequently hedge, contradict themselves mid-thought, and explicitly invite audience disagreement ("please leave a comment"), which is consistent with a peer-reflection podcast rather than an authoritative how-to. ## 🛡️ DARVO Analysis Not applicable — DARVO (Deny, Attack, Reverse Victim and Offender) describes a response pattern to being confronted with wrongdoing, typically in interpersonal or institutional conflict. This source contains no accusation-and-defense dynamic; the closest analog (Kurt's account of the client who hired a cheaper vendor and then filed an "emergency" request) shows Kurt declining to do free rescue work and stating a plain boundary ("this is the result of your decision"), but this is boundary-setting, not deny/attack/reverse-victim-offender behavior — he doesn't deny responsibility for something he did, attack the client's character, or claim victim status himself. No DARVO pattern is present. ## 🎯 Conclusion The bottom line: the two recurring failure modes both hosts identify — founders who won't stop being personally load-bearing, and agencies that absorb scope/pricing risk instead of pricing it explicitly — are two faces of the same problem: implicit expectations that were never turned into an explicit product or process. Practical next steps drawn from the conversation: (1) name and document who besides the founder can competently run the highest-touch moments of client delivery (e.g., launch week), even if imperfectly; (2) convert ad hoc "we'll just fix it" support into a priced, bounded product (their "unlimited warranty" idea) so boundary-setting doesn't have to happen client-by-client under duress; (3) decide deliberately whether to niche by product/workflow or by audience vertical, rather than drifting into "everything for everyone"; and (4) build an explicit policy for handling AI-generated RFPs before the volume makes ad hoc handling unsustainable. ## 🔄 Refactor Appendix — If I Could Turn Back Time (Agency Edition) > Density: 2–5 Literature atoms (H3), 0–3 Permanent candidates (H4). > Defaults: 3 Literature, 1 Permanent. Resonance filter: if you can't > articulate in one line why a claim matters, drop it. > > Konik claim-header rules: present tense, declarative, ≤10 words when > possible, searchable, unique, mirrors annotation focus if present. > > Atomicity: one declarative sentence per atom. "and"/"also" → split. > > Tag pool: #bmf · #addendum · #xref · #articleseed · #storystem · #share · #aphorisms ### 📚 Literature Atoms (H3) #### [H1] Refuse legacy-site rebuilds, sell only fresh builds > [!quote] ID:rw_atom1 > I would just do fresh builds and no more sales off of site auditing. **Context & use**: - Appears in the cold open, as Kurt's answer to "what would you refuse to sell if starting over" — framed against the risk of inheriting undocumented custom fields/CSS on someone else's build. - Matters because it's a concrete, falsifiable pricing/scoping policy (not just a vibe) that other agencies could adopt or test. **Tags**: #bmf **Highlight**: [view highlight](readwise://) <!-- atomicity: 1 idea ✓ --> #### [H1] Founder busywork crowds out sales and referral time > [!quote] ID:rw_atom2 > I became the the uh the the one minute manager, right? Well, if I could do it quickly, I'll just knock it out. **Context & use**: - Appears mid-conversation as Kurt self-diagnoses why enterprise deals eat his time — small tasks he should delegate instead get done personally. - Matters because it names a specific, recognizable trap (the "one-minute manager" reflex) with a stated cost: no funnel work, no referral networking. **Tags**: #bmf **Highlight**: [view highlight](readwise://) <!-- atomicity: 1 idea ✓ --> #### [H1] "Building yourself a job" is not building a company > [!quote] ID:rw_atom3 > This guy's just building himself a job. He's not building, you know, he's not building something that's duplicable that's going to grow a team and hire people and create jobs. **Context & use**: - Sourced from an Albuquerque small-business-incubator phrase Kurt recalls, used to explain why some agency owners can't afford to hire even when revenue looks healthy. - Matters as a sharp diagnostic question for any solo/founder-led service business deciding whether to scale a team. **Tags**: #bmf **Highlight**: [view highlight](readwise://) <!-- atomicity: 1 idea ✓ --> #### [H1] RFP literalism can be exploited against real intent > [!quote] ID:rw_atom4 > some other dude like company said asphalt that's just crushed rock we can deliver crushed rock easy that's cheap and so they bid on the job and they won the job **Context & use**: - A (self-flagged as possibly apocryphal) anecdote Kurt tells about a government road-building RFP won by delivering the technically-correct-but-useless literal spec. - Matters as a cautionary parable about writing (and responding to) RFPs precisely, especially now that AI-generated RFPs raise the odds of imprecise requirements. **Tags**: #storystem **Highlight**: [view highlight](readwise://) <!-- atomicity: 1 idea ✓ --> #### [H1] Productize maintenance as a priced "unlimited warranty" > [!quote] ID:rw_atom5 > that's four, five, eight, $10,000 a month. Just depends on the scale of the product project you're working on. **Context & use**: - Follows directly from the botched-outsourcing incident; the hosts float turning ad hoc rescue support into an explicit, priced maintenance tier. - Matters because it converts a reactive, boundary-drawing conversation into a proactive, sellable product with stated price anchors. **Tags**: #bmf **Highlight**: [view highlight](readwise://) <!-- atomicity: 1 idea ✓ --> ### 🧠 Permanent Candidates (H4) #### Unpriced boundaries become unpaid rescue work **Claim**: When an agency doesn't turn an implicit expectation (like emergency support) into an explicit, priced product, it ends up defending that boundary ad hoc, under pressure, client by client. **Evidence pointer**: rw_atom5 (unlimited warranty pricing) and the botched-outsourcing boundary story in the Main Content section. **Scope & conditions**: Applies to services businesses with recurring/maintenance components (hosting, LMS/e-commerce support, retainer work); less relevant to pure project-based, one-off engagements. **Links**: - no existing vault note identified — flag for synthesis pass (candidate cross-link: any existing note on agency pricing, retainer models, or scope-creep in the Product & Startup Instincts area of the vault) <!-- atomicity: 1 idea ✓ --> ### ✏️ Fleeting Queue - Check whether "niching by product vs. by audience" (Toby's WooCommerce/LMS framing) already has a vault note under Product & Startup Instincts — this episode adds a clean, quotable articulation of the distinction. - The "happiness = lack of responsibility" aside (which Toby immediately doubts) could seed a short reflective note on founder identity/burnout, separate from the pure agency-economics thread. ### → Things 3 (max 2 actions) - [ ] Cross-reference this doc's "unlimited warranty"/productized-maintenance atom against any existing agency-pricing notes in the vault during the next synthesis pass. - [ ] Flag the AI-generated-RFP theme (atom 4 + Main Content segment) as a candidate cross-link for any existing notes on AI's effect on sales/business-development workflows. <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Articles/If I Could Turn Back Time.md|If I Could Turn Back Time by Kurt Vonan & Toby Cryns]] ## Highlights - think what I wouldn't do is play in other people's gardens. I would just do fresh builds and no more sales off of site auditing. >> Interesting. I actually think I might do the opposite, honestly. Uh, but the one thing like in terms of not selling, there's this idea of like random one-off chaos. the idea that like someone comes in and I don't provide them with a firm procedure and process and firm boundaries and we still struggle with this and we're always trying to like like I'm pushing my team continually like how can we better define these ([View Highlight](https://read.readwise.io/read/01m0arvsc7y3md700q82qxwe0d)) - Note: Atom 1: Refuse legacy-site rebuilds, sell only fresh builds — Kurt's opening answer on refusing site-audit-driven rebuild sales. - Tags: atom/literature/h1 - task in that management software and instead it's almost like I became the the uh the the one minute manager, right? Well, if I could do it quickly, I'll just knock it out. Well, I end up just knocking out a lot of things and I should be focused on the funnel, new contacts, new sales, marketing, networking, you know, and to be clear, networking backwards like with existing customers, you know, are are you still happy? Is everything great? Who do you know that we should know? You know, and try and grow through referral that way, too. Which if you're busy doing tasks, you're not doing that. ([View Highlight](https://read.readwise.io/read/01m0arwhe963b8xra0pkc1b3a5)) - Note: Atom 2: Founder busywork crowds out sales and referral time — Kurt's "one minute manager" self-diagnosis. - Tags: atom/literature/h1 - Valley Economic Development Center in Albuquerque. And the big phrase then for people would they they would help people start new companies, you know, they'd be like, "Well, this person's realistically based on their business plan, they're building themselves a job." Like they would say that all the time, right? This guy's just building himself a job. He's not building, you know, he's not building something that's duplicable that's going to grow a team and hire people and create jobs. And of course, it's the economic development center. So, they really wanted to focus on companies that were building jobs for other people. But we run into a lot of ([View Highlight](https://read.readwise.io/read/01m0arwr0cpwb67afr3ajvhpa6)) - Note: Atom 3: "Building yourself a job" is not building a company — Albuquerque incubator anecdote Kurt recounts. - Tags: atom/literature/h1 - a road built to some department of defense thing and they said they wanted you know they wanted to have so much asphalt that led to this facility and so a bunch of companies bid on like making a real road and some other dude like company said asphalt that's just crushed rock we can deliver crushed rock easy that's cheap and so they bid on the job and they won the job and then they laid out all that crushed rock and and the government was like no no no we need a road these are like these are trucks like this this it needs a real road and they said that's not what the bid was ([View Highlight](https://read.readwise.io/read/01m0arwy0dwt35y18yb0535qs5)) - Note: Atom 4: RFP literalism can be exploited against real intent — the asphalt/crushed-rock government-bid parable. - Tags: atom/literature/h1 - warranty. Like we will if something break, you know, like that's the scenario. I kind of like that as a product offering. Well, and that's completely scalable, which is interesting when you think about like if you were to say, "Oh yeah, we're going to offer an unlimited warranty. We take care of all the all the maintenance, all the updates, all the thing. Just send us your content. We make it happen." I mean, that's four, five, eight, $10,000 a month. Just depends on the scale of the product project you're working on. >> Very interesting. >> I told you in the e-learning space, we have user support we provide. That's ([View Highlight](https://read.readwise.io/read/01m0arx2n6d8s56dsm2nehg789)) - Note: Atom 5: Productize maintenance as a priced "unlimited warranty" — hosts propose a $4-10k/month maintenance tier. - Tags: atom/literature/h1