all

wiki/concepts/ai-market-shift.md

@@ -0,0 +1,74 @@
+# AI Market Shift
+
+#concept #ai #positioning
+
+## Summary
+
+AI is simultaneously the thing that destroys the hourly service model, the tool that removes the cost of building offers, and — least obviously — an instrument for qualifying buyers. The sources treat AI as a market restructuring rather than a product category. This page is the **market-side** view; its labor-side twin — how AI restructures teams, roles, and careers — is [[future-of-engineering-work]].
+
+## Current Understanding
+
+**Three distinct roles, worth keeping separate:**
+
+| Role | Claim | Source |
+|---|---|---|
+| **Substitute** | The buyer has a ~$200/mo AI alternative → competing on rate zeroes margin; hourly development is dead | [[2026-06-15-rodenko-selling-development-expensively]] |
+| **Complement** | For every $1 spent on AI, a company spends ~$6 on specialists to configure it — AI opens a new funnel rather than taking work | [[2026-06-15-rodenko-selling-development-expensively]] |
+| **Tool** | AI does the deck-and-doc drudgery; the leverage that used to require a paid coach is now free | [[2026-07-17-design-the-perfect-offer]] |
+| **Filter** | Give a working AI skill away free 30 days; the reaction qualifies the buyer (below) | [[2026-06-15-rodenko-selling-development-expensively]] |
+| **Leveler** | Domain knowledge on demand — "whatever business you want to be in, Claude will also tell you how to do it"; collapses the no-expertise barrier to *entering* a market | [[2026-07-29-start-a-business-with-claude-code]] |
+
+The substitute and complement claims sit together coherently: AI eats undifferentiated execution and creates demand for the judgment that directs it. That is the whole strategic argument of this vault in one line — and it is why [[niche-selection]] says go where AI is weak and [[productized-service]] says stop selling execution.
+
+**AI as a qualification filter** — origin [[2026-06-15-rodenko-selling-development-expensively]] (a founder gives a free AI-skill on call one; of 10 calls, 5 return, 1 closes a $100k project). Don't hide the AI; weaponize it. Give a working AI skill away free for 30 days and read the reaction:
+
+| Reaction | Meaning |
+|---|---|
+| "It works" | Your value isn't needed. **Not a client.** |
+| "We never got to it" | The task has no budget. **Not a client.** |
+| "Weak, needs specifics" | **Target client.** |
+
+This inverts the usual anxiety. The fear is that AI reveals your work to be replaceable; the filter accepts that for some buyers it *is*, and uses the giveaway to find the buyers for whom it isn't — cheaply, before you've spent a sales cycle on them. It also does [[pain-discovery]]'s job: the "needs specifics" answer *is* the specification.
+
+**The demand-side sequel: if products are cheap, attention and distribution are the scarcities** ([[2026-07-26-how-to-build-a-billion-dollar-company-2027]], [[oskar-hartmann]], added 2026-07-26). In the vibe-coding era "everyone has 10–15 great products sitting in Cloud Code," so the differentiator moves from building to **distribution** ([[sales-channel-as-moat]]) — the same execution-is-commodity premise the RU sources state for services, restated for products by a third tradition. AI also *amplifies the noise it created*: 2,000 unread LinkedIn messages ("agents mail for everyone"), every channel saturated, attention "the most expensive resource on the planet" — which quietly strengthens [[relationships-as-moat]]'s case that AI-floodable channels devalue first (he independently notes offline events becoming *more* economical). And on the capital side, the same shift concentrates money: Anthropic/OpenAI's ~$4B private-equity joint ventures are a classic **land grab** (install the technology into hundreds of thousands of portfolio companies through every channel at once), while the top labs "suck nearly all free cash" out of the venture market — for everyone else, venture effectively closes ([[venture-fit]]).
+
+**The leveler role, and an odd alliance with the adversarial evidence** (added 2026-07-29). The claim ([[2026-07-29-start-a-business-with-claude-code]], a 42s [[dan-martell]] short — attributed same day; slogan-grade, and his first claim in this page's table) is that AI removes "I don't have experience in that industry" as a barrier to starting. Note the geometry against [[ai-productivity-evidence]]: the measured gains are **novice-tilted** — which cuts *against* the expert-productivity hype but mildly *for* this role, since a founder entering a new domain is exactly a novice in it. The same evidence still contests the short's step 5 ("then ask Claude to build the product"). Unresolved whether the leveler holds outside commodity digital services (regulated/physical domains).
+
+**What's scarce now.** Not the ability to produce the artifact, but knowing which questions to feed the tool ([[2026-07-17-design-the-perfect-offer]]). Corroborating detail: the AI's offer recommendation (workflow + dashboard + agent) independently matched the human coach's best-practice structure — the tool is a legitimate co-designer, not a novelty.
+
+## Evidence
+
+- **Primary:** ~$200/mo substitute; $1:$6 AI-to-specialist spend ("AI sells servicing, not product"); the free-30-day AI-skill filter with the $100k close; "narrow niche = where AI is powerless" — [[2026-06-15-rodenko-selling-development-expensively]]
+- The $1:$6 ratio also appears in [[2026-06-15-making-money-with-ai-2026]] and via the meta-analysis; solo-founder revenue figures (Rezi $293k/mo) there feed the "team size no longer signals seriousness" thread
+- Labor-side of the same shift: coding cost → 0, "the game is how you use it" — [[2026-07-06-sebastian-interview-ai-and-software-engineering]]
+- **Counter-evidence (adversarial):** AI's measured effect is modest and often negative for experts, trust is low/falling — the substitute premise is weaker than claimed — [[ai-productivity-evidence]] / [[2026-07-18-ai-productivity-adversarial-evidence]]
+- Condensed restatement — [[2026-06-15-selling-development-services-in-the-ai-era]]
+- Vibe-coding product glut ("10–15 products in Cloud Code"); AI noise (2,000 LinkedIn messages); attention as scarcest resource; the ~$4B PE land grab; capital suction — [[2026-07-26-how-to-build-a-billion-dollar-company-2027]] ([[oskar-hartmann]]) — note the product-glut claim shares the commoditization premise [[ai-productivity-evidence]] contests
+- "AI does the deck-and-doc drudgery — the leverage that used to require hiring a coach is now free. What's scarce is knowing which questions to feed it." — [[2026-07-17-design-the-perfect-offer]]
+- "The AI-generated recommendation matched the actual best-practice structure — the tool is a legitimate co-designer." — [[2026-07-17-design-the-perfect-offer]]
+- Leveler role ("Claude will also tell you how to do it"; AI as full GTM stack) — [[2026-07-29-start-a-business-with-claude-code]] ([[dan-martell]], no evidence offered; see [[claude-code]])
+
+## Related Pages
+
+- [[future-of-engineering-work]] — the labor-side twin of this page
+- [[niche-selection]] — AI weakness defines where the defensible niche is
+- [[productized-service]] — the substitution pressure is the argument for productizing
+- [[pain-discovery]] — the free-giveaway filter doubles as discovery
+- [[pricing-from-value]] — a $200/mo substitute is the floor rate competition collapses toward
+- [[ai-productivity-evidence]] — the empirical test of whether AI is the substitute this page assumes
+- [[claude-code]] — the named tool behind the leveler and build-engine roles
+- [[overview]]
+
+## Contradictions / Uncertainty
+
+- **The $1:$6 ratio is now attributable but still uncited at root.** It appears in Rodenko and the make-money-AI video, but neither gives a primary source — it reads like an analyst statistic repeated between creators. `Status: tentative` — do not quote as fact.
+- **The ~$200/mo substitute is asserted, not demonstrated.** Whether it genuinely substitutes for a dev contract or only for its commodity floor is exactly the question that decides how much of this vault's advice applies — and no source tests it. [[2026-07-06-sebastian-interview-ai-and-software-engineering]] complicates it: at the enterprise scale the substitute isn't even installable (locked-down VMs), so "the buyer has a $200/mo alternative" may hold for SMB and not for regulated enterprise.
+  - **Update (2026-07-18) — empirical evidence now tests this, and it tilts toward *complement*, not *substitute*.** [[ai-productivity-evidence]] (via the vault's first adversarial source, [[2026-07-18-ai-productivity-adversarial-evidence]]) finds AI's measured productivity effect is modest (≈14–19% average) and, for experienced developers on familiar code, *negative* (METR RCT: −19%), with only ~3% of developers highly trusting AI output and ~46% distrusting it. A tool that slows experts and that most developers distrust is not obviously a drop-in replacement for a developer — it substantiates the doubt this bullet already raised, and lends weight to the **complement** row of the table above ($1:$6) over the **substitute** row. Caveats: the evidence is early-2025-scoped and novice-tilted, so it bites hardest on the *high* end (experts) and says least about the commodity floor the substitute claim targets.
+- **"Go where AI is powerless" assumes a static frontier.** The sources are dated mid-2026 and mostly ignore that today's AI-weak niche may not be next year's — the one concrete durable example (COBOL, no training data) is in the Sebastian interview, not the sales sources.
+- The 30-day giveaway filter has an unexamined cost: giving the skill away to the "it works" segment means handing your product to non-clients for free. Whether that's a real loss depends on whether they'd ever have paid — plausibly not, which is the point.
+
+## Next Questions
+
+- What's the source of the $1:$6 figure, and does it hold outside enterprise?
+- How fast is the AI-weak frontier actually moving in the user's target niche?
+- What is the smallest useful "AI skill" that can be given away in the 30-day filter without giving away the method?

wiki/concepts/ai-productivity-evidence.md

@@ -0,0 +1,50 @@
+# AI Productivity — Measured vs. Claimed
+
+#concept #ai #evidence
+
+## Summary
+
+The empirical counterweight to the vault's dominant premise. Where the vault's promotional sources (twelve at this page's creation; nineteen of twenty as of 2026-07-29) *assert* AI has zeroed the cost of commodity software work, the rigorous evidence (RCTs, a top-5-journal field study, large surveys) shows the real effect is **modest (≈14–19%), context-dependent, tilted toward NOVICES not experts, and systematically overstated by self-report.** It **qualifies rather than demolishes** the thesis — no study finds AI worthless — but it directly inverts two load-bearing claims and is the vault's first source with evidentiary standing rather than sales incentive. Anchored entirely by [[2026-07-18-ai-productivity-adversarial-evidence]]; single-source, so `Status: tentative`, but its inputs are the highest-provenance in the vault.
+
+## Current Understanding
+
+**Two direct inversions of the popular thesis:**
+
+1. **"AI zeroed the cost of skilled dev work"** → the strongest *developer-specific* RCT (METR, 2025) found 16 experienced open-source maintainers were **19% *slower*** completing real tasks on their own repos with early-2025 AI. The cost didn't go to zero; for experts on familiar code it went *up*.
+2. **"Seniors up, juniors irrelevant"** ([[seniority-and-ai]]) → the best skill-distribution study (Brynjolfsson, Li & Raymond, *QJE* 2025) found the **least-experienced gain most** (+34% vs. ~0 and small quality *declines* for experts). A GitHub Copilot RCT independently found less-experienced developers benefit more. AI's productivity dividend accrues to novices, not seniors.
+
+**The perception trap (why the hype is self-sustaining).** METR's developers forecast a 24% speedup, *still* estimated +20% after finishing, and were measured −19% — a ~39-point gap between felt and real. This matters because "it feels faster / I shipped more" is the exact evidence most promotional AI-productivity claims are built on. Self-report is not measurement.
+
+**Individual speed ≠ shipped software.** DORA 2024 found AI adoption correlated with *reduced* delivery stability (and, that year, throughput — reversed in DORA 2025). Stack Overflow 2025 (~49k devs): only ~3% "highly trust" AI accuracy while ~46% distrust it (up from 31%), even as adoption hit 84%; ~45% say debugging AI code is time-consuming. The artifact isn't finished when it's generated.
+
+**The honest reading.** Held to the same standard as the promotional sources, this evidence does **not** prove AI is worthless — average effects are positive (14–15%). It proves the effect is *smaller, unevenly distributed, and easier to overstate* than "cost → zero" implies. The vault's strategic advice can survive a modest, novice-tilted AI; it cannot survive on the premise that AI is a full substitute for a developer.
+
+**⚠ Time-scope.** All figures are 2023–2025, tied to specific tool generations. METR labels its result "historical"; the Copilot RCT used 2022 Copilot; DORA reversed a 2024 finding in 2025. This is **not** the live 2026 state of the art — it is a corrective against extrapolating hype, not a prediction.
+
+## Evidence
+
+- Whole concept (all six findings, effect sizes, designs, caveats, and the two refuted claims) — [[2026-07-18-ai-productivity-adversarial-evidence]]
+- Primary roots cited there: METR RCT (arXiv:2507.09089); Brynjolfsson/Li/Raymond *QJE* 140(2) 2025 (NBER w31161) — **customer-support agents, not devs** (scope caveat); GitHub Copilot RCT (arXiv:2302.06590); DORA 2024; Stack Overflow 2025 Developer Survey
+
+## Related Pages
+
+- [[ai-market-shift]] — the claim this most directly tests (is a $200/mo AI a real *substitute*?)
+- [[seniority-and-ai]] — the claim this most directly *inverts* (novices gain most)
+- [[future-of-engineering-work]] — "coding cost → 0 / teams collapse" qualified by modest, uneven effects
+- [[2026-07-06-sebastian-interview-ai-and-software-engineering]] — the vault's strongest statement of the thesis this counterbalances
+- [[overview]]
+
+## Contradictions / Uncertainty
+
+- **Scope mismatch on the strongest skill result.** The +34%-novice finding is customer-support agents, not developers — directional counter-evidence, not same-population proof about coding. The developer-specific studies (METR, Copilot) point the same way, which is what keeps it credible.
+- **Speed, not labor-market value.** Every finding measures task speed/productivity; the "juniors irrelevant" thesis is about wages, hiring, and headcount, which no source here measures. So this inverts the *productivity* claim without settling the *employment* claim — and the "experts see small quality declines / juniors lack judgment to catch AI errors" mechanism actually lends partial support to [[seniority-and-ai]]'s risk argument.
+- **Small samples / significance.** METR n=16 (significant across 246 tasks, but a narrow population); the Copilot RCT's key experience coefficient is not significant at 0.05.
+- **Time-sensitivity is the biggest limit** (above). Treat every number as a dated snapshot.
+- **This source has its own incentives too:** GitHub/Microsoft authored the pro-Copilot RCT (COI); Stack Overflow has a mild interest in AI skepticism; DORA/Google is independent. Held to the vault's usual standard.
+
+## Next Questions
+
+- Does METR's −19% persist, vanish, or reverse on **mid-2026 agentic tools**? A properly powered follow-up RCT is the key missing piece — and would decide how much of this page survives.
+- Does "novices gain most" hold on **real, complex** codebases, or invert where juniors can't catch AI's errors?
+- Given this, should [[ai-market-shift]]'s "$200/mo substitute" and [[dmitry-rodenko]]'s "hourly dev is dead" carry a stronger `Status: contested`?
+- What would a *pro-thesis* rigorous source look like — is there RCT-grade evidence that AI **does** zero the cost for some real dev segment (greenfield, juniors, specific stacks)?

wiki/concepts/client-acquisition-channels.md

@@ -0,0 +1,97 @@
+# Client Acquisition Channels
+
+#concept #outbound #sales
+
+## Summary
+
+Where to find clients, as distinct from how to work a channel once you're in it (that's [[sales-discipline]]). The vault holds **five** maps of this territory: a detailed 17-channel taxonomy (AB Analytics), a 3-step niche→outbound→social motion (Tony), a flat rejection of *all* online channels in favor of in-person (Sebastian), a three-lever scaling map ([[dan-martell]]), and a ranking by attention economics ([[oskar-hartmann]]). These do not agree, and the disagreement is the most consequential open question in the vault for anyone deciding where to spend time.
+
+## Current Understanding
+
+**The taxonomy** ([[2026-06-15-17-ways-first-client]]) — three tiers, and the rule to pick one from each and run all three for 90 days:
+
+| Tier | Character | Examples |
+|---|---|---|
+| Common | Crowded; a floor, don't stay | Freelance platforms, LinkedIn outreach, content marketing, cold email, [[referrals]] |
+| Low-key | Less competition, better clients | Chamber of Commerce, BNI/service clubs, industry associations, high-end hotels, car shows, local conferences, golf, premium gyms/country clubs |
+| Out-of-the-box | Highest effort/reward | Strategic partnerships, productized services, in-person workshops, case-study→webinar funnel |
+
+**Tony's motion** ([[2026-06-15-more-clients-dev-agency]]): **niche → outbound → social**. Niche is the precondition (no ICP → can't outbound). Outbound posture is either high-touch/low-volume (podcasts, roundtables, lunches) or high-volume/low-touch (LinkedIn, cold email). Social presence (~3 posts/wk on LinkedIn) is a **trust layer** that "greases the wheels" of outbound rather than generating direct leads.
+
+**Four positions on online content/outreach — arranged from most to least bullish:**
+
+| Position | Source | Claim |
+|---|---|---|
+| **Content *is* the engine** | [[2026-07-18-information-is-free-implementation-is-paid]] ([[dan-martell]], near-certain) | Give away the whole playbook as *scrambled* free content — it's the primary lead source *and* the price anchor; you charge for implementation + sequencing, not information |
+| **Content is the engine *and* the prerequisite for paid** | [[2026-07-20-referrals-will-sink-your-business]] ([[dan-martell]]) | "The new paid is organic" — pick content, attack it 90 days, then promote the organic pieces that already worked as ads. Publishing is also *practice at explaining* ([[technical-founder-trap]]) |
+| Use it, layered | Tony | Post 3×/wk from the start as a trust layer under outbound |
+| Delay it | AB Analytics | Don't start content until $10–15k/mo from outbound, or you starve; but online outreach (LinkedIn, cold email) is a live channel now |
+| **Abandon it** | [[sebastian]] | Sales agencies, cold calling, email, LinkedIn campaigns, content, SEO = "Big zero"; only in-person builds the trust that closes |
+
+The spread on the *organic-content* channel specifically is now the vault's widest: from "it is the entire lead engine" ([[information-vs-implementation]]) to "Big zero" ([[sebastian]]). The two are not necessarily incompatible — they plausibly describe different buyers (short-form-feed prosumers/SMB vs. locked-down enterprise) — but no source tests it. **Correction (lint 2026-07-29):** this paragraph previously read the content pole as having "gained a second voice." It has not. All four content-pole sources are [[dan-martell]] (07-18 near-certain, 07-20/07-23/07-29 confirmed), so the head-count never moved — it is **one coaching corpus against [[sebastian]]'s one interview**, neither with conversion data.
+
+**A second, competing taxonomy — the three levers** ([[2026-07-20-referrals-will-sink-your-business]]). Where AB Analytics maps 17 channels in three tiers, [[dan-martell]] claims there are **exactly three ways** to make people aware of you — **publish content, paid ads, partnerships** — and that you must **pick one and commit for 90 days**. Two things about it are worth recording precisely:
+
+- **What it omits is the argument.** Outbound and [[referrals]] are absent — not rated low, simply not counted as growth levers. The levers are *scalable* demand motions; the vault's entire first-client apparatus (warm intros, cold email, Chamber of Commerce, in-person events) is **one-to-one**. So this is not a rival map of the same territory: it is a map of *scalable demand generation*, addressed to a founder who already has clients and a stalled $1.5M. *(Qualified 2026-07-22: the original "all three are one-to-many" reading overstated it — the partnerships lever is one-to-few-to-many, and its partner-recruiting layer is one-to-one relational work. See [[partnerships]].)*
+- **The reconciliation the vault infers** (no source states it): one-to-one channels get you clients #1–#N; a [[marketing-system]] is what stops #N from being the ceiling. Under that reading, the three-lever map doesn't displace the 17-channel map — it succeeds it by stage.
+- **The third lever now has a mechanism** ([[2026-07-22-stop-cold-calling-do-this-instead]]): partnerships = **borrowed credibility** — a partner who already holds the buyer's trust walks you in pre-sold; scale it by reverse-engineering and recruiting the partner *archetype*, not by optimizing individual deals. Detail on [[partnerships]]. Same author as the taxonomy itself, so the map is now two-sources deep but still one voice.
+
+**A counter-position on cold outbound** (same source): cold-calling into enterprise is "the hardest path" — procurement friction, meeting access, org churn — and partners are the shortcut. This lands on the channel [[2026-06-15-more-clients-dev-agency|Tony]] and [[ab-analytics]] run as live (cold email, LinkedIn outreach). Two things keep it from being a flat contradiction: it is **scoped to enterprise** (the source itself limits the claim to ~$10K+ ACV relationship-driven deals), and the playbook still involves approaching strangers — outbound *redirected at partners*, not abolished. Notable convergence: [[dan-martell]] and [[sebastian]] — the vault's opposite poles on content — **agree that cold outreach doesn't open enterprise doors**, and both prescribe trust-mediated entry instead; they differ only on whose trust (borrowed via a partner vs. built in person). That is the strongest support yet for the audience-dependent reconciliation below.
+
+**Direct conflict on channel count.** [[ab-analytics]]: pick **3** channels, run 90 days. [[dan-martell]]: pick **1** lever, run 90 days. Same time unit, opposite N, and *both* present their rule as the anti-dabbling discipline. See Contradictions.
+
+**The same author's $0 protocol runs two engines in parallel** ([[2026-07-23-make-my-first-100k-in-month]], added 2026-07-23). Addressed to a founder at zero, Martell prescribes **inbound and outbound simultaneously** — inbound (give-everything-away content) as the long-term engine, outbound as this week's cash: mine phone contacts → **"ask past the person"** ("do you know anyone with this problem?" — often lands on "yeah, me") → referral-name openers → AI-built list of 100 as backfill → close by chat-DM or **cold call** (job: qualify + book, never sell; 100 no's/day). Three things follow for this page: (1) outbound — absent from his three-lever map — is fully present at $0, which **supports the vault's stage reading** (the lever map is a scaling protocol, not a starting one); (2) "run both in parallel" sits against his own "pick one lever" with no stated boundary — a within-author tension logged on [[dan-martell]]; (3) the man who titled a clip "stop cold calling" **teaches cold calling here** (worked example: AI voice agents for local businesses) — which all but confirms the enterprise-vs-SMB scoping of the anti-cold-outbound position below.
+
+**The $0 protocol, compressed to short-form** ([[2026-07-29-start-a-business-with-claude-code]], added 2026-07-29; owner-attributed to [[dan-martell]] same day — his 5th confirmed source): AI-scraped prospect lists + AI-written cold email/call scripts as the *entire* first channel for a new service — landing page and outbound before any product exists. What looked like an independent match to his $0 blueprint (AI-built list of 100, cold outreach at the start) turned out to be **the same author restating himself** — framework stability, zero corroboration. It does still tighten one thing from inside his corpus: cold outbound appears at the $0/SMB end *in every format he publishes*, never at enterprise — the stage/segment scoping is not a one-clip artifact. Compliance caveat (scraped lists vs GDPR/CAN-SPAM) on the source page.
+
+**A third taxonomy — channels ranked by attention economics** ([[2026-07-26-how-to-build-a-billion-dollar-company-2027]], [[oskar-hartmann]], added 2026-07-26). Attention is "the most expensive resource on the planet" (12h screen time, ~40 GB/day per head; AI made every channel noisier — 2,000 unread LinkedIn messages, agents mailing for everyone). His hierarchy: **search ads** (intent already expressed) → **banner/Meta** (interruption, pricier per result) → **offline events** (returning — companies now find offline *more* economical) → **TV/Super Bowl** (~$10M/30s, untargeted, yet claimed to beat much targeted spend). Two upshots for this page: (1) *"the average product that shouts displaces the better product that stays silent"* — an independent, brutal restatement of why channel choice can't be skipped; (2) the AI-noise claim strengthens the in-person pole's hand — the channels Sebastian rated "Big zero" are exactly the ones AI floods first, and Hartmann independently notes offline events *returning*. His channel-quality bar for what counts at all: **repeatable with predictable acquisition cost** — one-off spikes and single partner deals are boosts, not channels ([[sales-channel-as-moat]]).
+
+**A counter-position on whale-first clients** (same source): landing giants early is a trap for a small operator — Pediant sold Walmart and Best Buy, integration dragged 1.5 years, the champion manager left, the successor wouldn't own the decision, the deal restarted/died; for the corporation that's "next investment committee," for the startup it's the wall. The mechanism (long cycles vs. short runway; org churn outliving the deal) is scoped to product startups burning capital, but the org-churn half applies to any long enterprise cycle — a caveat sitting directly under the [[partnerships]] enterprise-entry route and [[sebastian]]'s enterprise thesis. Services deals are smaller and faster than platform integrations, so the transfer is partial; recorded, not resolved.
+
+**And a third position on channel count** (same source): one repeatable channel first (FlatPay built a billion-dollar company on door-to-door alone), but **"one channel = concentration risk — a resilient system is multichannel"**, with the AI land-grab (Anthropic/OpenAI ~$4B PE joint ventures) running *all* channels at once as the scaled exemplar. That is: **1 → then many**, by stage — which happens to be exactly the reconciliation the vault had already inferred for pick-1-vs-pick-3, now stated (almost) by a source. See Contradictions.
+
+**Where they *agree*** — and this is easy to miss: AB Analytics' entire Tier 2 (Chamber, associations, hotels, car shows, gyms, country clubs) is **in-person**, and its most-underrated pick is the Chamber of Commerce. So AB Analytics and Sebastian both rate in-person relationship channels as the high-value ground. They differ on whether online channels are *worthless* (Sebastian) or *a legitimate lower tier* (AB Analytics). The likely reconciliation is **audience**: Sebastian sells to large regulated enterprises where trust is everything and buyers ignore cold outreach; AB Analytics and Tony target SMBs/startups where online outreach still converts. See Contradictions.
+
+**Cross-links to the offer side:** channels only work after [[niche-selection]] (Tony: niche is upstream of everything), and "productize services" appears as both a channel (AB Analytics Tier 3) and the delivery model ([[productized-service]]).
+
+## Evidence
+
+- 17-channel three-tier taxonomy; pick-3-run-90-days; Chamber of Commerce as most underrated — [[2026-06-15-17-ways-first-client]]
+- niche→outbound→social; high-touch vs high-volume; social as trust layer — [[2026-06-15-more-clients-dev-agency]]
+- "Sales agencies, cold calling, email marketing, LinkedIn campaigns, content, SEO. Zero. Big zero." — [[2026-07-06-sebastian-interview-ai-and-software-engineering]]
+- Content-as-primary-engine (scramble strategy, 5×10×4 factory) — [[2026-07-18-information-is-free-implementation-is-paid]], detailed on [[information-vs-implementation]]
+- Content-timing conflict (Tony vs AB Analytics), surfaced by [[2026-06-15-meta-analysis-selling-dev-in-ai-era]]
+- Three-lever taxonomy, pick-one/90-days, "the new paid is organic", referral dependency as a ceiling — [[2026-07-20-referrals-will-sink-your-business]], detailed on [[marketing-system]]
+- Partnerships mechanism (borrowed credibility, partner-archetype recruiting); cold enterprise outbound as the hardest path — [[2026-07-22-stop-cold-calling-do-this-instead]], detailed on [[partnerships]]
+- Parallel inbound+outbound at $0; the phone-mining ladder ("ask past the person"); SMB cold-call script — [[2026-07-23-make-my-first-100k-in-month]] ([[dan-martell]])
+- Attention-economics hierarchy; "average loud beats better silent"; whale-client trap (Pediant); one-repeatable-channel-then-multichannel; offline events returning — [[2026-07-26-how-to-build-a-billion-dollar-company-2027]] ([[oskar-hartmann]], independent tradition)
+- Cold outbound as the entire $0 channel, AI-executed (scraped list, generated script) — [[2026-07-29-start-a-business-with-claude-code]] ([[dan-martell]], 5th confirmed; within-author restatement, slogan-grade)
+- The concrete first-touch tool: [[2026-06-15-linkedin-mail-template]]
+
+## Related Pages
+
+- [[sales-discipline]] — how to work a channel (cadence, follow-up) once chosen
+- [[referrals]] — the highest-converting channel in the taxonomy, detailed (and why it can neither bootstrap client #1 nor scale past a ceiling)
+- [[marketing-system]] — whether the channels add up to a machine you can turn up; the three-lever map lives there
+- [[partnerships]] — the third lever's mechanism; the borrowed-credibility enterprise entry
+- [[relationships-as-moat]] — why the in-person channels may dominate as AI floods online
+- [[information-vs-implementation]] — the organic-content channel worked out in full (give away know-how, sell sequencing)
+- [[niche-selection]] — the precondition for any channel
+- [[productized-service]] — both a Tier-3 channel and the delivery model
+- [[sales-channel-as-moat]] — what a channel is *for* at the company level: the repeatable machine as the defensible asset
+- [[overview]]
+
+## Contradictions / Uncertainty
+
+- **Online vs in-person is unresolved and high-stakes.** `Status: tentative`. Best current reconciliation: it's an **audience** difference (enterprise → in-person only; SMB/startup → online still works), not a universal law. But no source tests this directly; Sebastian states his "Big zero" as general. [[2026-07-18-information-is-free-implementation-is-paid]] widens the gap to its extreme — content as the *entire* engine — without adding evidence, so the reconciliation still rests on inference, not data.
+- **Content-marketing timing is a three-way split.** Tony (start now, *as a trust layer under outbound*) vs AB Analytics (wait until $10–15k/mo, or content starves you) vs [[information-vs-implementation]] (start now, *as the primary lead engine*). The meta-analysis reconciled the first two as trust-layer vs primary-channel; the third source rejects that framing outright by making content the channel. The "audience-dependent" escape is weaker here than for the Sebastian split, because all three are US SMB-oriented coaching sources — so this is a genuine strategy disagreement, not obviously a buyer-type difference. Untested.
+- **Pick one channel or pick three?** [[dan-martell]] (one lever, 90 days) vs [[ab-analytics]] (three channels, 90 days). `Status: tentative`. Best available reconciliation — untested and inferred, not stated by either — is that they name different units: a *lever* is a broad discipline (content spans reels, lives, shorts, posts), a *channel* is a specific venue, so "one lever" may contain three "channels". If that's wrong, one of the two rules is simply mistaken, and both are asserted with equal confidence and equal absence of data. **Complication (2026-07-23):** Martell's own $0 blueprint runs inbound *and* outbound in parallel — two motions at once, from the man prescribing one. Either the pick-one rule is stage-scoped (scale only) or it isn't a rule; his corpus never says. **Third voice (2026-07-26):** [[oskar-hartmann]] holds *both ends explicitly* — one repeatable channel builds the company (FlatPay: door-to-door only), multichannel makes it resilient at scale ("one channel = concentration risk"). This is the closest any source comes to *stating* the staged reconciliation the vault had inferred; it doesn't settle the starting N (1 vs 3), but it converts "pick one vs pick three" from a flat contradiction into a question of *when*.
+- **The three-lever map excludes the vault's whole first-client toolkit** (outbound, referrals, in-person events). Read here as a *stage* difference — scaling vs. starting — but that reading is the vault's inference, not the source's claim, and it conveniently dissolves a conflict that might be real. *(2026-07-22: the exclusion turns out to be softer than it looked — the partnerships lever's own playbook runs on in-person events and individual relationship-building, i.e. the first-client toolkit pointed at partners.)*
+- **"Stop cold calling" is enterprise-scoped advocacy from an interested voice — scoping now confirmed from inside his own corpus (2026-07-23).** Martell's anti-outbound position rests on his own war stories, and his prescribed alternative still involves approaching strangers. His $0-SMB blueprint ([[2026-07-23-make-my-first-100k-in-month]]) then prescribes cold calling outright — so the position is segment-scoped, not general. Where the buyer is SMB, the vault's outbound material (Tony, AB Analytics, and Martell himself) is aligned; the anti-cold position applies only at the enterprise end.
+- All AB Analytics channel metrics are promotional (accelerator-member examples) — see [[ab-analytics]].
+
+## Next Questions
+
+- ✅ **Answered 2026-07-26** — for [[eugene]], which 3 channels fit: [[2026-07-26-eugene-90-day-plan]] commits to **one lever (relationship-mediated one-to-one) across three venues** — warm contact mining, one *recurring* industry room (machine-builder/automation association or trade fair, not a generic Chamber), and partner-archetype recruiting among integrators/equipment vendors. This satisfies the pick-1 and pick-3 rules simultaneously under the units reading above. Sebastian's in-person rule **does** override the online tier there — but only because the plan assumes his buyers are enterprise-lite (assumption A5); if that assumption is wrong the online tier reopens, which is stated as the plan's load-bearing risk. The niche itself remains a vault inference, not his stated choice.
+- Is there a buyer-type map: which channels convert for enterprise vs SMB vs startup vs consumer?
+- What's the minimum in-person cadence that builds the "recognition value" [[relationships-as-moat]] describes?

wiki/concepts/cloning-over-originality.md

@@ -0,0 +1,63 @@
+# Cloning Over Originality
+
+#concept #method
+
+## Summary
+
+Originality is a *downstream* product of copying, not an upstream input. Copy proven approaches at 10,000% first, adapt later — and copy the boring parts, because success is a thousand small decisions rather than one brilliant one. Now fully sourced from [[2026-06-15-how-to-get-rich-cloning]] (the [[mohnish-pabrai]] case study), no longer only via the distillation.
+
+`Status: two voices, two traditions; no dissent` (upgraded by lint 2026-07-29 — the label still read "well-sourced within its lineage / one advocacy video," which the sentence below had already superseded). Founding evidence is one advocacy video built around a single exemplar (Pabrai). **Update 2026-07-26: the thesis gained its first independent second voice** — [[oskar-hartmann]] ([[2026-07-26-main-principle-of-successful-business]]), from a different tradition, with three fresh instances (below). Still no dissenting source.
+
+## Current Understanding
+
+**"Originality is downstream of cloning, not upstream."** Copy first at 10,000%, adapt second ([[2026-06-15-selling-development-services-in-the-ai-era]]).
+
+**Clone the boring parts.** Success is ~1,000 small decisions, not one genius move — so copy the morning routine, how distractions get handled, how time is defended. The instinct is to copy the visible strategy and skip the mundane operating habits; the claim is that the mundane habits are where the result actually lives.
+
+**Letter of the rules > spirit of the rules — at the start.** "Spirit of the rules" is for masters; beginners use it to excuse skipping discipline. A sharp, self-aware constraint: it names the exact rationalization ("I understand the principle, so I don't need the practice") that lets someone feel advanced while doing none of the work.
+
+**The Pabrai method — clone from multiple sources.** Buffett for investing, Munger for thinking, Graham for principles, philosophers for life decisions. Originality is an **emergent property of the combination**: nobody else assembled those same pieces the same way. This is the page's most load-bearing idea, because it dissolves the apparent conflict with [[methodology-as-moat]] — if you clone from one source you're a copy, but a specific combination is unclonable in practice even though each component is public. Whether combination alone is *sufficient* differentiation is unexamined; see Contradictions. Full case study — including the "$650k charity lunch with Buffett as *guru dakshina*" — on [[mohnish-pabrai]].
+
+**Two illustrations of the discipline** (from [[2026-06-15-how-to-get-rich-cloning]]): the *food-channel story* — a friend's polished, subtitled, edited recipe channel grew slowly while the niche's top channel ran no subtitles, no music, ~30-sec videos; she cloned the format exactly → 100K then 500K views, and only then experimented. The *barber analogy* — nobody invents their own haircut technique on day one; you stand behind the best barber for weeks, copy everything, then branch. Both make the same point: **beginners mistake a proven operator's omissions for oversights**, when they're usually deliberate.
+
+**The gas-station parable.** One station wipes windshields and checks tires for free, and has a queue. The station across the street watches this every day, never copies it, and goes bankrupt. The failure was not a lack of information — the winning move was visible daily and free to copy. It was **ego**. This is the whole page in one image: the barrier to cloning is almost never knowing what to clone.
+
+**The independent second voice — cloning as an anti-intuition discipline** ([[2026-07-26-main-principle-of-successful-business]], [[oskar-hartmann]], added 2026-07-26). Three instances from the VC/product world, each pairing cloning with *measurement* rather than taste:
+
+- **Top utility-app studios "forbid themselves from inventing"** — they launch ~20 apps at once and let money vote ([[sell-before-build]]). Institutionalized anti-originality: the ban is the discipline.
+- **Oliver Samwer's eBay clone for Germany**: copied all 100 features as non-working buttons, watched click logs, built in click-count order — "intuition deceives, always." Cloning plus instrumentation beats both invention *and* naive copying (he cloned the feature list but let *data* pick the build order).
+- **The $5M robot-data founder** explicitly copied his playbook from 10 companies that had grown the same way on LLM-training data — clone the *business motion*, apply it to the adjacent market.
+
+This voice adds something Pabrai's story lacks: Pabrai clones *judgment* (Buffett's decisions), Hartmann's cases clone *mechanisms and then measure* — which answers this page's standing worry that cloned strategy fails on unobservable details. If the details are unobservable, instrument them (Samwer's logs) instead of guessing.
+
+**Why this belongs in a sales vault.** It's the meta-method behind every other page: [[sales-discipline]] is the boring part to clone; [[methodology-as-moat]] is the output; the ladder in [[offer-ladder]] was itself copied from a coach on a call.
+
+## Evidence
+
+- **Primary:** the whole thesis — 10,000%-or-nothing, clone-the-boring-parts, letter>spirit, multi-source combination, gas-station parable, Pabrai→Buffett case, food-channel and barber illustrations — [[2026-06-15-how-to-get-rich-cloning]]
+- Condensed restatement: "Originality is downstream of cloning… копируй на 10 000%, потом адаптируй" — [[2026-06-15-selling-development-services-in-the-ai-era]]
+- Convergent (different author): "business buys a proven method, not uniqueness" — [[2026-06-15-rodenko-selling-development-expensively]] via [[methodology-as-moat]]
+- **Independent second voice:** app studios that forbid inventing; Samwer's fake-button clone built in click order; the robot-data founder copying 10 LLM-data playbooks — [[2026-07-26-main-principle-of-successful-business]] ([[oskar-hartmann]])
+- Indirect: the [[2026-07-17-design-the-perfect-offer]] method is itself a cloned template (backwards math → ladder → deck)
+
+## Related Pages
+
+- [[mohnish-pabrai]] — the exemplar and his multi-source cloning
+- [[methodology-as-moat]] — the moat is a *combination* of cloned parts, not an invention
+- [[sales-discipline]] — the boring, cloneable operating habits
+- [[niche-selection]] — "don't invent a novel service" is the same instinct applied to offers
+- [[sell-before-build]] — the measurement half of clone-then-measure
+- [[2026-06-15-how-to-get-rich-cloning]] — primary source
+- [[overview]]
+
+## Contradictions / Uncertainty
+
+- **Named figures are stated but unverified.** [[mohnish-pabrai]] now has an entity page and the primary video is ingested, but its figures (Buffett 31%/40yr, Pabrai ~$154M, the $650k lunch) are asserted by an advocacy video without citation — broadly consistent with public accounts, not independently checked here. Buffett/Munger/Graham are recorded on the Pabrai page as supporting cast rather than as their own entities.
+- **Combination-as-originality is asserted, not argued.** If your combination is public (as it is, once you sell it), what stops it being cloned in turn — by the very logic this page endorses? The sources' implicit answer is that execution of 1,000 small decisions doesn't transfer even when visible; the gas-station parable supports this psychologically rather than structurally.
+- Tension with [[niche-selection]]'s "go where AI is powerless": cloning is exactly what an LLM does well. A method assembled entirely from public, cloneable sources is more exposed to substitution than one built on private domain knowledge. Unaddressed by the source.
+
+## Next Questions
+
+- Which specific operators should be cloned for *this* vault's business, and which boring parts of theirs are actually observable?
+- Does "clone at 10,000%" survive contact with a market that has already seen the original?
+- Would a primary Pabrai source (his book/letters) confirm the "clone the boring parts" emphasis, or is it the video creator's gloss?

wiki/concepts/future-of-engineering-work.md

@@ -0,0 +1,58 @@
+# Future of Engineering Work
+
+#concept #ai
+
+## Summary
+
+How AI restructures engineering *labor and roles* (as opposed to the services *market*, which is [[ai-market-shift]]). From [[2026-07-06-sebastian-interview-ai-and-software-engineering]]: once "AI can write software" is settled, the whole game is *how you use it* — and that cascades into team size, tooling, the enterprise, open source, and identity.
+
+## Current Understanding
+
+**The premise:** "It's not a question *if* AI can write software anymore — it's just a question of *how* you use it." Cost of writing code trends to zero; leverage moves to direction and verification.
+
+**Teams collapse from ~8 to 2–3.** No more scrum master + PM + requirements engineer + big dev team — instead one coordination/ownership role plus one or two people managing coding agents, sharing responsibilities. Coordination overhead can now exceed the work: on a small 2-person project Sebastian is **faster alone** than synchronizing who-does-what. (Cross-source: "team size is no longer a signal of seriousness" — the 4-person squad at ~$7M/yr in [[2026-06-15-rodenko-selling-development-expensively]]; solo-founder Rezi at $293k/mo in [[2026-06-15-making-money-with-ai-2026]].)
+
+**Bring-your-own-harness vs company-managed — and the business opportunity.** [[eugene]]'s thesis: every developer should build a personal harness on top of Claude Code (his own: a Telegram-like UI, one agent per project, inter-agent messaging, per-agent memory, "done thinking" signals; tools like **Conductor** for git-worktree-per-chat). [[sebastian]]'s counter: compliance and liability make ad-hoc per-developer setups impossible at scale — "it has to be a company-managed resource." **→ open market: compliant, centrally-managed, company-standard harnesses for large regulated teams.** This is a [[niche-selection]]-shaped opportunity ("go where the indie tools can't").
+
+**Enterprise reality is far more locked down than the indie world:** managed VMs, no personal laptops, zero self-installed tools; a ~1,200-engineer Roche SAP program; banks moving from banning AI to cautious adoption "because it's just so good."
+
+**Two smaller theses:** open source will *grow* (near-free code is easy to give away; Eugene's cynical read: OSS is mostly marketing). Legacy/hobby niches persist (COBOL in banks — no training data; people who code for love "like an old-timer car") but not where time/quality/money matter.
+
+**The philosophical turn — decouple identity from profession.** As many professions collapse into "prompt the AI," people who tie identity to their job title ("I *am* a doctor") will feel worthless; the advice is to separate *who you are* from *what you do*. "Fundamentally I'm Eugene — I'm not a programmer."
+
+**Where the human value goes** is covered by the sibling pages: judgment ([[seniority-and-ai]]), ownership ([[product-ownership]]), and trust ([[relationships-as-moat]]).
+
+## Evidence
+
+- "It's not a question *if* AI can write software… it's just a question of *how* you use it." — [[2026-07-06-sebastian-interview-ai-and-software-engineering]]
+- Team collapse to 2–3; coordination overhead > work; faster-alone — same source
+- BYO-harness demo and Conductor; compliance counterpoint; the managed-harness market — same source
+- Enterprise lockdown; Roche ~1,200 engineers; banks ban→adopt — same source
+- OSS grows; COBOL/old-timer legacy niches — same source
+- Identity decoupling — same source
+- "Team size no longer a signal": squad model — [[2026-06-15-rodenko-selling-development-expensively]]; solo Rezi — [[2026-06-15-making-money-with-ai-2026]]
+- **Counter-evidence (adversarial):** the "coding cost → 0" premise is qualified — AI's measured effect is modest (≈14–19%), can be *negative* for experts, and team-level delivery *stability* fell with AI adoption (DORA 2024) — [[ai-productivity-evidence]] / [[2026-07-18-ai-productivity-adversarial-evidence]]
+
+## Related Pages
+
+- [[ai-market-shift]] — the market-side twin of this labor-side page
+- [[seniority-and-ai]] · [[product-ownership]] · [[relationships-as-moat]] — where human value migrates
+- [[niche-selection]] — the enterprise-harness gap is a niche opportunity
+- [[ai-productivity-evidence]] — the empirical qualifier on "coding cost → 0" and team collapse
+- [[team-growth-ceiling]] — if teams collapse to 2–3, each person's growth rate becomes a larger share of the company's ceiling
+- [[eugene]] · [[sebastian]] · [[virtido]]
+- [[overview]]
+
+## Contradictions / Uncertainty
+
+- **BYO vs managed harness** is a live disagreement between the two speakers, not a settled point; the reconciliation ("personal for individuals, managed for enterprise") is the vault's synthesis. `Status: tentative`.
+- **OSS motivation** is disputed within the source (Eugene: marketing; Sebastian: expects more).
+- Team-collapse numbers (8→2–3) and "faster alone" are one founder's experience on small projects; Sebastian is explicit he doesn't know how this plays out on ~1,200-engineer programs.
+- **The "coding cost → 0" premise is empirically qualified (2026-07-18).** [[ai-productivity-evidence]] finds AI's real effect is modest (≈14–19% average, negative for experts on familiar code), and — most relevant to *team* restructuring — DORA 2024 found AI adoption correlated with *lower delivery stability* (individual speed didn't convert to better shipping; DORA reversed the throughput half in 2025, stability persisted). This doesn't refute team collapse, but it undercuts the premise that the coding *itself* is now free and frictionless; the coordination and verification work this page centres on is exactly where the measured cost stays. Early-2025-scoped — see the source's time caveat.
+- Identity-decoupling is philosophy, not evidence — included as a recorded view, not a claim.
+
+## Next Questions
+
+- What does a compliant enterprise harness actually require (audit, secrets management, standardization) — and is anyone shipping one?
+- Does the 8→2–3 collapse hold on large programs, or only on small teams?
+- If [[eugene]] is the vault owner, is the enterprise-harness market the business this vault should be scoping?

wiki/concepts/information-vs-implementation.md

@@ -0,0 +1,80 @@
+# Information vs Implementation
+
+#concept #content-marketing #positioning
+
+## Summary
+
+The strategy of publicly teaching your entire know-how to sell your delivery. The claim: **information is free, but implementation and *sequencing* are paid** — so give away every individual step as free content and charge for putting the steps in the right order and executing them. `Status: tentative` — and, as of 2026-07-23, **effectively single-voice**: the concept's founding source was anonymous, but [[2026-07-23-make-my-first-100k-in-month]] (named: [[dan-martell]]) reuses its three distinctive mechanisms verbatim, making Martell its near-certain author. What was recorded on 2026-07-20 as "a second, independent voice" for content-as-engine is therefore almost certainly the *same* voice — the corroboration this page briefly claimed is withdrawn (superseded note under Contradictions).
+
+## Current Understanding
+
+**The thesis** ([[2026-07-18-information-is-free-implementation-is-paid]]): the best marketing content is *exactly what you do in-house for paying clients* — your internal playbook, step by step. Publishing the *what* (the know-how) does not remove demand for the *how* (the sequenced, done-with-you/done-for-you delivery). What the buyer actually pays for is:
+
+1. **Sequencing** — knowing the *order* the steps combine into a working system.
+2. **Implementation** — doing it, or doing it with/for them.
+
+Each free piece teaches a real, valuable step; the assembly is withheld. This reframes the hoarding instinct: holding your best material in-house doesn't make you look valuable — it means *nobody knows you have it*.
+
+**The scramble trick — the mechanism that makes "give it all away" safe.** Post the pieces *out of order across topics*, never in a runnable sequence within one topic:
+
+- Don't post: A1, A2, A3 … A10, then B1, B2 …
+- Post: **A1, B1, C1, D1, E1, A2, B2, C2 …**
+
+Every individual video still teaches something, so you look expert on every swipe — but the sequence a viewer would need to actually implement the whole system is missing. *"You could put an A-to-Z course on YouTube in a completely out-of-whack order, and people would still pay you for the same content put in the right order."* The moat is **friction, not secrecy**: a motivated viewer could re-sort by topic, so this withholds convenience, not information.
+
+**The content-idea factory (5 × 10 × 4 = 200)** — the operational half, so you never run dry:
+
+| Layer | Count | What |
+|---|---|---|
+| Hot buttons | 5 | Big pain areas the ICP feels |
+| Nuanced pains each | 10 | Specific, observable problems |
+| Pain-ideas | **50** | ≈50 days, then loop |
+| Formats each | 4 | clone / talking head / green screen / +1 |
+| Pieces | **200** | ~⅔ of a year, near-daily |
+
+**Every piece is pain → solution.** Open on a *nuanced, observable* pain that "describes the viewer's world better than they can describe it themselves" (→ *"how do you know?"*), then teach the fix. Never open on the solution. The pains are generated with the AI prompt developed on [[pain-discovery]].
+
+**The pricing payoff.** Fifty free expert videos make a $997 offer feel *cheap* — the giveaway is the price anchor. See [[pricing-from-value]].
+
+**What the second source adds** ([[2026-07-20-referrals-will-sink-your-business]]). It shares the "publish your know-how, daily, at volume" bet but arrives from a different direction and contributes three things this page didn't have:
+
+1. **A reason to publish beyond distribution.** Content is *practice at explaining what you do* — the reps fix the [[technical-founder-trap]], and the explaining is itself the unlock. This page treated publishing purely as lead-gen.
+2. **The organic→paid bridge.** *"The new paid is organic"*: content-shaped ads win, and the way to run paid without burning cash is to promote an organic piece that **already** worked. So the content engine isn't only a channel — it's the creative pipeline paid ads require. Neither source's model conflicts here; they compose.
+3. **A patience budget** — ~6 months before the system yields leads ([[marketing-system]]). This page's factory produces 200 pieces / ~⅔ of a year but never says when to expect a return.
+
+Where they **differ**: the scramble trick is unique to the first source and is about *withholding sequence*; the second source's advice is simply to publish more, with no concern for what order the audience receives it in. Those are compatible but not the same strategy — one guards the assembly, the other doesn't think it needs guarding.
+
+**The 07-23 restatement, and the first outcome number** ([[2026-07-23-make-my-first-100k-in-month]]). The named-Martell $100K blueprint restates this page's whole machinery inside its inbound step: feed each offer deliverable to AI for "10 **nuanced and observable** problems," build hook-first content on them (*"if I can describe my customer's pain better than they can, I'm the expert"*), give everything away, and get paid for the **sequence of implementation** — step 1 (audit) → step 100 (fully automated), scrambled in content (A1, B2, C1…). Because this is (almost certainly) the same author, it is framework *stability*, not corroboration. What it does add is the vault's **first outcome figure** for content-as-engine: his second company Flowtown claimed **350K unique visitors → 50K customers** off blog content, against a first company that built product before marketing and died (*"crickets"*). Self-reported, unverified, and from the 2010s blog era — but until now the concept had zero numbers of any grade.
+
+## Evidence
+
+- Whole specific mechanism (thesis, scramble trick, 5×10×4 factory, pain→solution structure, price-anchor argument) — [[2026-07-18-information-is-free-implementation-is-paid]] (anonymous; author now near-certainly [[dan-martell]])
+- Second voice for content-as-primary-engine (daily volume, explain what you do, organic→paid bridge, reps-not-views) — [[2026-07-20-referrals-will-sink-your-business]], [[dan-martell]], [[marketing-system]] — **no longer counted as independent** (same suspected author as the founding source)
+- Restatement of scramble + nuanced-pain prompt in a named-Martell source; Flowtown 350K visitors → 50K customers (first outcome figure, self-reported) — [[2026-07-23-make-my-first-100k-in-month]]
+- Adjacent same-school framing "people buy the standard/method, not the labor" — [[2026-07-17-design-the-perfect-offer]], [[methodology-as-moat]]
+
+## Related Pages
+
+- [[client-acquisition-channels]] — this is the organic-content channel, developed; and a data point in the online-vs-in-person split
+- [[marketing-system]] — the second source's frame: content is one of three levers, and the prerequisite for paid
+- [[technical-founder-trap]] — why a technical operator finds "just explain what you do" hard, and why the reps matter
+- [[pain-discovery]] — the nuanced-pain prompt is shared machinery (name the pain better than the buyer can)
+- [[pricing-from-value]] — free content as the anchor that makes the paid offer feel cheap
+- [[methodology-as-moat]] — "sequencing is the paid good" is a moat framing (the order is the defensible asset)
+- [[cloning-over-originality]] — splinter an internal playbook into out-of-order pieces
+- [[productized-service]] — the withheld "implementation" is the productized delivery
+- [[overview]]
+
+## Contradictions / Uncertainty
+
+- `Status: tentative` — the scramble trick and 5×10×4 factory remain single-voice with **no conversion data** (Flowtown is a visitor/customer count from a different business model and era, self-reported). A plausible mechanism asserted as fact.
+- **Superseded (2026-07-23): the "independent second voice" reading of 2026-07-20.** The founding source's anonymous speaker is now near-certainly [[dan-martell]] himself — [[2026-07-23-make-my-first-100k-in-month]] (which names him) reuses the scramble trick, the "nuanced and observable problems" prompt, and the "describe their pain better than they can" line verbatim. The prior framing ("one voice for the mechanism, two for the bet") collapses to **one voice for both**, pending owner confirmation. The concept's entire support is now: one author's repeated advocacy + his own company anecdote.
+- **Directly contradicts [[sebastian]]**, who rates content marketing / SEO a "Big zero" and says only in-person builds closing trust. Best current read: audience-dependent (SMB/prosumer feeds → content converts; locked-down enterprise → it doesn't). See [[client-acquisition-channels]].
+- **Moat tension.** If sequencing is the moat, it collides with [[methodology-as-moat]]'s "proven method is the moat" only partially — sequencing *is* a proven method, so they agree — but it also sits under [[cloning-over-originality]] (copy everything): a sequence shown piecemeal is more re-derivable than a method kept private. Unresolved whether "scrambled but public" is a durable moat or just a head start.
+- **ICP mismatch.** The worked example anchors to $500K–$2M-revenue buyers, larger than the vault's usual SMB framing.
+
+## Next Questions
+
+- Does the scramble actually convert, or do sophisticated viewers re-sequence and self-serve? No evidence either way.
+- For the vault owner ([[eugene]]), whose stated blocker is building a network: is a scrambled-content engine a faster path than the in-person channels favored in [[2026-07-17-best-method-first-client]] — or a slower one that only pays off at audience scale?
+- How does this compose with warm/in-person channels — content as the trust layer *under* outbound (Tony's model in [[client-acquisition-channels]]) rather than a standalone lead source?

wiki/concepts/marketing-system.md

@@ -0,0 +1,88 @@
+# Marketing System
+
+#concept #marketing #content-marketing
+
+## Summary
+
+The distinction between **demand you generate** and **demand that arrives**. A marketing system has one defining property: **money in at the top produces more money out at the bottom**. Anything that doesn't have that property — [[referrals|referrals]], word of mouth, an inbound trickle — is not a system, however well it converts, because you cannot turn it up. Carried by a single author — [[dan-martell]], across [[2026-07-20-referrals-will-sink-your-business]] and now [[2026-07-22-stop-cold-calling-do-this-instead]] (which restates the taxonomy and fills in the third lever) — so `Status: tentative` on the three-lever framework. **Since 2026-07-26 the core claim has an independent second voice:** [[oskar-hartmann]] ([[2026-07-26-how-to-build-a-billion-dollar-company-2027]], VC/product tradition) independently makes the *existence of a repeatable channel with predictable acquisition economics* the defining difference between a company and a "tumor" — one-off spikes and referral luck don't count ([[sales-channel-as-moat]]). The machine-vs-arriving-demand distinction is now cross-tradition; the specific taxonomy (three levers, pick one) remains Martell-only. The page names a layer the vault previously had no page for: not *where* to fish ([[client-acquisition-channels]]) and not *how consistently* to work it ([[sales-discipline]]), but **whether a machine exists at all**.
+
+## Current Understanding
+
+**The diagnostic.** Referral-led growth is the classic false positive: it feels like validation and reads as a badge ("all word-of-mouth!"), but it is evidence that the system work was skipped. Its signature is a hard revenue ceiling that the founder misreads as a market limit. The claim: founders who built the system hit the same number in ~18 months **and can keep going** — the difference is not speed, it's whether there's a throttle. Counter-position recorded in full on [[referrals]].
+
+**The three levers.** Exactly three ways to make more people aware of you:
+
+| Lever | What it is | Note |
+|---|---|---|
+| **Publish content** | Organic reels, lives, shorts, posts | Cheapest to start, hardest skill to build |
+| **Paid ads** | Meta / Google / etc. | Best paid ads *are* organic content — see below |
+| **Partnerships** | Someone with credibility walks you into their customer base | Mechanism supplied 2026-07-22 — see [[partnerships]] |
+
+All three cost something; all three are different skills. **Pick the one you're most compelled to do and commit for 90 days** — the failure mode is dabbling in all three. This collides with [[ab-analytics]]'s "pick 3, run 90 days" rule; see Contradictions. The second source restates both the taxonomy (as Publish / Paid / Partners) and the pick-one rule verbatim in structure — evidence the framework is stable for this author, **not** corroboration, since it is the same voice.
+
+**The third lever, filled in** ([[2026-07-22-stop-cold-calling-do-this-instead]]): partnerships run on **borrowed credibility** — a partner who already holds the buyer's trust (e.g. a system integrator with a large contract in the account) walks you in pre-sold, collapsing enterprise entry friction. The lever quality comes from the throttle: you can't make clients refer more ([[referrals]]), but you *can* recruit more partners — reverse-engineer the partner that worked and systematically acquire the archetype. Full mechanism, economics, and caveats on [[partnerships]]. Note it qualifies this page's one-to-many framing: partner *acquisition* is one-to-one relational work (events, win the individual — the [[relationships-as-moat]] motion aimed at partners), with the leverage arriving at the account layer. One-to-few-to-many, not one-to-many.
+
+**The organic→paid bridge — "the new paid is organic."** Organic content is not an alternative to paid ads, it is their prerequisite:
+
+1. The best-performing Meta ads now *look like content*, and the platform rewards content-shaped ads.
+2. Paid ads at volume need a **creative pipeline** — most founders have never built one, because they aren't content creators yet.
+3. So the rule is: take an organic piece that **already worked**, then run *that* as an ad.
+
+Skip this and paid burns cash — you're buying distribution for creative that was never tested for free.
+
+**Reps, not views.** The metric substitution that makes the 90 days survivable:
+
+| Wrong metric | Right metric |
+|---|---|
+| How many views did this get? | Am I getting better? |
+| Did this one go viral? | How many reps did I do this week? |
+
+You do not decide what goes viral; rep volume is the only controllable variable. *"Most of you get bored with your marketing before the market ever does — and you just stop."* This is the same discipline [[sales-discipline]] reaches from the outbound side (consistency beats intensity, 30 min/day beats 5 hours monthly) — two traditions converging on process-metrics-over-outcome-metrics is the claim's main support.
+
+**The time budget** — stated up front so you don't quit at day 60:
+
+| Month | What happens |
+|---|---|
+| 0–3 | 90-day attack on publishing. Skill-building, no system yet. |
+| 3–6 | Second 90 days. Pipeline now exists. |
+| 6+ | System begins producing leads. |
+| 6–18 | $1.5M → $10M "no problem" (unsourced). |
+
+**Scope note — this is a *scaling* protocol, not a *starting* one; the author's own start protocol now confirms it.** The advice is delivered to a founder with an existing client base and a stalled $1.5M. The levers exclude outbound and referrals, which is exactly the one-to-one ground the vault's first-client answer ([[2026-07-17-best-method-first-client]]) stands on. (The original "all three are one-to-many" reading is now qualified — the partnerships lever is one-to-few-to-many, and its partner-recruiting layer uses the first-client toolkit itself; see above.) Read as staged rather than opposed: warm/in-person one-to-one gets you clients #1–#N; a marketing system is what stops #N from being the ceiling. **Since 2026-07-23 this staging has same-author support:** Martell's $0→$100K blueprint ([[2026-07-23-make-my-first-100k-in-month]]) prescribes phone-mining outbound, cold calls, and chat-closing for the start — the very motions his lever map omits — with inbound content running alongside as the long-term engine. So his own corpus behaves as if the lever map begins *after* the first clients. The cost of that support: his start protocol runs **two engines in parallel**, colliding with this page's pick-one rule (see Contradictions). Neither video states the handover point; the staging remains inference, now consistent with rather than tested by the sources.
+
+## Evidence
+
+- Whole concept (money-in→money-out definition, three levers, pick-one/90-days, "the new paid is organic", reps-not-views, 6-month budget, referral-dependency diagnostic) — [[2026-07-20-referrals-will-sink-your-business]], [[dan-martell]] (single source)
+- Taxonomy + pick-one rule restated; partnerships mechanism (borrowed credibility, partner-archetype recruiting) — [[2026-07-22-stop-cold-calling-do-this-instead]] (same author — consistency, not corroboration)
+- The $0 start protocol (inbound + outbound in parallel; outbound present pre-scale) — [[2026-07-23-make-my-first-100k-in-month]] (same author; supports the staged reading, strains the pick-one rule)
+- Process-over-outcome metrics reached independently from outbound — [[sales-discipline]], [[2026-06-15-17-ways-first-client]]
+- Content-as-primary-engine, the content lever worked out — [[information-vs-implementation]], [[2026-07-18-information-is-free-implementation-is-paid]] (near-certainly the *same* author — consistency, not corroboration; independence withdrawn 2026-07-23)
+- **Independent corroboration of the machine-vs-arriving-demand core:** repeatable channel with predictable economics as the company-defining asset; spikes and partner luck excluded — [[2026-07-26-how-to-build-a-billion-dollar-company-2027]] ([[oskar-hartmann]], different tradition; detailed on [[sales-channel-as-moat]])
+
+## Related Pages
+
+- [[partnerships]] — the third lever, worked out in full (borrowed credibility, partner-archetype recruiting)
+- [[referrals]] — the channel this concept diagnoses as a ceiling when it's the *only* one
+- [[client-acquisition-channels]] — *where* to fish; this page is *whether the machine exists*
+- [[sales-discipline]] — *how consistently*; reps-not-views is the shared discipline
+- [[information-vs-implementation]] — the content lever, worked out in full (what to actually publish)
+- [[technical-founder-trap]] — the source's diagnosis of *why* technical founders never build one
+- [[dan-martell]] — the source's author
+- [[sales-channel-as-moat]] — the independent, company-level restatement of the same machine
+- [[overview]]
+
+## Contradictions / Uncertainty
+
+- `Status: tentative` — **the three-lever framework is one author across three clips** ([[dan-martell]]: 07-20, 07-22, 07-23 — restatement, not corroboration); only the machine-vs-arriving-demand *core* has an independent second voice ([[oskar-hartmann]], 2026-07-26). Coaching clips, **no data**: the $1.5M→$10M, ~18-month, and six-month-lag figures are unsourced. The supporting viral anecdotes (Tones and I, Oliver Anthony) are survivorship selection and support far less than they're used for.
+- **Pick one vs. pick three.** [[dan-martell]] says commit to one lever for 90 days; [[ab-analytics]] says run three channels for 90 days ([[2026-06-15-17-ways-first-client]]). Same time unit, opposite N, and both frame their rule as the anti-dabbling discipline. Possibly reconcilable by scope — Martell's "levers" are broad one-to-many *disciplines* (content is one lever but many channels), AB Analytics' are specific *channels* — but no source says so. Unresolved. **And Martell's own $0 blueprint breaks the rule** ([[2026-07-23-make-my-first-100k-in-month]]): inbound and outbound "two engines, always in parallel." Either pick-one applies only at scale, or the rule bends when he writes for beginners — his corpus doesn't say which. **Third position (2026-07-26):** [[oskar-hartmann]] — one repeatable channel builds the company, but "one channel = concentration risk"; resilient systems are multichannel. Closest statement yet of the staged reconciliation; see [[client-acquisition-channels]].
+- **Directly contradicted by [[sebastian]]**, for whom content, SEO, and paid are all "Big zero" and only in-person builds closing trust. This page is the strongest statement yet of the pole Sebastian rejects — see [[client-acquisition-channels]].
+- **The independent second voice is adversarial on lever 3** (lint 2026-07-29). [[oskar-hartmann]] corroborates this page's *core* (a channel must be repeatable with predictable economics) while attacking its **partnerships** lever: partner-as-savior plays land 100–200× below expectations, "you are their 46th priority." So the one out-of-school voice supporting the machine claim does not support the lever taxonomy built on it — detailed on [[partnerships]].
+- **Incentive.** The source sells founder coaching; "you skipped the real work, budget six months" is also the shape of his offer.
+- **Untested for solo operators.** Daily-live + 2-reels-a-day assumes marketing *is* the founder's job. A solo developer delivering client work cannot obviously sustain it, and the source never addresses the trade-off.
+
+## Next Questions
+
+- Is there any evidence — of any quality — for the six-month lag, or is it a motivational number chosen to prevent quitting?
+- ✅ ~~What does the *partnerships* lever actually consist of?~~ Answered 2026-07-22 by [[2026-07-22-stop-cold-calling-do-this-instead]] → [[partnerships]]. The highest-fit-for-a-technical-operator hunch survives: the required skill is targeted relationship-building, not publishing. Still same-author and anecdote-grade.
+- For [[eugene]]: does the staged reading above hold — in-person for client #1, then a system so client #10 isn't the ceiling — or does building the system early beat sequencing it late?
+- Does the organic→paid bridge apply to B2B services at all? The evidence offered is consumer/creator-economy (music virality, Meta reels), not services procurement.

wiki/concepts/methodology-as-moat.md

@@ -0,0 +1,62 @@
+# Methodology as Moat
+
+#concept #positioning
+
+## Summary
+
+What is defensible is not the work — a thousand people can do the work — but *your specific way of doing it*. Several sources land here; two of them produce the vault's most quotable line and its most useful correction to it. Note this is now one of **three** competing moat accounts in the vault: [[relationships-as-moat]] argues the real moat is in-person trust, and [[sales-channel-as-moat]] (added 2026-07-26) argues it is the repeatable distribution machine — with the product/method as the commodity. See Contradictions.
+
+## Current Understanding
+
+**"People don't buy your time. They buy your standards."** ([[2026-07-17-design-the-perfect-offer]]) The operational consequence is a language rule:
+
+| Never say | Say instead | Why |
+|---|---|---|
+| "3 hours per month **with me**" | "3 hours of training **with my team**" (or "me or my team") | Buyers want the standard, not your presence. Promise yourself and fail to show → they're upset. Promise the team and show up anyway → bonus. |
+| "I do AI for you" | "This is my specific methodology for [outcome]" | People buy methodology, not labor — that's what "productized" means. |
+
+The "me or my team" rule is also what makes a service *scalable*: an offer that requires you personally cannot be delivered by anyone else, which caps the business at your calendar and makes [[productized-service]] impossible.
+
+**The correction: proven, not unique.** [[dmitry-rodenko]] sharply inverts the instinct to sound novel — *"Бизнес покупает не уникальность, а проверенный способ"*: business buys a **proven method**, not uniqueness. "Unique" reads to a buyer as *"I'm afraid — don't experiment on me."* ([[2026-06-15-rodenko-selling-development-expensively]], condensed in the distillation)
+
+This sits in real tension with the video, which advises framing the offer "in a way that sounds unique even if the underlying service isn't." Both can hold only under a specific reading: the *packaging* should feel distinctive enough to escape comparison-shopping, while the *method* must read as battle-tested rather than experimental. Distinctive positioning, unremarkable risk. `Status: tentative` — this reconciliation is synthesis, not stated by either source.
+
+**Sequencing is the moat's public form.** [[2026-07-18-information-is-free-implementation-is-paid]] reaches the same claim from the marketing side: you can give away every *step* (the information) as free content and still get paid, because what's defensible is the **sequence** — the order the steps combine into a working system. *"Information is free; implementation and sequencing are paid."* This agrees with "buy the standard, not the labor," but it strains the [[cloning-over-originality]] tension below: a sequence shown publicly (even scrambled) is more re-derivable than a method kept private, so whether "scrambled but public" is a durable moat or merely a head start is unresolved. See [[information-vs-implementation]].
+
+**Expertise = knowing where the rocks are.** "Знание, где подводные камни — это и есть твоя экспертиза" ([[2026-06-15-konspekt-aphorisms]]). This is what a method encodes and what a buyer can't get from a substitute — and it's the thing that makes accountability ([[outcome-based-selling]]) survivable rather than reckless. [[seniority-and-ai]] reaches the identical conclusion from the labor side: the senior's product *is* knowing where things break.
+
+**The floor beneath the moat:** *"If you're at the level of an Indian dev, you are one — just more expensive"* — recorded from [[2026-06-15-konspekt-aphorisms]] as a claim about commoditized skill (with the caveat noted there — the phrasing leans on a nationality stereotype and is not reused in this vault's own writing). The usable point: without a differentiated method, you compete only on rate, and [[pricing-from-value]] holds that rate competition ends in bankruptcy.
+
+## Evidence
+
+- "People don't buy your time. They buy your standards." — [[2026-07-17-design-the-perfect-offer]]
+- "Methodology is the moat — a thousand people can do 'the thing'; only you have *your way* of doing it." — [[2026-07-17-design-the-perfect-offer]]
+- The "with me" → "with my team" language rule — [[2026-07-17-design-the-perfect-offer]]
+- "Бизнес покупает не уникальность, а проверенный способ. Уникально = «боюсь, не экспериментируйте на мне»." — [[2026-06-15-rodenko-selling-development-expensively]]
+- "Знание, где подводные камни — это и есть твоя экспертиза" + 2–3 Before/After case studies as minimum proof — [[2026-06-15-konspekt-aphorisms]]
+- Convergent from the labor side: senior judgment = risk reduction — [[2026-07-06-sebastian-interview-ai-and-software-engineering]]
+- "Information is free; implementation and sequencing are paid" (the moat as *order*, not steps) — [[2026-07-18-information-is-free-implementation-is-paid]]
+
+## Related Pages
+
+- [[relationships-as-moat]] — competing account #2: the moat is in-person trust, not method
+- [[sales-channel-as-moat]] — competing account #3: the moat is the repeatable distribution machine
+- [[seniority-and-ai]] — the labor-side version of "knowing where it breaks is the product"
+- [[productized-service]] — the method is what gets productized
+- [[outcome-based-selling]] — a proven method is what lets you promise an outcome
+- [[cloning-over-originality]] — where the method comes from in the first place (copied, then adapted)
+- [[information-vs-implementation]] — the marketing-side version: sell the sequence, give away the steps
+- [[pricing-from-value]] — no method → rate competition → no margin
+- [[overview]]
+
+## Contradictions / Uncertainty
+
+- **Three moats, competing.** [[relationships-as-moat]] ([[sebastian]]) holds that as AI levels skill, *in-person trust* — not method — is the last defensible asset; [[sales-channel-as-moat]] ([[oskar-hartmann]], 2026-07-26) holds that the *repeatable distribution channel* is, with the method itself commoditized by vibe-coding. All three can be true at different layers (method = what you deliver; relationships = one channel's trust substrate; channel = the machine that repeats), but they direct time/money differently: productizing vs. showing up vs. building the machine. Which dominates likely depends on [[niche-selection]] and stage. Unresolved.
+- **"Sound unique" vs. "don't be unique"** — a live tension between the video and Rodenko, reconciled above only tentatively (distinctive packaging + unremarkable risk).
+- Circularity worth flagging: [[cloning-over-originality]] says copy everything at 10,000%; this page says your method is the moat. If the method is cloned, the moat is cloned too. The sources' implicit answer is that the *combination* is unclonable (Pabrai's emergent-originality argument) — but neither states this explicitly and it is not obviously sufficient.
+
+## Next Questions
+
+- How does a buyer distinguish "proven method" from "confident marketing"? Case studies with numbers are the only proof mechanism either source offers.
+- At what point does a cloned method become "yours" enough to be a moat?
+- Is "standards" (video) the same thing as "proven способ / method" (distillation), or two different claims that merely rhyme?

wiki/concepts/niche-selection.md

@@ -0,0 +1,62 @@
+# Niche Selection
+
+#concept #positioning
+
+## Summary
+
+Who you sell to dominates what you sell. Every source makes audience choice the highest-leverage decision — the video via "hungry crowd beats best burger", Rodenko via "80% of sales is WHO you talk to, not WHAT", and Tony most bluntly: **"niche is upstream of everything"** — without an ICP you can't outbound, can't productize, and can't delegate sales at all ([[2026-06-15-more-clients-dev-agency]]).
+
+## Current Understanding
+
+**The market picks the offer, you don't invent it.** Don't design a novel service; find what the market is already asking for and name its bottleneck back to it ([[2026-07-17-design-the-perfect-offer]]). The burger analogy: *"Is it better to have the best burger in town, or be around a bunch of hungry people?"* — hungry crowd wins every time. Corollary from the fitness-coaching example: market saturation is never the real problem; the problem is the right offer in front of the wrong people.
+
+**If it won't sell, suspect the audience before the offer.** "Если оффер не продаётся — почти всегда не та аудитория" ([[2026-06-15-selling-development-services-in-the-ai-era]]). Reinforced by: *if even one person bought, there's no reason others won't — the problem is never the product, it's WHO and HOW.* This is a useful debugging heuristic and also an unfalsifiable one; it can rationalize away a genuinely bad offer indefinitely. Hold it as a first hypothesis, not a conclusion.
+
+**Three selection rules** (primary: [[2026-06-15-rodenko-selling-development-expensively]] for 1–2, [[2026-06-15-17-ways-first-client]] for 3):
+
+1. **Sell to leadership, not implementers.** To an implementer your AI is a threat to their job, and you are a risk to be blocked. To leadership, you deliver a KPI. This is the vault's clearest account of *why* the same offer lands or dies depending on the seat it's pitched to.
+2. **Go where AI is powerless** — narrow industry methodologies LLMs don't know (Rodenko: "not profitable to feed them"). Niche depth is the moat precisely because the substitute can't reach it.
+3. **Specificity beats volume** — "Shopify dev for fashion brands" beats "web developer" everywhere. Against "we do everything for everyone" (also Tony's mistake #2).
+
+**Pick the segment before you build** ([[2026-06-15-making-money-with-ai-2026]]): choosing a target segment is an explicit step *before* implementation in all three monetization pipelines — "solve a concrete pain, don't build a platform."
+
+**The buyer default at $1K+/month: business owners** ([[2026-07-23-make-my-first-100k-in-month]], [[dan-martell]]): small-business owners feel all three buyable outcomes (time, money, status — [[outcome-based-selling]]) and decide fast — no committee. A coarser cut than "sell to leadership" but the same logic: pick the seat where the pain converts to a purchase decision. Same source adds the vault's first **supply-side** filter, Ikigai — love it / good at it (reframed: *what do people tell me* I'm good at) / world needs it / will pay for it — a check on the seller, complementing this page's market-side rules; only "will they pay" overlaps the [[pain-discovery]] machinery, and the other three quadrants are motivational rather than evidential.
+
+**SOM beats TAM — the same rule from the venture side** ([[2026-07-26-how-to-build-a-billion-dollar-company-2027]], [[oskar-hartmann]], added 2026-07-26; vocabulary defined on [[tam-sam-som]]). Investors love a big TAM, but the start must be a **small market where you can take a meaningful share *now***: "AI agent answering calls for HVAC/plumbers/roofers" beats "AI agents for every profession"; Manifest became a unicorn on **immigration law alone**; Fab.com's peak was $100M on design home goods for a loyal base. His formula — *big market + small winnable sub-market + MVP, not a fantasy product* — is this page's specificity rule restated by a **third independent tradition** (VC/product world, after the US coaching and RU dev-sales schools). That makes narrow-first the vault's most independently-converged claim after the core thesis itself. One nuance he adds that the services sources don't: the narrow segment is *for winning now*, with the big market kept behind it — niche as a beachhead, not a destination.
+
+**Both halves of the pincer.** Note that rules 2 and 3 point the same way as the [[productized-service]] commodity test: the narrower and more domain-loaded the category, the less substitutable it is, and the more [[pricing-from-value]] becomes available. Niche choice is upstream of pricing power.
+
+## Evidence
+
+- Hungry crowd vs. best burger; fitness-coaching saturation example — [[2026-07-17-design-the-perfect-offer]]
+- "Listen to what the market is already asking for" — [[2026-07-17-design-the-perfect-offer]]
+- "Niche is upstream of everything"; the generalist-vs-niched table; stack-marketing mistake — [[2026-06-15-more-clients-dev-agency]] (Tony)
+- "80% is WHO, not WHAT"; "sell to leadership, not implementers"; "go where AI is weak" — [[2026-06-15-rodenko-selling-development-expensively]]
+- "The most important thing is WHO you make the offer to"; "if one bought, others will" — [[2026-06-15-konspekt-aphorisms]]
+- "Shopify dev for fashion brands beats web developer"; niche specificity beats volume — [[2026-06-15-17-ways-first-client]]
+- Pick a target segment before building — [[2026-06-15-making-money-with-ai-2026]]
+- "At $1K+/mo sell to business owners"; the Ikigai supply-side filter — [[2026-07-23-make-my-first-100k-in-month]] ([[dan-martell]])
+- Condensed restatement — [[2026-06-15-selling-development-services-in-the-ai-era]]
+- SOM > TAM; HVAC-agent vs all-professions; Manifest immigration-law unicorn; "big market + small winnable sub-market + MVP" — [[2026-07-26-how-to-build-a-billion-dollar-company-2027]] ([[oskar-hartmann]], third independent tradition)
+
+## Related Pages
+
+- [[pain-discovery]] — what you do once the audience is chosen
+- [[client-acquisition-channels]] — niche is the precondition for any channel
+- [[pricing-from-value]] — the "no money" objection branch is an audience-selection failure
+- [[productized-service]] — the commodity test is the same insight from the offer side
+- [[ai-market-shift]] — AI weakness is what defines the defensible niche
+- [[future-of-engineering-work]] — the compliant-enterprise-harness gap is a niche opportunity
+- [[overview]]
+
+## Contradictions / Uncertainty
+
+- **"It's always the audience" is unfalsifiable as stated.** Combined with "if one person bought, the product is fine", it provides a permanent excuse never to fix the offer. Neither source names the condition under which the offer *is* the problem.
+- The 80/20 WHO-vs-WHAT split is a figure of speech, not a measurement. Uncited.
+- **Tension with [[ai-market-shift]]:** "go where AI is powerless" assumes LLM capability is static. If the AI-weak niche is a moving frontier, a niche chosen on that basis has an unknown shelf life. No sales source addresses this — though [[2026-07-06-sebastian-interview-ai-and-software-engineering]] gives the one concrete example of a durable AI-weak niche (COBOL: no training data) plus a *different* kind of durable niche entirely (the compliant enterprise harness, defended by regulation rather than by AI weakness — see [[future-of-engineering-work]]).
+
+## Next Questions
+
+- What *is* the falsification condition — how many wrong audiences before the offer is the problem?
+- Which industry methodologies are durably AI-weak vs. merely not-yet-covered?
+- Does "sell to leadership" survive in orgs where implementers hold procurement veto?

wiki/concepts/offer-ladder.md

@@ -0,0 +1,65 @@
+# Offer Ladder
+
+#concept #offer-design #pricing
+
+## Summary
+
+A three-tier price structure — entry, core, top — designed **middle-out**: nail the core offer first, then bracket it above and below. A second worked example arrived 2026-07-23 ([[2026-07-23-make-my-first-100k-in-month]], [[dan-martell]]) with an explicit rationale the first lacked: **the flanking tiers are decoys** whose only job is to make the core tier sell. The two examples disagree on ratios, and the two sources are plausibly the same author — treat the structure as one school's recurring pattern, not a law.
+
+`Status: tentative` — two examples, possibly one voice.
+
+## Current Understanding
+
+**The ladder built live on-camera** ([[2026-07-17-design-the-perfect-offer]]):
+
+| 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 |
+
+**Middle-out is the actual insight.** Anchor on the core tier first, then design entry and top around it — it's easier to move a prospect up or down from a defined middle than to build up from scratch. This also composes with the backwards math in [[pricing-from-value]]: the core tier *is* the price you divided your revenue target by, so the ladder is derived from the target rather than guessed.
+
+**The stated bracketing rule** (checklist item 5): entry ≈ 40–50% of core, top ≈ 5× core. Checked against the live example: $444 / $997 = 45% ✓, and $5,000 / $997 ≈ 5× ✓. The rule is arithmetically consistent with the example — but the example is also the only evidence for the rule, so this confirms nothing. It may simply be a description of one ladder.
+
+**Tier shape, not just price.** The structure that varies across tiers isn't only cost but *who does the work and how far it reaches*: entry is done *with* the client once; core is recurring delivery *for* them; top is deployment *across* their org plus training. That progression mirrors the DIY → DWY → DFY ladder in [[productized-service]], from a different source — the one point of cross-source support this page has.
+
+**The second ladder — decoys around the core** ([[2026-07-23-make-my-first-100k-in-month]]):
+
+| Tier | Price | Delivery | Purpose |
+|---|---|---|---|
+| Low — DIY | ½× core ($500/mo) | Playbooks handed over, client executes | Anchors the low end |
+| **Core** | **1× ($1,000/mo)** | **Productized service — you do it** | **The one you sell — 100/month = $100K** |
+| High — DFY | 10× core ($10,000/mo) | Everything managed + team training | Decoy that makes core look like a steal |
+
+Same skeleton as the 07-17 ladder (DIY-ish entry, productized ~$1K/mo core, org-wide top), same DIY→DFY leverage progression across tiers — but this source states outright what the first only implied: *both flanking tiers exist so the middle tier prints*. Under the decoy reading, questions like "do entry buyers ascend?" partly dissolve — the flanks aren't meant to convert, they're priced anchors. Note the ratios differ: entry ½× vs. ~45%, top **10×** vs. **5×**.
+
+## Evidence
+
+- The $444 / $997 / $5,000 ladder table — [[2026-07-17-design-the-perfect-offer]]
+- "Anchor on the core tier first, then design entry and top around it" — [[2026-07-17-design-the-perfect-offer]]
+- "Build a 3-tier ladder around that core (entry ≈ 40–50% of core, top ≈ 5× core)" — checklist item 5, [[2026-07-17-design-the-perfect-offer]]
+- "Middle-out ladder design — nail the core tier, then bracket it above and below" — §8, [[2026-07-17-design-the-perfect-offer]]
+- Indirect support for a *different* ladder (leverage, not price): DIY → DWY → DFY — [[2026-06-15-17-ways-first-client]]
+- Second ladder ($500 / $1,000 / $10,000 monthly), decoy rationale, "sell the core 100× = $100K" — [[2026-07-23-make-my-first-100k-in-month]] ([[dan-martell]])
+
+## Related Pages
+
+- [[pricing-from-value]] — the core tier's price comes from backwards math
+- [[productized-service]] — each rung must be a productized outcome, not a time bucket
+- [[outcome-based-selling]] — tiers should differ by outcome scope, not hours included
+- [[2026-07-17-design-the-perfect-offer]] — the origin
+- [[overview]]
+
+## Contradictions / Uncertainty
+
+- **Two examples, unstable ratios, and possibly one author.** The 07-17 ladder brackets at ~45% / 5×; the 07-23 ladder at 50% / **10×**. The second example doubles the top-tier multiple, so the "rule" wobbles even inside the school that uses it. Worse for independence: the 07-17 speaker is unnamed and plausibly [[dan-martell]] himself (see [[dan-martell]] Contradictions) — if so, this is one person's habit observed twice, not replication. What *is* consistent across both: a ~$1K/mo productized core, a DIY-ish half-price entry, and an org-wide top tier.
+- **The two sources disagree on what the flanks are *for*.** 07-17 treats all three tiers as sellable (entry $444 sessions were sold); 07-23 says the flanks are decoys that exist to be declined. Different theories of the same structure — a real design decision the vault can't settle.
+- The $444 entry tier is a one-off 90-minute session while core and top are monthly recurring — so the "40–50% of core" comparison is between a one-time fee and a monthly one. The ratio is arithmetically tidy but compares unlike units, which weakens it further as a rule.
+- **The rest of the vault argues for *one* package, not a price ladder.** Rodenko, AB Analytics, and Tony all describe a single fixed-price productized offer after 2–3 identical projects ([[productized-service]]); none tiers it into entry/core/top. AB Analytics' DIY→DWY→DFY is a *leverage* progression (who does the work), not three price points of the same service. So the middle-out **price** ladder remains confined to the US coaching school (two examples, possibly one voice). Whether a solo operator should ladder prices at all, or just ship one DFY package, is unresolved — and the independent-source weight still leans toward one package.
+
+## Next Questions
+
+- Does the ladder help or dilute focus before product-market fit? (The other source's advice implies: ship one package first.)
+- Should the entry tier be recurring too, to make the ratio meaningful?
+- What's the actual conversion path — do entry buyers ascend to core, or are they a separate audience?

wiki/concepts/outcome-based-selling.md

@@ -0,0 +1,59 @@
+# Outcome-Based Selling
+
+#concept #offer-design #sales
+
+## Summary
+
+Sell the result the buyer wants, not the deliverables you produce or the hours you spend. Sources across all three traditions converge on this; the Russian distillation pushes it one step further by adding **accountability for the result** as the thing actually being purchased, and [[dan-martell]] adds the time/money/status triad and the five offer elements.
+
+## Current Understanding
+
+The move is a reframe of the same work:
+
+| Deliverable framing | Outcome framing |
+|---|---|
+| "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" |
+| "We develop X on Y stack" | Category named by pain + result |
+
+Nobody wants "a workflow, a dashboard, and an agent" — they want hours of their week back and the business running without them ([[2026-07-17-design-the-perfect-offer]]).
+
+**Accountability is the real product.** The sharpest claim in the vault: *sell the result and accountability for it* — origin [[2026-06-15-rodenko-selling-development-expensively]] ("sell SOLUTIONS, not work" in [[2026-06-15-konspekt-aphorisms]]). Willing to take accountability → the AI era enriches you; unwilling → a 12-month death sentence. This explains *why* outcome framing commands a premium — the seller is absorbing risk the buyer would otherwise carry. It also sets the boundary: an outcome you can't actually be accountable for is not an offer, it's a liability. No source addresses what happens when a guaranteed outcome isn't delivered.
+
+**The supply-side twin: product ownership.** Promising an outcome is only survivable if the delivery culture actually *owns* outcomes rather than tickets — see [[product-ownership]] ([[sebastian]]'s "no one ever needed a programmer; people have problems you solve"). Outcome-selling and outcome-owning are the sales-side and work-side of the same principle.
+
+**What outcomes are made of — time, money, status** ([[2026-07-23-make-my-first-100k-in-month]], [[dan-martell]]): people pay for exactly three things — buy back my hours (time), make/save me money (the easiest sell: pay money → get more money), or raise my standing (status — routinely ignored and underpriced). A useful taxonomy of *which* outcome to promise; at $1K+/mo he aims all three at **business owners**, who feel each and decide fast. "Features tell; outcomes sell" — don't say "I do marketing for $1K/month," say "I'll get you 10 new clients a month."
+
+**The five offer elements** (same source): every offer states an **outcome**, a **deliverable** (what shows up weekly/monthly), an **investment** (never "cost"), a **risk reversal** — a specific guarantee ("10 leads/month," "save 10 hours/week") — and **urgency** (limited slots, deposit to lock in). The risk-reversal element is this vault's accountability claim operationalized as a checklist item; note it inherits the same gap flagged below — a guarantee is named, its mechanics never are.
+
+**Outcomes must be countable.** The working examples are all numeric: 10 hrs/week (= 40 hrs/month, recurring); "spend 10× less on X". This connects to the tactical minimum in [[2026-06-15-selling-development-services-in-the-ai-era]] — 2–3 case studies with Before/After **numbers**, "without them you have nothing to sell a result with." An outcome without a number is a slogan.
+
+## Evidence
+
+- "Sell outcomes, not deliverables" — the entire §8 cross-cutting principles of [[2026-07-17-design-the-perfect-offer]]
+- The buy-back-10-hours reframe and its 40 hrs/month math — [[2026-07-17-design-the-perfect-offer]]
+- **Primary:** "sell result + accountability, not hours"; "12-month death sentence" — [[2026-06-15-rodenko-selling-development-expensively]]
+- "Sell SOLUTIONS, not work"; "2–3 Before/After case studies… without them you have nothing to sell a result with" — [[2026-06-15-konspekt-aphorisms]]
+- "Benefit → then feature" (польза → потом фича) — [[2026-06-15-making-money-with-ai-2026]]
+- Time/money/status triad; "features tell, outcomes sell"; the five offer elements incl. risk reversal — [[2026-07-23-make-my-first-100k-in-month]] ([[dan-martell]])
+- Supply-side twin: "no one ever needed a programmer; people have problems you solve" — [[2026-07-06-sebastian-interview-ai-and-software-engineering]]
+- Condensed restatement — [[2026-06-15-selling-development-services-in-the-ai-era]]
+
+## Related Pages
+
+- [[product-ownership]] — the supply-side twin: owning outcomes, not tickets
+- [[productized-service]] — the vehicle that makes outcome-selling repeatable
+- [[pricing-from-value]] — an outcome is what price gets justified against
+- [[pain-discovery]] — the outcome is the inverse of the bottleneck you find
+- [[methodology-as-moat]] — the method is how you can promise the outcome credibly
+- [[overview]]
+
+## Contradictions / Uncertainty
+
+- **Guarantee mechanics are undefined.** Both sources use "guarantee" freely ("I guarantee 10 hours/week", "if we guaranteed the result"), neither specifies refund, remediation, or measurement. `Status: tentative` — the word may be doing rhetorical rather than contractual work.
+- How is "10 hours/week bought back" actually measured and agreed on with the client? Unaddressed by both.
+
+## Next Questions
+
+- What does a real guarantee clause look like in a $1K/mo productized contract?
+- Which outcomes are safely promisable vs. dependent on client behavior (e.g. the client must actually adopt the workflow)?
+- How do you sell an outcome for work whose value is *avoided* cost (security, reliability) where the counterfactual is unobservable?

wiki/concepts/pain-discovery.md

@@ -0,0 +1,66 @@
+# Pain Discovery
+
+#concept #sales
+
+## Summary
+
+The offer is found by interrogating the market, not by introspection. Sources across all three traditions describe the same loop — find the bottleneck, name it back as the offer — while the distillation adds a qualification filter that decides whether a pain is worth selling to at all, and [[oskar-hartmann]] adds the acute-pain test (revealed preference at its purest).
+
+## Current Understanding
+
+**The loop:** talk to prospects → find the bottleneck → name it back to them as the offer ([[2026-07-17-design-the-perfect-offer]]). Worked example: "business owners aren't using AI → they'd want workflow automation → the offer is a calendar audit that identifies 3 workflows and buys back 10 hrs/week." The prescribed question is *"what's your biggest bottleneck around [your domain]?"*, asked of 5–10 prospects in the niche.
+
+**Watch spend, not talk** — origin: [[2026-06-15-rodenko-selling-development-expensively]] (the Zendesk motion). What people say they want and what they already pay for are different data. Find an operational cost line, then:
+
+> *"How much do you spend on X?"* → *"And if you spent 10× less — would we talk?"*
+
+The insurance built into the 10× ask: even if you're off by half, you still delivered 5×. This is a strictly better opener than the bottleneck question, because a budget line is evidence and a stated bottleneck is an opinion. Rodenko maps the biggest cost line by company type: service firms → payroll; manufacturing → materials; narrow industries → sector-specific SaaS.
+
+**"Pain with money" — the four-part filter.** A pain qualifies only if *all four* hold:
+
+1. It recurs often.
+2. It costs the business money.
+3. It's already being solved with duct-tape workarounds.
+4. The founder understands its value.
+
+Missing any → not a client. **Origin:** the B2B pipeline in [[2026-06-15-making-money-with-ai-2026]] (the distillation inherited it). Criterion 3 is the subtle one: an existing workaround is proof of both budget and felt pain, whereas an unsolved problem may simply not matter enough. Criterion 4 is why [[niche-selection]] says sell to leadership — the same pain fails this filter when pitched at the wrong seat. That same source adds the discovery motion around it: find *many* companies → DM 3–4 questions about manual tasks (~10% reply) → validate the pain has money before building.
+
+**The acute-pain test — revealed preference at its purest** ([[2026-07-26-main-principle-of-successful-business]], [[oskar-hartmann]], added 2026-07-26): *"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."* His exemplar: hospitals — 1.5-hour waits, zero good reviews, you pay anyway. When pain is that acute, people pay **for the concept**, before polish exists — which is what makes [[sell-before-build]]'s pre-payment tests possible at all. This extends the "watch spend, not talk" line to its endpoint: the strongest qualification isn't what they spend on, it's what they *keep paying for despite bad service*. His targeting question sharpens the filter further: who — **by name** — is the smallest group with the most acute pain? (A SOM statement; see [[tam-sam-som]].)
+
+**Your old clients are the warmest pain data.** Call your 3–5 best and ask *"what result were you paying me to get?"* — pointedly **not** "why did you choose us?", which only returns "good team" ([[2026-06-15-rodenko-selling-development-expensively]]; echoed in [[2026-06-15-konspekt-aphorisms]]: "the money is with your old clients"). The first question recovers the outcome you were actually bought for, which is the raw material for [[outcome-based-selling]]. The vault's most immediately actionable item.
+
+**AI as a free diagnostic** — the 30-day giveaway sorts prospects by their reaction; see [[ai-market-shift]].
+
+**Naming the pain in the buyer's own words (content-side).** A distinct application of the same skill: [[2026-07-18-information-is-free-implementation-is-paid]] mass-produces *nuanced, observable* pains with an AI prompt — *"Make a list of 10 nuanced but observable problems business owners between \$500K and \$2M in revenue have around [hot button]."* The modifiers do the work: "nuanced but observable" forces specifics over clichés, and the revenue band anchors to the ICP, so the output "describes the viewer's world better than they can describe it themselves." This is pain articulation for *marketing* (open a video on the pain, then teach the fix), not live qualification — but it's the same core move as the bottleneck question and the old-client question: surface the pain, name it back. See [[information-vs-implementation]].
+
+## Evidence
+
+- "Talk to prospects, find the bottleneck, name it back to them as the offer" + the calendar-audit worked example — [[2026-07-17-design-the-perfect-offer]]
+- "Ask 5–10 prospects: what's your biggest bottleneck around [your domain]?" — checklist item 3, [[2026-07-17-design-the-perfect-offer]]
+- **Primary (spend/10× opener, old-client script, cost-line-by-company-type):** [[2026-06-15-rodenko-selling-development-expensively]]
+- **Primary (four-part "pain with money" filter + the DM-many-companies motion):** [[2026-06-15-making-money-with-ai-2026]]
+- "The money is with your old clients" — [[2026-06-15-konspekt-aphorisms]]
+- The nuanced-observable-pain AI prompt (content-side pain articulation) — [[2026-07-18-information-is-free-implementation-is-paid]]
+- The acute-pain test (hospitals; "pays even when everything is bad"); smallest-group-by-name targeting — [[2026-07-26-main-principle-of-successful-business]] ([[oskar-hartmann]])
+- Condensed restatement of all of the above — [[2026-06-15-selling-development-services-in-the-ai-era]]
+
+## Related Pages
+
+- [[niche-selection]] — choose the audience before interrogating it
+- [[outcome-based-selling]] — the discovered pain, inverted, becomes the outcome
+- [[productized-service]] — repeated identical pains are the productization trigger
+- [[ai-market-shift]] — the AI giveaway as a qualification instrument
+- [[information-vs-implementation]] — the same pain-naming skill, pointed at content instead of a sales call
+- [[sell-before-build]] — downstream: the paid experiment that confirms what discovery suggested
+- [[overview]]
+
+## Contradictions / Uncertainty
+
+- **Stated vs. revealed preference.** The video's method (ask about bottlenecks) is exactly the kind of self-report the distillation warns against ("watch what they spend on, not what they say"). Not a flat contradiction — the video's example does end at a budget-relevant outcome — but the distillation's method is the more rigorous of the two. `Status: tentative` on the bottleneck question as a standalone tool.
+- The 10× framing assumes the cost line is compressible by an order of magnitude. Neither source discusses what to do when it isn't.
+
+## Next Questions
+
+- Which operational cost lines are actually 10× compressible with AI, and which just look it?
+- How do you run the "what result were you paying me for?" call without seeding the answer you want?
+- What replaces old-client mining for someone with no past clients?

wiki/concepts/partnerships.md

@@ -0,0 +1,76 @@
+# Partnerships
+
+#concept #sales #marketing
+
+## Summary
+
+The third lever of [[marketing-system]] — **someone with existing credibility walks you into their customer base** — and, since 2026-07-22, the only lever the vault holds a worked mechanism for ([[2026-07-22-stop-cold-calling-do-this-instead]], [[dan-martell]]). The core asset is **borrowed credibility**: the buyer arrives pre-sold because a party they already trust made the introduction, which collapses the friction that makes cold enterprise outbound brutal (procurement, meeting access, closing before the org reshuffles). The claim that earns it *lever* status: unlike client [[referrals]], partner flow **has a throttle** — you cannot make past clients refer more, but you *can* recruit more partners. The mechanism remains single-author, but since 2026-07-26 the page holds a **second, independent voice** — [[oskar-hartmann]] — who is adversarial on partner-as-savior hope (results "100–200× below expectations") while converging on the one structural rule Martell also states: many partners, never one gatekeeper. `Status: tentative` on the mechanism; the *warning* is now two-voice.
+
+## Current Understanding
+
+**The mechanism — borrowed credibility.** Enterprise buyers filter on trust, and cold outreach carries none. A partner who already holds the account (a system integrator with a multi-million-dollar contract) transfers theirs in one introduction. Claimed economics: $95K contracts three weeks post-intro; one partner → seven pharma companies in a single motion. Both sides win — the partner is paid not in commission but in **account value** (a vendor who delivers strengthens the partner's own position) — which is why the introductions repeat.
+
+**The system, not the intro.** The failure mode is treating a good partner as luck. The prescribed move is to reverse-engineer the one that worked and recruit the *archetype*:
+
+1. Where did we actually meet? (channel)
+2. What was true about them — role, company type, buyer profile? (archetype)
+3. How many more like them exist on that same channel? (market of partners)
+4. Can I create content specifically for that audience?
+5. Can I use their success story to attract more like them?
+6. Can I structure my offer so it's stupid-easy for them to say yes?
+
+Then work it as its own funnel: find who inside the partner org decides "who do we bring in" → attend **their** events, not your peers' events → win the individual first → deliver → let the wins recycle you into more accounts. *"Ten good partners can replace an outbound sales team."* Don't optimize the deal; optimize the partner-acquisition system.
+
+**The independent second voice — partner hope is a startup-killer** ([[2026-07-26-how-to-build-a-billion-dollar-company-2027]], [[oskar-hartmann]], added 2026-07-26). The first non-Martell voice on this page, and it arrives mostly as a warning. His claims: **partners almost always disappoint** — a bank already has 15 products of its own it can't sell to plan, plus 30 partner products; yours is lost in that pile ("you are their 46th priority"). If a single partner is the gatekeeper to the channel, they take all the margin. He reports watching companies enter "huge partner channels" and land **100–200× below expectations**. His own history sharpens rather than contradicts it: his first store grew to $20M on *one* partner deal (10% of revenue, open books) — which he files as a **one-off boost, not a channel**, because partner management changes, audits arrive, terms flip, and by then you must be able to stand in open auctions on your own statistics.
+
+**Where the two voices actually land relative to each other:**
+
+- **Convergent on structure:** Hartmann's condition for partnerships working — **many partners** (never one gatekeeper), product sitting naturally on top of their services — is Martell's "recruit the archetype, don't treasure the one intro" stated from the failure side. Both reject the single-partner bet; neither rejects the many-partner system.
+- **Adversarial on posture:** Martell sells the lever as the *shortcut* into enterprise; Hartmann's through-principle is "partners are a bad **first** channel." The reconciliation writes itself but is the vault's, not either source's: partner *intros as one recruited channel among others* (Martell's actual system) survive both voices; *partnership as the salvation plan* survives neither.
+- **Scope split:** Martell's partner refers you into accounts you then close and serve; Hartmann's failure cases are partners *as the distribution channel itself* (the bank sells your product for you). The disappointment mechanism (their priorities, their shelf, their margin) applies with full force to the second and only partially to the first — a referring partner spends an introduction, not shelf space.
+
+**Where it sits relative to the vault's other machinery:**
+
+- **vs. [[referrals]]** — same output (a warm, trust-carrying intro), opposite control structure. A client referral is *derived* demand: it requires a prior satisfied client and cannot be turned up. A partner intro is *recruited* demand: the input (partner count) is under your control. This is the answer to the referrals page's long-standing question of whether a throttled referral variant exists.
+- **vs. [[relationships-as-moat]]** — partner *acquisition* is exactly Sebastian's motion (show up at events, in person, win an individual through repeated contact), aimed at partners instead of buyers. The convergence is notable because it comes from the author of the vault's most content-bullish source: even the content pole prescribes **relationship-mediated entry for enterprise**. The difference is only whose trust opens the door — trust you *built* (Sebastian) vs. trust you *borrow* (Martell).
+- **vs. [[marketing-system]]'s one-to-many framing** — this lever is really **one-to-few-to-many**: relational one-to-one work at the partner layer, leverage at the account layer. The vault's earlier characterization of all three levers as one-to-many motions is qualified accordingly.
+- **vs. cold outbound** — the title says "stop cold calling," but the playbook still opens with approaching a stranger. Outbound isn't eliminated; it's **redirected at a smaller, higher-leverage audience** where one yes multiplies.
+- **Fit for the technical operator.** [[marketing-system]] flagged partnerships as possibly the highest-fit lever for a founder who dislikes publishing — this source supports that: the required skill is targeted relationship-building (networking *with a criterion*, the same motion [[dmitry-rodenko]] prescribes for one's own network), not becoming a content creator.
+
+**Scope, per the source:** mid-market/enterprise, agencies, B2B services, ~$10K+ ACV. Not low-ticket DTC. The exemplar partner class — system integrators (Tata, IBM Global Services) — exists only in enterprise ecosystems; the SMB analogue is unnamed.
+
+## Evidence
+
+- Entire mechanism (borrowed credibility, both-win economics, reverse-engineering questions, playbook, ten-partners claim, scope) — [[2026-07-22-stop-cold-calling-do-this-instead]], [[dan-martell]] (single source, anecdote-grade)
+- "Strategic partnerships" as a Tier-3 out-of-the-box channel and "referral partners" as a Tier-1 LinkedIn motion — [[2026-06-15-17-ways-first-client]] (independent naming of the channel, no mechanism)
+- Cold outreach doesn't close enterprise — independently reached by [[sebastian]] ("Big zero"), on different grounds ([[2026-07-06-sebastian-interview-ai-and-software-engineering]])
+- Partner-referrals escape the cold-start problem — already noted on [[referrals]] before this source arrived
+- **Counter-position:** partners almost always disappoint (46th-priority problem, gatekeeper margin capture, 100–200× shortfall); works only with many partners; one partner deal = boost, not channel — [[2026-07-26-how-to-build-a-billion-dollar-company-2027]] ([[oskar-hartmann]], independent of Martell)
+
+## Related Pages
+
+- [[marketing-system]] — the taxonomy this lever belongs to
+- [[referrals]] — the unthrottled sibling; the throttle distinction lives on both pages
+- [[client-acquisition-channels]] — where this sits among all channels; the anti-cold-outbound position
+- [[relationships-as-moat]] — the borrowed-vs-built trust comparison
+- [[dan-martell]] — the voice behind the mechanism
+- [[oskar-hartmann]] — the independent counter-voice on partner hope
+- [[sales-discipline]] — pick-one-commit-fully, restated here
+- [[eugene]] — the operator this lever may fit best
+- [[overview]]
+
+## Contradictions / Uncertainty
+
+- `Status: tentative` — the mechanism is **single-source and anecdote-grade**: the author's own war stories ($95K, 7 pharma companies), no cohort, no failure cases, told by someone selling the discipline. The NJ pharma story is survivor-selected; failed partner plays are invisible. **Update 2026-07-26:** the missing failure cases now exist — [[oskar-hartmann]] supplies them (100–200× shortfalls, gatekeeper margin capture), though as stage war stories of the same evidentiary grade, from the *distribution*-partnership scope rather than the referring-partner scope.
+- **Two voices disagree on when the lever is playable.** Martell: the shortcut into enterprise. Hartmann: "partners are a bad *first* channel." They converge only on the many-partner structure. Whether a *referring* partner (Martell's kind) escapes Hartmann's disappointment mechanism — because an intro costs the partner nothing, unlike shelf space — is the vault's own reconciliation, `tentative`, stated in Current Understanding.
+- **The entry bar is unstated and probably decisive.** The anecdotes come from a funded SaaS founder. Whether a Tata-class integrator takes any meeting with a solo unknown is exactly the question the source skips — and the answer determines whether this lever is available to the vault's owner at all.
+- **Internal tension with the title.** "Stop cold calling" is delivered alongside a playbook whose step 3 is introducing yourself to a stranger at an event. The honest version of the claim is "aim your outbound at partners, not buyers" — redirection, not abolition.
+- **Partner intros are still referral-shaped at the account level.** If the partner relationship goes quiet, the flow stops — the throttle argument holds only while partner *recruitment* keeps running. The source doesn't address partner churn.
+- **The same author disfavors this lever's deal size at the start (2026-07-23).** In [[2026-07-23-make-my-first-100k-in-month]] Martell "personally dislikes" the 10-customers-×-$10K model — the exact ~$10K+ ACV territory this playbook is scoped to — and steers $0 founders to 100×$1K SMB instead. Read together: partnerships is his lever for an *established* B2B operator, not his recommended opening game. Stage-dependent, but neither clip draws the line; logged on [[dan-martell]].
+
+## Next Questions
+
+- What do smaller-scale partners get paid — account value only, or explicit rev-share — and does an unpaid-alignment play survive outside the integrator-with-a-huge-contract setting?
+- What is the **SMB partner archetype** for dev services: agencies without dev capacity, MSPs, accountants, hardware vendors? (For [[eugene]]'s computer-vision/embedded work: industrial-equipment vendors and machine-builder integrators are the obvious candidates — untested inference.)
+- Minimum credibility bar: what does a partner need to see (case study, niche authority, a delivered project inside one of their accounts?) before the first walk-in?
+- Does the reverse-engineering system survive contact with N=1 luck — i.e., what if the first good partner is genuinely unrepresentative of a recruitable archetype?

wiki/concepts/pricing-from-value.md

@@ -0,0 +1,67 @@
+# Pricing From Value
+
+#concept #pricing
+
+## Summary
+
+Price against the value of the outcome to the buyer, never against your cost or your competitors' rates. Both sources agree that rate competition is terminal; each contributes a distinct tool — a backwards-math model for setting price, and an objection test for defending it.
+
+## Current Understanding
+
+**Backwards math sets the number** ([[2026-07-17-design-the-perfect-offer]]): pick the monthly revenue target → divide by price → that's the client count. $10,000 ÷ $1,000/mo = 10 clients. If the count feels unrealistic, raise the price rather than chase volume. Restated at larger scale in [[2026-07-23-make-my-first-100k-in-month]] as the **money map**: five price×count routes to $100K/mo, of which only **~100 × ~$1K/mo** is judged sane — 1×$100K is concentration risk, 10×$10K "heavy per-deal," 1,000×$100 too many closes, 10,000×$10 unreachable. Same floor ($1K/mo minimum), plus a stated ceiling for a starting operator (**below $10K/mo** — "every conversation should be worth having") and a language rule (the price is an *investment*, never a *cost*).
+
+**The $1,000/mo floor**, with two justifications:
+
+1. *Buyer-side:* for AI/business services, one new client is worth ~$1K to the buyer — worst case they recoup the fee with a single win.
+2. *Seller-side:* below ~$100/mo there's no margin to fund the work that would make the service good. **Pricing constrains quality**, so a low price is self-fulfilling.
+
+The seller-side argument is the more portable one; the buyer-side "one client ≈ $1K" figure is domain-bound and plausibly fails where buyer LTV is far below or above $1K.
+
+**"Expensive" doesn't exist — "I don't see what for" exists** — origin: [[2026-06-15-rodenko-selling-development-expensively]] (condensed in the distillation). The diagnostic:
+
+> *"If we guaranteed the result — is price still the problem?"*
+> - **Yes** → they have no money. (Wrong buyer — see [[niche-selection]].)
+> - **No** → they never trusted the value. (Your problem, and fixable.)
+
+This is the most operationally useful item in the vault: it converts a vague objection into a binary about which of two different problems you have.
+
+**The Zendesk story makes value pricing concrete** ([[2026-06-15-rodenko-selling-development-expensively]]): a client paying $30k/mo for Zendesk was sold a $2k/mo custom solution; the $100k project paid back in ~4 months. The price wasn't argued down — it was anchored to a cost line the buyer already felt. The outreach reduces to "how much do you spend on X?" → "and if it were 10× less?" (see [[pain-discovery]]). Value pricing works when the value is a number the buyer already pays.
+
+**Price as a competitive weapon = bankruptcy** ([[2026-06-15-selling-development-services-in-the-ai-era]]). With a ~$200/mo AI substitute at the bottom of the market, undercutting has no floor to stand on. The escape is not a better rate but a different category — see [[productized-service]] (commodity test) and [[niche-selection]].
+
+**Pricing power is the PMF test** ([[2026-07-26-how-to-build-a-billion-dollar-company-2027]], [[oskar-hartmann]], added 2026-07-26): if you **raise prices and the customer flow doesn't fall**, you have Product-Market Fit; "whoever sells too cheap has no PMF." And if you cannot set your price at all — a marketplace sets it, discounts aren't yours to give — "you're not an entrepreneur, you're in a simulation of entrepreneurship." This gives the sell-dear school something it lacked: a *test* with a direction of causation. The vault's prior tools diagnose a price objection after the fact (guarantee test); this one uses price as the *probe* — raise it and watch. His companion diagnosis — **most entrepreneurs sell below the real, full cost** (forgotten lines: distribution, repeat acquisition, amortization, write-offs — see [[unit-economics]]) — reaches "sell dear" from the cost side rather than the value side. Notably, this is the first voice from *outside* the coaching/dev-sales schools (a VC/product investor) to join the position, which is worth more to the page's confidence than a fifth in-school restatement.
+
+**Anchoring.** Design the core tier first, then bracket it — see [[offer-ladder]]. A second anchor sits *upstream* of the offer: [[2026-07-18-information-is-free-implementation-is-paid]] argues that 50 free expert videos make a $997 offer feel *cheap* by the time the buyer reaches it — the giveaway pre-sets the reference price before any pitch. See [[information-vs-implementation]].
+
+## Evidence
+
+- Backwards math table (price floor / why $1K / client math) — [[2026-07-17-design-the-perfect-offer]]
+- The money map (five routes to $100K/mo; $1K floor, sub-$10K ceiling; "investment" language) — [[2026-07-23-make-my-first-100k-in-month]] ([[dan-martell]])
+- "Under $100/mo there's no margin to fund the work that would make the service any good" — [[2026-07-17-design-the-perfect-offer]]
+- **Primary:** the guarantee test, "expensive doesn't exist," the Zendesk $30k→$2k story, and "price as a weapon = bankruptcy" — [[2026-06-15-rodenko-selling-development-expensively]] (condensed in [[2026-06-15-selling-development-services-in-the-ai-era]])
+- Convergent: "price as incentive devalues you permanently… fastest path to bankruptcy" — [[2026-06-15-more-clients-dev-agency]] (Tony)
+- Solution margin 30–50% vs. staff-aug price race — [[solution-vs-staff-augmentation]]
+- Pricing power as PMF test; "sells too cheap = no PMF"; the full-cost diagnosis; "simulation of entrepreneurship" — [[2026-07-26-how-to-build-a-billion-dollar-company-2027]] ([[oskar-hartmann]], independent tradition)
+
+## Related Pages
+
+- [[outcome-based-selling]] — the value that price is measured against
+- [[offer-ladder]] — how the price points get arranged
+- [[productized-service]] — what makes value pricing structurally possible
+- [[niche-selection]] — the "no money" branch of the objection test is an audience problem
+- [[solution-vs-staff-augmentation]] — the margin consequence of the model choice
+- [[information-vs-implementation]] — free content as the upstream anchor that makes the offer feel cheap
+- [[unit-economics]] — the cost side of the same price: what the "sell dear" spread must actually cover
+- [[overview]]
+
+## Contradictions / Uncertainty
+
+- **The $1K floor is asserted, not derived — and its "second" assertion may be the same speaker.** It originates in one domain (AI services for small business), and its 2026-07-23 restatement is [[dan-martell]], who is plausibly also the unnamed 07-17 speaker (see [[dan-martell]]) — if so, the floor has been stated twice by one person, not confirmed. `Status: tentative` outside that context.
+- **Currency and market are unstated.** The video reasons in USD for a US-ish SMB market; the Russian distillation names a ~$200/mo AI substitute without a market. Whether the $1K floor transfers across markets is untested.
+- No source disagrees on pricing — four converge from the "sell dear" school (Rodenko, Tony, the video, the distillation), and since 2026-07-26 a fifth from **outside** it ([[oskar-hartmann]], VC/product tradition — pricing power test, full-cost floor). The out-of-school voice upgrades this from one coherent viewpoint to a genuine cross-tradition convergence — but all five are still advocacy; the vault has no adversarial view of value pricing (no documented case where raising prices *did* collapse the flow of a viable business).
+
+## Next Questions
+
+- What is the actual floor in the user's own market and currency?
+- How do you price when buyer LTV is *far above* $1K — does the "one client recoups it" logic then argue for a much higher floor?
+- What does the guarantee test do with a buyer who says "yes, still too expensive" but demonstrably *has* money? (Neither branch fits.)

wiki/concepts/product-ownership.md

@@ -0,0 +1,43 @@
+# Product Ownership
+
+#concept #ai
+
+## Summary
+
+The durable human skill once AI writes the code: owning the *outcome a user actually experiences*, not the ticket you were handed. From [[2026-07-06-sebastian-interview-ai-and-software-engineering]]. It is the supply-side twin of [[outcome-based-selling]] — the same "outcomes, not deliverables" principle, seen from inside the engineering work rather than the sale.
+
+## Current Understanding
+
+**Ownership = putting yourself in the user's shoes** and understanding what they'll expect — a mindset/personality trait, not a task list. The reframe: stop thinking *"what needs to be done"* (tickets); start thinking *"what problem needs to be solved."* "No one ever needed a programmer… people have problems that you are solving."
+
+**The profile-picture story** (the whole idea in one anecdote): an engineer implemented "change your photo," ticked every acceptance criterion, and shipped it *ugly* — the photo visible in the corner — because they never looked at the actual result. Meeting the spec is not owning the outcome.
+
+**Why AI raises the stakes.** When code is nearly free, acceptance-criteria-following is exactly what the AI does; the human's remaining value is judging whether the result is actually *good* for the user. Sebastian's sharp version: if you don't understand what to build, "you will simply not be an engineer anymore" — or you get closer to the product and the software gets *better* product-wise (if not always technically). This connects to [[seniority-and-ai]] (the senior's judgment is what catches "spec met, outcome bad") and to [[relationships-as-moat]] (understanding the client's real problem is the same skill that wins trust).
+
+**For a services business** this is the through-line to the sales side: [[outcome-based-selling]] can only promise an outcome if the delivery culture actually owns outcomes. Ownership is what makes an outcome guarantee survivable rather than reckless.
+
+## Evidence
+
+- "No one ever needed a programmer… people have problems that you are solving." — [[2026-07-06-sebastian-interview-ai-and-software-engineering]]
+- The profile-picture story (spec met, result ugly, never looked) — same source
+- "Stop thinking what needs to be done; start thinking what problem needs to be solved." — same source
+- Move-up-the-value-chain conclusion: from "produce the solution" to "understand and frame the problem, then direct and verify the AI." — same source
+
+## Related Pages
+
+- [[outcome-based-selling]] — the demand-side twin (sell outcomes)
+- [[seniority-and-ai]] — judgment as the senior's product; ownership is part of it
+- [[future-of-engineering-work]] — the role shift from coder to problem-owner
+- [[relationships-as-moat]] — understanding the client's problem is the shared skill
+- [[overview]]
+
+## Contradictions / Uncertainty
+
+- Single-source (the interview) and framed as a personality trait — the source offers no method to *teach* ownership, only to recognize its absence. `Status: tentative` as a trainable skill vs an innate trait.
+- "The software gets better product-wise, if not always technically" concedes a real tradeoff (product-owner engineers may ship technically worse code) that the source doesn't resolve.
+
+## Next Questions
+
+- Can ownership be trained/hired for, or only selected? What interview signal reveals it?
+- Where's the line between "own the outcome" and scope creep, when the AI makes gold-plating cheap?
+- Does product-owner-engineering degrade technical quality enough to matter in regulated/high-liability work?

wiki/concepts/productized-service.md

@@ -0,0 +1,74 @@
+# Productized Service
+
+#concept #offer-design
+
+## Summary
+
+Selling a named, fixed-scope, fixed-price outcome delivered by a repeatable method — instead of selling your hours to be spent however the client directs. Nearly every source in this vault treats productization as the central move of a service business, and all frame the alternative (custom hourly work) as economically fatal. [[2026-06-15-17-ways-first-client]] (AB Analytics) calls it "the single biggest change to his client acquisition."
+
+## Current Understanding
+
+A productized service keeps the same underlying delivery work but changes what is *sold*: an outcome with a method behind it, rather than labor with a rate attached.
+
+**Why the hourly model fails**, per the two sources' distinct arguments:
+
+- *Margin argument:* ~90% of service businesses sell time; netted out per real hour, owners earn below minimum wage — "could make more cash working at McDonald's" ([[2026-07-17-design-the-perfect-offer]]).
+- *Substitution argument:* the buyer now has a ~$200/mo AI alternative, so competing on rate zeroes the margin ([[2026-06-15-selling-development-services-in-the-ai-era]]). *(The substitute premise is now empirically contested — [[ai-productivity-evidence]] finds AI's measured effect modest and uneven; the margin argument above stands on its own regardless.)*
+
+These are different arguments for the same conclusion, arrived at from different traditions — which is the main reason to hold this concept with confidence.
+
+**When to productize.** The two sources answer differently and the difference is practical:
+
+| Source | Trigger | Implied posture |
+|---|---|---|
+| [[2026-07-17-design-the-perfect-offer]] · [[2026-07-23-make-my-first-100k-in-month]] | Immediately — derive the offer from a revenue target and market conversations, sell it, *then* build delivery ("do the marketing before you build the thing") | Offer-first |
+| [[2026-06-15-rodenko-selling-development-expensively]] · [[2026-06-15-17-ways-first-client]] | After **2–3 identical projects**, then fix price, fix scope, name the package | Delivery-first |
+
+The delivery-first trigger is the more conservative and more defensible one, and it remains the majority *independent* view (Rodenko, AB Analytics, Tony all say productization *follows* niche/repetition): you can only fix a scope you have actually shipped repeatedly. The offer-first camp gained a second source on 2026-07-23 — [[dan-martell]]'s $100K blueprint, whose whole thesis is sequence (offer → demand → close → *only then* build), backed by his one before/after pair (product-first Maritime Vacation died; marketing-first Flowtown didn't) — but the 07-17 source is plausibly the same author (see [[dan-martell]]), so the camp may still be one voice. Reconciliation: *productize the offer early, productize the delivery contract only once the work repeats.* `Status: tentative` — this is synthesis, not a claim any source makes.
+
+**The format triage** ([[2026-07-23-make-my-first-100k-in-month]]) — the sharpest statement of *why* productized service is the starting format: custom services sell hours (no leverage); products (apps, SaaS, courses) are expensive, slow, and risky to build first; a productized service prices like a product while needing nothing built — and **customer cash funds the eventual product**. The productized service is not the end state but the bridge to one.
+
+**Pre-sell before building — now three traditions.** Martell's mechanic: landing page + waitlist before a line of code; offer a **$50 "top of the waitlist"** slot; money in = validated demand *plus* build capital, no money = don't build. This is the same discipline [[2026-06-15-making-money-with-ai-2026]] states from the RU side ("validate market and pain before writing code"; "most AI projects die from idea → code → launch") — with the useful addition that the validation signal is **paid**, not verbal. **Since 2026-07-26 a third tradition supplies the full toolkit:** [[oskar-hartmann]]'s "sell first, then build" ([[2026-07-26-main-principle-of-successful-business]]) — signal hierarchy (click < waitlist < payment < **pre-payment**), cheap-experiment menu (AI-mockup blast, payment-screen tests, Wizard-of-Oz manual delivery for the first 10 clients), and the sharpened bar: an *unpaid* waitlist doesn't count, which makes Martell's paid-slot variant the load-bearing detail. The discipline now has its own page — [[sell-before-build]].
+
+**The leverage ladder** (DIY → DWY → DFY): Done-For-You is the highest-leverage rung — primary source [[2026-06-15-17-ways-first-client]] (echoed by the distillation). This is about *who does the work*; it is a different axis from the price ladder in [[offer-ladder]], which is about *how much is done*.
+
+**Build fast, benefit first.** [[2026-06-15-making-money-with-ai-2026]]: MVP in **7–14 days**, usefulness over features, and templatize repeated solutions into a reusable "library." Validating market and pain *before* writing code is the whole discipline — "most AI projects die from idea → code → launch."
+
+**The commodity test.** Remove the word "development" and your stack name from the offer. If nothing remains, you're a commodity — the category must be pain + result, not technology ([[2026-06-15-rodenko-selling-development-expensively]]). Tony's version: stop marketing the stack ("excellent .NET developer"), target the audience the stack implies ([[2026-06-15-more-clients-dev-agency]]).
+
+**Team size is no longer the productization signal.** A productized shop can be small: a 4-person squad at ~$7M/yr ([[2026-06-15-rodenko-selling-development-expensively]]) or a solo founder at $293k/mo ([[2026-06-15-making-money-with-ai-2026]]) — see [[future-of-engineering-work]].
+
+## Evidence
+
+- "Productize — same delivery, but framed and sold as a specific outcome with a repeatable method" — [[2026-07-17-design-the-perfect-offer]]
+- "~90% of service businesses get paid for time, not outcomes"; owners net below minimum wage — [[2026-07-17-design-the-perfect-offer]]
+- "Hourly development is dead"; ~$200/mo AI alternative; commodity test; "category = pain + result"; productize after 2–3 identical projects — [[2026-06-15-rodenko-selling-development-expensively]]
+- DIY → DWY → DFY as the leverage ladder and "single biggest change to client acquisition" — [[2026-06-15-17-ways-first-client]]
+- Niche → productization → team scaling; don't market the stack — [[2026-06-15-more-clients-dev-agency]]
+- Benefit before feature; MVP in 7–14 days; validate before coding; templatize into a library — [[2026-06-15-making-money-with-ai-2026]]
+- Format triage (custom/product/productized), "customer cash funds the product," marketing-before-building, $50 paid-waitlist validation — [[2026-07-23-make-my-first-100k-in-month]] ([[dan-martell]])
+- Condensed restatement of the above — [[2026-06-15-selling-development-services-in-the-ai-era]]
+
+## Related Pages
+
+- [[outcome-based-selling]] — what a productized offer sells
+- [[sell-before-build]] — the validation discipline that precedes packaging (signal hierarchy, experiment toolkit)
+- [[offer-ladder]] — how productized offers get tiered
+- [[methodology-as-moat]] — why the repeatable method is the defensible part
+- [[pricing-from-value]] — productization is what makes value pricing possible
+- [[solution-vs-staff-augmentation]] — the model choice that productization commits you to
+- [[future-of-engineering-work]] — why a productized shop can now be tiny
+- [[ai-productivity-evidence]] — the empirical test of the substitution premise this page leans on
+- [[overview]]
+
+## Contradictions / Uncertainty
+
+- **When to productize** is genuinely disputed (see table above): three delivery-first sources vs. two offer-first — but the two offer-first sources are possibly one author ([[dan-martell]]), so on independent voices it may still be 3:1. **Update (2026-07-26): the offer-first camp gains its first genuinely independent voice** — [[oskar-hartmann]]'s "sell first, then build" ([[sell-before-build]]) is offer-first stated as a categorical rule, from outside the Martell corpus. Careful with scope, though: Hartmann argues *demand must be proven by payment before building*, which the delivery-first camp doesn't deny — their claim is about when to **fix scope/price** on work you've shipped, not about building on spec. Read precisely, the camps may answer different questions (validate-before-*build* vs standardize-after-*repetition*), and both can hold at once — that reading would dissolve the dispute entirely, but it is the vault's synthesis, not any source's. On raw voices: now roughly 3 delivery-first vs 2–3 offer-first.
+- The "90% / below minimum wage" claim is uncited and rhetorical in tone.
+- **No source examines where hourly billing *works*.** Regulated/legacy/high-liability domains plausibly still command healthy hourly rates — and [[2026-07-06-sebastian-interview-ai-and-software-engineering]] notes COBOL/enterprise holdouts persist, a hint the vault otherwise lacks. Every productization source is advocacy from the same school. **Update (2026-07-18):** the vault now *has* an adversarial source ([[ai-productivity-evidence]]), but it contests the **AI-capability premise** this page leans on (the substitution argument), **not** the productization *model* — so a genuine productization-failure source is still the specific missing piece here.
+
+## Next Questions
+
+- What breaks first when you fix the scope of work that isn't actually repeatable yet?
+- Does the ~$200/mo AI substitute really threaten mid/high-end dev contracts, or only the commodity floor?
+- Is there a domain where the productized model is known to fail? The vault's first adversarial source ([[ai-productivity-evidence]]) tests the AI-capability premise but not the productization model itself — a productization-failure source remains the gap.

wiki/concepts/referrals.md

@@ -0,0 +1,79 @@
+# Referrals
+
+#concept #sales #outbound
+
+## Summary
+
+The highest-converting, lowest-cost channel in the vault — and the one you cannot use to get started, or to scale. A referral is a warm introduction from a satisfied client or a trusted contact; it converts far better than cold outreach at near-zero cost, but it structurally requires an existing relationship, so it **can't bootstrap client #1**. The sources agree it is badly under-exploited: most clients would refer, but almost none are asked. Primary source [[2026-06-15-17-ways-first-client]] (AB Analytics); the relational mechanism behind it is [[relationships-as-moat]].
+
+**Since 2026-07-20 the page carries a counter-position** ([[2026-07-20-referrals-will-sink-your-business]], [[dan-martell]]): referrals convert brilliantly and *therefore* seduce founders into never building a system they can turn up. The channel now has a documented failure mode at both ends — it can't start you, and it can't scale you.
+
+## Current Understanding
+
+**The ask-rate gap is the whole opportunity.** ~**91% of clients are willing to refer, but only ~11% are ever asked** ([[2026-06-15-17-ways-first-client]]). The channel isn't weak — it's unworked. The fix is a discipline, not a trick:
+
+- **Ask immediately after delivery** — the enthusiasm window is short; "waiting for the right moment" loses it ([[sales-discipline]]).
+- **Be specific** — "know anyone spending \$100k/yr on helpdesk?" (a criterion) beats "know anyone who needs a developer?" — the network-with-a-*criterion* motion in [[2026-06-15-rodenko-selling-development-expensively]] is the same move.
+- **Make it frictionless** — remove every step between a client's willingness and the actual introduction.
+
+**Two engines produce referrals, and they are different mechanisms:**
+
+1. **Transactional** — a delivered [[outcome-based-selling|outcome]] earns an explicit ask right after it lands ([[2026-06-15-17-ways-first-client]]).
+2. **Relational** — trust built by repeated in-person contact produces referrals *organically*: "there's this guy, I've met him a few times, I trust him" → recognition → referral ([[relationships-as-moat]], [[sebastian]]). Here the referral is emergent, not requested.
+
+These complement rather than conflict: the ask *converts* existing goodwill into an introduction; the relationship is what *creates* the goodwill in the first place.
+
+**The flywheel — and its cold-start problem.** "Client #1 is hardest, #5 easier, #10 comes to you" ([[2026-06-15-17-ways-first-client]]) — referrals compound, which is why they dominate at scale. But the same property makes them useless at the start: **a referral needs a prior satisfied client, so it cannot bootstrap the first one** ([[2026-07-17-best-method-first-client]]). This is the vault's sequencing constraint — referrals are the *reward* for the first engagement, not the *route* to it, which is why the [[client-acquisition-channels|first-client question]] resolves to warm/in-person channels instead.
+
+**A third engine: mining the network you already have** ([[2026-07-23-make-my-first-100k-in-month]], [[dan-martell]] — added 2026-07-23). The **"ask past the person"** move: go through phone contacts (usually 100–200) asking *"do you know anyone with this problem?"* — the indirect frame lowers the stakes, so it often lands on *"yeah — me"*, and otherwise yields warm intros whose names power the next opener ("Bob suggested I reach out…"). This is referral-shaped output — a warm, name-carrying introduction — produced **without any past client**, which makes it the one referral-adjacent motion that dodges this page's cold-start constraint: it draws on personal goodwill instead of delivered outcomes. Same specificity discipline as the ask-rate paragraph above (ask with a criterion, i.e. Rodenko's network-with-a-criterion motion, pointed at one's own contact list). Cost: it spends social capital that delivery hasn't yet earned, and the source offers no numbers.
+
+**Referral partners ≠ client referrals.** A distinct source is people who serve your ICP without competing — vendors, adjacent consultants — a strategic-partnership motion ([[client-acquisition-channels]] Tier 3), plus "referral partners" on LinkedIn ([[2026-06-15-17-ways-first-client]] Tier 1). Same output (a warm intro), different origin (a partner's audience, not your past client), and — usefully — **not** subject to the cold-start problem, since a partner can refer before you have any clients of your own. **As of 2026-07-22 this distinction has a worked-out page:** [[partnerships]] — partner intros are *recruited* demand with a throttle (you control partner acquisition), which is exactly what client referrals lack, and what qualifies partnerships as a [[marketing-system]] lever while client referrals stay a multiplier.
+
+### Counter-position: dependency is a ceiling, not an achievement
+
+[[2026-07-20-referrals-will-sink-your-business]] ([[dan-martell]]) is the vault's first source to argue *against* this channel, and its target is precise. It does **not** dispute that referrals convert best or cost least — it disputes **referral dependency as a primary strategy**:
+
+- **"We grew on referrals" is a warning sign, not a badge.** It is evidence the founder skipped building a system where *money in at the top produces more money out at the bottom* ([[marketing-system]]).
+- **The ceiling gets misdiagnosed.** A founder stalled at ~$1.5M reads it as a market limit; the source reads it as a missing system. Referral flow has no throttle — you cannot spend more to get more of it.
+- **The seduction is the conversion rate itself.** Precisely *because* referrals close so well and cost so little, they postpone the unpleasant, slow-compounding work (content, paid, partnerships) until the founder is years behind. Claim: founders who built the system reach the same revenue in ~18 months **and keep going**.
+
+**How this composes with the rest of the page.** The cold-start constraint and this ceiling are the same structural property observed at opposite ends: a referral is always *derived* from an engagement that already happened, so it can neither precede your first client nor exceed the rate at which your existing base generates goodwill. Referrals are a **multiplier on demand you already created** — excellent, and never the source of demand. The practical consequence is sequencing, not abandonment: work the ask-discipline above (it is nearly free and badly under-exploited), and do **not** treat the resulting flow as evidence that acquisition is solved.
+
+**Standing caveat:** this is a counter-*position*, not counter-*evidence* — a coaching clip with no data, from someone selling the alternative. It fills the page's long-flagged adversarial gap only partially. See Contradictions.
+
+## Evidence
+
+- **Primary:** referrals highest-converting & ~0 cost; the 91%-would / 11%-asked gap; ask right after delivery, be specific, make it frictionless; "client #1 is hardest… #10 comes to you"; referral partners — [[2026-06-15-17-ways-first-client]]
+- Ask-immediately timing and the short enthusiasm window — [[sales-discipline]]
+- Relational engine: trust → recognition → referrals; the in-person mechanic — [[relationships-as-moat]], [[2026-07-06-sebastian-interview-ai-and-software-engineering]]
+- "Go through your network with a *criterion*" (the specific-ask motion) and "the money is with your old clients" — [[2026-06-15-rodenko-selling-development-expensively]], [[2026-06-15-konspekt-aphorisms]]
+- The cold-start constraint (referrals can't bootstrap client #1) — [[2026-07-17-best-method-first-client]]
+- "Ask past the person" — network mining that yields warm intros before any client exists — [[2026-07-23-make-my-first-100k-in-month]] ([[dan-martell]])
+- **Counter-position:** referral dependency as a growth ceiling; "warning sign, not a badge"; the missing-system diagnosis — [[2026-07-20-referrals-will-sink-your-business]], [[dan-martell]], [[marketing-system]]
+
+## Related Pages
+
+- [[client-acquisition-channels]] — referrals is a Tier-1 channel in the taxonomy; this page is its detail
+- [[marketing-system]] — the counter-position's core: demand you can turn up, versus demand that arrives
+- [[partnerships]] — the throttled sibling: warm intros you *recruit* instead of inherit
+- [[sales-discipline]] — the ask-timing and cadence that actually work the channel
+- [[relationships-as-moat]] — the relational engine that produces referrals without an explicit ask
+- [[outcome-based-selling]] — you get referred for a delivered, countable outcome
+- [[pain-discovery]] — old-client mining ("what result were you paying me for?") reuses the same warm contacts
+- [[overview]]
+
+## Contradictions / Uncertainty
+
+- **The 91% / 11% figures are promotional and uncited.** They come from [[2026-06-15-17-ways-first-client]] (AB Analytics, whose named examples are paid-accelerator members) — attributable, not verified. `Status: tentative` on the specific numbers; the *directional* claim (referrals are under-asked) is corroborated independently by the relationship sources.
+- **Ask vs. emergence — a mild method tension.** AB Analytics prescribes an explicit post-delivery *ask*; [[sebastian]]'s model has referrals *emerge* from repeated trust, no ask required. Probably complementary (the ask captures goodwill the relationship created), but no source reconciles the two directly.
+- ~~**No adversarial source**~~ — **partially resolved 2026-07-20.** [[2026-07-20-referrals-will-sink-your-business]] documents exactly what was missing: where referral-led growth caps out and why founders misread the cap. But it is **advocacy against advocacy**, not evidence: a coaching clip, no data, no failed-founder cohort, and its author sells the prescribed alternative ([[dan-martell]]). Its unsourced numbers ($1.5M ceiling, ~18 months, six-month lag) are `Status: tentative` and must not be repeated as fact. What genuinely survives is the *structural* argument — referral flow has no throttle — which does not depend on any of the figures.
+- **The two failure modes may be one claim, and the vault should not double-count it.** "Can't bootstrap client #1" ([[2026-07-17-best-method-first-client]]) and "can't scale past a ceiling" (this source) are both consequences of referrals being *derived* demand. Treating them as two independent findings would overstate the corroboration; they are one property observed twice.
+- **Unresolved: where the boundary sits.** The counter-position is aimed at a ~$1.5M business with an existing client base; the vault's other referral material is aimed at reaching client #1. No source says at what point working the ask-discipline stops being sufficient and system-building becomes urgent — so the practical question ("when do I stop riding referrals?") has no answer here.
+
+## Next Questions
+
+- What is the actual post-delivery script that asks *specifically* without feeling transactional — and does it differ for the transactional vs. relational engine?
+- Does "frictionless" mean a formal referral program (incentives) or just a well-timed human ask? The sources imply the latter; neither tests incentives.
+- For [[eugene]] (no past clients yet), client-referrals are unavailable until after engagement #1 — the referral-adjacent routes open to him now are the relational engine ([[relationships-as-moat]]), *referral partners* ([[partnerships]]), and — added 2026-07-23 — **"ask past the person"** on his existing contacts. Which converts first for a technical operator with a thin commercial network is untested.
+- **At what revenue or client count does referral dependency become the binding constraint?** The counter-position asserts a ceiling exists but locates it only by anecdote. Without that threshold, "don't rely on referrals" is unactionable for anyone below it.
+- ✅ ~~Is there a version of referrals *with* a throttle?~~ Answered 2026-07-22, and by the same author who raised the ceiling argument: **yes — partner-sourced intros**, scaled by recruiting the partner archetype rather than waiting for goodwill ([[2026-07-22-stop-cold-calling-do-this-instead]] → [[partnerships]]). This also dissolves the apparent self-contradiction in Martell's corpus (referral dependency sinks you, yet his flagship enterprise play runs on warm intros): the difference is control of the input, not the shape of the output. Same-author, anecdote-grade — the *structural* distinction stands on its own; the economics don't.

wiki/concepts/relationships-as-moat.md

@@ -0,0 +1,55 @@
+# Relationships as Moat
+
+#concept #positioning
+
+## Summary
+
+When AI equalizes skill and floods every online channel with indistinguishable content, the one asset it cannot commoditize is in-person human trust. This is [[sebastian]]'s standout claim in [[2026-07-06-sebastian-interview-ai-and-software-engineering]], and it sits in productive tension with the vault's other moat account, [[methodology-as-moat]].
+
+## Current Understanding
+
+**The argument:** Claude *levels* pure programming skill — 20 years of experience vs a fresh grad on the same subscription produces similar output. So the differentiator moves entirely to communicating with clients and understanding their problems — and, above that, to real relationships. As bots become indistinguishable from humans on LinkedIn and even on calls ("in 10 years… zero" ability to tell), **in-person connection becomes the scarce, decisive edge**, and it *appreciates* precisely as AI makes everything else cheap.
+
+**The mechanics of a connection** (the most actionable part):
+
+- It forms not on the first meeting but when you meet the **same person in different circumstances** → recognition value → trust → [[referrals]]. ("There's this guy Eugene — I met him a couple of times, he's real, I trust him.")
+- **Be memorable in your humanness** — lead with something human (renovating a house, two kids, a cat), not "I run a software company," which everyone forgets. Because everyone uses the same AI tools, everything online looks identical; humanity is the differentiator. (Virtido's `humans.verti.com` "human badge" riffs on this.)
+- **What builds it:** showing up in person 2–4 days/week (lunches, networking events, conferences, open days). **What doesn't:** online outreach — "Big zero."
+
+**Convergence from the opposite pole (added 2026-07-22).** [[dan-martell]] — the vault's most content-bullish voice and Sebastian's direct opposite on online channels — independently lands on the same claim for enterprise: cold outreach doesn't open those doors, **trust does**, and his partner-recruiting playbook is Sebastian's own mechanics (go to events, show up in person, win the individual) aimed at partners instead of buyers ([[2026-07-22-stop-cold-calling-do-this-instead]] → [[partnerships]]). The difference is the trust's origin — Sebastian *builds* it over repeated encounters; Martell *borrows* it from a partner who already has it. Borrowing is faster but rented (it stops if the partner relationship does); building is slower but owned. That two voices who agree on almost nothing else both make trust the enterprise entry mechanism is real cross-voice support — though note both are still anecdote-grade on this point.
+
+**Partial corroboration, not just one voice.** [[2026-06-15-17-ways-first-client]] independently rates in-person channels (Chamber of Commerce, associations, car shows, premium gyms, country clubs) as its highest-value tier, and its "show up 3× = regular, 6× = trusted" mirrors Sebastian's recognition-through-repetition mechanic exactly. Two sources from different worlds converging on repeat-in-person-contact is the reason to weight this highly. Where they diverge is only on whether online channels are worthless or merely a lower tier — see [[client-acquisition-channels]].
+
+**Relationship to the other moat.** [[methodology-as-moat]] says the defensible asset is *your proven way of doing the work*; this page says it's *who trusts you in person*. Both can be true and they reinforce (a proven method gives you something real to be trusted *for*), but they point time and money in different directions — into productizing a method vs. into showing up. The vault does not resolve which dominates; likely both, weighted by [[niche-selection]] (enterprise/high-trust buyers → relationships; productizable SMB pains → method).
+
+## Evidence
+
+- "The only way to get a real connection is to stand face to face in the same room… shake their hand, and have a conversation." — [[2026-07-06-sebastian-interview-ai-and-software-engineering]]
+- Claude levels skill → communication/relationships become the differentiator — same source
+- Recognition-through-repeat-encounters; "be memorable in your humanness"; `humans.verti.com` — same source
+- Independent corroboration: in-person Tier 2 and "show up 3×/6×" — [[2026-06-15-17-ways-first-client]]
+- The "simplified B2B" path (know owners → meet → solve → paid; "connections matter") — [[2026-06-15-making-money-with-ai-2026]]
+- Trust as the enterprise entry mechanism, reached by the content pole's own author (borrowed via partners; events, win-the-individual) — [[2026-07-22-stop-cold-calling-do-this-instead]], [[partnerships]]
+
+## Related Pages
+
+- [[methodology-as-moat]] — the competing/complementary account of the moat
+- [[client-acquisition-channels]] — the in-person-vs-online debate this anchors
+- [[referrals]] — what in-person trust produces (the relational engine, no explicit ask)
+- [[partnerships]] — the borrowed-trust variant of the same entry mechanism
+- [[seniority-and-ai]] — the same "skill is leveled" premise, applied to careers
+- [[future-of-engineering-work]] — why online content converges to noise
+- [[sebastian]] · [[eugene]] · [[virtido]]
+- [[overview]]
+
+## Contradictions / Uncertainty
+
+- **Generality is unproven.** `Status: tentative`. Sebastian states "online = Big zero" as universal, but his evidence is one enterprise-services firm. The online channels he dismisses are exactly the ones AB Analytics/Tony report working for SMB/startup buyers. Best read: audience-dependent, not a law — see [[client-acquisition-channels]].
+- **Self-serving framing risk.** Sebastian sells relationship-heavy enterprise services and a "human badge"; the claim flatters his own model. Corroboration from AB Analytics' in-person tier is what keeps it from being a single interested voice.
+- **Scalability tension.** In-person 2–4 days/week doesn't obviously scale the way productization does; the vault hasn't reconciled "relationships are the moat" with "productize to escape selling your time."
+
+## Next Questions
+
+- Does in-person trust actually beat a strong productized offer for SMB buyers, or only for enterprise?
+- What's the throughput ceiling of a relationships-first model, and does it cap growth vs a productized one?
+- How does a remote/asynchronous operator build "recognition value" without 2–4 in-person days/week?

wiki/concepts/sales-channel-as-moat.md

@@ -0,0 +1,50 @@
+# Sales Channel as Moat
+
+#concept #gtm #positioning
+
+## Summary
+
+The vault's **third moat candidate**: not your method ([[methodology-as-moat]]), not your relationships ([[relationships-as-moat]]), but a **repeatable, scalable sales channel with predictable acquisition economics**. Source: [[2026-07-26-how-to-build-a-billion-dollar-company-2027]] ([[oskar-hartmann]]). The claim in one line: *products are now cheap to build (everyone has "10–15 great products in Cloud Code"), so the differentiating, reusable, defensible asset is the distribution machine — "уникальный, масштабируемый, повторяемый канал ценнее уникальной технологии."* Single source, `Status: tentative` — but it names a moat neither prior account covers, and it is the only one of the three stated as an *investor's* screening criterion rather than a practitioner's self-description.
+
+## Current Understanding
+
+**The core contrast — Pediant vs FlatPay.** Pediant had superior technology (QR payments) and landed Walmart and Best Buy; integrations dragged, champions churned, the startup died. FlatPay had a commodity product (payment terminal) with a dead-simple promise ("1% commission, no asterisks") and a **door-to-door sales force** in Holland/Germany — one rep sells 10–20 terminals a month — and became a billion-dollar company. The kicker: FlatPay's founder is on his **sixth business run through the same distribution playbook**. The channel, once built, accepts *any* product — which is exactly the property a moat needs and a product rarely has.
+
+**Why a channel is a moat mechanically** ([[unit-economics]]): a business that has run a channel long enough *knows its LTV* and can rationally pay up to ~⅓ of a client's lifetime profit on day one (US credit cards: ~$1,000 CAC). A newcomer without that knowledge can't bid against them — the burned-in channel is an **entry barrier**, and venture money exists largely to fund that burn until the LTV math closes. Restated in the author's second source ([[2026-07-26-main-principle-of-successful-business]]: post-PMF, spend $80–100 CAC precisely so competitors can't afford entry) — framework stability, not corroboration.
+
+**Repeatable is the load-bearing word.** One-off spikes don't count ("Michael Jackson rose from the grave and told people to come" — not a channel). Nor do one-off partner deals: Hartmann's own first store hit $20M on a single 10%-of-revenue traffic deal, which he explicitly files under *boost, not system* — partner management changes, audits arrive, terms flip, and by then you need the statistics to compete in open auctions. The test is: **can you spend a predictable amount and get a predictable customer, again and again?**
+
+**Relation to the vault's other two moats.** Not rivals — different layers: the method is *what* you deliver, relationships are *one particular channel's* trust substrate, the channel-moat is the *machine* that makes any of it repeat. It is also the closest thing to an independent restatement of [[marketing-system]]'s "money in at the top → more money out at the bottom" definition — from a different tradition, which is worth more than another Martell clip saying it. Where it *does* take a side: against [[methodology-as-moat]]'s implicit premise that the differentiated method is the scarce thing — in Hartmann's telling the product/method is the commodity and distribution is scarce, which is Sebastian's "relationships" argument generalized beyond in-person.
+
+**Stage nuance the source itself carries:** FlatPay built **one** repeatable channel (door-to-door); the AI land-grab example (Anthropic/OpenAI ~$4B PE joint ventures) runs **all channels at once**; and his through-principle says one channel = concentration risk, resilient = multichannel. Read together: one repeatable channel gets you the company, multichannel makes it durable — which happens to match the vault's staged reading of pick-1-vs-pick-3 ([[client-acquisition-channels]]).
+
+## Evidence
+
+- Pediant vs FlatPay contrast; "channel worth more than technology"; sixth-business playbook — [[2026-07-26-how-to-build-a-billion-dollar-company-2027]]
+- LTV×⅓ CAC / entry-barrier mechanism — same source, detailed on [[unit-economics]]
+- Convergent (same claim, different tradition): a marketing system is "money in → more money out," and referral/word-of-mouth flow is not one — [[marketing-system]], [[2026-07-20-referrals-will-sink-your-business]] ([[dan-martell]])
+- Convergent from the services side: a repeatable *method* is what gets sold ([[methodology-as-moat]]) — but the method-vs-channel priority is contested, see below
+- Slogan echo (2026-07-29): "distribution is the moat, not code — landing page + outbound = go-to-market; the product is the last step" — [[2026-07-29-start-a-business-with-claude-code]] ([[dan-martell]], attributed same day; folds into his existing marketing-system convergence above — asserts the priority, supplies none of the repeatability/CAC mechanics that make this page's claim a *moat* claim)
+
+## Related Pages
+
+- [[methodology-as-moat]], [[relationships-as-moat]] — moat candidates #1 and #2
+- [[marketing-system]] — the same machine described from the operator's side
+- [[client-acquisition-channels]] — the channel taxonomy this concept ranks
+- [[unit-economics]] — the math that makes a channel defensible
+- [[venture-fit]] — what funding the channel-burn implies
+- [[oskar-hartmann]] — the source's voice
+- [[overview]]
+
+## Contradictions / Uncertainty
+
+- `Status: tentative` — single source for the *mechanism*, stage-talk grade, told by a coach/investor selling a founder program. The FlatPay and Pediant details are unverified war stories. The 2026-07-29 echo turned out to be [[dan-martell]] (attributed same day) — so it folds into the already-recorded Martell convergence rather than adding a voice, and corroborates nothing load-bearing (no repeatability test, no CAC logic) — status unchanged.
+- **Three moats now compete for the same investment dollar.** Method says productize; relationships say show up; channel says build the machine. All three can't be the *first* priority for a solo operator. Likely resolution is stage- and audience-dependent (method → something to sell; relationships/channel → how it repeats), but no source arbitrates.
+- **Scope:** the exemplars are product companies (terminals, e-commerce). Whether a *services* firm can own a channel-moat in this sense — or whether for services the channel-moat just *is* relationships/partnerships — is untested in the vault.
+- The "products are commodities now" premise leans on the vibe-coding claim, which [[ai-productivity-evidence]] contests at the expert end.
+
+## Next Questions
+
+- What is the services analogue of FlatPay's door-to-door — the one channel a dev-services operator could run repeatably to 10–20 closes/month?
+- Does the LTV×⅓ CAC rule transfer to B2B services where LTV is lumpy project revenue, not subscription flow?
+- Is there a documented case of a services firm whose *channel* (not method or relationships) was the demonstrable moat?

wiki/concepts/sales-discipline.md

@@ -0,0 +1,91 @@
+# Sales Discipline
+
+#concept #sales #outbound
+
+## Summary
+
+The execution layer: consistency over intensity, follow-up past the point most people quit, and a founder who does the selling. The primary source is now [[2026-06-15-17-ways-first-client]] (AB Analytics), with [[2026-06-15-rodenko-selling-development-expensively]] for the founder-led-sales claim. This is also where the vault's sharpest disagreement lives — not merely calls-vs-chat, but whether *any online channel works at all* ([[sebastian]]: "Big zero").
+
+## Current Understanding
+
+**Consistency beats intensity** — 30 minutes a day beats 5 hours once a month ([[2026-06-15-selling-development-services-in-the-ai-era]]). The corollaries:
+
+- **5 touches minimum.** ~80% of deals close after the 5th contact; most people quit after the 1st.
+- **3 channels × 90 days.** Don't add new methods until these are mastered. Channel-hopping = zero.
+- **Ask for [[referrals]] immediately after delivery.** 91% of clients are willing to refer; only 11% are asked. The enthusiasm window is short — "waiting for the right moment" loses it.
+- **Customize every first touch.** A template exists to be adapted, never mass-mailed — the concrete instance is the [[2026-06-15-linkedin-mail-template]].
+- **Cold-email subject lines carry 47% of open rate** — spend 50% of your time there. Specific beats generic: *"Quick question about [Company]'s checkout flow"* >> *"Ideas to improve your site"*.
+- **Follow-up cadence:** Day 0 → 3 → 7 → 14 → 30 (break-up email) — the concrete schedule behind "5 touches" ([[2026-06-15-17-ways-first-client]]).
+
+These figures now trace to a named primary source ([[2026-06-15-17-ways-first-client]], AB Analytics) rather than only the distillation — but that source is promotional (accelerator-member examples), so the numbers are attributable, not independently verified; see Contradictions.
+
+**Measure reps, not results — and budget the lag.** [[2026-07-20-referrals-will-sink-your-business]] ([[dan-martell]]) reaches consistency-over-intensity independently, from the content side rather than outbound, and adds the two pieces this page lacked:
+
+- **The metric substitution.** Not *how many views / did it convert* but *am I getting better / how many reps this week*. Outcomes aren't controllable; rep volume is the only input you own. *"Most of you get bored with your marketing before the market ever does — and you just stop."*
+- **The time budget — six months before a marketing system produces leads.** Stated up front precisely so the operator doesn't quit at day 60. The vault's other discipline claims prescribe a cadence (90 days, 5 touches) but never say how long before the cadence pays; this supplies that number, albeit unsourced. See [[marketing-system]].
+
+Two unconnected traditions — a US content coach and a Russian-language outbound practitioner — landing on process-metrics-over-outcome-metrics is the strongest support this page's core discipline claim has. Neither offers data; the convergence is the evidence.
+
+**The closing playbook at volume** ([[2026-07-23-make-my-first-100k-in-month]], [[dan-martell]] — added 2026-07-23). Two closing channels for a $0 operator, chat first:
+
+- **Sell by chat:** every new follower gets "are you here for [content] or [help growing your business]?" (second option last — primes the yes) → pain-awareness questions → offer-doc link → Stripe payment link. He claims 8 figures sold this way.
+- **Cold call:** the call's job is **not to sell** — qualify and book a meeting from a meeting. The opener is a curiosity question in the prospect's world plus an explicit "I've got nothing to sell."
+- **Objections vs. obstacles** — the most portable tool here: concerns raised *before* the offer are obstacles, *after* it are objections; **surface them up-front so they become obstacles** ("do you have a budget to solve this?"). If they arrive after the pitch, you're playing defense. This is the vault's first concrete principle for the "objection-handling script" gap flagged by [[2026-06-15-meta-analysis-selling-dev-in-ai-era]] — a principle, still not a script.
+- **Volume rules:** first 5 calls are throwaways — don't self-judge on them; no answer → **call back within 30 seconds** (second ring reads "urgent"); feed call transcripts to AI to find where you stumble; target **100 no's per day**; **spend nothing** (tools, equipment) until customers have paid.
+
+"100 no's per day" is reps-not-views pushed to its extreme — the metric is rejections collected, an input, not closes, an outcome. Same author as the reps-not-views paragraph below, so consistency rather than corroboration.
+
+**Founder = head of sales.** If you haven't locked in the next level, that's normal — the founder goes back to selling. There is no stage at which this delegates away cleanly ([[2026-06-15-selling-development-services-in-the-ai-era]]). **A third tradition now states it as an investment criterion** ([[2026-07-26-how-to-build-a-billion-dollar-company-2027]], [[oskar-hartmann]], added 2026-07-26): "I'll hire a salesperson" is "a childish idea"; in every large company the founder personally broke through the first customers "like a vacuum-cleaner salesman" — uncomfortable and necessary — and Hartmann says he **does not invest** where the founder doesn't sell. Founder-led first sales is now the vault's most broadly converged discipline claim: RU dev-sales (Rodenko), US coaching (Martell's blueprint has the founder cold-calling), and the VC/product world all state it independently.
+
+**"A year of repackaging is for people afraid to pick up the phone."** Real feedback in a week beats a year of planning. This is the distillation's central discipline claim and a direct rebuke to offer-polishing — worth holding against [[offer-ladder]] and [[productized-service]], both of which are offer-design activities that can absorb unlimited time. **Cross-tradition convergence (2026-07-26):** [[oskar-hartmann]] states the same claim as an investor's red flag — "we've been working on this since 2016, no revenue yet" is "the fattest minus"; duration without revenue is absence of evidence, and he'd "rather talk to a team that started a week ago" ([[2026-07-26-main-principle-of-successful-business]]). His corollary discipline: **endure the pain of reality early** — willingness to launch ugly and look stupid is what separated his two portfolio teams ([[sell-before-build]]). Rodenko's phone-fear diagnosis and Hartmann's duration red flag are the same claim from opposite sides of the table (seller's coach / investor screening pitches).
+
+**Deal psychology** ([[2026-06-15-selling-development-services-in-the-ai-era]]): the client is not a prize — a deal is expertise exchanged for money, neither charity nor a favor. Professionals choose which fights to enter: an athlete doesn't "participate", they go to **win**; a commander doesn't enter a battle without seeing the conditions for victory. Practically, this licenses disqualifying prospects — which is what makes the filters in [[pain-discovery]] and [[ai-market-shift]] usable rather than merely clever.
+
+## Evidence
+
+- **Primary (AB Analytics):** consistency>intensity ("30 min/day beats 5 hours once a month"), 5 touches / ~80% after the 5th, 3 methods × 90 days, referrals 91% would / 11% asked, subject line 47%, Day 0→3→7→14→30 cadence, webinar 60/20/20 → 15–25% — all in [[2026-06-15-17-ways-first-client]]
+- **Primary (Rodenko):** "Founder = head of sales"; "a year of repackaging is for people afraid to pick up the phone" — [[2026-06-15-rodenko-selling-development-expensively]]; the athlete/commander "choose your fights" psychology — [[2026-06-15-konspekt-aphorisms]]
+- **Independent corroboration (content side):** reps-not-views, "bored with your marketing before the market", the six-month lag before a system produces leads — [[2026-07-20-referrals-will-sink-your-business]], [[marketing-system]]
+- Same claims, condensed, in the distillation [[2026-06-15-selling-development-services-in-the-ai-era]]
+- Chat DM flow, cold-call qualify-and-book, objections-vs-obstacles, 100 no's/day, 30-second callback, spend-nothing-until-paid — [[2026-07-23-make-my-first-100k-in-month]] ([[dan-martell]])
+- Founder sells first, always — as an investor's screening criterion — [[2026-07-26-how-to-build-a-billion-dollar-company-2027]] ([[oskar-hartmann]], third independent tradition)
+- Duration-without-revenue red flag; launch-ugly / endure-reality-early — [[2026-07-26-main-principle-of-successful-business]] ([[oskar-hartmann]])
+- Chat-first counterposition: "the market is fatigued by sales calls" — [[2026-07-17-design-the-perfect-offer]]
+- In-person-only counterposition: online outreach is "Big zero" — [[2026-07-06-sebastian-interview-ai-and-software-engineering]]
+
+## Related Pages
+
+- [[client-acquisition-channels]] — *where* to fish; this page is *how* to work a channel once chosen
+- [[marketing-system]] — *whether the machine exists*; shares the reps-not-views discipline and supplies the six-month lag
+- [[referrals]] — the channel the follow-up discipline unlocks (ask-immediately, be-specific)
+- [[relationships-as-moat]] — the in-person pole of the channel disagreement below
+- [[pain-discovery]] — what the touches are actually for
+- [[niche-selection]] — discipline against the wrong audience is wasted effort
+- [[cloning-over-originality]] — discipline is precisely the "boring part" to clone
+- [[outcome-based-selling]] — case studies are the follow-up's ammunition
+- [[overview]]
+
+## Contradictions / Uncertainty
+
+**Calls vs. chat — the two sources disagree.**
+
+| [[2026-07-17-design-the-perfect-offer]] | [[2026-06-15-selling-development-services-in-the-ai-era]] |
+|---|---|
+| The market is fatigued by sales calls | Founder is the main salesperson; a year of repackaging is for people afraid to pick up the phone |
+| Educated buyers often know more about what you sell than you do — forcing a discovery call is friction, not qualification | 5 touches minimum, 3 channels × 90 days, customize every first touch |
+| Default to selling in chat; escalate to a call only if the buyer asks | Webinar formula 60/20/20 → 15–25% conversion (a synchronous, call-like motion) |
+| "You can literally make a million dollars a month over chat" | — |
+
+Partial reconciliation: these may be about different *stages* — the video is about the closing motion (a buyer who already knows what they want shouldn't be forced onto a call), the distillation about the prospecting motion (nobody comes to you at all without consistent outbound). They're not strictly incompatible; a chat-first close is compatible with disciplined multi-touch outbound. But the postures genuinely differ in spirit, and the "million dollars a month over chat" line is unsupported motivational framing rather than evidence.
+
+**Update (2026-07-23): the split softens further — one source now prescribes both.** [[2026-07-23-make-my-first-100k-in-month]] runs chat-DM *and* cold calls side by side as the two closing channels, chat as the easier start. And if the chat-first 07-17 speaker is Martell too (plausible — see [[dan-martell]]), then the "market is call-fatigued" pole and the "100 cold calls a day" pole are the *same person* addressing different buyers, which would dissolve calls-vs-chat from a doctrine dispute into channel-by-context. Unconfirmed.
+
+**The deeper split — does online outreach work at all?** [[sebastian]] rejects the whole apparatus: sales agencies, cold calling, email, LinkedIn campaigns, content, SEO = "Big zero"; only in-person builds the trust that closes. That is a flat contradiction of the 3-channels/cold-email discipline above, not a stage distinction. Best current reconciliation is **audience** (enterprise buyers ignore cold outreach; SMB/startup buyers still convert on it) — see [[client-acquisition-channels]] and [[relationships-as-moat]]. `Status: tentative` — genuinely unresolved.
+
+**The statistics are now attributable but still not verified.** They trace to [[2026-06-15-17-ways-first-client]] (AB Analytics), a named primary source — an upgrade from "uncited via distillation." But that source is promotional (its success stories are paid-accelerator members), so treat the figures (80%/5th touch, 91% vs 11%, 47% subject line, 15–25% webinar) as one practitioner's marketing-flavored claims, not independent data.
+
+## Next Questions
+
+- Is the online-vs-in-person split an audience difference (enterprise vs SMB), or does Sebastian's "Big zero" generalize?
+- What are the 3 channels for this vault's owner ([[eugene]]) specifically — and does his buyer type favor in-person per Sebastian?
+- Do any of the cited percentages have a source beyond the AB Analytics video?

wiki/concepts/sell-before-build.md

@@ -0,0 +1,69 @@
+# Sell Before Build
+
+#concept #validation #strategy
+
+## Summary
+
+Prove demand with **paid money before building anything** — because building is the most expensive, least reversible move, and every cheaper signal lies. Founded as a page by [[2026-07-26-main-principle-of-successful-business]] ([[oskar-hartmann]]), but the rule itself is now held by **three independent traditions**: RU dev-sales ("validate market and pain before writing code"), [[dan-martell]] (the $50 paid waitlist; offer → pre-sell → build), and Hartmann (the full experiment toolkit below). That makes it one of the vault's best-converged disciplines. A 2026-07-29 short restates the rule in AI-era compression ([[2026-07-29-start-a-business-with-claude-code]]) — initially anonymous, owner-attributed same day to [[dan-martell]]: **within-author restatement, not a fourth voice** (he already counts among the three traditions); the echo-grade caution paid off, since no independence weight had been granted. What this page adds over [[productized-service]]'s validation paragraph: the **signal hierarchy**, the **toolkit**, and the **red flags**.
+
+## Current Understanding
+
+**The signal hierarchy** — what counts as evidence of demand, weakest to strongest:
+
+1. **Click on a button** — weak.
+2. **Email / waitlist signup** — stronger, and deceptive ("interesting!" is free).
+3. **Payment** — the only real signal. *"Голос деньгами"* — voting with money.
+4. **Pre-payment** — the supreme form: the customer finances your build. The humanoid-robot-data founder sold **$5M of prepaid contracts before collecting any data**; Tesla took 100K paid Model 3 preorders before building — "a $1.5T company still tests demand."
+
+Corollary from the Zavent anti-case: if customers will *only* pay months after delivery, that's not merely weaker demand — **you have become a bank financing your clients**, which is a different business with different economics ([[unit-economics]]).
+
+**The toolkit, ordered by cost:**
+
+| Experiment | Mechanics | Cost | Caveat |
+|---|---|---|---|
+| AI-mockup + priced offer | Generate the most beautiful image of the thing; send to the target community with a real price and "who's with me?" | ~Nothing | Hartmann's coworking test: ~5,000 reached, 0 buyers, project killed pre-build |
+| Landing → **payment screen** | A plain landing page doesn't qualify; the test ends at a payment attempt | Small | One word in the offer can move conversion 3–5× |
+| Fake payment screen | Full-looking app; at payment: "Error, payment failed"; keep intent data | <$1,000/app | **Deceptive** — see Contradictions |
+| Fake-door buttons | Ship all features as non-working buttons; build in click-count order (Samwer's eBay clone) | Small | Click is the *weakest* signal — use for prioritization, not demand proof |
+| Wizard-of-Oz manual MVP | Deliver the value **by hand for the first 10 clients**, then automate | Labor only | The honest workhorse for services; Builder.ai is both its exemplar and its cautionary tale (see source page) |
+| Visible pre-order / paid waitlist | Charge (even partially) before building — Martell's $50 top-of-waitlist slot | ~Nothing | The honest high-signal variant |
+
+**Why cheap and frequent beats right:** intuition always deceives (the app studios found "quit casino" dead and "quit porn" live; Samwer's click order was "never what you'd guess"), so the discipline is many small falsifications, not one confident bet. The 12-week portfolio contrast: team A ran 10 tests and had constant customer signal; team B was still building with zero — same money, "the only difference is the willingness to launch ugly and look stupid." Failing at $1K is safe; failing after a 6-month build is fatal. This is [[sales-discipline]]'s reps-not-views logic applied to *what to build* rather than *how to market*.
+
+**The red flag inverted:** "we've been working on it since 2016, no revenue" reads as dedication and is disqualifying — duration without revenue is absence of evidence. Cross-tradition convergence: Rodenko's *"a year of repackaging is for people afraid to pick up the phone"* is the same claim from the services side ([[sales-discipline]]).
+
+**The AI-era compressed variant** ([[2026-07-29-start-a-business-with-claude-code]], added 2026-07-29): stand up the *appearance* of a business with [[claude-code]] (landing page, invented company name, waitlist), close paying customers by cold outbound, and only then have the AI build the product. Two points of contact with this page's machinery: (1) its internal waitlist is **unpaid** and so fails the vault's own bar — but the playbook's actual validation event is the **closed sale**, which sits above mere payment in the hierarchy, so it passes the money bar where it counts; (2) the invented-company front belongs with the toolkit's deception-based rows (a fake *business* rather than a fake payment screen) — same signal logic, same unmodeled reputational/legal exposure. Author: [[dan-martell]] (attributed 2026-07-29) — which makes the unpaid waitlist a **within-author drift** from his own $50-paid-slot rule, logged on his page. 42 seconds, no case.
+
+**Boundary with the vault's other machinery:** [[pain-discovery]] finds *which* pain might pay (talk, watch spend); this page is the *experimental confirmation* step (make them pay, small). The acute-pain test bridges the two: if people pay even when the product is bad (hospitals), the pain is acute enough to sell a concept. Then [[productized-service]] packages what the test proved, and customer cash funds the build (Martell's format-triage logic — same sequence).
+
+## Evidence
+
+- Signal hierarchy, all toolkit rows, coworking/Zavent anti-cases, Tesla/robot-data/Samwer cases, 12-week contrast, red flag, checklist — [[2026-07-26-main-principle-of-successful-business]] ([[oskar-hartmann]])
+- $50 paid-waitlist pre-sell; offer → pre-sell → build sequence; "customer cash funds the product" — [[2026-07-23-make-my-first-100k-in-month]] ([[dan-martell]])
+- "Validate market and pain before writing code"; "most AI projects die from idea → code → launch" — [[2026-06-15-making-money-with-ai-2026]] (RU tradition)
+- Convergent red-flag from the services side: "год перепаковки — для тех, кто боится взять трубку" — [[2026-06-15-rodenko-selling-development-expensively]] via [[sales-discipline]]
+- Within-author restatement ([[dan-martell]], slogan-grade): sell via cold outbound before any product exists; "then ask Claude to build it" — [[2026-07-29-start-a-business-with-claude-code]]
+
+## Related Pages
+
+- [[productized-service]] — what gets packaged once the test pays; holds the when-to-productize dispute
+- [[pain-discovery]] — upstream: finding the candidate pain; the acute-pain test lives on both pages
+- [[unit-economics]] — pre-pay vs post-pay decides whose balance sheet carries the build
+- [[sales-discipline]] — the same anti-perfectionism discipline, marketing-side
+- [[cloning-over-originality]] — the toolkit itself is cloned (Samwer → Hartmann; 10 LLM-data companies → robot-data founder)
+- [[niche-selection]] / [[tam-sam-som]] — "the smallest group with the most acute pain, by name" is a SOM statement
+- [[oskar-hartmann]], [[overview]]
+
+## Contradictions / Uncertainty
+
+- `Status: tentative` on the specific mechanics (single-source, war-story figures); the *rule* itself (money before build) is three-tradition and as solid as anything in the vault.
+- **Two toolkit rows are deception-based** (fake payment screen, fake-door buttons): they collect purchase intent under false pretenses, carry consumer-protection exposure in some jurisdictions, and their reputational cost if discovered is unmodeled by the source. The honest variants (visible pre-order, paid waitlist, manual MVP) deliver most of the same signal; the vault records the deceptive mechanics without endorsing them. A third deception-shaped variant arrived 2026-07-29: the invented-company front ([[2026-07-29-start-a-business-with-claude-code]]) — same caveat applies.
+- **Tension with the articulation thread:** "don't dictate what the customer should want — build what's demanded" sits against [[outcome-based-selling]]/[[pain-discovery]]'s claim that naming a pain *better than the buyer can* is the value-add. Likely scoped — product demand testing vs service framing — but no source draws the line.
+- The traffic-arbitrage trainer recommendation doesn't transfer cleanly to services (no cheap payment-screen A/B); the transferable core is "smallest paid test."
+- Survivorship in the positive cases: Tesla and the $5M founder are selected wins; the fake-payment studios' failure rate across their 20-app batches is exactly the data not shared.
+
+## Next Questions
+
+- ~~What is the smallest *paid* test for a dev-services offer — a paid audit? a deposit-backed discovery sprint?~~ **Proposed answer 2026-07-26** ([[2026-07-26-eugene-90-day-plan]]): a **fixed-price, fixed-scope paid diagnostic** scoped to *one* line/device/process. It clears four constraints at once — money before build, small enough to skip procurement, produces the missing case study, and doubles as an [[offer-ladder]] entry rung. Vault inference, **untested**; no source states it. Its live falsifier: if free feasibility assessments are the industrial norm, the paid bar can't sit here and must move downstream.
+- Where is the legal line for fake-door testing in the owner's jurisdiction(s)?
+- Does pre-payment willingness vary by market culture (US vs EU vs CIS B2B), and does the Zavent post-pay trap generalize to enterprise services where net-60/90 is standard practice?

wiki/concepts/seniority-and-ai.md

@@ -0,0 +1,53 @@
+# Seniority and AI
+
+#concept #ai
+
+## Summary
+
+Counter-intuitively, AI raised demand for senior engineers and made juniors "completely irrelevant," even though a junior + Claude could in theory produce the same output. The senior's real product is **risk reduction** — knowing where things go wrong and catching dangerous agent actions. From [[2026-07-06-sebastian-interview-ai-and-software-engineering]]. **This claim is now contested:** rigorous evidence finds AI's productivity gains accrue *most* to the least-experienced — the direct inverse of "juniors irrelevant." See the counter-evidence below and [[ai-productivity-evidence]].
+
+## Current Understanding
+
+**Why seniors win:** 20 years of experience = 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" — so the value is in a human who recognizes the trained-in failure modes before they ship.
+
+**The junior risk is a security argument, not a quality one:** the habit of reflexively clicking "yes… yes… allow for all future" is how "API keys are leaked, databases get dumped or deleted." A junior can't evaluate a 250-line bash script an agent proposes; 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 actionable rule that falls out: **read what you approve** — don't reflexively "allow all."
+
+**The judgment, concretely** (the printer anecdote): a senior solved an unfamiliar Java direct-printing protocol in ~30 min with Claude Code on a 2-day deadline — his edge was knowing *how to instruct and verify*, not how to code. Directing-and-verifying is the skill that survives; raw coding is the skill that's leveled.
+
+**The squeeze and its second-order problem:** if juniors can't get in, the pipeline that *produces* seniors breaks. The source raises the senior/junior inversion but does not address where the next generation of seniors comes from — an open contradiction, not a resolved point.
+
+**Counter-evidence — the productivity direction is empirically inverted (2026-07-18).** The best skill-distribution study (Brynjolfsson, Li & Raymond, *QJE* 2025) found AI's measured gains are *largest for the least-experienced* (+34%) and near-zero — with small quality *declines* — for experts; a GitHub Copilot RCT points the same way. So on measured productivity, AI helps juniors most, not seniors ([[ai-productivity-evidence]], [[2026-07-18-ai-productivity-adversarial-evidence]]). **But the contradiction is narrower than it looks, and cuts two ways:** (1) that study is *customer-support agents, not developers*, and measures task *speed*, not the labor-market *value* (wages/hiring) this page is really about — so it inverts the productivity claim without settling the employment claim; (2) the same evidence shows experts suffer *quality* declines and that AI output needs a human to catch its errors — which actually *supports* the "senior = risk reduction / juniors can't evaluate a 250-line agent script" mechanism. Net: "juniors gain least from AI" is contradicted; "juniors are dangerous with unsupervised agents / seniors reduce risk" survives. The two claims were conflated in the original and are now separable.
+
+**Relationship to the rest of the vault:** this is the career-side consequence of the same premise as [[relationships-as-moat]] ("Claude levels pure programming skill"). What rises instead is judgment ([[product-ownership]]) and trust ([[relationships-as-moat]]). It also sharpens [[methodology-as-moat]]: a senior's "knowing where the rocks are" ([[2026-06-15-konspekt-aphorisms]]) is exactly the risk-reduction product described here.
+
+## Evidence
+
+- Seniors more valuable, juniors "completely irrelevant" — [[2026-07-06-sebastian-interview-ai-and-software-engineering]]
+- "AI does the same mistakes humans do because it's trained on our mistakes." — same source
+- The "allow for all future" → leaked keys / dumped databases security argument — same source
+- The printer anecdote (instruct-and-verify beats coding) — same source
+- Standout conclusion: "Seniority = risk reduction." — same source
+- Convergent: "knowing where the rocks are is your expertise" — [[2026-06-15-konspekt-aphorisms]]
+- **Counter-evidence (adversarial):** AI's productivity gains are largest for the *least*-experienced (Brynjolfsson +34% novices; Copilot RCT) — inverts "juniors irrelevant" on the productivity axis — [[ai-productivity-evidence]] / [[2026-07-18-ai-productivity-adversarial-evidence]]
+
+## Related Pages
+
+- [[product-ownership]] — the other durable human skill
+- [[relationships-as-moat]] — shares the "skill is leveled" premise
+- [[future-of-engineering-work]] — team collapse and the coder→director shift
+- [[methodology-as-moat]] — knowing-where-it-breaks as the defensible product
+- [[ai-productivity-evidence]] — the empirical counter: AI's gains tilt to novices, not seniors
+- [[overview]]
+
+## Contradictions / Uncertainty
+
+- **The pipeline paradox is unresolved:** if juniors are frozen out, seniors stop being produced. Single-source; the interview names the inversion but not the fix. `Status: tentative`.
+- Sebastian runs a services firm that sells senior judgment — the claim flatters his own staffing model. Partly offset by the concrete security reasoning, which stands on its own.
+- "Juniors completely irrelevant" is rhetorical overstatement; the security argument only shows juniors are *dangerous with unsupervised agent access*, not that they have no role. Now backed by evidence: AI's *productivity* dividend goes disproportionately to juniors ([[ai-productivity-evidence]]), so "irrelevant" is the wrong word on that axis — though whether that translates to junior *hiring/wages* is unmeasured, and the "can't supervise an agent safely" risk remains.
+- **A single interview vs. a body of studies.** This page's claim is one founder's assertion (with a self-interested staffing model); the counter is an RCT + a peer-reviewed field study + two large surveys. On evidentiary weight the adversarial side is stronger — but it is early-2025-scoped and mostly non-developer, so neither side is settled. `Status: contested`.
+
+## Next Questions
+
+- If juniors are frozen out, how does anyone become a senior — apprenticeship on supervised agents?
+- Is "senior = risk reduction" a durable moat, or does better agent tooling (permissioning, sandboxing) erode the security gap?
+- Which senior judgment transfers to directing AI, and which was tied to hand-coding and now decays?

wiki/concepts/tam-sam-som.md

@@ -0,0 +1,48 @@
+# TAM / SAM / SOM
+
+#concept #strategy #positioning
+
+## Summary
+
+The standard market-sizing frame — three nested circles from "everyone who could conceivably buy" down to "who you can win now." In the vault it matters for one directional rule: **investors reward the outer circle, execution starts from the inner one** ([[2026-07-26-how-to-build-a-billion-dollar-company-2027]], [[oskar-hartmann]]: SOM > TAM at the start). It is the venture-vocabulary form of the vault's oldest rule, [[niche-selection]]'s "niche is upstream of everything."
+
+## Current Understanding
+
+**The three circles:**
+
+| Term | Expands to | Means | Example (from the source's own case) |
+|---|---|---|---|
+| **TAM** | Total Addressable Market | Everyone in the world who could conceivably buy a product like yours | "AI agents for every profession" |
+| **SAM** | Serviceable Available Market | The slice your actual product and channels could reach | US home-services businesses |
+| **SOM** | Serviceable Obtainable Market | The slice you can realistically **win now**, given who you are today | "AI agent answering calls for HVAC/plumbers/roofers" |
+
+**The directional rule — SOM > TAM at the start.** Pitch decks lead with TAM because venture math needs outlier room ([[venture-fit]]); but the start must be a small market where you can take a meaningful share *immediately*. Hartmann's formula: **big market + small winnable sub-market + MVP, not a fantasy product.** His exemplar: Manifest (Дэн Мишин) became a unicorn starting from **immigration law alone**, not "AI lawyer"; Fab.com's healthy peak was $100M on design home goods for a loyal base — it died reaching for the outer circle ([[venture-fit]]).
+
+**The beachhead reading.** The TAM doesn't disappear — it stays *behind* the SOM as the growth story. This is the nuance the frame adds over the services sources' niche rule: a niche is not (necessarily) a destination, it's the winnable entry point to a larger market. Compare [[niche-selection]]'s "Shopify dev for fashion brands beats web developer" — same move, stated without the outer circles.
+
+**Terminology note:** the ingested source uses only TAM and SOM; **SAM is standard industry vocabulary supplied for completeness** (from general knowledge, not from any ingested source). Definitions of the boundaries vary across the industry — some define SOM as a near-term revenue forecast rather than a segment — so treat the circles as a thinking frame, not a measurement standard.
+
+## Evidence
+
+- "Investors love a big TAM, but start from a SOM — a small market where you can take a significant share *now*"; HVAC-agent vs all-professions; Manifest immigration-law unicorn; big-market + winnable-sub-market + MVP formula — [[2026-07-26-how-to-build-a-billion-dollar-company-2027]] ([[oskar-hartmann]])
+- The same rule without the vocabulary, from two other traditions: "niche is upstream of everything" (Tony), "80% is WHO not WHAT" (Rodenko), "Shopify dev for fashion brands" (AB Analytics) — [[niche-selection]]
+- SAM definition and boundary caveats — general knowledge, **no ingested source** (recorded 2026-07-26 from a Q&A session)
+
+## Related Pages
+
+- [[niche-selection]] — the vault's canonical page for *choosing* the inner circle; this page supplies the sizing vocabulary
+- [[venture-fit]] — why decks lead with TAM, and what chasing it prematurely did to Fab.com
+- [[sales-channel-as-moat]] — the SOM is where a repeatable channel gets proven before it scales outward
+- [[oskar-hartmann]] — the voice that brought the frame into the vault
+- [[overview]]
+
+## Contradictions / Uncertainty
+
+- **SAM is unsourced within the vault** — standard industry usage, added for completeness and marked as such. If a future ingested source defines the circles differently, that source wins and this page records the conflict.
+- The frame assumes the beachhead-to-bigger-market path is real; [[niche-selection]] notes some niches are chosen precisely for durable narrowness (AI-weak methodologies). A SOM picked as a *beachhead* and a niche picked as a *fortress* are different strategies wearing the same circle — no source distinguishes them.
+- Sizing numbers attached to these terms in pitch practice are notoriously constructed top-down; nothing in the vault yet covers *how to size* any circle honestly.
+
+## Next Questions
+
+- For [[eugene]]: what is his SOM in one sentence — and is his narrow segment (industrial-equipment CV/embedded) a beachhead to a larger market or a fortress niche?
+- Is there an honest bottom-up sizing method (customer count × realistic price from [[pricing-from-value]]) worth adding when a source supplies one?

wiki/concepts/team-growth-ceiling.md

@@ -0,0 +1,61 @@
+# Team Growth Ceiling
+
+#concept #leadership #team
+
+`Status: tentative` — single source, a promotional-style leadership clip with anecdotal evidence only. Speaker identified 2026-07-20 as [[dan-martell]] (confirmed by the vault owner), who also carries [[marketing-system]] — so this page and that one are **one author, not two independent voices**.
+
+## Summary
+
+A company's growth is capped by its people's growth: to double the business, each team member must roughly double too. The ceiling is human, not market. Leadership's job is to make that math explicit and run mechanisms that force honesty about who is growing — rather than silently tolerating stagnation.
+
+## Current Understanding
+
+The single source ([[2026-07-19-your-company-cant-outgrow-your-team]]) proposes one thesis plus four mechanisms:
+
+1. **State the growth math out loud** — "the company doubling means you doubling" cannot stay implicit. *"Good got you on the team. Great keeps you on the team."*
+2. **Teach a philosophy, not a task list** — the speaker's "Business Athlete" framework (only two of seven practices captured: *have a coach* — people own their own development; *have a practice schedule* — "practice until we can't get it wrong"). Behaviors, not skills.
+3. **Public scoreboard, private criticism** — everyone's standing visibly posted creates self-driven accountability; hard conversations stay in the 1-on-1.
+4. **The Keeper Test** (via Netflix) — "would I fight to keep them against a 30% offer?" Every "no" becomes a documented development plan or a departure; the point is forced honesty, not fast firing.
+5. **Values as hire → inspire → fire** — screen for values before skills, tie decisions to them, and name the violated value at every firing. *"Values aren't what you say they are. They're what you tolerate."* Includes the aphorism *"Complexity fails, simple scales."*
+
+This is the vault's first page about **running the delivery organization** — distinct from Branch A (selling) and Branch B (AI's labor shift), though it becomes more load-bearing if Branch B is right: in a 2–3 person AI-era team, one non-growing person is a third of capacity.
+
+**What the author attribution reveals (added 2026-07-20).** With the speaker identified as [[dan-martell]], this page and [[marketing-system]] turn out to be the same argument pointed in two directions:
+
+| | Internal (this page) | External ([[marketing-system]]) |
+|---|---|---|
+| The stall | Company plateaus | Revenue plateaus (~$1.5M) |
+| The misdiagnosis | "The market is capped" | "The market is capped" |
+| The real cause | People stopped growing | No system was ever built |
+| The mechanism | *"Practice until we can't get it wrong"* | *"The only thing you control is the volume of the reps"* |
+
+Two things follow. First, Martell's unifying claim is **the ceiling is never the market** — every plateau is relocated to something the founder controls. Second, both halves run on the same engine: **deliberate practice at volume**, applied to people in one case and to publishing in the other. That coherence makes the worldview easier to evaluate as a whole — and see Contradictions for why it is also the reason to discount it slightly.
+
+## Evidence
+
+- All claims: [[2026-07-19-your-company-cant-outgrow-your-team]] — anecdotal leadership talk, no data; framework only partially captured (5 of 7 practices missing).
+- Author: [[dan-martell]] — attribution confirmed by the vault owner 2026-07-20 (curator testimony; the clip itself names no speaker).
+- Same author applying the same practice-at-volume mechanism outward — [[2026-07-20-referrals-will-sink-your-business]], [[marketing-system]]
+
+## Related Pages
+
+- [[dan-martell]] — the author; his other material sits in Branch A
+- [[marketing-system]] — the same "the ceiling is never the market" argument aimed outward
+- [[future-of-engineering-work]] — team collapse 8→2–3 makes per-person growth rate more decisive, strengthening this thesis for small teams
+- [[methodology-as-moat]] — internal philosophy-as-operating-system is the inward sibling of the outward "sell your proven method"
+- [[sales-discipline]] — same consistency-over-intensity logic applied to selling instead of people development
+- [[overview]]
+
+## Contradictions / Uncertainty
+
+- **No counter-evidence in the vault, but no support either** — single anecdotal source; nothing tests whether public scoreboards or the Keeper Test work outside larger sales-flavored orgs.
+- **The cross-branch coherence is not corroboration.** This page and [[marketing-system]] agreeing that "the ceiling is never the market" is **one man's worldview stated twice**, not two findings. Note the convenience, too: a founder coach whose diagnosis is always "the constraint is internal and fixable" is describing a world in which coaching is always the answer. That is a reason to hold both pages `tentative` independent of the missing data.
+- **"Have a coach" is one of the seven Business Athlete practices** — taught by a coach. Not disqualifying, but it belongs on the record beside the framework.
+- **Possible tension with tiny teams:** the Keeper Test presumes you could part with a "no" — in a 2–3 person team each member may be a single point of failure, making the test harder to act on (raised, unresolved).
+- Growth framing assumes headcount-stable scaling through people development; Branch A's productization logic scales through *method*, not people — the two are complementary but unreconciled by any source.
+
+## Next Questions
+
+- ✅ Speaker identified ([[dan-martell]], 2026-07-20). Still open: recover the full Business Athlete framework (7 practices) and the three values — his other published material is now a findable route to both.
+- Does the vault's owner ([[eugene]]) even have a team yet? If solo, this concept is dormant until first hire — worth flagging in any 90-day plan query.
+- Find a source on people-development vs. process/productization as the scaling constraint for small agencies.

wiki/concepts/technical-founder-trap.md

@@ -0,0 +1,58 @@
+# Technical Founder Trap
+
+#concept #positioning #marketing
+
+## Summary
+
+Technical founders are excellent at **solving** problems and poor at **explaining** how they solve them — and the explaining is what sells. *"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."* ([[dan-martell]], [[2026-07-20-referrals-will-sink-your-business]]). The claim is that this single gap is upstream of a technical founder's marketing failure: not laziness, not the wrong channel, but the absence of a communication skill they never had to build. `Status: tentative` — one source asserts the mechanism with no data — but it connects several existing pages that were describing the same disease from different sides.
+
+## Current Understanding
+
+**The mechanism.** Solving and explaining are different skills, and a technical career selects hard for the first while never testing the second. The founder's instinct — *give me the problem, I'll go* — is precisely what makes them valuable in delivery and invisible in market. The source's claim is sequencing: **communication is the unlock**, and only after it exists do the paid channels work, "because you now have something to say and know how to say it." Publishing is therefore proposed as *practice*, not just distribution — the stated reason for going live daily is to get reps at explaining ([[marketing-system]]).
+
+**The same failure, seen from the buyer's side.** [[dmitry-rodenko]]'s central diagnostic says *"'expensive' doesn't exist — 'I don't see what for' does"* ([[pricing-from-value]]). That is this concept restated as a symptom: when a buyer can't see what the money is for, the usual cause is not that the value is absent but that it was never articulated. Two unconnected traditions — a US founder coach and a Russian-language dev-sales practitioner — land on the same point from opposite ends of the transaction. That convergence, not either source alone, is the reason to take this seriously.
+
+**Why it compounds with the rest of the vault.** Nearly every asset the vault tells a developer to build is *articulation-dependent*:
+
+- [[methodology-as-moat]] — a proven method you cannot describe is not a sellable asset; "people buy your standards" presumes the standards are legible.
+- [[outcome-based-selling]] — selling a countable outcome instead of hours *is* an act of explanation; the outcome has to be named before it can be priced.
+- [[information-vs-implementation]] — the content mandate is literally "explain what you do"; its 5×10×4 factory is a machine for forcing the reps.
+- [[pain-discovery]] — the standard is naming the buyer's pain *better than they can name it themselves* ("how do you know?"). That is an explanation skill aimed at their world rather than yours.
+- [[productized-service]] — fixing scope, price, and **name** is packaging, i.e. explanation crystallized into an offer.
+
+Read together: the vault's whole selling chain assumes an articulation capability it never asks whether the reader has. This page is where that assumption is made explicit.
+
+**The product-startup form of the same trap — feature #26 syndrome** ([[2026-07-26-how-to-build-a-billion-dollar-company-2027]], [[oskar-hartmann]], added 2026-07-26). His live example: an AI startup's team is building the 26th feature in Jira while revenue sits below 1M ₽/month — "the most valuable thing right now is not feature #26, it's a repeatable go-to-market." Same disease, different symptom: Martell's founder can't *explain*, Hartmann's founder *builds instead of selling* — both are the technical instinct ("give me the problem and I'll go") consuming the hours that selling needs. Hartmann's paired rule — the founder is the company's chief salesperson, no exceptions, and he won't invest otherwise ([[sales-discipline]]) — is the blunt behavioral fix where Martell prescribes the skill-building one (reps at explaining). A third tradition independently locating the constraint *outside* the building work strengthens the page's core claim more than another coaching source would. No framework is offered — the remedy is reps at explaining in public (answer questions, add value, explain what you do), measured as reps rather than views. See [[marketing-system]] and [[sales-discipline]].
+
+## Evidence
+
+- The trap, the "same guy" framing, and communication-as-unlock — [[2026-07-20-referrals-will-sink-your-business]], [[dan-martell]] (single source for the concept as stated)
+- *"'Expensive' doesn't exist — 'I don't see what for' does"* (the buyer-side symptom) — [[2026-06-15-rodenko-selling-development-expensively]], [[pricing-from-value]]
+- "Explain what you do" as the content mandate, and a factory for practising it — [[2026-07-18-information-is-free-implementation-is-paid]], [[information-vs-implementation]]
+- Name the pain better than the buyer can — [[pain-discovery]]
+- Feature-#26 syndrome; founder-as-chief-salesperson as the behavioral fix — [[2026-07-26-how-to-build-a-billion-dollar-company-2027]] ([[oskar-hartmann]], independent tradition)
+- Slogan-grade restatement of the build-instead-of-sell form: stated audience is "developers who over-invest in building and under-invest in selling," blocker diagnosed as psychological, not technical — [[2026-07-29-start-a-business-with-claude-code]] ([[dan-martell]], attributed 2026-07-29 — same author as this page's founding source, so restatement, not corroboration)
+- Adjacent, from the labor-market side: value migrates to judgment and client-facing ownership, both articulation-heavy — [[product-ownership]], [[future-of-engineering-work]]
+
+## Related Pages
+
+- [[marketing-system]] — the source's prescribed cure (publish for reps); this page is its diagnosis
+- [[information-vs-implementation]] — what to actually say once you can explain
+- [[pricing-from-value]] — the buyer-side symptom ("I don't see what for")
+- [[methodology-as-moat]] — an inarticulable method is not a moat
+- [[product-ownership]] — owning an outcome requires being able to state it
+- [[eugene]] — the vault's resident technical operator, whose stated blocker this reframes
+- [[overview]]
+
+## Contradictions / Uncertainty
+
+- `Status: tentative`. **Single source, asserted not demonstrated**, and self-serving: a coach who sells communication-heavy programs diagnosing communication as the bottleneck. No data, no counterfactual, no failed cohort.
+- **[[sebastian]] offers a rival diagnosis of the same symptom.** If a technical founder isn't winning work, Sebastian's answer is not "you can't explain" but "you have no in-person relationships" — the fix is recurring physical presence, not better articulation ([[relationships-as-moat]]). These are genuinely different causal claims about the same observation, and the vault has no evidence to choose between them. They are not exclusive: trust may be necessary and articulation sufficient, or vice versa.
+- **Possible reverse causation.** "Can't explain it" may be downstream of not having a [[niche-selection|chosen niche]] or a repeatable [[productized-service|package]] — you can't explain a service that isn't yet a definite thing. Under that reading the fix is offer clarity, not communication practice, and the vault leans that way elsewhere ("category = pain + result").
+- **The convergence argument is weaker than it looks.** Rodenko's "I don't see what for" is about a *specific* sales conversation; this source's claim is about a founder's *general* market invisibility. Same theme, different scope — treat the convergence as suggestive, not confirmatory.
+
+## Next Questions
+
+- Is the bottleneck articulation or offer definition? A cheap test: can the founder state the outcome, buyer, and price in one sentence? If yes, the problem is distribution; if no, it's [[productized-service]], not this page.
+- Does publishing actually train explanation, or only train *performing* explanation for a feed? The two may diverge for B2B services sold in private conversations.
+- For [[eugene]] — a computer-vision/embedded developer whose stated blocker is building a network — is the missing skill really networking, or the ability to say what he does in a sentence a non-engineer repeats to someone else? (That second form is also what makes a [[referrals|referral]] transmissible.)

wiki/concepts/unit-economics.md

@@ -0,0 +1,59 @@
+# Unit Economics
+
+#concept #pricing #finance
+
+## Summary
+
+The full-cost arithmetic beneath a price — what it actually costs to win, serve, and *keep* a customer, and what margin must remain. Founded by [[2026-07-26-how-to-build-a-billion-dollar-company-2027]] ([[oskar-hartmann]]), this page **partially fills a gap the vault's own meta-analysis flagged from the start** ("B2B unit economics — CAC/LTV — unfilled by the corpus"). Partial, because the source's principles are general and its examples consumer-grade; the B2B-services version is still missing. `Status: tentative` — single author (two sources since 2026-07-26: the Zavent post-pay trap and the CAC-burn restatement are the same voice, so consistency rather than corroboration).
+
+## Current Understanding
+
+**The central diagnosis: most entrepreneurs sell below the real cost.** Not below the *visible* cost — below the full one. Systematically forgotten lines:
+
+- distribution and sales cost (the channel itself is a cost of goods — [[sales-channel-as-moat]])
+- **repeat** acquisition and retention (winning the customer once is not winning them)
+- transport, amortization
+- inventory write-offs
+
+The resulting "cash gaps" founders explain away as timing are, in Hartmann's telling, **real losses** that were priced in from the day the price was set. This is [[pricing-from-value]]'s "sell dear" rule arrived at from the cost side rather than the value side — an independent tradition converging on the same instruction.
+
+**The sequence:** (1) prove the product is *needed*; (2) prove you can produce it **far below** willingness-to-pay; (3) the spread must cover *everything* — marketing, distribution, sales, warehouse — **with a buffer**. Note the order: demand first, cost structure second, price last. Compare [[productized-service]]'s validate-before-build rule — same discipline, one level deeper.
+
+**The buffer rule / best-year fallacy:** never take your best year as the base. The best year is a once-a-decade anomaly; budget from it and every normal year reads as a crisis. Outside razor-thin retail, margin must carry a buffer.
+
+**LTV → CAC → moat:** a business that has run its channel long enough to *know* lifetime value can pay up to **~⅓ of lifetime profit** for a customer on day one (US credit-card customer ≈ **$1,000 CAC**; 1,000 customers = $1M — "it doesn't come cheaper"). That spending level is an **entry barrier**: competitors without the LTV statistics can't rationally match the bid. This is also the honest explanation of loss-making venture rounds — they fund negative unit economics until the LTV arrives ([[venture-fit]]).
+
+**Post-payment turns you into your customer's bank** ([[2026-07-26-main-principle-of-successful-business]], added 2026-07-26 — same author, second source). The Zavent anti-case: demand looked strong, but customers would only pay **3 months after delivery**, so the company was silently financing its clients — a working-capital cost that belongs on the forgotten-lines list above. When prepayment was required, conversion collapsed, revealing the real demand level. Twin lessons: **prepayment willingness is itself a unit-economics variable** (it decides whose balance sheet carries the build — [[sell-before-build]]), and payment *timing* is part of the full cost of a sale.
+
+**The CAC-burn barrier, restated** (same source): once PMF is proven and unit economics are positive, deliberately spend heavily per customer ($80–100 CAC in his example) so no newcomer can afford to enter. Consistent with the ⅓-of-LTV rule from his first source — framework stability for this author, not corroboration.
+
+**Pricing power as the PMF test** (recorded in full on [[pricing-from-value]]): if raising prices doesn't shrink the customer flow, you have PMF; if a marketplace sets your price, "you're in a simulation of entrepreneurship." Unit economics you don't control aren't yours.
+
+## Evidence
+
+- Full-cost list, cash-gaps-are-losses, the three-step sequence, buffer/best-year rule, LTV×⅓ CAC, $1,000 credit-card CAC, entry-barrier logic — [[2026-07-26-how-to-build-a-billion-dollar-company-2027]]
+- Zavent post-payment trap ("a bank financing its clients"); $80–100 CAC-burn barrier restated — [[2026-07-26-main-principle-of-successful-business]] (same author — consistency, not corroboration)
+- Convergent from the value side: price must fund the work that makes the service good ("below ~$100/mo there's no margin…") — [[2026-07-17-design-the-perfect-offer]], [[pricing-from-value]]
+- Convergent: Solution-model margin 30–50% vs staff-aug rate race — [[solution-vs-staff-augmentation]]
+- The gap this partially fills — flagged in [[2026-06-15-meta-analysis-selling-dev-in-ai-era]]
+
+## Related Pages
+
+- [[pricing-from-value]] — the value side of the same price; pricing power lives there
+- [[sales-channel-as-moat]] — the channel whose cost and payback this math governs
+- [[venture-fit]] — negative unit economics as a deliberate, funded phase
+- [[productized-service]] — validate-before-build is step 1 of the sequence here
+- [[marketing-system]] — "money in → more money out" is a unit-economics statement
+- [[overview]]
+
+## Contradictions / Uncertainty
+
+- `Status: tentative` — one source; every number ($1,000 CAC, ⅓-of-LTV) is a stage figure without citation.
+- **The examples are consumer/product; the vault's domain is B2B services.** Services LTV is lumpy (projects, retainers), churn behaves differently, and "repeat acquisition cost" may be the [[referrals]]/[[partnerships]] machinery rather than ad spend. The transfer is plausible but unshown — the flagged B2B gap is *narrowed*, not closed.
+- **Tension with the vault's spend-nothing school:** Martell's $0 blueprint says spend nothing until customers pay ([[sales-discipline]]); Hartmann describes rationally spending $1,000 to acquire one customer. Reconcilable as stages (pre-LTV-knowledge vs post-), but that seam is exactly what neither source specifies.
+
+## Next Questions
+
+- What are CAC and LTV for a niched dev-services operator, concretely — and does the ⅓ rule mean anything when LTV is 2–3 projects?
+- Where is the line between a venture-fundable negative-unit-economics phase and Fab.com-style self-deception ([[venture-fit]])?
+- Which of the forgotten cost lines apply to services (repeat acquisition, surely; write-offs — as unbilled rework?)?

wiki/concepts/venture-fit.md

@@ -0,0 +1,48 @@
+# Venture Fit
+
+#concept #strategy #finance
+
+## Summary
+
+Whether a business belongs on the venture track at all — and what happens when one that doesn't is stretched onto it. Founded by [[2026-07-26-how-to-build-a-billion-dollar-company-2027]] ([[oskar-hartmann]]): **only ~1% of businesses fit venture**, fundraising is an *obligation* rather than a success, and "растяжка на венчурные ожидания" (stretching onto venture expectations) kills otherwise-healthy companies. New territory for the vault — no prior source discussed funding structure — and directly relevant to the owner's implicit default (bootstrapped services). `Status: tentative` — single source, but the central case is one the speaker claims a shareholder's view of.
+
+## Current Understanding
+
+**The 1% rule.** Venture math needs outlier outcomes; European VCs reportedly won't engage below $100B+ potential. Everything else — most real businesses — is structurally mis-fit for the instrument, not merely "too small yet."
+
+**The cautionary case — Fab.com** (Hartmann was a shareholder): a genuinely good niche business ($50M→$100M revenue, loyal design-goods audience) raised at a **$1.5B valuation**, inheriting a $10B-revenue expectation. The prescribed behaviors followed — marketing spend up, international expansion, more countries, more product lines, free shipping everywhere — and **"the only thing that grew was losses."** It never got back to $100M; bankrupt. The mechanism worth keeping: the round didn't fund the existing business, it **replaced the business with a different, imaginary one**, and the real one died in the costume.
+
+**The alternatives are not consolation prizes:**
+
+- The top-20 largest **private** US companies do $30B+ revenue and still belong to founding families.
+- Slow mid-market growth ($10M→$100M) is "вполне себе бизнес" — just not a venture one.
+- Hartmann's own ShoppingLive: built on "a couple hundred thousand dollars," ~9-month payback, reinvested profits → Russia's #1 TV shop, one of his best-ROI ventures.
+- The 2026 twist: AI labs (Anthropic, SpaceX, OpenAI) are absorbing nearly all free venture cash anyway — "you're either a top AI lab or, for the venture market, you don't exist" ([[ai-market-shift]]). The default path for everyone else is his "amusement park" model: 9-month-payback units, reinvest, grow slowly.
+
+**Relation to the vault:** this is the funding-layer version of a discipline the vault already holds at the offer layer — refuse borrowed expectations, price and grow from real economics ([[unit-economics]]). It also implicitly sides with the vault's whole services thesis: a niched dev-services firm is definitionally in the 99%, and per this source that is a *fine place to be*, not a failure state. Note the counterweight inside the same source: venture money is the rational instrument when a [[sales-channel-as-moat|channel]] must be burned in at negative unit economics before LTV lands — so the claim is "know which game you're in," not "venture is bad."
+
+## Evidence
+
+- 1% rule, $100B screen, Fab.com collapse, private-company alternatives, ShoppingLive case, AI capital suction — [[2026-07-26-how-to-build-a-billion-dollar-company-2027]] (single source)
+- Venture rounds as deliberate negative-unit-economics funding — same source, on [[unit-economics]]
+
+## Related Pages
+
+- [[unit-economics]] — the math that decides which track you're on
+- [[tam-sam-som]] — the sizing vocabulary venture decks lead with, and why execution starts at the inner circle
+- [[sales-channel-as-moat]] — what venture money legitimately buys
+- [[ai-market-shift]] — the 2026 capital landscape that shrinks the venture door further
+- [[venture-fit]] is the funding-layer sibling of [[pricing-from-value]]'s refuse-borrowed-benchmarks discipline
+- [[eugene]] — the owner's implicit track (bootstrapped services) — this page says that default is sound
+- [[overview]]
+
+## Contradictions / Uncertainty
+
+- `Status: tentative` — single source; the 1% figure and $100B screen are assertions; Fab.com's collapse has public reporting but the *causal* story (the round killed it, not e-commerce headwinds) is the speaker's interpretation from inside.
+- Survivorship in the alternatives: family-owned giants and ShoppingLive are selected successes of slow growth, exactly the selection error the source criticizes elsewhere (best year ≠ base).
+- The vault has no pro-venture voice to balance this — one more single-sided position, flagged as such.
+
+## Next Questions
+
+- Where do AI-era dev-services firms sit — is there now a venture-fundable services shape (agent-ops, harness platforms), or does the 1% rule exclude services categorically?
+- What is the minimum honest test that a business is in the 1% before taking the obligations?