Do You Have an Agency or a Job?  🔗 **Source:** [Do You Have an Agency or a Job?](https://www.youtube.com/watch?v=3FH7CP-z44U) > [!note]+ Document Notes > tags: [agency-business, value-based-pricing, team-building, wordpress-freelancing, profit-margin, apprenticeship] > author: Kurt von Ahnen, Toby Cryns > source: The WP Minute (Agency Action podcast) > reference: https://www.youtube.com/watch?v=3FH7CP-z44U > date created: {{date:YYYY-MM-DD}} {{time:HH:mm}} > > # 🏷️ Title: Do You Have an Agency or a Job? > <!-- deep-read:sections start --> ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - [Agency Action on The WP Minute](https://thewpminute.com/) - [Mañana No Mas (Kurt von Ahnen)](https://manananomas.com/) - [The Mighty Mo! (Toby Cryns)](https://www.themightymo.com/) ## 📝 Summary - Two WordPress agency owners — Kurt von Ahnen (Mañana No Mas) and Toby Cryns (The Mighty Mo!) — debate what separates a real agency from a glorified self-made job, then walk through pricing, team structure, growth, and the cost of complexity. - It matters because most freelancers and small shops never make the mental shift from "earn rent by the first" to "build a sustainable entity," and that shift decides whether the business survives a downturn or a founder's burnout. - Key stakeholders: solo freelancers, agency owners, the WordPress training/education community, students entering the field, and clients who pay for professionalism over customization. - Risks and tradeoffs surfaced: growth that adds headcount and revenue but shrinks margin and freedom; letting subcontractors talk to clients (scope creep vs. relationship depth); chasing simplicity you'll never reach; hiring people who want to climb out of the exact roles you need filled. - Bottom line: an agency is defined by economic sustainability and protected margin, not by team size or how custom the work is. Price for value, guard margin over revenue, and build processes (and people) that match the work you actually have. ## 📖 Main Content The episode opens with the framing question: when you started, were you building an agency or just making a job for yourself? Toby admits he was only making a job. Kurt and Toby then try to define the difference. The cleanest definition they land on: a job is capped by your time and energy, while an agency is "a sustainable thing… you're growing a garden versus planting a plant." Kurt's jalapeño analogy carries the point — one plant for one pepper to prove you grew something, versus a garden that produces 150–200 and feeds the neighbors too. A second definition is economic. Kurt's test: when you sell a job in the last week of the month, are you pricing it at the bare minimum to make rent, or at a value where anyone on your team could do the work and you'd still be profitable and growing? That reframes "agency" as a pricing posture, not an org chart. Both hosts agree an agency doesn't require a full-time team sharing cubicles. Kurt runs a global roster of contractors he brings in by specialty — "me and the team" — and notes some people will reject that as "not really your team." In the gig economy, they argue, you have to be open to what a team can look like. The core mechanism that makes an agency possible is **value-based pricing plus overhead that buys back your time**. Kurt's "lifetime deal" digression makes the scalable-thinking point concrete: freelancers buy software one license, one project at a time and bill it back; agency owners buy bundles and amortize a single license across 20–25 client sites, folding it into a hosting package. That's the difference between project thinking and business thinking. The conversation's sharpest practical thread is **who talks to the client and what that costs**. Toby tracks team performance partly by phone-call-to-email-thread ratio, betting calls shorten threads and justify the premium clients pay over a Fiverr seller they'll never speak to. But direct contact cuts both ways. Kurt's "graphics girl" story shows an artist selling a $9,000 scope inside a call priced at $2,500–$3,000 — "you sold the work, but you didn't know how to collect the funding." Toby's fix was hiring a project manager who bills for things Toby would have given away. His only framework for the team: think about the relationship, the work, the company's sustainability, and use your best judgment — plus read the contract before any call and scope anything not explicitly included. Kurt's counter-story (getting chewed out for telling a client "no" as an undisclosed subcontractor) shows the same risk from the other side: the wrong word from someone with client access muddies perception and margin alike. The middle of the episode wrestles with **whether growth is a trap**. More clients, employees, and revenue don't guarantee more profit, freedom, or happiness — sometimes the opposite. Kurt is transparent that he's living this question right now, launching a local apprenticeship program in Kansas (low cost of living, aging population) tied to a college, aimed at keeping young talent local, teaching them to run businesses, and warming the bench for hires. The hypothetical they pose: a 25-person team needing $1.6M in annual billables while the owner takes home $40K — what do you do when you've been trapped by your own growth? Toby's honest answer is that there are no universal answers; surviving businesses are the ones that "figured out ways to exist." His current iteration focuses on operations, relationships, and coaching over obsessing about profit. The closing themes are **simplicity vs. complexity** and **right team size**. Kurt keeps a deliberately narrow stack (Lifter LMS, the Fluent suite, Gravity Forms as backup) and sells expertise, not customization — "it's not the customization that drives the value, it's the professional." His AI-chatbot story is the centerpiece: a client wanted a chatbot; Kurt talked them down to a members-only FAQ block using existing content restriction, because they lacked the content to train a bot and an internet-sourced bot might quote Tony Robbins at their members. Toby reframes simplicity honestly — he's chased it for 20 years and always lands on "straightforward," not "simple," and he's added QA overhead this year on purpose. The team-size discussion ends on the human reality of tedious work: people hired for tedious tasks want to climb the ladder, which forces unexpected growth. Both hosts celebrate the rare hire who wants to stay put — the "I see myself at this desk" candidate, the retired IT manager happy to embed course videos, the Home Depot worker who just wants to put the paint away. Kurt closes on trust: a teammate could steal clients and there's little he'd do about it, so he extends "naive trust" and refuses to worry about it. Toby agrees that's a fitting note to end on — most things, you don't need to worry about. Contested or uncertain claims worth flagging: the "smiling teller" hiring anecdote is secondhand and unverified; the enterprise migration numbers ($250–300K SaaS → $100K migration + $65–70K/yr) are presented as typical but are a single operator's framing; and the claim that growth tends to shrink owner take-home is asserted from experience, not data. ## 🗒️ Notes #### Agency vs. job — the core definition - A job is capped by your time and energy; an agency is "a sustainable thing… an entity," like growing a garden versus planting a plant. - A high-earning value-based solo (with an assistant) is still a job — "without them the empire dissolves immediately." - An agency need not be full-time staff in cubicles. Kurt runs global contractors brought in by specialty: "me and the team." - The real test is economic: do you price so anyone on the team could do the work and you'd still profit and grow, or just enough to make rent on the first? #### Value-based pricing and scalable thinking - Overhead in an agency exists to buy back your time and leave room to grow. - Without value-based fees you can't grow beyond your hourly rate. - Lifetime-deal/bundle test: freelancers buy one license per project and bill it back; agency owners amortize one license across 20–25 sites and bake it into hosting. - "That's business thinking… scalable business thinking over multiple clients." #### Service design — response time and contact points - Toby tracks phone-call-to-email-thread ratio; calls should shorten threads and speed delivery. - Clients pay a premium for one-business-day response times and real conversation versus a Fiverr seller managed entirely in-platform. - He couldn't deliver one-day response 15 years ago — only building a team made the service level possible. #### The cost of letting the wrong person sell - "Graphics girl" sells a $9K scope inside a $2,500–$3,000 logo project: "you sold the work, but you didn't know how to collect the funding." - Fix: a project manager who bills for work Toby would have given away; framework is "use your best judgment" plus read the contract and scope anything not explicit. - Mirror risk: Kurt, as an undisclosed subcontractor, said "no" to a client and got chewed out — "Don't tell them no. Tell them you'll think about it." - Lesson: subcontractor-to-client access muddies perception and margin; Kurt prefers being the single point of contact. #### Is growth a trap? - More clients/employees/revenue ≠ more profit, freedom, or happiness — often the opposite. - Kurt's live example: launching a local Kansas apprenticeship with a college to keep young talent local, lower the average age of town, grow the tax base, and warm the bench for hires. - Students leave school assuming they'll "go find a job" — but Wix laid off ~20%, Stellar WP had cuts. Kurt thinks in revenue, not jobs. - Trap hypothetical: 25 people, $1.6M billables needed, owner nets $40K — how do you simplify out of it? #### Hiring, tedium, and accidental scaling - People hired for tedious work (e.g., embedding course videos) want to climb the ladder within ~6 months, forcing you to hire more juniors → accidental growth. - The rare ideal hire wants to stay: the "I see myself right here at this desk" candidate got the job; a forced-into-retirement IT manager happily took the tedious video work; Kurt's Home Depot story — "I just want to put the paint away." - A teammate was let go for refusing phone work that was in the job requirement. - Co-working front-desk lesson: hire people who want others to succeed, not people chasing their own advancement. #### Simplicity vs. complexity and the right stack - Kurt keeps a narrow niche stack: Lifter LMS, Fluent suite (Form/CRM/Support/Booking), Gravity Forms as backup. - Custom work loses control and margin: "when I lose control, I notice I also lose margin." - Value comes from the professional, not customization: clients "don't even understand what we're doing… they don't want to know the details." - AI-chatbot story: talked a client down to a members-only FAQ block using existing content restriction; they lacked content to train a bot, and an internet-sourced bot might "respond with quotes from Tony Robbins." - Toby: 20 years chasing simplicity always ends at "straightforward," not simple; added QA overhead this year on purpose. #### Team size and trust - The Mighty Mo runs ~12 people; Kurt's team is about half that with different billing/time usage. - Open question left unresolved: is a 5-person agency better than a 50-person or a 1-person agency? - Kurt sets the no-poaching expectation in the contract but extends "naive trust" — "there's nothing I can do about it… so I'm just not going to worry about it." - Closing advice: most things, you don't need to worry about. ## 📚 References - [The WP Minute — Agency Action](https://thewpminute.com/) — the show's home; Slack community mentioned as open to the public. - [Mañana No Mas](https://manananomas.com/) — Kurt von Ahnen's agency. - [The Mighty Mo!](https://www.themightymo.com/) — Toby Cryns's agency (SEO, website/WordPress development). - [Lifter LMS](https://lifterlms.com/) — Kurt's primary e-learning stack. - [Fluent suite (FluentCRM)](https://fluentcrm.com/) — Form, CRM, Support, Booking tools Kurt standardizes on. - [Gravity Forms](https://www.gravityforms.com/) — fallback form tool in Kurt's stack. ## 🗣️ Paraphrase - The opening segment reframes a familiar identity question: most people who "have an agency" actually built a job, capped by their own hours. The distinction the hosts draw isn't headcount — it's sustainability and pricing. You have an agency when your prices let anyone on the team do the work profitably, and a job when your prices only cover this month's bills. - The practical core is margin protection. Value-based pricing, software bought in bundles and amortized across clients, a single point of contact, and a project manager who actually invoices for scope all exist to defend margin. The recurring villain is the freelancer mindset — pricing per project, underbilling, and selling work without collecting the money for it. - The back half is a candid meditation on growth and complexity. Growth can trap you (more revenue, less take-home), simplicity is a white whale you never fully catch, and the people you hire for tedious work usually want out of it fast. The hosts' resolution is less about systems and more about judgment, trust, and matching your team and stack to the work you actually have — then not worrying about the rest. ## 📰 Newsletter Two WordPress agency veterans, Kurt von Ahnen and Toby Cryns, sat down on Agency Action to settle a question that quietly haunts a lot of us: do you actually run an agency, or did you just build yourself a job with extra steps? Their answer is refreshingly unglamorous — it's not about team size or how much React you can write. It's about whether your pricing makes the business sustainable when you're not the one doing the work. The episode is full of WordPress-shaped lessons. Kurt's narrow, opinionated stack (Lifter LMS plus the Fluent suite, Gravity Forms when Fluent can't) is a masterclass in selling expertise over customization. The standout moment: a client asked for an AI chatbot, and Kurt talked them all the way down to a members-only FAQ block built on content restriction they already had — because they didn't have the content to train a bot, and a web-sourced one might start quoting Tony Robbins to their members. That's the kind of "no" that keeps margin intact and clients happy. For the community and training folks, Kurt's Kansas apprenticeship program is worth watching. He's partnering with a local college to teach students they can build remote businesses instead of hunting for jobs that keep getting laid off (see Wix, Stellar WP). If you mentor newcomers, that "you can run your own thing" message is the gap to fill. Jump into the WP Minute Slack to keep the conversation going. ## ✅ Action Items #### DevRel - Developer advocacy: produce a talk/demo on "agency vs. job" economics for WordCamp business tracks — value-based pricing and margin-over-revenue with measurable before/after margin examples. - Education: build a short workshop on niche-stack mastery (pick one LMS, one form suite) and amortizing licenses across client sites; office hours for solo-to-agency transitions. - Developer experience: publish a contract/scope template and a "read the contract before the call" checklist contributors can fork. - Developer marketing: content series on personal branding as the value driver ("they're paying for the professional, not the customization"). - Community management: open the apprenticeship-model playbook as a community resource; survey freelancers on the job-vs-agency mental shift. - Internal/external/cross-project: align training content with real agency hiring needs (people who want to stay in tedious roles vs. climbers). #### OSPO - Policy & Governance: not applicable to this source — no open-source governance content. Closest tie: codify contributor expectations the way Kurt codifies no-poaching in contracts. - License Compliance: note the plugin-license amortization pattern (one bundle across many sites) and verify it against each plugin's license terms before recommending. - Security Management: not applicable to this source. - Software Inventory: maintain a curated "approved agency stack" inventory mirroring Kurt's narrow-stack discipline. - Developer Support: consultation hours for agency owners on tooling standardization. - Community Engagement: not applicable to this source. - Strategic Alignment: not applicable to this source. #### Community - Maintainers: not directly applicable — adapt the "right team size" question to maintainer-team sizing and burnout. - Contributors: build onboarding paths that name both tracks — contributors who want to grow and contributors happy in steady, scoped roles. - Sponsors: frame sponsorship asks around sustainability and margin, not headcount/growth vanity metrics. - Ecosystem: cross-agency mentorship circles for owners facing the growth-trap stage. #### WordPress - Core: not applicable to this source. - Core Performance: not applicable to this source. - Core AI: capture the "don't bolt on an AI chatbot without content" lesson as responsible-AI guidance for site builders. - Core Program Team: not applicable to this source. - Mobile: not applicable to this source. - Playground: build a Playground demo of content-restriction-as-FAQ as the simple alternative to a chatbot. - Community: turn the apprenticeship model into a meetup/WordCamp playbook for local talent pipelines. - Training: lesson plans on value-based pricing, scope management, and niche-stack expertise for Learn WordPress; certification pilot for "agency operations." - Marketing: narrative campaign on margin over revenue and "agency vs. job" for the business audience. - Support: document the single-point-of-contact and one-day-response-time service patterns as support-design references. - Design: capture the "graphics scope creep" story as a cautionary scoping case study for design handoffs. - Documentation: examples-first docs on content restriction (members-only blocks) as the FAQ pattern. - Photos/TV/Polyglots/Accessibility/Meta/CLI/Hosting/Tide/Openverse/Themes/Plugins: not applicable to this source. #### The WPCC - Programs: fund/replicate local apprenticeship tracks that teach business-building, not just coding. - Projects: documentation sprints on agency operations and pricing. - Funding experiments: microgrants/stipends for owners mentoring newcomers into independent practice. ### FAIR - Technical independence: not applicable to this source. - Policies and covenants: the no-poaching contract clause is a small analog — funding/relationship covenants set expectations up front. - Productized governance artifacts: turn Kurt's "best judgment" framework into a written team decision-rights one-pager. #### Practitioner action items (agency owners) - Run the pricing test on your next proposal: could anyone on your team do this profitably, or is it priced to make rent? - Pick a niche stack and become the expert in it; resist one-off custom builds that bleed margin. - Put a billing gatekeeper (PM) between your generosity and your invoices. - Give client-facing team members the contract and a "scope it before you promise it" rule. - Before adding headcount, model whether new revenue actually grows your take-home or just your obligations. - Hire deliberately for the role you have — including people who genuinely want to stay put. ## 🧪 Hypotheses - Agencies that price by value (vs. hourly/rent-driven) maintain higher net margin per employee than those that don't. - Inserting a project-manager billing gatekeeper increases captured scope revenue without measurable client-churn increase. - Agencies with a deliberately narrow stack show higher project margins than generalist shops taking custom work. - Headcount growth past a threshold correlates with flat or declining owner take-home pay (the "growth trap"). - Hiring explicitly for role-stability (not advancement) reduces churn in tedious-but-necessary roles. - Single-point-of-contact agencies experience less scope creep than those allowing direct subcontractor-client communication. ## 📊 Methodology - Cross-sectional survey of WordPress agencies capturing pricing model, stack breadth, headcount, owner take-home, and net margin; regress margin on pricing model and stack breadth. - A/B or pre/post study within agencies that add a PM billing gatekeeper: compare captured scope revenue and churn before/after. - Cohort study tracking apprenticeship graduates vs. traditional hires on retention and role satisfaction. - Time-series analysis of owner take-home against headcount to test the growth-trap inflection point. - Qualitative interviews on scope-creep incidents tied to who held client contact. ## ❓ Questions - At what headcount does the growth trap typically bite for WordPress agencies, and what predicts it? - Does narrow-stack specialization cap total revenue even as it raises margin? - How do you screen for "wants to stay in the role" without filtering out genuinely good candidates? - What's the real client-churn cost of single-point-of-contact vs. open team access? - Can apprenticeship pipelines actually convert to retained staff, or mainly seed future competitors (and is that fine)? - How does AI change the value of "the professional" if clients can self-serve simple builds? ## 🔮 Future Research - Benchmark data on margin-vs-revenue across agency sizes and pricing models in the WordPress ecosystem. - Outcomes of local talent-pipeline/apprenticeship programs as a hiring strategy in low-cost regions. - The effect of AI tooling on agency value propositions — does "expertise and relationship" hold its premium? - Frameworks for the simplicity/complexity tradeoff: when added QA/process overhead pays for itself. ## 💡 Implications - Practice: agency owners should treat pricing and margin — not headcount — as the success metric, and design teams/stacks around the work they actually have. - Policy: training organizations should teach business-building and pricing alongside technical skills. - Security: the "don't ship an AI chatbot without content/guardrails" lesson is a responsible-deployment cue for client work. - Education: apprenticeship and mentorship models can address both the talent shortage and the "I didn't know I could run my own thing" gap. - Funding models: community funding could back local pipelines and owner mentorship that strengthen the ecosystem's small-business layer. ## 🧠 Learning Styles Assessment - Reading level estimate: Flesch-Kincaid Grade ~7–8 (conversational spoken English, short clauses, informal vocabulary). Flesch Reading Ease likely ~65–75 (fairly easy). #### 👀 Visual learners - Present: none — audio-only transcript with no diagrams or screenshots. - Improve: add a job-vs-agency comparison table, a margin-vs-revenue chart, and a stack diagram (Lifter + Fluent suite). #### 🔊 Aural learners - Present: strong — this is a podcast with natural narration and dialogue. - Improve: ship a 3-minute audio recap of the five core lessons. #### 🗣️ Verbal learners - Present: strong — vivid analogies (jalapeño garden, white whale, emotional bank account, "put the paint away"). - Improve: add a glossary (value-based pricing, margin, scope creep, single point of contact). #### 🧩 Kinesthetic learners - Present: low — no exercises or labs. - Improve: a worksheet to price one real project by value and compute margin; a "read the contract before the call" checklist. #### 🧠 Logical learners - Present: moderate — clear cause/effect (custom work → lost control → lost margin). - Improve: a decision tree for "should I take this custom request?" and a growth-trap break-even model. #### 🧑‍🤝‍🧑 Social learners - Present: the WP Minute Slack invitation. - Improve: a peer cohort or roundtable for owners at the growth-trap stage. #### 🧘‍♀️ Solitary learners - Present: reflective framing ("the exact spot I am in right now"). - Improve: journaling prompts on whether you've built an agency or a job. #### 🌿 Naturalistic learners - Present: the garden/jalapeño growth metaphor ties business to ecosystem thinking. - Improve: extend the "sustainable garden" frame into a lifecycle model of an agency. ## 📊 Accessibility Assessment #### Screen reader semantics - Present: N/A for raw audio; the show notes/web page would carry headings and landmarks. - Improve: publish a structured transcript with semantic headings per segment. #### Keyboard navigation - Present: N/A to a podcast; applies to the player/page. - Improve: ensure the embedded player is keyboard-operable with visible focus. #### Contrast and readability - Present: N/A to audio. - Improve: meet 4.5:1 on the episode page and transcript. #### Text resizing and reflow - Present: N/A to audio. - Improve: ensure transcript reflows at 200% zoom without clipping. #### Media and captions - Present: a transcript exists (this document's source); YouTube auto-captions likely. - Improve: publish a corrected, downloadable transcript and verified captions; no autoplay. #### Forms and interactions - Present: N/A. - Improve: label the Slack signup and any contact forms with clear errors and adequate target size. #### Standards reference - Gaps map mainly to WCAG 2.2 AA 1.2.1/1.2.2 (captions/transcripts) and 1.4.3 (contrast) on the hosting page. ## 🌍 DEIB Assessment #### Cultural breadth - Present: a globally distributed contractor team is described; agency names use Spanish ("Mañana No Mas"). - Improve: add multi-region client examples and note locale/language considerations for global teams. #### Inclusive language - Present: mostly plain and friendly. Concern: "graphics girl" is used repeatedly; the speaker catches himself ("graphics person") but reverts. - Improve: default to role titles (designer, graphic artist); avoid gendered descriptors. #### Neurodiversity support - Present: conversational, chunked into clear themes. - Improve: add headings/timestamps and an icon+text summary for easier navigation. #### Representation - Present: a young female designer and an older retiree are both portrayed positively in different roles; ageism is named and pushed back on (forced retirement). - Improve: balance quoting and avoid tying a single woman on the team to a gendered label. #### Psychological safety - Present: respectful, candid tone; both hosts admit failures and uncertainty. - Improve: when discussing letting employees go, add framing on fair process and support. ## ✅ Logical Validity #### Strong reasoning - Analogical (strong): the garden-vs-plant and jalapeño analogies cleanly map sustainability and scale onto a familiar image — strong because the mapping (capacity, surplus, sharing) holds across the analogy. - Causal (strong): "custom/inconsistent work → loss of control → loss of margin" is a coherent causal chain backed by repeated firsthand examples; clarify further with actual margin figures per project type. - Inductive (moderate-strong): the AI-chatbot-to-FAQ story generalizes a sound principle (match the tool to existing content and guardrails) from a concrete case; strengthen by noting when a chatbot *would* be justified. - Deductive (implicit): "an agency is economically sustainable; a job is capped by your time → a value-priced solo with no slack is still a job" follows validly from the stated definitions. #### Fallacies - Hasty generalization — Kurt on freelancers ("I don't see a lot of freelancers… coming to bat with that mentality… the Fiverr economy"). Location: software/lifetime-deal segment. Weakness: broad claim about a whole population from personal observation. Fix: qualify ("many freelancers I encounter…") and cite or concede variation. - Anecdotal evidence — the secondhand "California bank hired tellers by who looked happiest in a 3-minute video" story used to justify a hiring heuristic. Weakness: unverified, single, secondhand case generalized into a practice. Fix: present as illustrative only, or back the "friendliness predicts front-line fit" claim with research. - Anecdotal/small-sample — the "people hired for tedious work always want to climb in ~6 months" claim. Location: hiring/tedium segment. Weakness: a pattern from a few hires stated as a near-law. Fix: hedge ("often") and acknowledge the counterexamples they themselves cite (the desk-stayer, the retiree). - False dilemma (mild) — recurring "agency vs. job" and "simplicity vs. complexity" framings. Weakness: real businesses sit on a spectrum; Toby partly corrects this with "straightforward, not simple." Fix: present as a continuum, which the hosts mostly do. - Note: these are typical of candid conversational podcasts and don't undermine the central, well-supported thesis (price for value, protect margin). #### Tone of voice - Candid, peer-to-peer, and self-deprecating ("I had projects 15 years ago… I could not deliver"; "people make fun of me behind my back"). Warm and pragmatic, with light humor (the Home Depot paint and "Captain Claude" asides). Low on hype, high on lived experience. ## 🛡️ DARVO Analysis - Deny: no meaningful denial pattern. Both hosts openly own past failures rather than minimize them. - Attack: none directed at accusers; the mildest edge is dismissiveness toward the "Fiverr economy" and undercutting freelancers, but it's a market critique, not a personal attack on a credibility-challenger. - Reverse victim/offender: not present. When Kurt describes being "chewed out" as a subcontractor, he relays it as a lesson about perception, not to recast himself as a victim. - Overall: DARVO is not applicable to this source — it's a cooperative discussion with no accusation-and-defense dynamic. ## 🎯 Conclusion - Bottom line: you have an agency, not a job, when your pricing makes the business sustainable without you doing the work — and when you defend margin over revenue. Team size and customization are distractions; value, professionalism, and a tight stack are the engine. - Practical next steps for readers: run the value-pricing test on your next proposal; standardize on a narrow niche stack; put a billing gatekeeper between your generosity and your invoices; hand client-facing staff the contract and a scope-first rule; model owner take-home before you grow headcount; and hire deliberately for the roles you actually have — including the people who are happy to stay in them. ## 🔄 Refactor Appendix — Do You Have an Agency or a Job? > 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. ### 📚 Literature Atoms (H3) #### [H1] An agency is sustainable; a job is capped by your time > [!quote] ID:rw_h1 > "an agency is a sustainable thing. like it's an entity that you you know you're growing a garden verse planting a plant." **Context & use**: - Opening definition segment. - The whole episode's thesis in one line — the test for whether you built a business or a self-job. **Tags**: #xref #aphorisms <!-- atomicity: 1 idea ✓ --> #### [H2] Price so the team is profitable, not so you make rent > [!quote] ID:rw_h2 > "am I selling that job at a value that anybody on my team could do that and we're still profitable and it and it goes into growing a business." **Context & use**: - Value-based pricing segment. - Operational definition of "agency" as a pricing posture, not an org chart. **Tags**: #xref #aphorisms <!-- atomicity: 1 idea ✓ --> #### [H3] Selling work isn't the same as collecting the money > [!quote] ID:rw_h3 > "you sold the work, but you didn't know how to collect the funding." **Context & use**: - The "graphics girl" scope-creep story ($2,500 job sold as $9,000 of work). - Why client-facing team members need scoping/billing guardrails. **Tags**: #xref <!-- atomicity: 1 idea ✓ --> #### [H4] Growth doesn't guarantee profit, freedom, or happiness > [!quote] ID:rw_h4 > "more clients, more employees, more revenue doesn't necessarily mean more profit, more freedom, more happiness. Sometimes it means the opposite." **Context & use**: - The "is growth a trap?" segment. - Counters the default assumption that scaling up is always progress. **Tags**: #xref #aphorisms <!-- atomicity: 1 idea ✓ --> #### [H5] Clients pay for the professional, not the customization > [!quote] ID:rw_h5 > "it's not the customization that drives the value. It's the professional." **Context & use**: - Simplicity-vs-complexity / personal-branding segment. - Justifies a narrow stack and expertise-led positioning over custom code. **Tags**: #xref #aphorisms <!-- atomicity: 1 idea ✓ --> ### 🧠 Permanent Candidates (H4) #### [P1] Margin, not revenue, is the operating metric of a sustainable agency **Claim** (one sentence, Courtney's voice): An agency stays alive on protected margin, so every pricing, hiring, and customization decision should defend margin before it chases revenue. **Evidence pointer**: [[#H2]] and [[#H5]] > [!quote] > "margin to me is what runs my agency, not not necessarily just revenue." **Scope & conditions**: Holds for service businesses where labor is the main cost; breaks when a deliberate low-margin loss-leader buys strategic position or recurring revenue. **Links**: - [[Value-based pricing]] — because extends - [[Growth as a trap]] — because contrasts on revenue-vs-margin - [[Niche stack specialization]] — because applies-in agency operations <!-- atomicity: 1 idea ✓ --> ### ✏️ Fleeting Queue - [F1] Capture the AI-chatbot-to-FAQ story as a reusable "match the tool to existing content" client-conversation pattern — episode simplicity segment #fleeting #inbox - [F2] Worth a post: "I see myself at this desk" — hiring for role-stability vs. advancement in agency teams #articleseed #fleeting #inbox ### → Things 3 (max 2 actions) - [ ] Draft a value-pricing + margin worksheet for the WordPress training track — agency-ops curriculum #things - [ ] Outline an "agency vs. job" talk for a WordCamp business track #things <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Articles/Do You Have an Agency or a Job.md|Do You Have an Agency or a Job? by youtube.com]] ## Highlights - is an agency is a sustainable thing. like it's an entity that you you know you're growing a garden verse planting a plant. Uh versus a job is really like ([View Highlight](https://read.readwise.io/read/01kvrdxt4dy98yr2d7dwkf9d0v)) - Note: Central metaphor: agency = a garden you grow (sustainable entity) vs. a job = planting one plant. - Tags: atom/literature/h1, agency - mortgage on the first or am I selling that job at a value that anybody on my team could do that and we're still profitable and it and it goes into growing a business. That's like so your ([View Highlight](https://read.readwise.io/read/01kvrdxxg17fgmv90j1fe69x22)) - Note: The delegation/profitability test: can anyone on the team do this work at a price that's still profitable? - Tags: atom/literature/h2, pricing ## Links - [[3. Resources/Permanent Notes/Agency Growth Is Healthy Only When Margin and Delegation Scale]] — evidence-for: the source supplies the delegation, margin, and freedom tests that distinguish an agency from an enlarged job. - [[3. Resources/Permanent Notes/The Workhorse Trap Prevents Leadership Emergence]] — extends: delivery that depends on the owner prevents both scale and leadership growth. ## Links - [[Protected Margin Defines a Sustainable Agency]] — distilled claim: pricing must leave profit when the founder delegates delivery. - [[A Metric Is Vanity Only Against Your Own Outcome Data]] — applies-in: revenue doesn't prove sustainability without margin and independence outcomes. - but not the money." Like, you sold the work, but you didn't know how to collect the funding. And you we can't I don't ([View Highlight](https://read.readwise.io/read/01kvrdy2svyebr1akmzqv5kpsh)) - Note: Classic agency failure mode: selling the work but not knowing how to collect payment. - Tags: client-management, atom/literature/h3 - realize that more clients, more employees, more revenue doesn't necessarily mean more profit, more freedom, more happiness. Sometimes it means the opposite. I'm seeing this over ([View Highlight](https://read.readwise.io/read/01kvrdy40brxrs400k6rjz5w48)) - Note: Growth ≠ profit/freedom/happiness — sometimes the opposite. The core counter-intuitive claim. - Tags: business, atom/literature/h1 - increasing margin. And margin to me is what runs my agency, not not necessarily just revenue. So, hypothetically, you're ([View Highlight](https://read.readwise.io/read/01kvrdy8nq9z4tmjkd0kdzqnvd)) - Note: Margin, not revenue, is what actually runs the agency. - Tags: atom/literature/h1, business - clients, it's not the customization that drives the value. It's the professional. ([View Highlight](https://read.readwise.io/read/01kvrdy6ppyksekm0fcav1jxeb)) - Note: Value lives in the professional/relationship, not the customization itself. - Tags: atom/literature/h2, pricing