all

wiki/sources/2026-06-15-17-ways-first-client.md

@@ -0,0 +1,52 @@
+# 17 Ways to Get Your 1st Client as a Developer in 2026 (AB Analytics)
+
+#source #sales #outbound #marketing
+
+## Source Metadata
+
+- **Date:** batched 2026-06-15; underlying video undated. Duration 40:49.
+- **Raw path:** `raw/sources/17 ways to get your 1st client as a developer in 2026.md`
+- **Source type:** YouTube video conclusions — <https://www.youtube.com/watch?v=mugDs0XaQ1A>
+- **Speaker:** founder of [[ab-analytics]] (B2B AI consulting, LA) and the *Code to CEO* accelerator.
+- **Ingestion date:** 2026-07-17
+- **Provenance role:** Primary source for the "AB Analytics" citations in [[2026-06-15-selling-development-services-in-the-ai-era]] — the origin of the follow-up statistics, the 3-channels×90-days rule, the DIY→DWY→DFY ladder, and the webinar formula.
+
+## Core Claims
+
+1. **Fish where no one else is fishing.** Most engineers fight for scraps on the same crowded channels (Upwork, generic LinkedIn/X). 17 channels are stacked in three tiers: common, low-key, out-of-the-box.
+2. **Pick 3 methods — one per tier — and run them daily for 90 days** before adding more. "Consistency beats intensity every single time. 30 minutes a day beats five hours once a month."
+3. **Follow up ≥5 times** — ~80% of sales happen after the 5th contact; most devs quit after one.
+4. **Niche specificity beats volume** — "Shopify developer for fashion brands" outsells "web developer" everywhere.
+
+## Key Evidence / Details
+
+**Tier 1 — common (do not stay here):** (1) freelance platforms — ~18% take, race to the bottom, only sensible for a true beginner in a low-cost country; (2) **LinkedIn** — profile = resume+portfolio+sales page; connect with decision-makers and referral partners; never sell in message one; (3) **content marketing** — the contrarian rule: *don't start until you already make $10–15k/mo from outbound*, else you starve; content is a leverage layer, not a first channel; (4) **cold email** — subject line carries **47%** of the open, spend 50% of your time there; body < 100 words: context → observation → value → proof → one CTA; (5) **referrals** — highest-converting, ~0 cost; the gap is **91% would refer, only 11% are asked** — ask right after delivery, be specific, make it frictionless.
+
+**Follow-up cadence:** Day 0 → 3 → 7 → 14 → 30 (break-up email). This is the origin of the "5 touches" and cadence claims elsewhere in the vault.
+
+**Tier 2 — low-key (local/in-person):** Chamber of Commerce (the speaker's most underrated — 4000+ in the US, member directory = pre-qualified list, show up 3× = "regular", 6× = trusted, then invited to speak); local business groups (BNI members average ~$20k/yr in referred business); industry associations; high-end hotels ("sauna + bar" strategy); car shows/expos (rich attendees = business owners); local conferences (begging for speakers → instant credibility); golf courses (2 clients from ~40–50 hrs ≈ 20× ROI); premium gyms + country clubs (5am crowd = execs; he moved Crunch → **Equinox** for the $200+/mo ICP).
+
+**Tier 3 — out-of-the-box:** strategic partnerships (vendors serving your ICP); **productize services** — "the single biggest change to his client acquisition" — DIY → DWY → **DFY** (his focus today); in-person workshops (paid or free, libraries/co-working give space); case-study → **webinar funnel** — formula **60% teach / 20% case study / 20% offer → 15–25% conversion**; one webinar = 3–6 months of work.
+
+**Cross-cutting:** lifestyle-integrate the in-person channels (gym/hotels/car shows you'd attend anyway); track every stage (outreach→response→meeting→proposal→close); "client #1 is hardest, #5 easier, #10 comes to you."
+
+## Connections
+
+- [[client-acquisition-channels]] — this is the primary source for the channel taxonomy
+- [[sales-discipline]] — 5 touches, 3×90, consistency>intensity, cadence, webinar formula
+- [[relationships-as-moat]] — the Tier-2 in-person channels *partially agree* with Sebastian, while Tier-1 online channels contradict him
+- [[productized-service]] — the DIY→DWY→DFY ladder
+- [[niche-selection]] — niche specificity beats volume
+- [[ab-analytics]] — speaker/org
+
+## Open Questions
+
+- The speaker plugs the *Code to CEO* accelerator throughout; named successes ("Paul," "John," "Dom") are members → treat metrics as **marketing-flavored claims, not independent data** (the raw note flags this explicitly).
+- Premium-gym/country-club/hotel tactics assume disposable income and a major US city.
+- Direct conflict with [[relationships-as-moat]]: this source rates LinkedIn/cold-email as live channels; Sebastian rates online outreach "Big zero." Unresolved.
+
+## Change Impact on Wiki
+
+- Named primary source behind the follow-up statistics and cadence in [[sales-discipline]] (hedge downgraded from "uncited via distillation" to "attributable YouTube claim, promotional context").
+- Created [[client-acquisition-channels]] (channel taxonomy) and entity [[ab-analytics]].
+- Supplied the in-person-vs-online tension that anchors [[relationships-as-moat]].

wiki/sources/2026-06-15-how-to-get-rich-cloning.md

@@ -0,0 +1,47 @@
+# How to Get Rich So Fast It Feels Like CHEATING (Cloning)
+
+#source #method
+
+## Source Metadata
+
+- **Date:** batched 2026-06-15; underlying video undated. Duration 12:31.
+- **Raw path:** `raw/sources/How to Get Rich So Fast It Feels Like CHEATING.md`
+- **Source type:** YouTube video conclusions — <https://www.youtube.com/watch?v=KJSSvOY1UOk>
+- **Ingestion date:** 2026-07-17
+- **Provenance role:** The full primary source behind [[cloning-over-originality]] (previously single-sourced only through the distillation's "Pabrai/cloning" citation). Centers on [[mohnish-pabrai]].
+
+## Core Claims
+
+1. **The fastest path is shameless, total cloning** of someone who already won — including the boring parts. Almost nobody does it; the blocker is **ego, not information**.
+2. **Two ego traps:** the *originality trap* (schools call copying "cheating"; adults inherit the shame) and *half-hearted cloning* (dipping a toe for a week and quitting). Pabrai's rule: **10,000% or nothing** — sampling single ideas is tasting, not cloning.
+3. **Originality is an emergent property of deep, multi-source cloning** — not a starting condition.
+4. **Letter of the rules > spirit of the rules, at the start.** Spirit-of-the-rules thinking is for masters; beginners use it to skip discipline.
+
+## Key Evidence / Details
+
+**The gas-station parable (full form):** two stations across the street, identical product. One wipes windshields and checks tires free and is packed; the other watches daily and refuses to copy it, and goes bankrupt — from ego, not missing information.
+
+**Pabrai → Buffett case study:** picked up *One Up on Wall Street* at Heathrow; learned Buffett returned 31%/yr for 40+ years (most investors don't clear 10%); decided "copy everything, don't add my own twist"; read every Buffett letter, watched every interview, attended the Berkshire meeting 20+ years, copied the morning routine, business structure, 5–6 hrs daily reading, working alone; outcome ~**$154M**; in 2007 paid **$650,000** for a charity lunch with Buffett, framed as *guru dakshina*.
+
+**Multi-source cloning:** Buffett for investing, Charlie Munger for thinking, Benjamin Graham for principles, philosophers for life decisions — "nobody else stacked those exact pieces the same way."
+
+**Illustrations of the method:** the *food-channel story* — a friend's polished, edited, subtitled recipe channel grew slowly; the niche's top channel had no subtitles, no music, no on-screen text, ~30-sec videos, proven topics. She was doing the opposite "to be original." She cloned the format exactly → first video 100K views, next 500K, *then* experimented. The *barber analogy* — nobody invents their own haircut technique on day one; you stand behind the best barber for weeks, copy the wrist/grip/small-talk, then experiment. Beginners skip exactly this step when starting a business or channel.
+
+**Practical method:** (1) pick ONE (not five inspirations — Pabrai went all-in on Buffett before branching); (2) go deep, understand *how* they think; (3) clone the boring parts (success is ~1,000 small stacked decisions); (4) adjust only after your hands understand the craft.
+
+## Connections
+
+- [[cloning-over-originality]] — this is the concept's primary source
+- [[methodology-as-moat]] — the tension: a cloned method vs. a defensible one (resolved via "the combination is unclonable")
+- [[sales-discipline]] — discipline is precisely the "boring part" to clone
+- [[mohnish-pabrai]] — central figure
+
+## Open Questions
+
+- Buffett's 31%/40yr and Pabrai's ~$154M / $650k lunch are stated as fact but uncited here; broadly consistent with public accounts of Pabrai, but not independently verified in this vault.
+- Combination-as-originality is asserted, not argued — if a combination becomes public (as it does once sold), what stops it being cloned in turn? See [[cloning-over-originality]].
+
+## Change Impact on Wiki
+
+- Upgraded [[cloning-over-originality]] from single-source-via-distillation to a fully-sourced page; the `Status: tentative` was relaxed to reflect a real primary source (though still one advocacy video).
+- Created entity [[mohnish-pabrai]]; Buffett/Munger/Graham are recorded there and in [[cloning-over-originality]] rather than as separate pages (supporting cast).

wiki/sources/2026-06-15-konspekt-aphorisms.md

@@ -0,0 +1,43 @@
+# Конспект (Aphorisms)
+
+#source #sales #positioning
+
+## Source Metadata
+
+- **Date:** batched 2026-06-15; note created ~2026-06-11. A bare list of aphorisms, no headers.
+- **Raw path:** `raw/sources/Конспект.md`
+- **Source type:** Distilled aphorisms from a video — <https://www.youtube.com/watch?v=mnQX-JLi_oA> (the same video as [[2026-06-15-rodenko-selling-development-expensively]], so this is a terse companion capture of the Rodenko talk).
+- **Ingestion date:** 2026-07-17
+- **Provenance role:** The "Конспект" cited throughout the distillation and meta-analysis. Because it shares a source URL with the Rodenko video, its lines corroborate rather than add independent evidence.
+
+## Core Claims (the aphorisms)
+
+- **"If you're on the same level as an Indian dev, you gave nothing beyond what that Indian dev gave — to enter a different category of people."** (Recorded verbatim for fidelity; the point is about commoditized skill level, but the phrasing leans on a nationality stereotype and is **not** reused in this vault's own writing — see [[methodology-as-moat]].)
+- **Knowing where the underwater rocks are — that is your expertise.**
+- The survivors are specialists who know their narrow niche and write skills.
+- **Sell SOLUTIONS, not work.** Solutions cost more; on "work" you compete with Indian devs.
+- **The most important thing in your offer is WHO you make it to.**
+- If one person bought the product, there's no reason others won't — the problem isn't the product.
+- Professional athletes don't go to *participate*; they go to **win**. A commander doesn't enter a battle without seeing the conditions for victory.
+- **The money is with your old clients**, whose projects you closed long ago.
+- Take 2–3 case studies with Before/After numbers as proof of expertise, and go compete.
+- AI created a chance to get rich — and you're still out there selling hours.
+- An offer starts from a criterion: what do you have now? here's what we can offer to improve it.
+
+## Connections
+
+- [[methodology-as-moat]] — "expertise = knowing where the rocks are"; the "Indian dev" commodity line
+- [[outcome-based-selling]] — "sell solutions, not work"; 2–3 Before/After case studies
+- [[niche-selection]] — "the most important thing is WHO"; "if one bought, others will"
+- [[pain-discovery]] — "the money is with your old clients"
+- [[sales-discipline]] — the athlete/commander "choose your fights" psychology
+- Same-source companion: [[2026-06-15-rodenko-selling-development-expensively]]
+
+## Open Questions
+
+- Being a same-video capture, this adds emphasis but no independent corroboration for the Rodenko claims.
+
+## Change Impact on Wiki
+
+- Confirmed the wording behind several quotes already on the concept pages (traced now to their video).
+- No new concepts; reinforced [[methodology-as-moat]], [[outcome-based-selling]], [[niche-selection]], [[pain-discovery]].

wiki/sources/2026-06-15-linkedin-mail-template.md

@@ -0,0 +1,50 @@
+# LinkedIn Mail Template
+
+#source #outbound #sales
+
+## Source Metadata
+
+- **Date:** batched 2026-06-15.
+- **Raw path:** `raw/sources/Linked In mail template.md`
+- **Source type:** A reusable first-touch message template (tool, not an argument).
+- **Ingestion date:** 2026-07-17
+- **Provenance role:** The "Linked In mail template" listed as note #7 in the meta-analysis and referenced by the distillation. It is the concrete instance of the cold-message anatomy taught in [[2026-06-15-17-ways-first-client]].
+
+## Core Claims
+
+The template itself (verbatim structure):
+
+```
+Hi [Name],
+
+Saw your post about [specific detail]. [Thoughtful comment about it].
+
+I help [target audience] with [specific problem]. Just helped [similar company] achieve [specific result].
+
+If I could help you do the same, would you be open to a brief chat?
+
+[Your name]
+```
+
+Its structure encodes the vault's outbound rules: open with **specific** evidence you read their post (not a generic hook), state ICP + problem, offer one proof point with a concrete result, and end with a single low-friction CTA. It matches the AB Analytics cold-message anatomy almost line for line.
+
+## Key Evidence / Details
+
+- **Must be customized every time** — every source that mentions templates ([[sales-discipline]], the distillation, AB Analytics) warns against mass-mailing it. The blanks are load-bearing: "[specific detail]", "[specific problem]", "[specific result]" are the parts that make it not read as spam.
+- **No selling in message one** — the CTA is a chat, not a pitch, consistent with [[client-acquisition-channels]].
+
+## Connections
+
+- [[client-acquisition-channels]] — the LinkedIn/cold-email channel this instantiates
+- [[sales-discipline]] — customize-every-touch; the 5-touch cadence this opens
+- [[outcome-based-selling]] — "[specific result]" is where a Before/After case study goes
+- [[2026-06-15-17-ways-first-client]] — the source that teaches this anatomy
+
+## Open Questions
+
+- Its usefulness depends entirely on the quality of the research filling the blanks; the template alone is inert.
+- Sits inside the unresolved online-vs-in-person debate — see [[relationships-as-moat]] (Sebastian would rate this channel "Big zero").
+
+## Change Impact on Wiki
+
+- Recorded as the concrete artifact behind the outbound copy rules; linked from [[client-acquisition-channels]] and [[sales-discipline]]. No new concepts.

wiki/sources/2026-06-15-making-money-with-ai-2026.md

@@ -0,0 +1,45 @@
+# Как реально зарабатывать на ИИ в 2026 году (Making Money with AI in 2026)
+
+#source #ai #product
+
+## Source Metadata
+
+- **Date:** batched 2026-06-15; underlying video undated. Duration 19:20.
+- **Raw path:** `raw/sources/как реально зарабатывать на ИИ в 2026 году.md`
+- **Source type:** YouTube video conclusions — <https://www.youtube.com/watch?v=o7c4XdtzU30>
+- **Ingestion date:** 2026-07-17
+- **Provenance role:** The "видео про ИИ-монетизацию" cited by the distillation and meta-analysis. **Primary origin of the four-part "pain with money" filter** that appears on [[pain-discovery]].
+
+## Core Claims
+
+1. **Most AI projects die from "idea → code it in Claude/GPT → launch."** The right order is **validate market and pain first, write code last.**
+2. **Three monetization paths**, each with a pipeline: **B2C** (low ticket $10–50, mass market), **B2B** (ticket $100–$100k+, more manual), **everyday AI** (services to ordinary people — coursework, presentations, texts).
+3. **Solve a concrete pain, don't "build a platform."** Benefit before feature. A good product **embeds into an existing habit** rather than breaking it.
+
+## Key Evidence / Details
+
+**B2C pipeline (6 steps):** hypothesis → monetary market check (will they pay at all) → large-scale research (Reddit/X/YouTube/Telegram + GPT deep research) → manual data verification (GPT may fabricate) → pick a target segment (not "for everyone") → **only now** build.
+
+**B2B pipeline:** (0) pick a comfortable niche (online schools, HR agencies, lawyers…) → (1) find *many* companies (Telegram, X, LinkedIn, Google Maps, 2GIS, HH) → (2) "test the ground" via DMs, 3–4 questions about manual tasks (~10% reply) → (3) find **"pain with money": frequent, costs the business money, already solved with crutches, founder understands its value** → (4) MVP in **7–14 days**, usefulness over features. **Simplified B2B:** if you know business owners — meet, hear the pain, solve it, get paid → "connections matter."
+
+**Everyday-AI pipeline:** pick 2–3 services → collect sample work (cheap/free for friends) → find clients → run a Telegram channel, collect (filtered-positive) reviews → templatize into a "library." Scalable later into B2C/B2B.
+
+**The author's proof figures (all as claimed):** Rezi (B2C) $293,256/mo; Postiz (B2C) $109,000/mo; ChatSEO (B2B, started Nov 2025) $16,000/mo.
+
+## Connections
+
+- [[pain-discovery]] — primary source of the four-part "pain with money" filter
+- [[productized-service]] — MVP in 7–14 days; benefit-before-feature; templatize into a library
+- [[niche-selection]] — pick a target segment before building; "solve a pain, not a platform"
+- [[relationships-as-moat]] — the "simplified B2B" path (know owners → meet → solve → paid) rhymes with Sebastian's connections thesis
+- [[ai-market-shift]] — the solo-founder revenue figures feed the "team size is no longer a signal" thread
+
+## Open Questions
+
+- Rezi/Postiz/ChatSEO revenue figures are stated without citation; Rezi's ~$293k/mo especially should be treated as a claimed headline number.
+- Pipelines are generic; no unit economics (CAC/LTV) — a gap the meta-analysis also flags.
+
+## Change Impact on Wiki
+
+- Established the **named origin** of the four-part pain filter on [[pain-discovery]] (previously attributed only to the distillation).
+- Reinforced [[productized-service]] (MVP cadence, library/templatization) and the "team size ≠ seriousness" thread in [[ai-market-shift]]/[[future-of-engineering-work]].

wiki/sources/2026-06-15-meta-analysis-selling-dev-in-ai-era.md

@@ -0,0 +1,50 @@
+# Мета-анализ Inbox — продажа услуг разработки в эпоху ИИ (Meta-Analysis)
+
+#source #meta #sales #ai
+
+## Source Metadata
+
+- **Date:** 2026-06-15 (stated: "Мета-анализ от 15.06.2026").
+- **Raw path:** `raw/sources/Метаанализ Inbox - продажи разработки в эпоху ИИ.md`
+- **Source type:** Second-order synthesis mapping the seven "15-06-2026 Inbox" notes into one worldview and one action plan.
+- **Ingestion date:** 2026-07-17
+- **Provenance role:** Sibling to [[2026-06-15-selling-development-services-in-the-ai-era]] — both are derived from the same seven primary notes. This one keeps the source attributions and adds a 90-day roadmap; the distillation stripped tactics to keep only principles. **Neither is primary evidence**; the seven notes are.
+
+## Core Claims
+
+1. **All seven notes describe one worldview from different angles** — a coherent "textbook" for how a developer/agency survives and earns in 2026 once AI has zeroed hourly development.
+2. **TL;DR:** *Stop selling hours and stack. Find a narrow group with a concrete pain, package result + accountability into a productized offer, and knock methodically — 5 touches, across 3 channels, 90 days without switching.*
+3. **If you haven't categorized yourself, the market categorizes you by hourly rate.**
+
+## Key Evidence / Details
+
+**Note map (angle / level):** [[2026-06-15-konspekt-aphorisms|Конспект]] (principles) · [[2026-06-15-rodenko-selling-development-expensively|Как продавать дорого]] (strategy) · [[2026-06-15-making-money-with-ai-2026|как зарабатывать на ИИ]] (strategy) · [[2026-06-15-how-to-get-rich-cloning|How to Get Rich]] (meta-method) · [[2026-06-15-more-clients-dev-agency|more clients]] (tactics) · [[2026-06-15-17-ways-first-client|17 ways]] (channels) · [[2026-06-15-linkedin-mail-template|LinkedIn template]] (tool).
+
+**Eight cross-cutting theses** it identifies across authors: (1) hourly era over; (2) sell result + accountability; (3) category = pain + result; (4) niche is upstream of all; (5) money is with old clients; (6) AI is a qualification filter; (7) WHO > WHAT; (8) follow-up discipline (Day 0→3→7→14→30).
+
+**Conflicts it surfaces (useful):**
+- *Content-marketing timing* — Tony (3 posts/wk from the start) vs AB Analytics (don't start until $10–15k/mo). Reconciliation: LinkedIn presence as a *trust layer under outbound* ≠ content as a *primary channel*.
+- *Uniqueness vs cloning* — Pabrai (clone 10,000%) vs Rodenko ("buy a proven method, not uniqueness"): consistent. Synthesis: clone the operating system of the successful, but position in a narrow segment where nobody fights.
+- *Team size* — old 15-person T&M vs Rodenko's 4-person squad (~$7M/yr) vs solo-founder Rezi ($293k/mo): **team size is no longer a signal of seriousness.**
+
+**Gaps it flags (not covered by any note):** B2B unit economics (CAC/LTV); legal packaging of a solution contract (SLA/penalties); concrete AI-consulting niches for CIS/EU (all examples are US); the reader's own Before/After case studies; a lead-qualification script for "we'll think about it."
+
+**Its 90-day roadmap:** Week 1 audit & positioning (call 3–5 clients, find the profit pattern, write the offer formula, run the commodity test) → Month 1 first flow (3 channels = 1 common + 1 low-key + 1 creative; customize each first touch; 5 touches) → Months 2–3 productize (fixed DFY package; the Zendesk "how much do you spend on X / 10× less?" motion; add LinkedIn content once at $10–15k/mo).
+
+## Connections
+
+- [[2026-06-15-selling-development-services-in-the-ai-era]] — sibling distillation of the same corpus
+- All seven primaries (linked in the note map above)
+- [[client-acquisition-channels]] — the content-timing and 3-channel material
+- [[cloning-over-originality]] · [[niche-selection]] · [[productized-service]] · [[sales-discipline]] — the cross-cutting theses
+- [[overview]] — the vault's synthesis mirrors this note's "one worldview" framing
+
+## Open Questions
+
+- Being second-order, it repeats the primaries' uncited statistics; not independent corroboration.
+- Its gap list (unit economics, legal packaging, CIS/EU niches, own case studies, objection-handling) is a good agenda for future sources to fill — none are in this vault yet.
+
+## Change Impact on Wiki
+
+- Used as a cross-check that the vault's concept set matches the corpus's own self-analysis; its five identified gaps were carried into [[overview]]'s Open Threads.
+- No new concepts of its own (it summarizes); reinforced provenance links across the batch.

wiki/sources/2026-06-15-more-clients-dev-agency.md

@@ -0,0 +1,44 @@
+# How to Get More Clients as a Software Development Agency (Tony)
+
+#source #sales #outbound #positioning
+
+## Source Metadata
+
+- **Date:** batched 2026-06-15; underlying video undated. Duration 5:20.
+- **Raw path:** `raw/sources/How to get more clients as a software development agency.md`
+- **Source type:** YouTube video conclusions — <https://www.youtube.com/watch?v=sqSg0cM9xzE>
+- **Speaker:** Tony.
+- **Ingestion date:** 2026-07-17
+- **Provenance role:** Primary source for the "Tony (agency)" citations in [[2026-06-15-selling-development-services-in-the-ai-era]] and the meta-analysis.
+
+## Core Claims
+
+1. **Niche is upstream of everything.** Without a clear ICP you can't do outbound at all, projects stay one-off custom, margins stay low, and sales can't be delegated. "Niche → productization → team scaling."
+2. **Run a deliberate outbound motion** — high-touch/low-volume (podcasts inviting CXOs, roundtables, lunches) or high-volume/low-touch (LinkedIn conversational prospecting, cold email). Both work; mixing is fine.
+3. **Back it with a social presence (the trust layer).** LinkedIn, ~3 posts/week. Posts rarely generate direct leads — they **grease the wheels** of outbound; the difference between a dead profile and an active one is sometimes the difference between signing and not.
+4. **Software dev is a high-trust, high-relationship business** — even high-volume outbound must feel personal or it won't convert.
+
+## Key Evidence / Details
+
+**Three mistakes that kill dev-shop sales:** (1) marketing the tech stack ("excellent .NET developer") — buyers don't know what the stack means; target the *audience the stack implies*; (2) "we do everything for everybody" — alienates the niche; (3) price as an incentive (undercutting) — "devalues your service permanently… fastest path to bankruptcy."
+
+**How to find the niche:** look back at your most profitable clients for a pattern (problem/industry/software type) and double down; run messaging experiments; target the chosen ICP but don't reject other paying work while it ramps ("bills first").
+
+## Connections
+
+- [[niche-selection]] — Tony's "niche is upstream of everything" is a primary anchor for this concept
+- [[client-acquisition-channels]] — the high-touch vs high-volume posture, and the social-as-trust-layer idea
+- [[sales-discipline]] — social presence as a persistent complement to episodic outbound
+- [[productized-service]] — productization follows niche
+- [[pricing-from-value]] — price-as-hook = bankruptcy
+- Cross-source: the "social greases outbound" claim sits between AB Analytics ("don't start content until $10–15k/mo") and Sebastian ("online = zero") — see [[client-acquisition-channels]]
+
+## Open Questions
+
+- Tony flags a follow-up video on pricing as "the lever that can wipe out profits even with a full pipeline" — not in this vault.
+- "Social greases outbound" is asserted from experience, unquantified.
+
+## Change Impact on Wiki
+
+- Named primary source for [[niche-selection]]'s "niche is upstream" framing and the stack-marketing mistake.
+- Contributed the middle position in the content-marketing timing debate recorded in [[client-acquisition-channels]].

wiki/sources/2026-06-15-rodenko-selling-development-expensively.md

@@ -0,0 +1,65 @@
+# Как продавать услуги по разработке дорого (Rodenko — Selling Development Services at a Premium)
+
+#source #sales #pricing #positioning
+
+## Source Metadata
+
+- **Date:** batched 2026-06-15 ("15-06-2026 Inbox"); underlying video undated. Duration 58:22.
+- **Raw path:** `raw/sources/Как продавать услуги по разработке дорого.md`
+- **Source type:** YouTube video conclusions — <https://www.youtube.com/watch?v=mnQX-JLi_oA>
+- **Speakers:** [[dmitry-rodenko]] (SaaS Founders) and Натан (Nathan).
+- **Ingestion date:** 2026-07-17
+- **Provenance role:** This is the **primary upstream source** for most of the sales principles in [[2026-06-15-selling-development-services-in-the-ai-era]] (the "Роденко" citations there resolve to this video). Ingesting it converts many previously-uncited claims into ones attributable to a named speaker.
+
+## Core Claims
+
+1. **Hourly development is ending** — the buyer has a ~$200/mo AI alternative, so a rate war against cheap regions zeroes margin. Only **result and accountability** sell at a premium; everything else is cost the buyer will quickly compute.
+2. **"Expensive" doesn't exist — "I don't see what for" does.** (Origin of the guarantee test now on [[pricing-from-value]].)
+3. **Your value = what clients name when you ask "what result were you paying me to get?" Everything else is your cost.**
+4. **Category = pain + result, not technology.** The commodity test: remove "development" and the stack name — what's left? "A commodity with a bow on it is still a commodity."
+5. **Sell to leadership, not implementers.** To an implementer your AI is a job threat (you're a risk); to leadership you deliver a KPI.
+6. **Business buys a proven method, not uniqueness.** "Unique = I'm afraid, don't experiment on me."
+7. **Founder = head of sales.** "A year of repackaging is for people afraid to pick up the phone."
+
+## Key Evidence / Details
+
+**The guarantee test (canonical form):** *"If we guaranteed this result — is price still the problem?"* "Yes, still" → no money (not a client, haggling for its own sake). "No" → price was an excuse; the real gap was trust in value.
+
+**AI-as-filter, quantified:** a founder gives a ready AI-skill free on the first call ("try 30 days"). Of 10 first calls, 5 return for a second call, 1 closes a **$100k** project. Reaction meanings: "works" → value not needed; "didn't get to it" → no budget; "weak, too abstract, needs specifics" → **target client**.
+
+**Zendesk story (the canonical offer):** a client paid $30k/mo ($360k/yr) for Zendesk; the team built a custom solution for $2k/mo; the $100k project paid back in ~4 months. Outreach reduces to two questions: *"How much do you spend on Zendesk?"* → *"And if it were 30 instead of 300 — worth discussing?"* Ask about **real spend on a concrete operational action** and promise a **10× cut**. "Even if you're half wrong, you still delivered 5×." Don't chase "another Zendesk" — find similar operational pains in the same industry.
+
+**Where clients hide (spend structure):** service firms → payroll; manufacturing → materials then labor; narrow industries (fintech/medtech/cyber) → industry-specific SaaS spend. Aim the offer at the biggest cost line.
+
+**Squad-model (successful repositioning):** a former outstaffing shop whose seniors sat "on the shelf" next to $25/hr Indian devs stopped selling people; assembled squads of 4 (2 engineers + QA + PM); ICP = **startups that just raised a round** (shared pain: show investors results in 6 months); offer = "Start in 7 days, price of two US programmers, by month 6 you have something to show investors; if not, we finish at our expense." Now ~19 squads × $15–18k/mo ≈ **$7M/yr**, 90 people. They also teach their startups and help them find investors — building a "gang of founders" around themselves.
+
+**Solution vs Staff Aug** — full table on [[solution-vs-staff-augmentation]]. The **one valid combination**: sell and deploy a solution first, *then* leave a person on support — long cash flow plus continued contact. Two models otherwise require separate brands/sites.
+
+**Zero-budget tactics (15-person team):** audit closed projects (call and ask "what were you paying me for?"); drop "we need a 15-person team" as dogma (4 people close the same check); go through network with a *criterion* ("know anyone spending $100k/yr on helpdesk?"), not "I have 15 devs at $30/hr"; founder sells. "The best zero-budget marketing is to stop selling cheap. That's free."
+
+## Connections
+
+- [[pricing-from-value]] — origin of the guarantee test and "expensive doesn't exist"
+- [[outcome-based-selling]] — "sell result + accountability"; the Zendesk offer
+- [[pain-discovery]] — the spend-based 10× opener; old-client mining
+- [[niche-selection]] — 80% is WHO; sell to leadership; go where AI is weak
+- [[methodology-as-moat]] — "buy a proven method, not uniqueness"
+- [[solution-vs-staff-augmentation]] — primary source of the model comparison and the one valid combination
+- [[productized-service]] — productized offers win on cycle and margin
+- [[ai-market-shift]] — $200/mo substitute; $1:$6 AI-to-specialist spend; AI-as-filter
+- [[sales-discipline]] — founder-led sales; "afraid to pick up the phone"
+- [[dmitry-rodenko]] — speaker
+- Derived-from-this: [[2026-06-15-selling-development-services-in-the-ai-era]], [[2026-06-15-meta-analysis-selling-dev-in-ai-era]]
+
+## Open Questions
+
+- The $100k close and $7M squad figures are the speaker's anecdotes — plausible, uncorroborated.
+- "Solution + staff-aug on one brand always collapses" is stated as a law; only the one valid combination (solution → support) is examined.
+- The Zendesk 10× framing assumes an order-of-magnitude-compressible cost line. When is a cost *not* 10×-compressible?
+- Nathan's distinct contribution vs Rodenko's is not separated in the notes.
+
+## Change Impact on Wiki
+
+- Became the named primary source behind [[pricing-from-value]], [[outcome-based-selling]], [[solution-vs-staff-augmentation]], and much of [[niche-selection]]/[[pain-discovery]] — those pages' "uncited via distillation" hedges were downgraded accordingly (still YouTube-claim provenance, now attributable).
+- Added the **one valid Solution+StaffAug combination** and the **Squad-model** example to [[solution-vs-staff-augmentation]].
+- Created entity [[dmitry-rodenko]].

wiki/sources/2026-06-15-selling-development-services-in-the-ai-era.md

@@ -0,0 +1,106 @@
+# Принципы продажи услуг разработки в эпоху ИИ (Principles of Selling Development Services in the AI Era)
+
+#source #sales #positioning #pricing #outbound
+
+## Source Metadata
+
+- **Date:** 2026-06-15 (stated distillation date)
+- **Raw path:** `raw/sources/Принципы продажи услуг разработки в эпоху ИИ.md`
+- **Source type:** Russian-language meta-distillation — a synthesis of 5–7 prior notes, deliberately stripped of channels and tactics to leave only timeless principles
+- **Ingestion date:** 2026-07-17
+- **Upstream sources (now ingested — 2026-07-17):** the seven primary notes this was distilled from are now in the vault: [[2026-06-15-konspekt-aphorisms|Конспект]], [[2026-06-15-rodenko-selling-development-expensively|Роденко/Натан]], [[2026-06-15-17-ways-first-client|AB Analytics]], [[2026-06-15-how-to-get-rich-cloning|Pabrai/cloning]], [[2026-06-15-more-clients-dev-agency|Tony/dev-agency]], [[2026-06-15-making-money-with-ai-2026|AI-monetization video]], and the [[2026-06-15-linkedin-mail-template|LinkedIn template]]; a sibling synthesis is [[2026-06-15-meta-analysis-selling-dev-in-ai-era|the meta-analysis]].
+- **Format note:** This is a **second-order distillation** — for any claim, prefer citing the primary note above. Its attributions are imperfect (e.g. it credits "Роденко" with follow-up statistics that actually come from AB Analytics).
+
+## Core Claims
+
+1. **Hourly development is dead.** The buyer has a ~$200/mo alternative (AI). Competing on rate zeroes out margin.
+2. **"Expensive" doesn't exist. "I don't see what for" exists.** Test the objection: *"If we guaranteed the result — is price still the problem?"* Yes → they have no money. No → they never trusted the value.
+3. **Business doesn't buy uniqueness, it buys a proven method.** "Unique" reads to a buyer as *"I'm afraid — don't experiment on me."*
+4. **AI expands the funnel rather than eating it.** For every $1 a company spends on AI it spends ~$6 on specialists to configure it.
+5. **Sell the result and accountability for it, not hours.** Willing to take accountability → the AI era makes you rich. Unwilling → a 12-month death sentence.
+6. **Category = pain + result, not technology.** Commodity test: remove the word "development" and the stack name from your offer. What's left? Nothing → you're a commodity.
+7. **80% of sales success is WHO you talk to, not WHAT you say.** If the offer won't sell, it's almost always the wrong audience.
+8. **Sell to leadership, not to implementers.** To an implementer your AI is a threat to their job and you are a risk. To leadership you deliver a KPI.
+9. **Go where AI is powerless** — narrow industry methodologies LLMs don't know.
+10. **Originality is downstream of cloning, not upstream.** Copy at 10,000% first, adapt second.
+11. **Consistency beats intensity.** 30 min/day > 5 hours once a month.
+
+## Key Evidence / Details
+
+**Finding pain with money attached** — a pain qualifies only if all four hold: it recurs often; it costs the business money; it's already being solved with duct-tape workarounds; the founder understands its value. Missing any → not a client.
+
+**The spend-based opener:** watch what they *spend on*, not what they *say*. Find an operational cost line → *"How much do you spend on X?"* → *"And if you spent 10× less — would we talk?"* Even if you're off by half, you still delivered 5×.
+
+**AI as a qualification filter** — don't hide the AI, weaponize it. Give a working AI skill away free for 30 days:
+
+| Reaction | Meaning |
+|---|---|
+| "It works" | Your value isn't needed. Not a client. |
+| "We never got to it" | Task has no budget. Not a client. |
+| "Weak, needs specifics" | **Target client.** |
+
+**Mining existing clients:** the money is with your old customers. Call your 3–5 best and ask *"what result were you paying me to get?"* — **not** "why did you choose us?", which only ever returns "good team".
+
+**Numbers cited (all uncited by the distillation):**
+
+- ~80% of deals close after the 5th touch; most people quit after the 1st.
+- 91% of clients are willing to refer; only 11% are ever asked. The enthusiasm window right after delivery is short.
+- Cold-email subject line carries 47% of open rate — spend 50% of your time on it. *"Quick question about [Company]'s checkout flow"* >> *"Ideas to improve your site"*.
+- Webinar formula: 60% teaching + 20% case study + 20% offer → 15–25% conversion.
+- 3 channels × 90 days; don't add methods until these are mastered.
+
+**Productize after 2–3 identical projects** — fixed price, fixed scope, a package name. Ladder: DIY → DWY → **DFY (Done For You)** = highest leverage. Benefit first, then feature. MVP in 7–14 days.
+
+**On cloning (the Pabrai method):** clone from *multiple* sources (Buffett for investing, Munger for thinking, Graham for principles) — originality is an emergent property of the combination, because nobody assembled those same pieces the same way. Clone the *boring* parts: success is ~1,000 small decisions, not one brilliant one. **Letter of the rules > spirit of the rules — at the start**; "spirit of the rules" is for masters, and beginners use it to excuse skipping discipline. *Gas-station parable:* one station wipes windshields and checks tires free and has a queue; the one across the street watches this daily and never copies it, then goes bankrupt — not from missing information, but from ego.
+
+**Deal psychology:** the client is not a prize — a deal is expertise exchanged for money, not charity from you nor a favor from them. Professionals choose which fights to enter (an athlete doesn't "participate in competitions", they go to **win**; a commander doesn't enter a battle without seeing the conditions for victory). If even one person bought, there's no reason others won't — the problem is never the product, it's WHO and HOW. *"If you're at the level of an Indian dev, you are one — just more expensive."* Knowing where the underwater rocks are **is** your expertise.
+
+**Minimum tactical kit:** 2–3 case studies with Before/After numbers (without them you have nothing to sell a result with); a first-touch template, customized every time, never mass-mailed.
+
+**Anti-patterns table (verbatim structure):**
+
+| Do | Don't |
+|---|---|
+| Sell the result | Sell hours or the stack |
+| Category by pain+result | Category "we build X on Y" |
+| Solution or Staff Aug under separate brands | Both models on one site |
+| Customize every first touch | Mass-mail one template |
+| Price via value | Price as a competitive weapon (= bankruptcy) |
+| Narrow niche where AI is weak | "We do everything for everyone" |
+| Ask for referrals immediately | Wait for "the right moment" |
+| 5 follow-ups before "stop" | One shot and forget |
+| 3 channels × 90 days | Change channels weekly |
+
+## Connections
+
+- [[productized-service]] — the 2–3-identical-projects trigger and the DIY→DWY→DFY ladder
+- [[outcome-based-selling]] — result *and accountability for it*, the sharpest framing in the vault
+- [[pricing-from-value]] — "expensive doesn't exist" and the guarantee test
+- [[niche-selection]] — WHO over WHAT; sell to leadership; go where AI is weak
+- [[pain-discovery]] — the four-part "pain with money" filter and the spend-based opener
+- [[methodology-as-moat]] — business buys a proven method, not uniqueness
+- [[ai-market-shift]] — the $1:$6 ratio and AI-as-qualification-filter
+- [[sales-discipline]] — 5 touches, 3 channels × 90 days, referral timing, founder as head of sales
+- [[cloning-over-originality]] — the Pabrai method, sourced entirely from here
+- [[solution-vs-staff-augmentation]] — the model choice laid out side by side
+- Cross-source: [[2026-07-17-design-the-perfect-offer]] independently reaches the same productization conclusion from a different tradition
+
+## Open Questions
+
+- **Every statistic here is now traceable to a named primary note but still not independently verified** (80% / 5th touch, 91% vs 11% referrals, 47% subject line, 15–25% webinar → [[2026-06-15-17-ways-first-client]]; $1:$6 AI spend → [[2026-06-15-rodenko-selling-development-expensively]]). Their root sources are promotional YouTube videos. Attributable, not confirmed — do not repeat as fact.
+- ~~The 7 upstream notes live outside this vault.~~ **Resolved 2026-07-17:** all seven are now ingested into `raw/sources/` and summarized in `wiki/sources/` (see Source Metadata). Claims can now be traced to their primary note.
+- Is "hourly development is dead" true across the board, or only for commodity work? Regulated/legacy/high-liability domains plausibly still bill hourly at healthy rates. [[2026-07-06-sebastian-interview-ai-and-software-engineering]] adds partial counter-evidence (enterprise/COBOL holdouts).
+- The ~$200/mo AI alternative: is that a real substitute for a dev contract, or only for the low end of it? The claim is asserted, not demonstrated.
+- "Solution and staff aug under one brand will always collapse into staff aug" — stated as a law, with no counter-example examined.
+- *"If you're at the level of an Indian dev, you are one — just more expensive"* — recorded as written for fidelity. The underlying point is about commoditized skill level, but the phrasing trades on a nationality stereotype and shouldn't be reused in this vault's own writing.
+
+## Change Impact on Wiki
+
+Co-first ingest into an empty vault (alongside [[2026-07-17-design-the-perfect-offer]]).
+
+- Primary evidence for [[cloning-over-originality]], [[sales-discipline]], and [[solution-vs-staff-augmentation]] — all three were sourced solely from this page at first ingest.
+- Corroborating second stream for [[productized-service]], [[outcome-based-selling]], [[pricing-from-value]], [[niche-selection]], [[pain-discovery]], [[methodology-as-moat]], [[ai-market-shift]] — reached independently of the other source, which raises confidence in those.
+- Its founder-led-outbound posture conflicts with the other source's chat-first posture; recorded under Contradictions in [[sales-discipline]].
+- Its "business buys a proven method, not uniqueness" tensions against the other source's "frame it so it sounds unique"; recorded in [[methodology-as-moat]].
+
+**Update 2026-07-17 (second batch):** superseded as a *primary* source. With the seven upstream notes now ingested, this page is best treated as a **derived index** into them — concept pages that once cited it as primary now cite the specific note ([[2026-06-15-rodenko-selling-development-expensively]], [[2026-06-15-17-ways-first-client]], [[2026-06-15-how-to-get-rich-cloning]], [[2026-06-15-making-money-with-ai-2026]]). Its content is unchanged and still an accurate summary; only its citation status dropped from primary to secondary.

wiki/sources/2026-07-06-sebastian-interview-ai-and-software-engineering.md

@@ -0,0 +1,68 @@
+# Sebastian Interview — AI and Software Engineering
+
+#source #ai #interview #positioning
+
+## Source Metadata
+
+- **Date:** 2026-07-06 (file date; the conversation itself is undated — described as a pre-webinar talk)
+- **Raw path:** `raw/sources/sebastian interview - conclusions and insights.md`
+- **Source type:** ~56-min recorded conversation, conclusions document. Built from a Whisper large-v3 auto-transcript, speaker-diarized; quotes lightly cleaned. A few rapid-crosstalk moments may be mis-attributed.
+- **Ingestion date:** 2026-07-17
+- **Participants:** [[sebastian]] (founder of [[virtido]], ~11-yr software outsourcing firm) and [[eugene]] (interviewer; CV/embedded developer, content creator, builder of a custom Claude Code harness).
+- **Format note:** A conclusions/insights write-up, one interpretive layer above the transcript. Distinct in origin from the other sources in this vault (which are the "15-06-2026 Inbox" batch) — this is an independent stream.
+
+## Core Claims
+
+1. **The debate is settled: AI *can* write software. The whole game is now *how* you use it.** Cost of writing code trends to zero, so leverage moves entirely to directing and verifying the AI. See [[future-of-engineering-work]].
+2. **Teams collapse from ~8 to 2–3.** Scrum master + PM + requirements engineer + big dev team → one coordination/ownership role plus one or two agent-wranglers.
+3. **Bring-your-own-harness maximizes individual leverage but dies in the enterprise.** Compliance and liability forbid ad-hoc per-developer setups → **the business opportunity is compliant, company-standard managed harnesses** for large regulated teams. See [[future-of-engineering-work]], [[niche-selection]].
+4. **Pure coding skill is commoditized; judgment, ownership, and relationships appreciate.** Claude "levels" a 20-year veteran and a fresh grad to similar output.
+5. **Seniors became *more* valuable; juniors "completely irrelevant."** A senior's real product is risk reduction. See [[seniority-and-ai]].
+6. **Product ownership is the durable human skill** — own the outcome a user sees, not the ticket. See [[product-ownership]].
+7. **Relationships are the last non-commoditized asset, and only in-person builds them.** Online outreach (agencies, cold call, email, LinkedIn, content, SEO) is "Big zero." See [[relationships-as-moat]] — this is the source's standout and most contrarian claim.
+8. **Decouple identity from profession**, or "we will feel worthless in a couple of years."
+
+## Key Evidence / Details
+
+**Enterprise reality (Sebastian's lens):** biggest clients forbid personal laptops — engineers use a centrally managed VM with **zero** ability to install their own tools. Reference points: a Roche SAP transformation ran ~1,200 engineers for years; banks first banned AI outright, now adopt cautiously "because it's just so good."
+
+**Why seniors win / the junior security argument:** 20 years = knowing where things typically go wrong, so you don't let the AI make those mistakes ("AI does the same mistakes humans do because it's trained on our mistakes"). The junior risk is a *security* argument: reflexively clicking "allow for all future" is how "API keys are leaked, databases get dumped." A junior can't evaluate a 250-line bash script; a senior at least could. *"Give a junior fresh out of university access to this almighty Claude and then access to the codebase — they will [wreck] it in two days."*
+
+**The profile-picture story (ownership):** an engineer implemented "change your photo," ticked every acceptance criterion, shipped it ugly (visible in the corner) because they never looked at the result. Reframe: stop thinking "what needs to be done" (tickets); think "what problem needs to be solved." *"No one ever needed a programmer… people have problems that you are solving."*
+
+**Planning / the printer anecdote:** a colleague (Daniel) floated returning to waterfall; Sebastian disagrees — coordination overhead now exceeds the work. On a 2-person project (~1 day/week each) he is **faster alone**. A new printer needed a direct-printing protocol in Java (never written) working in 2 days; he went on-site and Claude Code solved it in ~30 min. His edge was knowing how to instruct and verify, not to code.
+
+**Connections — the mechanics:** a connection forms not at first meeting but when you meet the *same* person in *different* circumstances → recognition → trust → referrals. Be memorable in your humanness (renovating a house, two kids, a cat) — not "I run a software company," which everyone forgets, because everyone now uses the same AI tools and everything online looks identical. Virtido's playful `humans.verti.com` "human badge" riffs on this. What works: showing up in person 2–4 days/week. What doesn't: *"sales agencies, cold calling, email marketing, LinkedIn campaigns, content, SEO. Zero. Big zero."*
+
+**Side points:** open source will grow (code becomes nearly free to give away; Eugene's cynical read: OSS is largely marketing). Legacy/hobby niches persist (COBOL in banks — no training data; people who code "like driving an old-timer car") but not where time/quality/money matter. Outsourcing economics: great engineers exist everywhere, but a low-cost expectation selects for bad code — pay $10k/mo for excellent people; an $800/mo hire won't beat a good, well-paid engineer. AI helps non-programmers too: profile ~2,000 LinkedIn/HR contacts into Obsidian, build RAG over your own information — "you can put your whole life into a RAG."
+
+**Internal disagreements:** personal vs company-managed harness (Eugene vs Sebastian); planning/waterfall (Daniel vs Sebastian); OSS motivation (Eugene: marketing; Sebastian: expects more); networking channels (Eugene invested in LinkedIn/articles; Sebastian: online outreach is a waste vs in-person).
+
+## Connections
+
+- [[relationships-as-moat]] — the connections thesis, primary source
+- [[product-ownership]] — ownership as the durable skill
+- [[seniority-and-ai]] — senior/junior value inversion; risk reduction
+- [[future-of-engineering-work]] — team collapse, harness, enterprise lockdown, identity, OSS, legacy
+- [[client-acquisition-channels]] — Sebastian's "in-person only" is the sharp counter-pole to the outbound channel taxonomy
+- [[methodology-as-moat]] — competing account of *what* the moat is (method vs relationship)
+- [[ai-market-shift]] — the same AI shift, seen from the labor/enterprise side
+- [[sebastian]], [[eugene]], [[virtido]] — entities
+
+## Open Questions
+
+- How does AI transform *huge* (~1,200-engineer, multi-year) enterprise programs? Sebastian is candid he doesn't know.
+- How do you unify wildly different personal workflows into one company process? (Eugene + a collaborator spent a month, failed.)
+- Concretely, how does an individual build a connections network from a standing start? Principles given; the step-by-step is open.
+- Sebastian's "online outreach = Big zero" is one founder's experience in an enterprise-services context. Does it generalize, or is it audience-specific (big enterprise buyers vs. SMB/startup buyers, where the other sources' channels may work)?
+- Is [[eugene]] the owner of this vault? Internal details (the `insin` project, a custom Claude Code harness) match the vault owner's tooling. Recorded as inference, not fact.
+
+## Change Impact on Wiki
+
+Second-batch ingest; the only source in this batch not from the "15-06-2026 Inbox" corpus.
+
+- Created 4 new concepts primarily from this source: [[relationships-as-moat]], [[product-ownership]], [[seniority-and-ai]], [[future-of-engineering-work]].
+- Created entities [[sebastian]], [[eugene]], [[virtido]].
+- Introduced the vault's sharpest live contradiction: **in-person-only (Sebastian) vs. multi-channel outbound incl. online (AB Analytics / Tony / Rodenko)** — recorded in [[client-acquisition-channels]], [[sales-discipline]], and [[overview]].
+- Introduced a second moat account (relationships) alongside the existing one (methodology) — tension recorded in [[relationships-as-moat]] and [[methodology-as-moat]].
+- Broadened the vault's domain in [[overview]] from "selling services in the AI era" to also include positioning engineering work/careers.

wiki/sources/2026-07-17-design-the-perfect-offer.md

@@ -0,0 +1,76 @@
+# Design The Perfect Offer in Under 10 Minutes
+
+#source #offer-design #pricing
+
+## Source Metadata
+
+- **Date:** unknown (video publication date not recorded in raw file)
+- **Raw path:** `raw/sources/Design The Perfect Offer in Under 10 Minutes.md`
+- **Source type:** YouTube video conclusions/notes (09:35 runtime) — <https://www.youtube.com/watch?v=19QYlpGvcLo>
+- **Ingestion date:** 2026-07-17
+- **Format note:** The raw file is a distilled conclusions document, not a verbatim transcript. Claims are therefore already one interpretive layer removed from the speaker.
+
+## Core Claims
+
+1. **Productize or stay poor.** Selling "I do X for you" forces every engagement into custom hourly work. ~90% of service businesses operate this way and net **less than minimum wage** per real hour worked.
+2. **Backwards math sets the offer, not inspiration.** Pick a revenue target → divide by a ≥$1,000/mo price → that is your client count. $10,000 ÷ $1,000 = 10 clients.
+3. **$1,000/mo is the floor.** Below ~$100/mo there is no margin to fund delivery quality — pricing itself constrains how good the service can be. $1K is defensible for AI/business services because one new client is typically worth ~$1K to the buyer, so a single win recoups the fee.
+4. **Hungry crowd beats best burger.** Don't invent a novel service; listen to what the market already asks for and name its bottleneck back to it as an offer.
+5. **Anchor the ladder on the core tier, then bracket it.** Design the middle offer first, then build entry (~40–50% of core) and top (~5× core) around it.
+6. **People don't buy your time. They buy your standards.** Buyers want the methodology and the standard, not your presence.
+7. **The market is fatigued by sales calls.** Ship both a pitch deck and a text offer doc; default to selling in chat and escalate to a call only when the buyer asks.
+
+## Key Evidence / Details
+
+**The ladder built live on-camera:**
+
+| Tier | Price | What it is | Client gets |
+|---|---|---|---|
+| Entry | $444 (AI Jumpstart) | 90-min working session | One workflow built with them |
+| **Core** | **$997/mo** | The productized monthly | 1 personalized AI agent + dashboard + 1 new workflow/month |
+| Top | $5,000/mo (AI Ecosystem) | Full deployment | Rolled out business-wide + team training + monthly call |
+
+**The reframe that carries the whole method:**
+
+| Weak (service framing) | Strong (productized outcome) |
+|---|---|
+| "I'll audit your calendar and set up some automations" | "I guarantee I'll buy back 10 hours of your time per week using AI, for $1,000/mo — every month." |
+
+10 hrs/week × 4 = **40 hours/month** returned, recurring. Concrete, defensible, priceable.
+
+**Language rules:**
+
+- Never "3 hours per month **with me**" → say "with my team" (or "me or my team"). If you promise yourself and don't show, they're upset; promise the team and show up anyway, that's a bonus.
+- Never "I do AI for you" → say "this is my specific methodology for [outcome]".
+
+**On AI as co-designer:** the AI-generated recommendation (workflow + dashboard + agent) matched the coach's own best-practice structure. Claimed leverage: the deck-and-doc drudgery that used to require a paid coach is now free; what remains scarce is knowing which questions to feed it.
+
+**Audience:** solo operators and small agencies stuck in custom-hourly work (AI, marketing, coaching, consulting) wanting a recurring $1K–$5K/mo productized model without inventing a new category.
+
+## Connections
+
+- [[productized-service]] — this source is the primary evidence for the productization mechanic
+- [[offer-ladder]] — the three-tier structure and middle-out design rule originate here
+- [[outcome-based-selling]] — "buy back 10 hours/week" as the canonical outcome framing
+- [[pricing-from-value]] — the $1K floor and backwards-math model
+- [[niche-selection]] — hungry crowd over best burger
+- [[pain-discovery]] — "what's your biggest bottleneck around [domain]?"
+- [[methodology-as-moat]] — "people buy your standards"
+- [[ai-market-shift]] — AI as free offer-design labor
+- Cross-source: [[2026-06-15-selling-development-services-in-the-ai-era]] agrees on productization and outcome-selling, disagrees on sales-call posture
+
+## Open Questions
+
+- Who is the speaker/coach, and who is the guest whose ladder was built? The raw file names neither. **Update 2026-07-23: plausibly [[dan-martell]].** Evidence from [[2026-07-23-make-my-first-100k-in-month]] (named-Martell): this page's signature offer is *"buy back 10 hours of your time per week"* — *Buy Back Your Time* is Martell's book and flagship frame; the $997/mo core matches his $1K/mo sweet spot; the chat-first close matches his claimed 8-figures-by-chat channel; and the three-tier ~$1K-core ladder recurs there with a decoy rationale. Weaker than the 07-18 case (no verbatim mechanism reuse) — held as suspicion, not attribution. Owner confirmation would settle whether this "anchor" source is independent of the Martell corpus at all.
+- Is the "<minimum wage for 90% of service businesses" figure sourced, or rhetorical? No citation given.
+- Is "$1K is what one new client is worth" specific to lead-gen-adjacent buyers? It plausibly fails for buyers whose customer LTV is far below or above $1K.
+- The $444 / $997 / $5,000 ladder is one worked example on one call. Is the 40–50% / 5× bracketing a real rule or a post-hoc description of this single case?
+- "You can literally make a million dollars a month over chat" — unsupported, treat as motivational framing rather than evidence.
+
+## Change Impact on Wiki
+
+First ingest into an empty vault (alongside [[2026-06-15-selling-development-services-in-the-ai-era]]).
+
+- Created [[productized-service]], [[offer-ladder]], [[outcome-based-selling]], [[pricing-from-value]], [[niche-selection]], [[pain-discovery]], [[methodology-as-moat]], [[ai-market-shift]] — this source is a primary evidence stream for all eight.
+- [[offer-ladder]] is sourced almost entirely from this page; it has no corroboration and is marked `Status: tentative`.
+- Contributed the chat-first selling position that stands in tension with the founder-led outbound position in the other source; recorded under Contradictions in [[sales-discipline]] and [[overview]].

wiki/sources/2026-07-18-ai-productivity-adversarial-evidence.md

@@ -0,0 +1,62 @@
+# AI Coding Productivity — Empirical Evidence (Adversarial)
+
+#source #ai #evidence #adversarial
+
+## Source Metadata
+
+- **Date:** 2026-07-18 (compilation date; underlying studies span 2023–2025)
+- **Raw path:** `raw/sources/AI Coding Productivity - Empirical Evidence (deep research 2026-07-18).md`
+- **Source type:** **Deep-research synthesis** — a Claude Code `deep-research` run (6 search angles → 23 sources fetched → 104 claims → 25 adversarially verified, 23 confirmed / 2 refuted). Not a single external artifact.
+- **Ingestion date:** 2026-07-18
+- **Provenance role:** The vault's **first deliberately adversarial source** — commissioned (see [[2026-07-17-best-method-first-client]]'s lineage of open threads) to test the premise underlying both vault branches, that *AI has zeroed the cost of commodity software execution*. Second-order like the distillation, but its inputs are peer-reviewed papers, RCTs, and large-sample surveys rather than promotional videos — **higher-provenance than any prior source**, though still a synthesis.
+- **⚠ Time-scope:** every figure is tied to a specific tool generation (early-2025 and earlier). This is **2023–2025 evidence, explicitly NOT the live 2026 state of the art** — METR itself labels its result "historical"; DORA reversed one 2024 finding in 2025.
+
+## Core Claims
+
+1. **The evidence QUALIFIES the hype, it does not demolish it.** No study shows AI has zero/negative value in general. It shows the real effect is **modest (≈14–19%), context-dependent, novice-tilted, and overstated by self-report.**
+2. **"AI zeroed the cost of skilled dev work" is directly contradicted** by the strongest developer-specific RCT: experienced devs were **19% *slower*** with early-2025 AI ([METR]).
+3. **"Seniors up, juniors irrelevant" is directly inverted** by the best skill-distribution study: the **least-experienced gain most** (34% vs ~0 for experts) — and a Copilot RCT independently found less-experienced devs benefit most.
+4. **Self-reported productivity gains are unreliable evidence.** METR devs forecast +24%, felt +20%, measured −19% — a ~39-point perception gap. This is the exact "it feels faster" basis most promotional claims rest on.
+5. **Individual speed ≠ team delivery.** DORA 2024: AI adoption correlated with *reduced* delivery stability (and, in 2024, throughput). Trust is low and falling (SO 2025: ~3% highly trust, ~46% distrust).
+
+## Key Evidence / Details
+
+| # | Finding | Design | Population | Headline | Confidence |
+|---|---|---|---|---|---|
+| 1 | Experienced devs **19% slower** with AI | RCT | 16 expert OSS maintainers, 246 real tasks, their own mature repos, early-2025 tools | −19% completion time | HIGH (3-0) |
+| 2 | Perception ≫ reality | (within #1) | same | forecast +24%, post +20%, actual −19% | HIGH (3-0) |
+| 3 | Gains tilt to **least-skilled** | quasi-exp (diff-in-diff) | **5,179 customer-support agents — NOT devs** | +34% novices vs ~0 experts (avg +14–15%) | HIGH (3-0) |
+| 4 | Novices benefit more; toy-task speedup | RCT | 70 freelancers, one JS toy task, 2022 Copilot | +55.8% (toy); exp. coeff n.s. at 0.05 | MEDIUM |
+| 5 | AI hurt team **stability/throughput** | observational survey | DORA 2024 respondents | −7.2% stability / −1.5% throughput per +25% adoption | MEDIUM (throughput reversed in 2025) |
+| 6 | Trust low & falling; debugging tax | survey (~49k) | SO 2025 | ~3% highly trust, ~46% distrust; ~45% debugging is time-consuming | HIGH (3-0) |
+
+**Key primary sources:** METR (metr.org/blog/2025-07-10…, arXiv:2507.09089) · Brynjolfsson, Li & Raymond, "Generative AI at Work," *QJE* 140(2):889–942 2025 (NBER w31161) · GitHub Copilot RCT (arXiv:2302.06590) · DORA 2024 (dora.dev/research/2024) · Stack Overflow 2025 Developer Survey (survey.stackoverflow.co/2025/ai).
+
+**Verification honesty:** 2 claims were **refuted** during 3-vote checking — both versions of "66% spend more time fixing almost-right AI code" (the 66% actually measures *encountering* almost-right output; the real debugging-time figure is **45%**). Recorded so the error isn't silently repeated.
+
+## Connections
+
+- [[ai-productivity-evidence]] — the concept page this source anchors (measured vs. claimed AI productivity)
+- [[ai-market-shift]] — **challenges** the premise that a ~$200/mo AI is a genuine *substitute* zeroing rate competition; substantiates a doubt the vault already flagged (the "$200 substitute is asserted, not demonstrated" open question)
+- [[seniority-and-ai]] — **inverts** the productivity-gain direction of "seniors up, juniors irrelevant" (novices gain most) — while *not* settling the labor-market-value question, and partly supporting the "juniors can't catch AI's errors" risk mechanism
+- [[future-of-engineering-work]] — **qualifies** "coding cost → 0, teams collapse 8→2–3": effect sizes are modest and team-level delivery can worsen
+- Counter-pole to [[sebastian]]'s standout claims and to the whole "AI killed hourly dev" school ([[dmitry-rodenko]], [[ai-market-shift]])
+- [[overview]] — flips the standing "no adversarial source" gap
+
+## Open Questions
+
+- Does METR's −19% persist/reverse with **mid-2026 agentic tools**? The single most important missing piece; this source is explicitly historical.
+- Does "novices gain most" hold for **real** software work, or invert on complex/unfamiliar codebases where juniors can't catch AI errors?
+- The findings measure **speed**, not **labor-market value** (wages/hiring/headcount) — so they are directional counter-evidence to "juniors out," not a same-metric refutation.
+- Transient learning-curve cost vs. durable tax for the team-level effects? DORA's 2025 partial reversal cuts both ways.
+- Should [[dmitry-rodenko]]-style claims ("$200/mo AI substitute") now carry a stronger `Status: contested` given this evidence?
+
+## Change Impact on Wiki
+
+Thirteenth source; the vault's **first adversarial / empirical source** and its highest-provenance one.
+
+- Created concept [[ai-productivity-evidence]] as the durable home for the empirical counter-narrative.
+- Added counter-evidence sections to [[ai-market-shift]], [[seniority-and-ai]], [[future-of-engineering-work]] — recording contradictions explicitly (rule #5), **not** overwriting the sources' prior claims (Update Policy).
+- Flipped the long-standing gap in [[overview]] and [[index]] ("no adversarial source / 11-of-12 one school").
+- **No entity pages created** for METR / Brynjolfsson / DORA / Stack Overflow — they are cited as evidence rather than tracked as recurring subjects (consistent with the Buffett/Munger decision on [[mohnish-pabrai]]); revisit if a second study-based source arrives.
+- Deliberately framed as *qualifying*, not inverting, the thesis — the honest reading of the evidence.

wiki/sources/2026-07-18-information-is-free-implementation-is-paid.md

@@ -0,0 +1,86 @@
+# Information Is Free, Implementation Is Paid
+
+#source #content-marketing #demand-generation
+
+## Source Metadata
+
+- **Date:** unknown (video publication date not recorded in raw file)
+- **Raw path:** `raw/sources/Information Is Free, Implementation Is Paid.md`
+- **Source type:** YouTube video conclusions/notes (08:45 runtime) — <https://www.youtube.com/watch?v=knrSj8t2L9U>
+- **Ingestion date:** 2026-07-18
+- **Format note:** The raw file is a distilled conclusions document, not a verbatim transcript. Claims are one interpretive layer removed from the speaker; several tables in the raw are the note-taker's framing, not necessarily the video's wording.
+
+## Core Claims
+
+1. **Give away the know-how; charge for implementation and sequencing.** The best marketing content a service business can make is *exactly what it does in-house for paying clients* — the internal playbooks, step by step. Publishing the *what* does not remove demand for the *how* (the sequenced, done-with-you/done-for-you delivery); done right it *creates* demand.
+2. **The paid good is sequencing, not information.** *"Information is free. People pay for implementation and sequencing. That's why they pay you."* Each free video teaches a real, valuable step; what is withheld is the **order** in which the steps combine into a working system.
+3. **The scramble trick makes #1 and #2 compatible.** Post the pieces *out of order* across topics (A1, B1, C1, D1, E1, A2, B2 …), never in a runnable sequence within one topic. Every swipe shows expertise; no viewer can assemble the whole system from the feed, so the paid offer survives.
+4. **A content-idea factory removes the "I ran out of ideas" excuse.** 5 hot buttons × 10 nuanced pains = 50 pain-ideas (≈50 days of content), × 4 formats = **200 pieces** (near-daily for most of a year), then loop from pain #1 in a fresh format.
+5. **Precision-naming the buyer's pain is the whole conversion mechanism.** Open every piece on a *nuanced, observable* pain that "describes the viewer's world better than they can describe it themselves" → the viewer thinks *"how do you know?"* → you are an expert on sight. Then teach the fix.
+6. **Free content makes the paid offer feel cheap.** A $997 offer reads as a bargain *after* the viewer has watched 50 free expert videos — the giveaway is the price anchor.
+
+## Key Evidence / Details
+
+**The "5 × 10 × 4 = 200" content factory:**
+
+| Layer | Count | What it is |
+|---|---|---|
+| Hot buttons | 5 | Big pain areas the ICP feels (e.g. "AI agents") |
+| Nuanced pains per hot button | 10 | Specific, observable problems inside each hot button |
+| Pain-point ideas | **50** | 5 × 10 — ≈50 days of content, then loop |
+| Formats per idea | 4 | e.g. clone / talking head / green screen / +1 |
+| Total pieces | **200** | 50 × 4 |
+
+**The pain-generation prompt (verbatim structure from the video):**
+
+> *"Make a list of 10 nuanced but observable problems business owners who are between $500,000 and $2 million in revenue have around [HOT BUTTON]."*
+
+The modifiers carry the weight: **"nuanced but observable"** forces specifics over clichés; **"business owners between $500K and $2M"** anchors to a concrete ICP so the pains sound like *their* world; **"around [hot button]"** scopes the output. Example outputs (around "AI agents"): *"They have AI tabs open and personal subscriptions but zero AI doing recurring workflows"*; *"They bought the automation and built a co-pilot that added work"*; *"Every agent still runs through them — they're the bottleneck."*
+
+**The pain → solution structure (every piece):** (1) open on the nuanced pain — "Do you have a bunch of AI tabs open but nothing's actually automating your business?" → *"how do you know?"*; (2) teach the fix. Never open on the solution.
+
+**The scramble, stated plainly:**
+
+> *"You could literally create a course on how to do everything from point A to point Z, put the videos on YouTube in a completely out-of-whack order, and people would still pay you for the same content put in the right order."*
+
+**Why it doesn't cannibalize sales** (the speaker's inversion of the hoarding instinct):
+
+| Instinct | Reality (per speaker) |
+|---|---|
+| Give away best stuff → lose demand | Give away best stuff → *increase* demand |
+| Hold best stuff in-house → look valuable | Hold it in-house → nobody knows you have it |
+| Scrambled free content = leaks your system | Scrambled free content = proof of expertise **without a shortcut around you** |
+| A high price feels expensive | $997 feels **cheap** after 50 free expert videos |
+
+**Actionable sequence (as given):** list 5 hot buttons → generate 10 nuanced pains each via the prompt → pick 4 formats → batch in pain→solution pairs → publish scrambled across hot buttons → rotate at day 51 → splinter any internal N-step playbook into N out-of-order pieces.
+
+**Audience:** service-business owners/consultants/agencies who "hold their best stuff in-house" and can't see why content isn't converting; anyone afraid that teaching = losing clients; anyone who runs dry on content ideas by week 2.
+
+## Connections
+
+- [[information-vs-implementation]] — this source is the sole and primary evidence for the concept (thesis + factory + scramble)
+- [[client-acquisition-channels]] — develops the organic-content channel that the 17-channel taxonomy only listed; adds a fourth, maximally pro-online-content position to the online-vs-in-person split
+- [[pain-discovery]] — the "10 nuanced but observable problems" prompt is a concrete tool for the same skill (name the buyer's pain better than they can); note it targets *content*, not live sales discovery
+- [[pricing-from-value]] — "free content makes $997 feel cheap" is an anchoring mechanism (giveaway as price anchor)
+- [[methodology-as-moat]] — "sequencing is what's paid for" is a moat framing: the ordered method, not the steps, is the defensible asset
+- [[cloning-over-originality]] — "splinter your internal playbook into out-of-order pieces" is a distribution corollary (share the parts, withhold the assembly)
+- Cross-source: same US "sell dear / productize" school as [[2026-07-17-design-the-perfect-offer]] (both reach the $997 core price and "buy the standard/method, not the labor"); directly opposed to [[2026-07-06-sebastian-interview-ai-and-software-engineering]], which rates content marketing a "Big zero"
+
+## Open Questions
+
+- **Who is the speaker?** The raw file names no person or brand. **Near-certainly answered 2026-07-23: [[dan-martell]].** [[2026-07-23-make-my-first-100k-in-month]] — which names him — reuses this source's three distinctive mechanisms verbatim: the scramble trick ("out-of-whack order… pay you for the same content put in the right order" ↔ "scramble the steps; the ordered checklist is what customers pay to have executed"), the *"10 nuanced and observable problems"* AI prompt, and the *"describe their pain better than they can"* expertise claim. Inference from mechanism overlap, pending owner confirmation — but strong enough that this page's claims are treated as Martell's throughout the wiki (see [[information-vs-implementation]] for the downgrade this forced).
+- **No results, only mechanism.** Zero data on whether the scramble strategy actually converts (view→lead→sale rates, examples). It is a plausible theory presented as fact.
+- **The math is loose.** "200 pieces ≈ nearly a full year, near-daily" is really ~200 days (~⅔ of a year); "50 days then loop" and "200 pieces" describe different cadences depending on how many formats ship per day. Treat the numbers as illustrative, not a schedule.
+- **ICP band mismatch.** The prompt anchors to **$500K–$2M revenue** businesses — a larger buyer than the rest of the vault's SMB/$1K-a-month framing. Whether the same engine works for the vault owner's likely buyers is untested.
+- **Does the scramble survive a motivated viewer?** Anyone who searches the channel and sorts by topic can partially re-sequence. The moat is friction, not secrecy — unquantified.
+- **Platform-blind.** Assumes a short-form feed (YouTube/TikTok/Reels) where discovery is per-video and non-linear. Weaker where audiences binge playlists or read in order.
+
+## Change Impact on Wiki
+
+Twelfth source; first on **demand generation / content marketing** as a discipline (prior sources listed "content marketing" only as one channel among 17).
+
+- Created [[information-vs-implementation]] — new concept; this source is its only evidence, so it is `Status: tentative`.
+- Enriched [[client-acquisition-channels]] (organic-content channel now developed; added as the fourth and most pro-online voice, sharpening the online-vs-in-person contradiction with [[sebastian]]).
+- Enriched [[pain-discovery]] (the nuanced-pain prompt added as a content-side tool for the "describe their world better than they can" skill).
+- Added cross-link notes to [[pricing-from-value]] (free content as price anchor) and [[methodology-as-moat]] (sequencing as the paid, defensible good).
+- Does **not** fill the vault's standing adversarial gap — it is another advocate of the same US "sell dear / give-value" school, so agreement here remains unreplicated advocacy.

wiki/sources/2026-07-19-your-company-cant-outgrow-your-team.md

@@ -0,0 +1,50 @@
+# Your Company Can't Outgrow Your Team
+
+#source #leadership #team
+
+## Source Metadata
+
+- **Date of source:** undated (YouTube clip, 4:35)
+- **Raw path:** `raw/sources/Your Company Can't Outgrow Your Team.md`
+- **Source type:** US leadership/management video — conclusions note
+- **Speaker:** [[dan-martell]] — the clip itself names no speaker; attribution confirmed by the vault owner 2026-07-20, after it was raised as a stylistic inference during the [[2026-07-20-referrals-will-sink-your-business]] ingest
+- **Root URL:** https://www.youtube.com/watch?v=wE3TwzH-XCE
+- **Ingested:** 2026-07-19
+
+## Core Claims
+
+1. **A company can only grow as fast as its people.** Targeting 100% company growth means every team member must grow ~100% — otherwise the ceiling is human, not market. Leadership's job: make that expectation explicit and hold it. *"Good got you on the team. Great keeps you on the team, because 100% requires greatness."*
+2. **Teach a philosophy, not a task list** — the speaker's "Business Athlete" framework gives climbers a model to climb toward. Two of its seven practices are named: *have a coach* ("I'm not your coach" — people own their own development) and *have a practice schedule* ("we practice until we can't get it wrong, we don't practice to get it right").
+3. **Make performance public.** Everyone's standing is posted where the team can see it — self-driven accountability without constant enforcement. Discipline: **praise in public, criticize in private** (hard talks in the 1-on-1, not on the wall).
+4. **The Keeper Test** (borrowed from Netflix): *"If this person had an offer for 30% more tomorrow, would I fight to keep them?"* Yes → they belong. No → have the honest conversation and turn it into a development plan (or a departure). Silent tolerance of "no" answers rots the team.
+5. **"Shine a light" on bright spots.** Have the team member who thinks differently teach the rest, regardless of age/tenure — leadership training becomes peer-generated, not manager-generated.
+6. **Values must be operational: hire → inspire → fire.** Screen for values before skills; tie every decision back to them; when someone goes, name the value violated. *"Values aren't what you say they are. They're what you tolerate."*
+
+## Key Evidence / Details
+
+- Anecdotal only — a leadership talk, no data. Examples given: firing a leader who didn't develop their people; firing someone who added process complexity (*"Complexity fails, simple scales"*).
+- Six actionable takeaways in the raw note: state the growth math out loud; adopt an athlete-style philosophy; post the scoreboard; run the Keeper Test on every direct report; weekly bright-spot teaching; audit your last three fires for value-naming.
+- Five of the seven Business Athlete practices are *not* in the clip — the framework is only partially captured.
+
+## Connections
+
+- [[team-growth-ceiling]] — new concept page carrying this source's thesis and mechanisms.
+- [[dan-martell]] — the speaker (identified 2026-07-20); his Branch A material is [[marketing-system]] and [[technical-founder-trap]].
+- [[marketing-system]] — same author, same argument aimed outward: the plateau is never the market. See the comparison table on [[team-growth-ceiling]].
+- [[future-of-engineering-work]] — complementary tension: if AI collapses teams to 2–3 people, each person's growth rate matters *more*, which strengthens this source's premise for small teams.
+- [[methodology-as-moat]] — "philosophy, not task list" is the internal-facing sibling of selling a named methodology externally.
+- [[sales-discipline]] — "practice until we can't get it wrong" echoes the consistency-over-intensity discipline on the sales side.
+
+## Open Questions
+
+- ✅ **Who is the speaker? — resolved 2026-07-20: [[dan-martell]]**, confirmed by the vault owner after the ingest of [[2026-07-20-referrals-will-sink-your-business]] surfaced it as a stylistic inference. Consequence recorded on [[team-growth-ceiling]]: this source and [[marketing-system]] are **one author**, so their shared "the ceiling is never the market" frame is a single worldview, not two independent findings. (Provenance note: curator testimony, not a documentary citation — the clip still names no one.)
+- What are the other five Business Athlete practices and the three values referenced? Now findable — Martell's published material is the route.
+- Does public-scoreboard accountability translate to small (2–3 person) senior teams, or is it a sales-floor/larger-org pattern?
+- The Keeper Test's 30%-raise framing assumes replaceability is assessable — how does that interact with tiny AI-era teams where each member is a single point of failure?
+
+## Change Impact on Wiki
+
+- Created this page and [[team-growth-ceiling]] (new concept; first page in the vault about *running* the delivery org rather than selling or the AI labor shift).
+- [[overview]]: added Branch C (running the team) note — one-source branch, marked tentative.
+- [[future-of-engineering-work]]: added Related-Pages link to [[team-growth-ceiling]].
+- [[index]], [[log]] updated.

wiki/sources/2026-07-20-referrals-will-sink-your-business.md

@@ -0,0 +1,58 @@
+# Referrals Will Sink Your Business
+
+#source #marketing #content-marketing
+
+## Source Metadata
+
+- **Date of source:** undated (YouTube clip, 6:47)
+- **Raw path:** `raw/sources/Referrals Will Sink Your Business.md`
+- **Source type:** US coaching video — conclusions note; [[dan-martell]] coaching a founder stuck at ~$1.5M revenue
+- **Root URL:** https://www.youtube.com/watch?v=50CTmoSuCYE
+- **Ingested:** 2026-07-20
+
+## Core Claims
+
+1. **Referral-only growth is a failed *primary* strategy.** It feels like validation ("all word-of-mouth!") but it is evidence the founder skipped building a marketing system. The $1.5M ceiling is *not* a market problem — it is a missing system. Founders who did the system work reach the same revenue in ~18 months **and can keep going**.
+2. **A marketing system is defined by a single property: money in at the top produces more money out at the bottom.** Everything else is inbound luck you don't control. → [[marketing-system]]
+3. **There are exactly three levers for making people aware of you: publish content, paid ads, partnerships.** All three cost something; all three are different skills. **Pick one and commit for 90 days** — don't dabble in all three.
+4. **"The new paid is organic."** The best-performing Meta ads now *look like content*; the platform wants content-shaped ads. Most founders never build the **creative pipeline** paid ads need at volume, because they aren't content creators yet. Rule: take an organic post that already worked, then run *that* as an ad. Skip the step and paid burns cash. So 90 days of organic is not a detour from paid — it's the **prerequisite**.
+5. **The technical-founder trap.** *"You and I are the same guy — software people, systems thinkers. 'Give me your problem and I'll go.' You don't want to explain, you just want to do it."* Technical founders are great at **solving** and terrible at **explaining**. Communication is the unlock; only after it exists do paid ads work, "because you now have something to say and know how to say it." → [[technical-founder-trap]]
+6. **Measure reps, not views.** Wrong questions: *how many views? did it go viral?* Right questions: *am I getting better? how many reps this week?* You do not decide what goes viral; the only controllable variable is rep volume. *"Most of you get bored with your marketing before the market ever does — and you just stop."*
+7. **Budget six months of patience.** Months 0–3: 90-day attack, skill-building, no system. Months 3–6: pipeline exists. Month 6+: the system begins producing leads. Months 6–18: $1.5M → $10M "no problem."
+
+## Key Evidence / Details
+
+- **Concrete cadence the speaker runs himself:** go **live every day** (stated reason, repeated three times: *"you got to practice"*); **two reels a day**; no gear, just a phone; publish to Facebook, Instagram, YouTube Shorts. Learn to answer questions, add value, and — most importantly — **explain what you do**.
+- **What "attack it" means:** daily (not weekly) volume, active experimentation with hooks/formats/angles, job-level intensity, feedback loops, continuous new creative.
+- **Evidence quality: anecdotal advocacy, zero data.** No conversion figures, no cost-per-lead, no cohort of founders who tried and failed. The $1.5M→$10M and "~18 months" numbers are unsourced coaching claims.
+- **The two viral proof points are survivorship bias.** *Tones and I — "Dance Monkey"* (busker, one recording, billion+ streams) and *Oliver Anthony — "Rich Man North of Richmond"* (backyard, filmed on a bad phone, now touring millionaire) are used to support *"everyone is one creative project away from being a superstar."* Two selected winners cannot support that inference; the unobserved denominator is every person who shipped daily and never landed. The narrower claim the anecdotes *do* support — **you must still be shipping when it lands** — survives.
+- The one line the speaker leaves it on: *"You don't decide what you create that's gonna go viral. The only thing you control is the volume of the reps."*
+
+## Connections
+
+- [[marketing-system]] — **new concept page** carrying this source's central thesis (owned system vs. inbound luck; three levers; organic→paid bridge; the 6-month lag).
+- [[technical-founder-trap]] — **new concept page**: solving ≠ explaining, and why that gap is upstream of a founder's marketing problem.
+- [[referrals]] — this source is the vault's **first counter-position on referrals**, which every prior source rated the highest-converting channel. It does not dispute referral *conversion*; it disputes referral *dependency*. Recorded there in full.
+- [[client-acquisition-channels]] — a fourth, competing taxonomy (3 levers vs. the 17-channel/3-tier map), and a direct conflict on **how many channels to run** (pick 1 vs. pick 3).
+- [[information-vs-implementation]] — a second source for content-as-primary-engine, adding "explain what you do" and the organic→paid bridge. **Independence withdrawn 2026-07-23:** the founding 07-18 source is near-certainly the same author, so this is framework consistency, not corroboration.
+- [[partnerships]] — the third lever, named and dropped here; mechanism supplied by the same author 2026-07-22.
+- [[sales-discipline]] — "reps not views" is a near-exact restatement of consistency-over-intensity, arrived at independently; the 6-month patience budget is the missing time dimension.
+- [[dan-martell]] — new entity page.
+
+## Open Questions
+
+- ✅ **Same speaker as [[2026-07-19-your-company-cant-outgrow-your-team]]? — yes, confirmed by the vault owner 2026-07-20.** Raised here as a stylistic inference (same genre; the "Business Athlete" framework) and confirmed the same day. Consequences applied across the wiki: Branch C's lone source gains an author, and [[team-growth-ceiling]] + [[marketing-system]] are recorded as **one voice, not two** — their shared "the ceiling is never the market" frame is a worldview restated, not a finding replicated. See [[dan-martell]].
+- At what revenue does referral dependency actually become the binding constraint? The advice is aimed at ~$1.5M with an existing client base — it is silent on, and probably not addressed to, a pre-first-client operator.
+- Does "pick one lever" survive contact with a solo operator who has no team to absorb daily-live + 2-reels-a-day? The cadence assumes marketing is the founder's job, not a slice of it.
+- ✅ ~~No mechanism is given for *partnerships*, the third lever — it is named and dropped.~~ **Answered 2026-07-22** by the same author: [[2026-07-22-stop-cold-calling-do-this-instead]] supplies borrowed credibility + partner-archetype recruiting → [[partnerships]]. (Lint 2026-07-29: this page was the last one still showing the question open.)
+
+## Change Impact on Wiki
+
+- Created this page, [[marketing-system]], [[technical-founder-trap]], and [[dan-martell]].
+- [[referrals]]: added a **Counter-Position** section (referral dependency as a growth ceiling) and revised Contradictions — this closes the page's standing *"no adversarial source"* gap, though only partially (counter-*position*, not counter-*evidence*; see that page).
+- [[client-acquisition-channels]]: added the three-lever taxonomy, the pick-1-vs-pick-3 conflict, and a fifth row to the content-position table.
+- [[information-vs-implementation]]: upgraded from single-source; corroboration recorded, `tentative` narrowed.
+- [[sales-discipline]]: added reps-not-views corroboration and the 6-month patience budget.
+- [[eugene]]: added the technical-founder-trap lens on his stated networking blocker.
+- [[2026-07-19-your-company-cant-outgrow-your-team]]: recorded the speaker-attribution hypothesis — **confirmed same day** by the vault owner, then applied: speaker added to that page's metadata, [[team-growth-ceiling]] re-scoped as same-author-as-[[marketing-system]] (with the cross-branch comparison table), [[dan-martell]] extended to cover both branches.
+- [[overview]], [[index]], [[log]] updated.

wiki/sources/2026-07-22-stop-cold-calling-do-this-instead.md

@@ -0,0 +1,65 @@
+# Stop Cold Calling, Do This Instead
+
+#source #sales #partnerships
+
+## Source Metadata
+
+- **Title:** Stop Cold Calling, Do This Instead
+- **Speaker:** Dan Martell — named in the raw note itself (documentary attribution, unlike the 07-19 clip)
+- **Root source:** YouTube video, 4:38 — https://www.youtube.com/watch?v=wk5MpA2ckTI
+- **Raw path:** `raw/sources/Stop Cold Calling, Do This Instead.md`
+- **Source date:** undated (ingested 2026-07-22)
+- **Type:** conclusions note from a US coaching video; **third [[dan-martell]] source** in the vault
+
+## Core Claims
+
+1. **Pipeline or hope.** Every business either has a repeatable pipeline (attention → conversion → customer) or it stops growing. *"If you can't describe your pipeline in one sentence, you don't have one — you have hope."*
+2. **Exactly three pipeline sources — Publish, Paid, Partners** — and the rule to **pick one and go all in**. This restates the three-lever taxonomy from [[2026-07-20-referrals-will-sink-your-business]] verbatim in structure (publish/content, paid, partnerships), which confirms it is a stable framework for this author — and adds nothing to its evidence, since it is the same voice.
+3. **Cold outbound into enterprise is the hardest path** — procurement, getting the meeting, closing *before someone gets fired or the board reshuffles*. Anecdote: four years in a suit at 24 selling to Fortune 2000 ("you might as well go run an ultra marathon"; the PTSD-and-button-up-shirts bit).
+4. **Partnerships is the fastest lever, especially for enterprise, because of borrowed credibility** — someone the buyer already trusts walks you in, so the buyer arrives pre-sold. Anecdotes: one system integrator walked him into **7 New Jersey pharmaceutical companies** (Novartis, J&J, …) in one shot; **$95K contracts signed three weeks** after introduction.
+5. **Both sides win, which is why it repeats.** The integrator held a multi-million-dollar contract on the same account; bringing in a vendor who delivers strengthens the partner's position. No revenue-share mechanics are described — the partner's payoff is account value, not commission.
+6. **The insight is the system, not the intro.** Most founders treat a good partner as luck. The move is to **reverse-engineer the partner that worked** (six questions: where did we meet; what was true about them; how many more like them exist on that channel; can I make content for that audience; can I use their success story as bait; can I make my offer stupid-easy to say yes to) and become a *"professional recruiter of system integrators"* (his targets: Tata Consulting, IBM Global Services).
+7. **The playbook:** find who inside the partner org makes the "who do we bring in" decision → go to the **events they attend, not the events your peers attend** → win the individual first → let them bring you into accounts → deliver → systematize content/offer/story to attract more of the same partner archetype.
+8. **Ten good partners can replace an outbound sales team.**
+9. **Scope, stated by the source:** mid-market/enterprise, agencies, B2B services, deal sizes justifying a relationship motion (~$10K+ ACV). Explicitly not low-ticket DTC.
+
+## Key Evidence / Details
+
+| Claim | Support offered | Grade |
+|---|---|---|
+| Partner → 7 pharma companies in one shot | Personal anecdote, companies named | Unverifiable, survivor-selected |
+| $95K contracts 3 weeks post-intro | Personal anecdote | Unverifiable |
+| Partner's multi-million contract (the both-win logic) | Personal anecdote | Unverifiable, but the *structural* point (partner is paid in account value) stands without the figure |
+| Cold enterprise outbound is brutal | Personal experience, 4 years | Anecdote, though independently echoed by [[sebastian]] — see Connections |
+| Ten partners replace an outbound team | Assertion | No cohort, no numbers |
+
+Evidence grade overall: **advocacy** — a coaching clip built on the author's own war stories, no data, from someone who sells the prescribed discipline. Same grade as the other two Martell sources. What survives without the figures is the **mechanism**: borrowed credibility lowers enterprise entry friction, and partner *acquisition* is a controllable input where client referrals are not.
+
+## Connections
+
+- **[[partnerships]]** — created from this source; the full mechanism lives there
+- [[marketing-system]] — the third lever, previously "named and never explained," now explained; the standing open question there is closed
+- [[referrals]] — answers that page's open question "is there a version of referrals *with* a throttle?" — yes: partner-sourced intros, because you control partner recruitment
+- [[client-acquisition-channels]] — a new counter-position on **cold outbound** (the title's target), and a qualification to the "all three levers are one-to-many" reading
+- [[relationships-as-moat]] — convergence from an unexpected direction: the content pole's own author prescribes **trust-mediated, in-person entry** for enterprise (events, win the individual), differing from [[sebastian]] only on *whose* trust — borrowed vs. built
+- [[dan-martell]] — third source; extends the through-line (systematize the lucky win)
+- [[sales-discipline]] — "commit fully to one channel" restated
+- [[eugene]] — gives his networking blocker a *target*: recruit a partner archetype, not "network" generally
+
+## Open Questions
+
+- **What does the partner actually get?** The both-win logic here is account value (the integrator's multi-million contract benefits from a vendor who delivers). Is that generalizable, or do smaller-scale partner plays need explicit rev-share/referral fees?
+- **What is the minimum credibility bar?** The anecdote comes from a funded SaaS founder with a product. Would a Tata-class integrator take a meeting with a no-name solo developer at all? The source doesn't say.
+- **What is the SMB analogue?** If the buyer is SMB (Eugene's likely near-term market), the system-integrator archetype doesn't exist — are agencies, MSPs, accountants, or hardware vendors the equivalent partner class?
+- Recruiting a partner still requires approaching a stranger (event, introduction) — outbound redirected at a higher-leverage audience, not eliminated. The title over-promises relative to the mechanism; does the source's own playbook step 3 ("introduce yourself and win the individual over") differ from warm-ish cold outreach in anything but target selection?
+
+## Change Impact on Wiki
+
+- Created [[partnerships]] — new concept page; the third lever now has a mechanism, an economics sketch, and a scope
+- [[marketing-system]] — lever table updated (partnerships no longer unexplained); one-to-many characterization qualified; open question closed
+- [[client-acquisition-channels]] — cold-outbound counter-position added; three-lever paragraph updated
+- [[referrals]] — throttle question answered; referral-partners paragraph now points to [[partnerships]]
+- [[relationships-as-moat]] — borrowed-vs-built trust convergence recorded
+- [[dan-martell]] — third source added; partnerships question closed; through-line extended
+- [[eugene]] — partner-archetype reading of his networking blocker added
+- [[overview]], [[index]], [[log]] — counts, threads, contradictions updated

wiki/sources/2026-07-23-make-my-first-100k-in-month.md

@@ -0,0 +1,83 @@
+# If I Wanted to Make My First $100K/Month, I'd Do This
+
+#source #offer-design #sales #demand-generation
+
+## Source Metadata
+
+- **Date:** unknown (video publication date not recorded in raw file)
+- **Raw path:** `raw/sources/Make My First $100K in Month.md`
+- **Source type:** YouTube video conclusions/notes (22:54 runtime) — <https://www.youtube.com/watch?v=xj5gZq159lM>
+- **Speaker:** **[[dan-martell]]** — named in the raw note (fourth confirmed Martell source; "built and sold 3 multi-million-dollar companies")
+- **Ingestion date:** 2026-07-23
+- **Format note:** Distilled conclusions document, not a transcript — claims are one interpretive layer removed from the speaker.
+
+## Core Claims
+
+1. **$0 → $100K/month is a sequence problem, not a grinding problem.** Five steps in strict order: money math → productized service → three-tier offer → demand (inbound + outbound in parallel) → close by chat or call. Marketing comes **before** building anything.
+2. **The money map: ~100 customers × ~$1,000/month is the sweet spot.** Of five price×count routes to $100K/mo (1×$100K whale … 10,000×$10 mass-market), only the middle is sane. Floor: **$1,000/month minimum offer, below $10K/month** — "every conversation should be worth having." He *personally dislikes* the 10×$10K "enterprise-lite" model (still heavy per-deal).
+3. **People pay for exactly three things: time, money, status.** Money is easiest to sell; status is routinely ignored and underpriced. At $1K+/month, sell to **business owners** — all three motivations apply and they decide fast. Filter what *you* offer through **Ikigai** (love / good at / world needs / will pay), with "good at" reframed as *what do people tell me I'm good at*.
+4. **Productized service is the starting format** — custom services sell hours (no leverage), products are slow and risky to build; a fixed package with repeatable steps, priced like a product, funds the eventual product with customer cash.
+5. **Three-tier decoy pricing:** ½× DIY ($500/mo) / **1× core productized ($1,000/mo — the one you sell)** / 10× done-for-you ($10,000/mo). Both flanking tiers are **decoys** whose job is to make the core print. Every offer contains: outcome, deliverable, investment (never "cost"), **risk reversal** (a specific guarantee — "10 leads/month"), urgency.
+6. **Inbound: give everything away; monetize the sequence.** Per deliverable, AI-generate "10 **nuanced and observable** problems" the customer has → infinite hook-first content backlog. *"If I can describe my customer's pain better than they can, I'm the expert."* You still get paid for the **order of implementation** — in content you *scramble* the steps (A1, B2, C1…); the ordered checklist is what customers pay to have executed.
+7. **Outbound: mine what you already have.** Phone contacts → **"ask past the person"** ("do you know anyone with this problem?" — often answers "yeah, me", otherwise yields warm intros) → referral-name openers → AI-built list of 100 as backfill. Track a spreadsheet funnel.
+8. **Close by chat or cold call.** DM flow: content-or-help question → pain-awareness questions → offer-doc link → Stripe link (he claims 8 figures sold by chat). Cold call's job is **not to sell** — qualify + book a meeting from a meeting. **Surface objections before presenting so they become obstacles** ("do you have a budget to solve this?").
+9. **Volume discipline:** first 5 calls are throwaways; no-answer → call back within 30 seconds; feed call transcripts to AI to find where you stumble; goal **100 no's per day**; **spend nothing until customers have paid**.
+10. **Build only after money arrives.** Pre-sell with a landing page + waitlist; a **$50 "top of the waitlist" payment** is the demand proof. No money in → don't build.
+
+## Key Evidence / Details
+
+**The money map:**
+
+| Model | Customers | Price | Verdict |
+|---|---|---|---|
+| Whale | 1 | $100,000 | Concentration risk, elite skills |
+| Enterprise-lite | 10 | $10,000 | He dislikes it — heavy per-deal |
+| **Sweet spot** | **~100** | **~$1,000/mo** | **Recommended start** |
+| Prosumer | 1,000 | $100 | Too many closes |
+| Mass-market | 10,000 | $10 | Reach a new founder can't get |
+
+**Personal track record offered as evidence (self-reported, unverified):** second company **Flowtown** — 350K unique visitors → 50K customers from blog content; first company (Maritime Vacation) built product before marketing → *"crickets"* → failed. The one before/after pair behind "marketing before manufacturing."
+
+**The cold-call opener (paraphrased transcript):** a curiosity question scoped to the prospect's world ("have you looked into AI answering your calls…?"), an explicit "I've got nothing to sell," a peer-behavior nudge, then a 15-minute Zoom with a live demo. Worked example niche: **AI voice agents for local businesses** (SMB, not enterprise).
+
+**Artifact discipline:** offer doc (copywritten, sells on its own via a link) vs. pitch deck (bullets you speak over). **Never email the pitch deck** for "team review" — it gets forwarded and your plan hired out to someone else. Drafting is delegated to AI via "reverse prompting" ("…then ask me any question you need to get total clarity").
+
+**Audience:** aspiring founders at $0; service providers stuck on hourly/custom; SMB-focused agencies, AI-automation builders, consultants.
+
+## Connections
+
+- [[dan-martell]] — fourth confirmed source; see the within-author tensions below
+- [[pricing-from-value]] — the money map is the backwards math restated; $1K/mo floor re-asserted (same voice as the suspected 07-17 origin, so convergence is weak)
+- [[offer-ladder]] — a second three-tier ladder, now with an explicit **decoy** rationale and different ratios (½×/10× vs. 45%/5×)
+- [[outcome-based-selling]] — "features tell, outcomes sell"; the time/money/status triad; the five offer elements incl. risk reversal
+- [[productized-service]] — the custom/product/productized triage; **offer-first camp gains a source**; the $50 pre-sell waitlist converges with the RU validate-before-build rule
+- [[information-vs-implementation]] — the scramble trick and the "nuanced and observable problems" prompt **verbatim from a named Martell source** — the key to the 07-18 authorship question; plus Flowtown, the first (self-reported) outcome number for content-as-engine
+- [[client-acquisition-channels]] — inbound + outbound **in parallel**; cold calling prescribed for SMB; the phone-mining outbound ladder
+- [[sales-discipline]] — objections-vs-obstacles; 100 no's/day; 30-second callback; chat DM flow; don't spend until paid
+- [[referrals]] — "ask past the person" mines the personal network for warm intros **before any past client exists**
+- [[marketing-system]] · [[partnerships]] — stage tensions with the same author's scaling material (see below)
+- [[niche-selection]] — sell to business owners at $1K+; Ikigai as the supply-side filter
+- [[eugene]] — the $0-start blueprint matches his stage; the sweet-spot format fits his domain poorly (see entity page)
+
+## Open Questions
+
+- **Does the sweet spot survive contact with delivery?** 100 concurrent $1K/mo customers is a support/ops load the video never costs out — for a solo operator that may be *harder* than 10 × $10K, the model he dislikes.
+- **All numbers are self-reported.** Flowtown's 350K→50K, "8 figures by chat," and every rule of thumb ($1K floor, 100 no's/day, 30-second callback) carry no external verification.
+- **Within-author tension 1 — cold calling.** [[2026-07-22-stop-cold-calling-do-this-instead]] (same author): cold outbound is "the hardest path." Here: cold calling is one of two prescribed closing channels. Reconciliation is scope — that clip was ~$10K+ ACV enterprise; this one is $1K/mo SMB/local — but neither video states the boundary.
+- **Within-author tension 2 — parallel engines vs. pick one.** The three-lever material says pick **one** lever, 90 days. Here inbound and outbound run **in parallel** from day zero. Stage-scoped (start vs. scale)? Neither video says so.
+- **Within-author tension 3 — the $10K deal.** He "personally dislikes" 10×$10K, yet [[partnerships]] — his flagship enterprise play — is scoped ~$10K+ ACV. Stage-dependent again, unstated.
+- **The chat-vs-call posture blurs.** The suspected-same-author 07-17 video says the market is call-fatigued (chat-first); this one teaches cold calls alongside chat. If one speaker holds both, the positions are channel-by-buyer, not a doctrine.
+
+## Change Impact on Wiki
+
+Seventeenth source; fourth confirmed [[dan-martell]] — and the trigger for a **source-independence correction**: its verbatim reuse of the scramble trick and the "nuanced and observable problems" prompt makes Martell the near-certain author of the previously anonymous [[2026-07-18-information-is-free-implementation-is-paid]], and the "buy back 10 hours" signature makes him a plausible author of [[2026-07-17-design-the-perfect-offer]].
+
+- Created this page.
+- [[dan-martell]] — fourth source; money map; within-author tensions; suspected authorship of 07-18 (strong) and 07-17 (moderate).
+- [[information-vs-implementation]] — **downgraded** its "independent second voice" claim (the first voice was probably Martell too); added Flowtown as first, self-reported outcome data.
+- [[offer-ladder]] — second ladder + decoy rationale; no longer single-example, still possibly single-author.
+- [[productized-service]] — offer-first trigger gains a source; pre-sell waitlist mechanic added (cross-tradition convergence with validate-before-build).
+- [[pricing-from-value]] — floor restated; convergence caveat.
+- [[outcome-based-selling]] — time/money/status; five offer elements.
+- [[client-acquisition-channels]] · [[sales-discipline]] · [[referrals]] · [[marketing-system]] · [[partnerships]] · [[niche-selection]] · [[eugene]] — updated as described on each page.
+- Source pages [[2026-07-17-design-the-perfect-offer]] and [[2026-07-18-information-is-free-implementation-is-paid]] — speaker open questions updated with the new attribution evidence.

wiki/sources/2026-07-26-how-to-build-a-billion-dollar-company-2027.md

@@ -0,0 +1,61 @@
+# Как Построить МИЛЛИАРДНУЮ КОМПАНИЮ в 2027 (How to Build a Billion-Dollar Company in 2027)
+
+#source #gtm #strategy #pricing
+
+## Source Metadata
+
+- **Raw path:** `raw/sources/Как Построить МИЛЛИАРДНУЮ КОМПАНИЮ в 2027.md`
+- **Source type:** Conclusions note from a Russian-language YouTube video (34:52), https://www.youtube.com/watch?v=GE5qmn7M7lo
+- **Speaker:** [[oskar-hartmann]] (identified in the raw note by context: KupiVIP, ShoppingLive, Fab.com shareholder, "Создатель единорога" program)
+- **Date:** undated (2026 context — "land grab happening right now in AI")
+- **Ingested:** 2026-07-26
+- **Independence:** a genuinely new voice — **third tradition** in the vault (VC/product-startup world), independent of both the [[dan-martell]] corpus and the RU dev-sales cluster (Rodenko, AB Analytics, Tony)
+
+## Core Claims
+
+1. **A good product does not sell itself.** In the vibe-coding era everyone has "10–15 great products sitting in Cloud Code"; the startup graveyard grows faster than the list of successes. **Product-Market Fit is the start, not the finish.** What separates a billion-dollar company from a "tumor" is a **repeatable, scalable sales channel with predictable acquisition economics** ([[sales-channel-as-moat]]). Claimed illustration: "Tim Cook created more value than Steve Jobs — 45× growth of Apple without a single new product."
+2. **Five founder mistakes:** (1) building feature #26 instead of a go-to-market machine; (2) not selling personally — "I'll hire a salesperson" is a childish idea; the founder is the company's chief salesperson, and Hartmann won't invest where the founder doesn't sell; (3) targeting the whole TAM instead of a small winnable SOM ("AI agent answering calls for HVAC/plumbers" beats "AI agents for every profession"; Manifest became a unicorn on **immigration law alone**); (4) betting on giant clients — Pediant sold QR payments to Walmart/Best Buy, integrations dragged 1.5 years, the champion left, the deal died, and with it the startup; (5) hoping a partnership will "make everything fly" — **partners almost always disappoint** (your product is lost among a bank's 15 own + 30 partner products; a single gatekeeper partner takes all the margin; observed results **100–200× below expectations**). Partnerships work only with **many** partners and a product that sits naturally on top of their services ([[partnerships]]).
+3. **Channel beats technology — Pediant vs FlatPay.** FlatPay (payment terminal, "1% commission, no asterisks") built **door-to-door sales** in Holland/Germany: one rep sells 10–20 terminals/month → billion-dollar company; its founder is on his **sixth** business using the same distribution playbook — the channel, not the product, is the reusable asset.
+4. **Attention is the most expensive resource on the planet.** 12 hours of screen time, ~40 GB of information per head per day; AI made it worse (2,000 unread LinkedIn messages — agents mail for everyone). Channel hierarchy by attention economics: search ads (intent already expressed) → banner/Meta (interruption, pricier per result) → offline events (returning) → TV/Super Bowl (~$10M per 30s). "The average product that shouts displaces the better product that stays silent."
+5. **Businesses that find a channel know their LTV** and will pay up to **a third of a client's lifetime profit** to acquire them on day one (US credit-card client ≈ **$1,000 CAC**). Burned-in channels are an **entry barrier**; venture rounds exist to fund negative unit economics until LTV lands ([[unit-economics]]).
+6. **Land grab in AI, right now:** Anthropic and OpenAI struck **~$4B joint ventures** with private-equity firms holding hundreds of thousands of portfolio companies — every channel at once (partner, direct, phone, door-to-door). A resilient system is **multichannel**, channels reinforcing each other.
+7. **Only ~1% of businesses fit venture.** European VCs won't look below $100B+ potential. **Stretching a normal company onto venture expectations kills it** — Fab.com: $50M→$100M revenue on a loyal design niche, raised at $1.5B, chased $10B expectations, only losses grew, bankrupt. Alternatives: top-20 US **private** family-owned companies do $30B+ revenue; slow $10M→$100M mid-market growth is a fine business, just not venture; Hartmann's ShoppingLive was built on "a couple hundred thousand dollars" with ~9-month payback and became Russia's #1 TV shop ([[venture-fit]]).
+8. **AI is sucking up all free capital:** Anthropic, SpaceX, OpenAI will absorb nearly all free cash in the venture market this year — "you're either in a top AI lab, or for the venture market you don't exist." The rest should build "amusement parks" with 9-month payback and reinvest profits.
+9. **Most entrepreneurs sell cheaper than the real cost.** Forgotten cost lines: distribution and sales, *repeat* acquisition/retention, transport, amortization, inventory write-offs — the resulting "cash gaps" are actually **real losses**. Sequence: prove the product is needed → prove you can produce it far below willingness-to-pay → the spread must cover everything **with a buffer**. And never use your best year as the base — the best year is a once-a-decade anomaly ([[unit-economics]]).
+10. **Pricing power is the real PMF test.** If you can raise prices and the client flow doesn't fall — that's PMF. If you can't set your price (a marketplace sets it, discounts aren't yours to give) — "you're not an entrepreneur, you're in a simulation of entrepreneurship" ([[pricing-from-value]]). Marketplaces themselves are the most striking model: start free, end enormously profitable, because they hold the pricing power — and they survive the AI era.
+11. **One partner deal can boost, not build.** His own first store hit $20M via a single entrepreneurial deal (partner drove traffic, paid 10% of revenue post-factum, open books) — then the partner's management changes, audits arrive, terms flip to CPM; by then you must have the statistics to compete in auctions. One-off boosts don't replace systematic channels.
+12. **The entrepreneur's job, stripped of everything else: build and sell.** All else is derivative.
+
+## Key Evidence / Details
+
+- Named cases: Pediant (QR payments, Walmart/Best Buy — died), FlatPay (door-to-door terminals — billion-dollar), Fab.com (venture stretch — bankrupt; Hartmann a shareholder), Manifest / Дэн Мишин (immigration-law niche — unicorn), ShoppingLive (low-capital, high-ROI), Apple/Tim Cook (45× without new product).
+- Closing checklist the speaker poses to founders: real PMF or pleasant illusion? · narrow winnable segment? · which *aching* pain? · venture-fit or reinvest-and-grow-slow? · pricing power? · which channel lets you **repeat**? · full-cost pricing? · will you be the company's first salesperson?
+- Through-principles as stated: product → sell → repeat; SOM > TAM at the start; one channel = concentration risk; partners are a bad *first* channel ("you are their 46th priority"); attention is the most expensive resource; fundraising is an obligation, not success; whoever sells too cheap has no PMF; **sales channel is a moat**; founder sells first, always.
+
+## Connections
+
+- [[sales-channel-as-moat]] — new page; the source's central thesis (moat candidate #3, next to [[methodology-as-moat]] and [[relationships-as-moat]])
+- [[unit-economics]] — new page; full-cost pricing, LTV×⅓ CAC, buffer margin (partially fills a long-flagged vault gap)
+- [[venture-fit]] — new page; the 1% rule, venture stretch, the slow-growth alternative
+- [[partnerships]] — **first independent voice on the page**: adversarial on partner-as-savior, convergent with Martell on "many partners, never one gatekeeper"
+- [[pricing-from-value]] — pricing power as PMF test; "most sell cheaper than real cost" joins the sell-dear school from a *different* tradition
+- [[niche-selection]] — SOM > TAM independently restates "niche is upstream of everything" (Manifest case)
+- [[tam-sam-som]] — the sizing vocabulary itself (created 2026-07-26 from a follow-up Q&A)
+- [[client-acquisition-channels]] — channel hierarchy by attention; whale-client warning; the multichannel position
+- [[marketing-system]] — independent second voice for "a machine with predictable economics you can turn up"; FlatPay = one repeatable channel first, multichannel at scale
+- [[sales-discipline]] / [[technical-founder-trap]] — founder-sells gets a third tradition; feature-#26 syndrome is the trap's product-startup form
+- [[ai-market-shift]] — vibe-coding commoditizes the product artifact; attention scarcity; the AI land grab and capital suction
+- [[oskar-hartmann]] — new entity
+
+## Open Questions
+
+- Almost every figure is war-story grade: 100–200× partner shortfall, $1,000 CAC, ~$4B JVs, 12h/40GB attention numbers, $10M Super Bowl, Apple 45× — quoted from memory on stage, uncited. Attributable, not verified.
+- **Scope mismatch with the vault:** the address is to *product startups* choosing venture vs. bootstrapped growth; the vault's core domain is *dev services*. Which claims transfer (founder-sells, SOM>TAM, pricing power, full-cost pricing — plausibly all) and which don't (LTV×⅓ CAC math assumes recurring product LTV) is the reader's judgment, not the source's.
+- Incentive: Hartmann runs a paid "unicorn creator" program — like every coaching source in the vault, the diagnosis ("you lack GTM discipline") is adjacent to what he sells.
+- The Tim Cook claim ("45× without a single new product") is rhetorically effective and factually contestable (Watch, AirPods, services all shipped under Cook) — treat as a framing device, not a fact.
+- Does the door-to-door FlatPay playbook say anything for B2B services, or is it consumer/SMB-product-specific?
+
+## Change Impact on Wiki
+
+- Created [[oskar-hartmann]] (entity), [[sales-channel-as-moat]], [[unit-economics]], [[venture-fit]] (concepts).
+- Updated [[partnerships]] (first independent second voice — counter-position + partial convergence), [[pricing-from-value]] (pricing power test; cross-tradition convergence note), [[niche-selection]] (SOM>TAM, third-tradition convergence), [[client-acquisition-channels]] (multichannel position, whale-client warning, attention hierarchy), [[marketing-system]] (independent corroboration of the system idea; pick-one complication), [[sales-discipline]] (founder-sells third voice), [[technical-founder-trap]] (feature-#26 convergence), [[ai-market-shift]] (vibe-coding commoditization, attention scarcity, land grab), [[methodology-as-moat]] (third moat candidate cross-ref), [[eugene]] (pricing-power and SOM implications), [[overview]], [[index]], [[log]].

wiki/sources/2026-07-26-main-principle-of-successful-business.md

@@ -0,0 +1,59 @@
+# Главный Принцип УСПЕШНОГО БИЗНЕСА (The Main Principle of a Successful Business)
+
+#source #validation #strategy
+
+## Source Metadata
+
+- **Raw path:** `raw/sources/Главный Принцип УСПЕШНОГО БИЗНЕСА.md`
+- **Source type:** Conclusions note from a Russian-language YouTube video (17:52), https://www.youtube.com/watch?v=pHoWRl7MVwE
+- **Speaker:** [[oskar-hartmann]] (named in the raw note) — his **second** vault source
+- **Date:** undated (2026 context — AI mockups, humanoid-robot data market)
+- **Ingested:** 2026-07-26
+
+## Core Claims
+
+1. **Sell first, then build.** Building the product is the entrepreneur's most expensive and least reversible decision; before committing, prove with **cheap experiments** that the pain is acute enough that customers **pay money up front**. Waitlists, likes, "interesting" — none of it counts ([[sell-before-build]]).
+2. **The signal hierarchy:** button click (weak) < email/waitlist signup (stronger but deceptive) < **payment — the only real signal**. "Голос деньгами" — voting with money.
+3. **The cheap-experiment toolkit:**
+   - *AI-mockup blast* (his own anti-case): a beautiful AI-generated image of a coworking space for business owners, offered to ~5,000 people via 7–8 business clubs with named price and "20 seats, who's with me?" — **0 real buyers** despite his 100% conviction. Project killed for pennies instead of millions.
+   - *Fake payment screen*: top utility-app studios launch ~20 apps at once as full-looking shells; at the payment screen the user sees "Error, payment failed" — the studio keeps real willingness-to-pay data at **< $1,000 per experiment**. Findings: "quit casino" failed, "quit porn" worked, weight-loss always works. The studios **forbid themselves from inventing** — they let money vote.
+   - *Fake-door buttons* (Oliver Samwer's eBay clone for Germany, ~20 years ago): shipped all 100 buttons in the UI **non-functional**, watched click logs, built in click-count order. "Intuition deceives — always."
+   - *Wizard-of-Oz manual MVP*: when the product can't be cheaply mocked, deliver the value **by hand for the first 10 clients**, then automate. (His example: Build.ai [sic] — valued at $2B while "the AI" was 500 Indian specialists; "great way to *start* — at $2B you should probably have built the product.")
+   - *Pre-orders at any scale*: Tesla collected 100K paid Model 3 preorders, then built; same for Cybertruck — "a $1.5T company still tests demand; the principle doesn't depend on size."
+4. **Pre-payment is the supreme demand signal.** The MIT-graduate case: sold **$5M in prepaid contracts** for humanoid-robot training data ("fold shorts + sensors + video") *before collecting any data* — strategy copied from 10 companies that grew the same way on LLM data. Positive unit economics from day one. Anti-case: his own Zavent (meeting-room booking) — customers would only pay 3 months post-delivery, turning the company into "a bank financing its clients"; when prepayment was required, conversion collapsed. **If customers will pay up front, demand is real; if only post-pay, you're in a different business.**
+5. **The acute-pain test:** *"If the business only works when everything is perfect — it's a bad business. A good business is when everything is bad and people still come and pay."* Exemplar: hospitals — 1.5-hour waits, no good reviews, you pay anyway and say thank you. Acute pain means people pay **for the concept**, not for polish ([[pain-discovery]]).
+6. **The recommended trainer business is traffic arbitrage:** fastest feedback loop — buy traffic → landing → payment screen; a **single word** in the offer can move conversion 3–5×. Rule: a plain landing page doesn't qualify — there must be a **payment screen**.
+7. **The mindset differential:** two portfolio AI companies, 12 weeks, same money — team A ran 10 tests, updated the product repeatedly, constant customer signals; team B, still building, zero signals. Only difference: **willingness to launch ugly and look stupid**. "Success is usually not where you thought — and only frequent cheap tests find it."
+8. **Red flag: duration without revenue.** "We've been working on this since 2016, no revenue yet" is pitched as dedication and is "the fattest minus" — no revenue over a long project = no evidence. "I'd rather talk to a team that started a week ago."
+9. **CAC-burning as a moat, restated:** once PMF is proven and unit economics are positive, spend heavily per customer ($80–100 CAC) so no newcomer can afford to enter — consistent with his first source's ⅓-of-LTV entry-barrier logic ([[unit-economics]], [[sales-channel-as-moat]]).
+10. Через-principles: experiment while it's cheap ($1K mistake safe; 6-month build fatal); intuition always deceives; endure the pain of reality **early**; don't dictate what the customer should want — build what is already demanded.
+
+## Key Evidence / Details
+
+- The self-test checklist (raw note): smallest experiment that would falsify the hypothesis · what makes a customer pay *now*, pre-build · landing → **payment screen** (not signup) · can I collect (partial) prepayment · who — by name — is the smallest group with the most acute pain · will I walk to 10 concrete potential buyers and ask what they'd pay for right now · can I deliver the value by hand to the first 10 · if >3 months with no revenue, what actually stops an ugly launch tomorrow · does my business survive when everything goes wrong?
+- Named cases: coworking test (own, failed cheaply), utility-app studios, Samwer/eBay-Germany, Tesla Model 3/Cybertruck, humanoid-data founder ($5M prepaid), Zavent (own, post-pay trap), Build.ai [sic].
+
+## Connections
+
+- [[sell-before-build]] — new page; the whole discipline (signal hierarchy + toolkit) lives there
+- [[productized-service]] — validate-before-build gains a **third tradition**; the $50-paid-waitlist and RU validate-first rules now have a full toolkit behind them
+- [[pain-discovery]] — the acute-pain test ("still pay when everything is bad") is a new, revealed-preference diagnostic
+- [[cloning-over-originality]] — **first independent second voice**: Samwer's clone, app studios that forbid inventing, the data founder copying 10 LLM-data playbooks
+- [[sales-discipline]] — "since 2016, no revenue" red flag converges with Rodenko's "a year of repackaging is for people afraid to pick up the phone"; welcome bad news early
+- [[unit-economics]] — Zavent: post-payment = financing your customers (a forgotten cost line made vivid); CAC-burn barrier restated
+- [[sales-channel-as-moat]] — within-author consistency on the CAC entry barrier
+- [[oskar-hartmann]] — second source; framework stability
+- [[eugene]] — the checklist is directly runnable against his CV/embedded offer
+
+## Open Questions
+
+- **Ethics/legality of the deception-based tests are never addressed.** Fake payment screens ("error, payment failed") and fake-door buttons collect purchase intent under false pretenses — consumer-protection exposure varies by jurisdiction, and the reputational cost of a discovered fake is unmodeled. The vault records the mechanics without endorsing them; the honest variants (visible pre-order, paid waitlist, manual MVP) carry most of the same signal.
+- **"Build.ai" is almost certainly Builder.ai** (general knowledge, not from the source): the widely reported case matching the description — and that company **collapsed into insolvency in 2025 amid allegations its AI was largely manual work and its revenue overstated**. The source cites it as a quasi-positive "great way to start," which undercuts the example: the same case is also the cautionary tale for *never graduating* from Wizard-of-Oz (and for misrepresenting it to investors — the part Hartmann's framing skips).
+- All figures are war-story grade: 5,000 recipients / <5 replies, <$1K per app test, 100K preorders, $5M prepaid, $80–100 CAC, 3–5× one-word conversion swings — attributable, unverified.
+- The traffic-arbitrage recommendation sits oddly with the vault's services domain — a services operator can't A/B a payment screen as cheaply; the transferable core is "smallest paid test," not the mechanism.
+- Tension worth watching: "don't dictate what the customer should want" vs the vault's [[outcome-based-selling]]/[[technical-founder-trap]] thread, where articulating an outcome the buyer couldn't name *is* the value-add. Likely scoped (product demand vs service framing), unstated.
+
+## Change Impact on Wiki
+
+- Created [[sell-before-build]] (concept).
+- Updated [[productized-service]] (pre-sell now three traditions), [[pain-discovery]] (acute-pain test), [[cloning-over-originality]] (first independent second voice; status upgraded), [[sales-discipline]] (duration-without-revenue red flag convergence), [[unit-economics]] (Zavent post-pay trap; CAC-burn consistency), [[sales-channel-as-moat]] (consistency note), [[oskar-hartmann]] (second source), [[eugene]] (runnable checklist), [[overview]], [[index]], [[log]].

wiki/sources/2026-07-29-start-a-business-with-claude-code.md

@@ -0,0 +1,56 @@
+# Start a Business with Claude Code
+
+#source #validation #gtm #ai
+
+## Source Metadata
+
+- Date: undated (ingested 2026-07-29)
+- Raw path: `raw/sources/Start a business with Claude Code.md` (conclusions note; root: https://youtube.com/shorts/JpLgVf8Alys — "Stop pretending not to know how to start a business with Claude Code", 0:42)
+- Source type: US short-form video (YouTube Short); author **[[dan-martell|Dan Martell]]** — confirmed by the vault owner 2026-07-29 (the clip itself names no speaker); **fifth confirmed Martell source**
+- Ingestion date: 2026-07-29 (attributed same day)
+- Evidence grade: **the vault's shortest and thinnest source** — 42 seconds, no cases, no figures. Pure prescription; its value is compression: the Martell $0 protocol reduced to short-form, with [[claude-code]] as the executor.
+
+## Core Claims
+
+1. **Sell first, build second.** To go $0 → $1M with AI: use [[claude-code|Claude Code]] to stand up the *appearance* of a business, close paying customers via cold outbound, and only then have Claude build the product. Demand is validated with money before engineering effort is spent ([[sell-before-build]]).
+2. **The 5-step playbook:** (1) pick a service to sell (anything — video editing, AI automation); (2) Claude Code builds a landing page, invents a company name, wires a waitlist; (3) Claude Code scrapes the web for prospect contacts; (4) Claude Code writes the cold-outbound script for that ICP; (5) you email/call, book, close — *then* ask Claude to build the product.
+3. **Claude Code as the entire GTM stack**, not just the build engine: landing page, company identity, lead list, sales copy, and finally the product. The human's residual jobs are choosing the service and doing the close.
+4. **AI collapses the "I don't know how" excuse.** "Whatever business you want to be in, Claude will also tell you how to do it" — domain knowledge on demand; pre-existing expertise not required ([[ai-market-shift]]).
+5. **Distribution is the moat, not code.** Landing page + outbound = go-to-market; the product is the *last* step ([[sales-channel-as-moat]]).
+6. **The blocker is psychological, not technical.** "Stop pretending not to know"; the gap between aspiring founder and founder "is one cold email away" ([[sales-discipline]]).
+
+## Key Evidence / Details
+
+- No evidence in the vault's sense is offered — no case, no number, no cohort. Every claim is asserted.
+- Stated audience: aspiring solo founders sitting on ideas; **developers who over-invest in building and under-invest in selling** ([[technical-founder-trap]]); anyone using "no industry experience" as a reason not to start.
+- Step 5 ("ask it to build it for you") is flagged by the source itself as the step people underestimate — i.e. the capability claim is load-bearing, and it is exactly the claim [[ai-productivity-evidence]] contests at the expert end (though the leveler claim targets *novices in a domain*, the segment the evidence says gains most).
+- The internal waitlist (step 2) is **unpaid** — by the vault's own bar ([[sell-before-build]]: unpaid lists don't count) it is not the validation event. The playbook's actual validation event is the **closed sale** in step 5, which sits *above* mere payment in the signal hierarchy. The playbook passes the vault's money bar, just not where it appears to.
+
+## Connections
+
+- [[dan-martell]] — fifth confirmed source; every claim here restates his corpus (marketing-before-building, $0 cold outbound, AI-built lists), now compressed to 42 seconds
+- [[sell-before-build]] — the rule restated in AI-era compression; **within-author restatement**, not a fourth voice (Martell already counts among the rule's three traditions)
+- [[sales-channel-as-moat]] — "distribution is the moat, not code": Martell stating the priority claim; folds into his existing marketing-system convergence on that page (no mechanics added)
+- [[ai-market-shift]] — new role for AI: the **leveler** (domain knowledge on demand) — his first claim in that page's roles table
+- [[client-acquisition-channels]] — the $0 cold-outbound prescription, same author as the $0 blueprint it matches; framework stability, not a second voice
+- [[technical-founder-trap]] — the stated audience is that page's patient, build-instead-of-sell form; same author as the page's founding source, so restatement not corroboration
+- [[sales-discipline]] — bias to action; launch-ugly kinship
+- [[claude-code]] — the tool itself, now an entity
+- [[eugene]] — contrast case: his 90-day plan reaches the same sell-first conclusion but replaces the fake-company front with a paid diagnostic ([[2026-07-26-eugene-90-day-plan]])
+
+## Open Questions
+
+- ✅ ~~**Who is the author?**~~ — **[[dan-martell|Dan Martell]]**, confirmed by the vault owner 2026-07-29. His 5th confirmed source (possibly 7 of 20 with the two still-suspected). Consequence: every echo this source lent — sell-first, distribution-over-code, $0 cold outbound, the build-over-sell audience — is **within-author self-agreement**. The echo-grade discipline held: no page had granted it independence weight, so the attribution changed labels, not conclusions. Two within-author drifts logged on [[dan-martell]]: unpaid waitlist (vs his own $50 *paid* rule) and the invented-company front.
+- **Ethics/legality of the front.** An invented company name + landing page + waitlist before any capability exists is the deception-based end of the [[sell-before-build]] toolkit (kin to fake payment screens); web-scraped contact lists + cold email carry GDPR/CAN-SPAM exposure in the EU/US. The source models neither cost.
+- Does "Claude will tell you how" survive contact with regulated or physical domains (the vault owner's industrial CV niche), or only with commodity digital services like the source's own examples?
+
+## Change Impact on Wiki
+
+- Created this page and [[claude-code]] (first tool entity).
+- [[sell-before-build]]: fourth-voice echo recorded; the compressed services variant (close via outbound before building) and the fake-front caveat added.
+- [[ai-market-shift]]: **Leveler** row added to the roles table, with the novice-tilt synthesis.
+- [[client-acquisition-channels]]: second $0-stage cold-outbound voice noted under the Martell $0 protocol.
+- [[sales-channel-as-moat]]: slogan-grade second voice recorded in Evidence; status unchanged.
+- [[technical-founder-trap]]: audience-targeting bullet added to Evidence.
+- [[overview]]: source count 19 → 20; navigation updated.
+- **Attribution update (2026-07-29, same day):** owner confirmed Dan Martell as author. [[dan-martell]] updated to five confirmed sources (fifth-source positions block, within-author drifts); the echo/self-agreement relabel propagated to [[sell-before-build]], [[client-acquisition-channels]], [[sales-channel-as-moat]], [[technical-founder-trap]], [[ai-market-shift]], [[claude-code]]; [[index]] and [[overview]] denominators refreshed to 5-possibly-7 of 20.