commit 60176d2fdc74d7730b10625610464cd6b42e375f Author: EugeneTes Date: Thu Jul 30 11:15:52 2026 +0200 all diff --git a/.obsidian/app.json b/.obsidian/app.json new file mode 100644 index 0000000..9e26dfe --- /dev/null +++ b/.obsidian/app.json @@ -0,0 +1 @@ +{} \ No newline at end of file diff --git a/.obsidian/appearance.json b/.obsidian/appearance.json new file mode 100644 index 0000000..9e26dfe --- /dev/null +++ b/.obsidian/appearance.json @@ -0,0 +1 @@ +{} \ No newline at end of file diff --git a/.obsidian/core-plugins.json b/.obsidian/core-plugins.json new file mode 100644 index 0000000..639b90d --- /dev/null +++ b/.obsidian/core-plugins.json @@ -0,0 +1,33 @@ +{ + "file-explorer": true, + "global-search": true, + "switcher": true, + "graph": true, + "backlink": true, + "canvas": true, + "outgoing-link": true, + "tag-pane": true, + "footnotes": false, + "properties": true, + "page-preview": true, + "daily-notes": true, + "templates": true, + "note-composer": true, + "command-palette": true, + "slash-command": false, + "editor-status": true, + "bookmarks": true, + "markdown-importer": false, + "zk-prefixer": false, + "random-note": false, + "outline": true, + "word-count": true, + "slides": false, + "audio-recorder": false, + "workspaces": false, + "file-recovery": true, + "publish": false, + "sync": true, + "bases": true, + "webviewer": false +} \ No newline at end of file diff --git a/.obsidian/graph.json b/.obsidian/graph.json new file mode 100644 index 0000000..9628e1c --- /dev/null +++ b/.obsidian/graph.json @@ -0,0 +1,30 @@ +{ + "collapse-filter": false, + "search": "dan-martel", + "showTags": false, + "showAttachments": false, + "hideUnresolved": false, + "showOrphans": true, + "collapse-color-groups": false, + "colorGroups": [ + { + "query": "dan-martel", + "color": { + "a": 1, + "rgb": 14048348 + } + } + ], + "collapse-display": false, + "showArrow": false, + "textFadeMultiplier": 0, + "nodeSizeMultiplier": 1.32754677754678, + "lineSizeMultiplier": 1, + "collapse-forces": true, + "centerStrength": 0.518713248970312, + "repelStrength": 10, + "linkStrength": 1, + "linkDistance": 250, + "scale": 0.9999999999999997, + "close": false +} \ No newline at end of file diff --git a/.obsidian/workspace.json b/.obsidian/workspace.json new file mode 100644 index 0000000..fd0c2ef --- /dev/null +++ b/.obsidian/workspace.json @@ -0,0 +1,225 @@ +{ + "main": { + "id": "c3a039067d6ccded", + "type": "split", + "children": [ + { + "id": "9db2c45bb6cc3d59", + "type": "tabs", + "children": [ + { + "id": "c00e98c46612fa64", + "type": "leaf", + "state": { + "type": "markdown", + "state": { + "file": "wiki/concepts/sales-channel-as-moat.md", + "mode": "source", + "source": false + }, + "icon": "lucide-file", + "title": "sales-channel-as-moat" + } + } + ] + } + ], + "direction": "vertical" + }, + "left": { + "id": "6befcb09bda1768f", + "type": "split", + "children": [ + { + "id": "a50e04229321aade", + "type": "tabs", + "children": [ + { + "id": "f09c25129a01a079", + "type": "leaf", + "state": { + "type": "file-explorer", + "state": { + "sortOrder": "alphabetical", + "autoReveal": false + }, + "icon": "lucide-folder-closed", + "title": "Files" + } + }, + { + "id": "6174f95c42d6c64c", + "type": "leaf", + "state": { + "type": "search", + "state": { + "query": "", + "matchingCase": false, + "explainSearch": false, + "collapseAll": false, + "extraContext": false, + "sortOrder": "alphabetical" + }, + "icon": "lucide-search", + "title": "Search" + } + }, + { + "id": "538883ba7e5ca7a8", + "type": "leaf", + "state": { + "type": "bookmarks", + "state": {}, + "icon": "lucide-bookmark", + "title": "Bookmarks" + } + } + ] + } + ], + "direction": "horizontal", + "width": 300 + }, + "right": { + "id": "e5d021e9877463a8", + "type": "split", + "children": [ + { + "id": "69587e32b7c576fe", + "type": "tabs", + "children": [ + { + "id": "e6b0039a27587d2d", + "type": "leaf", + "state": { + "type": "backlink", + "state": { + "file": "wiki/concepts/sales-channel-as-moat.md", + "collapseAll": false, + "extraContext": false, + "sortOrder": "alphabetical", + "showSearch": false, + "searchQuery": "", + "backlinkCollapsed": false, + "unlinkedCollapsed": true + }, + "icon": "links-coming-in", + "title": "Backlinks for sales-channel-as-moat" + } + }, + { + "id": "f597b144c126a298", + "type": "leaf", + "state": { + "type": "outgoing-link", + "state": { + "file": "wiki/queries/2026-07-17-best-method-first-client.md", + "linksCollapsed": false, + "unlinkedCollapsed": true + }, + "icon": "links-going-out", + "title": "Outgoing links from 2026-07-17-best-method-first-client" + } + }, + { + "id": "740ac4e9f64a5c05", + "type": "leaf", + "state": { + "type": "tag", + "state": { + "sortOrder": "frequency", + "useHierarchy": true, + "showSearch": false, + "searchQuery": "" + }, + "icon": "lucide-tags", + "title": "Tags" + } + }, + { + "id": "66183b16cb6b19ad", + "type": "leaf", + "state": { + "type": "all-properties", + "state": { + "sortOrder": "frequency", + "showSearch": false, + "searchQuery": "" + }, + "icon": "lucide-archive", + "title": "All properties" + } + }, + { + "id": "798b76e26e832c05", + "type": "leaf", + "state": { + "type": "outline", + "state": { + "file": "wiki/queries/2026-07-17-best-method-first-client.md", + "followCursor": false, + "showSearch": false, + "searchQuery": "" + }, + "icon": "lucide-list", + "title": "Outline of 2026-07-17-best-method-first-client" + } + } + ] + } + ], + "direction": "horizontal", + "width": 300, + "collapsed": true + }, + "left-ribbon": { + "hiddenItems": { + "switcher:Open quick switcher": false, + "graph:Open graph view": false, + "canvas:Create new canvas": false, + "daily-notes:Open today's daily note": false, + "templates:Insert template": false, + "command-palette:Open command palette": false, + "bases:Create new base": false + } + }, + "active": "c00e98c46612fa64", + "lastOpenFiles": [ + "wiki/concepts/cloning-over-originality.md.tmp.31664.60157931c440", + "wiki/concepts/pain-discovery.md.tmp.31664.fd44069a7390", + "wiki/concepts/outcome-based-selling.md.tmp.31664.3afc0d2840e9", + "wiki/sources/2026-07-29-start-a-business-with-claude-code.md", + "wiki/queries/2026-07-26-eugene-90-day-plan.md.tmp.31664.8fdffc9b0403", + "wiki/overview.md.tmp.31664.baa841330c38", + "wiki/overview.md.tmp.31664.f6bf352a58b3", + "wiki/overview.md.tmp.31664.25a91d122cfb", + "wiki/concepts/client-acquisition-channels.md.tmp.31664.7305860e89c8", + "wiki/concepts/client-acquisition-channels.md.tmp.31664.48635f17ec90", + "wiki/concepts/client-acquisition-channels.md.tmp.31664.1274e2eed13f", + "wiki/concepts/client-acquisition-channels.md.tmp.31664.65d2c03d9c74", + "raw/sources/Start a business with Claude Code.md", + "wiki/concepts/offer-ladder.md", + "wiki/entities/dan-martell.md", + "wiki/entities/claude-code.md", + "raw/sources/Главный Принцип УСПЕШНОГО БИЗНЕСА.md", + "raw/sources/zBcWcignqng.conclusions.md", + "wiki/queries/2026-07-26-eugene-90-day-plan.md", + "wiki/concepts/sell-before-build.md", + "wiki/sources/2026-07-26-main-principle-of-successful-business.md", + "wiki/concepts/tam-sam-som.md", + "raw/sources/Как Построить МИЛЛИАРДНУЮ КОМПАНИЮ в 2027.md", + "wiki/concepts/venture-fit.md", + "wiki/concepts/unit-economics.md", + "wiki/concepts/sales-channel-as-moat.md", + "wiki/entities/oskar-hartmann.md", + "wiki/sources/2026-07-26-how-to-build-a-billion-dollar-company-2027.md", + "raw/sources/Make My First $100K in Month.md", + "wiki/sources/2026-07-23-make-my-first-100k-in-month.md", + "raw/sources/Stop Cold Calling, Do This Instead.md", + "raw/sources/ИИ глупый!.md", + "wiki/concepts/partnerships.md", + "wiki/sources/2026-07-22-stop-cold-calling-do-this-instead.md", + "index.md", + "wiki/concepts/ai-market-shift.md" + ] +} \ No newline at end of file diff --git a/CLAUDE.md b/CLAUDE.md new file mode 100644 index 0000000..2f8d726 --- /dev/null +++ b/CLAUDE.md @@ -0,0 +1,189 @@ +# LLM Wiki Schema (Operational Contract) + +You are the dedicated maintainer of this vault as a persistent, compounding wiki. + +## Mission + +Maintain a high-signal personal knowledge base where: + +- `raw/` contains immutable source materials. +- `wiki/` contains LLM-authored, continuously maintained markdown pages. +- `index.md` is the content catalog. +- `log.md` is an append-only chronological operation log. + +The user curates sources and asks questions. You perform all wiki maintenance. + +## Non-Negotiable Rules + +1. Never modify files inside `raw/`. +2. Always update `index.md` and `log.md` after any ingest/query/lint operation that changes the wiki. +3. Prefer editing existing pages over creating duplicates. +4. Use Obsidian-style wiki links (`[[page-name]]`) for internal references. +5. Record contradictions and superseded claims explicitly (do not silently overwrite history). +6. Keep claims attributable: include source links to `wiki/sources/*` pages. +7. Do not leave orphan pages intentionally; add at least one inbound and one outbound link when possible. +8. Keep writing concise, structured, and diff-friendly. +9. Every wiki page carries exactly one page-type hashtag (see Tagging Rules) matching its folder. + +## Folder Convention + +```text +raw/ + sources/ # immutable source markdown/text/pdf exports + assets/ # immutable local images/files referenced by raw sources + +wiki/ + overview.md # top-level synthesis and navigation + sources/ # one summary page per ingested raw source + entities/ # people, orgs, projects, places, tools + concepts/ # themes, ideas, methods, frameworks + timelines/ # optional chronological reconstructions + comparisons/ # side-by-side analyses + queries/ # durable outputs created from Q&A sessions + lint-reports/ # periodic health-check reports +``` + +## File Naming Rules + +- Use kebab-case for file names. +- Prefix source summary pages with date: `YYYY-MM-DD-title.md`. +- Prefer stable canonical pages: + - `wiki/entities/.md` + - `wiki/concepts/.md` +- If a page name collides, merge instead of creating suffixes unless truly distinct. + +## Tagging Rules + +Every page in `wiki/` starts with its page-type hashtag on its own line, directly after the `# ` heading (Obsidian inline tag format): + +```text +# <Title> + +#<type-tag> + +## <first section> +``` + +Folder → required tag: + +| Folder / file | Tag | +| ---------------------- | -------------- | +| `wiki/overview.md` | `#overview` | +| `wiki/sources/*` | `#source` | +| `wiki/entities/*` | `#entity` | +| `wiki/concepts/*` | `#concept` | +| `wiki/timelines/*` | `#timeline` | +| `wiki/comparisons/*` | `#comparison` | +| `wiki/queries/*` | `#query` | +| `wiki/lint-reports/*` | `#lint-report` | + +- Exactly one page-type tag per page; it must match the page's folder. +- Additional topical tags are allowed on the same line after the type tag (e.g. `#concept #ai-tooling`), but the type tag comes first. +- When creating any new page, add the tag immediately; when moving a page between folders, update the tag in the same operation. + +## Required Page Templates + +### 1) Source Summary (`wiki/sources/*.md`) + +Must include sections: + +- `# <title>` +- `#source` tag line (per Tagging Rules) +- `## Source Metadata` (date, raw path, source type, ingestion date) +- `## Core Claims` +- `## Key Evidence / Details` +- `## Connections` (links to entities/concepts/comparisons) +- `## Open Questions` +- `## Change Impact on Wiki` (what pages were updated and why) + +### 2) Entity / Concept Page + +Must include: + +- `# <name>` +- `#entity` or `#concept` tag line (per Tagging Rules) +- `## Summary` +- `## Current Understanding` +- `## Evidence` (bullets with links to `wiki/sources/*`) +- `## Related Pages` +- `## Contradictions / Uncertainty` +- `## Next Questions` + +### 3) Query Output (`wiki/queries/*.md`) + +Must include: + +- `#query` tag line (per Tagging Rules) +- Question asked +- Answer +- Evidence trail (links) +- Follow-up questions +- Whether this output changed existing pages + +## Standard Workflows + +### Workflow A: Ingest One Source + +When user says "ingest <source>": + +1. Read the raw source from `raw/sources/` (and `raw/assets/` references if needed). +2. Extract key claims, facts, entities, concepts, uncertainty. +3. Create/update one source summary in `wiki/sources/`. +4. Update relevant `wiki/entities/*` and `wiki/concepts/*` pages. +5. Update `wiki/overview.md` synthesis if this source materially changes understanding. +6. Update `index.md`. +7. Append ingest entry to `log.md`. +8. Report what changed, what is uncertain, and suggested next source/questions. + +### Workflow B: Answer Query + +1. Read `index.md` first. +2. Select relevant pages and synthesize answer with page citations. +3. If answer has durable value, save to `wiki/queries/YYYY-MM-DD-<slug>.md`. +4. If answer reveals new synthesis, update affected concept/entity pages. +5. Update `index.md` and append query entry in `log.md` when files changed. + +### Workflow C: Lint Wiki + +Run periodic health checks for: + +- contradiction detection across pages +- stale claims superseded by newer sources +- orphan pages / weak linking +- high-mention concepts lacking dedicated pages +- missing evidence links +- missing or folder-mismatched page-type tags (per Tagging Rules) + +Write report to `wiki/lint-reports/YYYY-MM-DD-lint.md`, then update `index.md` and `log.md`. + +## Citation & Evidence Policy + +- Prefer citing wiki source summaries (`wiki/sources/*.md`) rather than raw files in normal answers. +- If citing raw material directly, also reflect it into a source summary page. +- Mark uncertain or contested claims with `Status: tentative` in relevant section. + +## Update Policy + +- Never perform silent large rewrites. +- Preserve meaningful prior interpretations; move outdated material under a "Superseded" note when needed. +- Keep sections ordered consistently for predictable diffs. + +## Operational Commands (Natural Language) + +Supported intents: + +- "ingest <path-or-title>" +- "query: <question>" +- "lint wiki" +- "show recent changes" +- "suggest next sources" + +Always execute intents according to workflows above. + +## Session Start Checklist + +At start of every session: + +1. Read `index.md` and the latest section of `log.md`. +2. Identify last completed operation and current open questions. +3. Continue from prior state without resetting conventions. diff --git a/index.md b/index.md new file mode 100644 index 0000000..7f067e7 --- /dev/null +++ b/index.md @@ -0,0 +1,133 @@ +# Index + +Content catalog for this vault. Updated after every ingest, query, or lint operation that changes the wiki. + +## Status + +- Initialized: 2026-07-17 +- Last operation: 2026-07-29 — attribution update ([[2026-07-29-start-a-business-with-claude-code]] = **[[dan-martell]]**, owner-confirmed → his 5th confirmed source of 20 (possibly 7); all echoes from the same-day ingest relabeled within-author self-agreement; 8 pages updated) +- Sources ingested: 20 +- Wiki pages: 62 ([[overview]] + 20 sources + 27 concepts + 1 comparison + 9 entities + 2 queries + 2 lint reports) + +## Entry Points + +- [[overview|Overview]] — synthesis and navigation; **start here** +- [[log]] — chronological operation log + +## Sources + +**Anchors (independent traditions):** + +| Page | Date | Type | +|---|---|---| +| [[2026-07-17-design-the-perfect-offer]] | undated (ing. 07-17) | US offer-design video — productize, 3-tier ladder | +| [[2026-07-06-sebastian-interview-ai-and-software-engineering]] | 2026-07-06 | Interview — AI reshaping engineering work, careers, in-person moat | +| [[2026-07-18-information-is-free-implementation-is-paid]] | undated (ing. 07-18) | US content-marketing video — give away know-how, sell sequencing; scramble trick | +| [[2026-07-18-ai-productivity-adversarial-evidence]] | 2026-07-18 | **Adversarial** — RCT/peer-reviewed evidence AI's dev-productivity effect is modest, novice-tilted, overstated (METR, Brynjolfsson, DORA, SO) | +| [[2026-07-19-your-company-cant-outgrow-your-team]] | undated (ing. 07-19) | US leadership video (**Dan Martell**) — team growth ceiling, Keeper Test, values-as-tolerance | +| [[2026-07-20-referrals-will-sink-your-business]] | undated (ing. 07-20) | **Counter-position** — Dan Martell: referral dependency is a ceiling; 3 levers, pick 1; "the new paid is organic" | +| [[2026-07-22-stop-cold-calling-do-this-instead]] | undated (ing. 07-22) | US sales video (**Dan Martell**, 3rd) — partnerships lever: borrowed credibility, recruit the partner archetype; anti-cold-outbound for enterprise | +| [[2026-07-23-make-my-first-100k-in-month]] | undated (ing. 07-23) | US blueprint video (**Dan Martell**, 4th) — $0→$100K/mo sequence: money map (100×$1K), decoy tiers, inbound+outbound in parallel, chat/cold-call close, pre-sell waitlist | +| [[2026-07-26-how-to-build-a-billion-dollar-company-2027]] | undated (ing. 07-26) | RU video (**Oskar Hartmann** — third tradition, VC/product) — PMF is the start; repeatable channel as the moat; founder sells; SOM>TAM; partner-hope warning; pricing power = PMF; venture fits ~1% | +| [[2026-07-26-main-principle-of-successful-business]] | undated (ing. 07-26) | RU video (**Oskar Hartmann**, 2nd) — sell first, then build; only money votes (pre-payment supreme); cheap-experiment toolkit; acute-pain test; duration-without-revenue red flag | +| [[2026-07-29-start-a-business-with-claude-code]] | undated (ing. 07-29) | US 42s short (**Dan Martell**, 5th confirmed) — $0→$1M playbook: Claude Code as full GTM stack; sell via cold outbound, build last; AI as domain leveler; within-author restatement | + +**"15-06-2026 Inbox" batch** (six primaries, a meta-analysis, a template, a distillation): + +| Page | Role | +|---|---| +| [[2026-06-15-rodenko-selling-development-expensively]] | **Primary** — sell dear: guarantee test, Zendesk, Solution vs Staff-Aug | +| [[2026-06-15-17-ways-first-client]] | **Primary** — AB Analytics: 17 channels, follow-up stats, DFY ladder | +| [[2026-06-15-how-to-get-rich-cloning]] | **Primary** — Pabrai cloning method | +| [[2026-06-15-more-clients-dev-agency]] | **Primary** — Tony: niche → outbound → social | +| [[2026-06-15-making-money-with-ai-2026]] | **Primary** — three AI monetization paths; "pain with money" filter | +| [[2026-06-15-konspekt-aphorisms]] | Primary (aphorisms; same video as Rodenko) | +| [[2026-06-15-linkedin-mail-template]] | Tool — first-touch template | +| [[2026-06-15-meta-analysis-selling-dev-in-ai-era]] | Second-order — maps the seven notes + 90-day plan | +| [[2026-06-15-selling-development-services-in-the-ai-era]] | Second-order distillation (now a derived index) | + +## Entities + +| Page | Kind | One line | +|---|---|---| +| [[sebastian]] | person | Virtido founder; enterprise-harness + in-person-moat theses | +| [[eugene]] | person | Interviewer; BYO-harness; likely the vault owner | +| [[dmitry-rodenko]] | person | Most-cited sales methodology (SaaS Founders) | +| [[mohnish-pabrai]] | person | The cloning exemplar | +| [[dan-martell]] | person | Founder coach; 5 confirmed sources (+2 suspected — possibly 7 of 20), the only voice spanning two branches; "the ceiling is never the market" | +| [[oskar-hartmann]] | person | VC/product-world entrepreneur (KupiVIP, Fab.com); third independent tradition, 2 sources; "channel beats technology"; "sell first, then build" | +| [[virtido]] | org | Sebastian's enterprise services firm | +| [[ab-analytics]] | org | AB Analytics / Code to CEO; channels + DFY | +| [[claude-code]] | tool | Anthropic's agentic coding tool; build engine, GTM stack, domain leveler — first tool entity | + +## Concepts + +**Selling services:** + +| Page | One line | +|---|---| +| [[ai-market-shift]] | AI eats execution, creates demand for judgment; AI-as-filter | +| [[niche-selection]] | WHO dominates WHAT; niche is upstream of everything | +| [[pain-discovery]] | Pain with money; watch spend not talk; old-client mining | +| [[outcome-based-selling]] | Sell result *and accountability*, not hours | +| [[productized-service]] | Fixed scope/price/name; DIY→DWY→DFY | +| [[pricing-from-value]] | "Expensive" doesn't exist; guarantee test; backwards math | +| [[methodology-as-moat]] | Moat candidate #1: your proven method | +| [[offer-ladder]] | Entry/core/top, middle-out — price ladder is `tentative` | +| [[client-acquisition-channels]] | Where to fish; 17-channel taxonomy; online-vs-in-person | +| [[sales-discipline]] | Consistency; 5 touches; 3 channels × 90 days | +| [[referrals]] | Highest-converting, ~0-cost channel; 91% would / 11% asked; can't bootstrap client #1 — **and can't scale you** (counter-position added 07-20) | +| [[partnerships]] | The throttled warm intro: borrowed credibility walks you into enterprise; recruit the partner archetype — `tentative`, single-author | +| [[marketing-system]] | Money in at top → more money out at bottom; 3 levers, pick 1 × 90 days; "the new paid is organic"; ~6-month lag — `tentative` | +| [[technical-founder-trap]] | Technical founders solve but can't explain; explaining is what sells — `tentative` | +| [[cloning-over-originality]] | Copy at 10,000% first; originality is emergent | +| [[information-vs-implementation]] | Give away the steps free (scrambled), charge for implementation + sequencing | +| [[sales-channel-as-moat]] | Moat candidate #3: the repeatable channel with predictable CAC (Pediant vs FlatPay) — `tentative` | +| [[unit-economics]] | Full-cost pricing, LTV×⅓ CAC, buffer margin; partially fills the flagged CAC/LTV gap — `tentative` | +| [[venture-fit]] | ~1% of businesses fit venture; venture stretch kills (Fab.com); slow reinvested growth is legitimate — `tentative` | +| [[tam-sam-som]] | Market-sizing circles; SOM > TAM at the start; beachhead vs fortress niche — SAM part unsourced | +| [[sell-before-build]] | Only money votes: signal hierarchy, cheap-experiment toolkit, Wizard-of-Oz — rule is 3-tradition; mechanics `tentative` | + +**Engineering work in the AI era:** + +| Page | One line | +|---|---| +| [[future-of-engineering-work]] | Team collapse 8→2–3; harness market; identity | +| [[seniority-and-ai]] | Seniors up, juniors squeezed; senior = risk reduction | +| [[product-ownership]] | Own outcomes, not tickets (supply-side of outcome-selling) | +| [[relationships-as-moat]] | Moat candidate #2: in-person trust | +| [[ai-productivity-evidence]] | **Adversarial** — measured AI effect is modest & novice-tilted; contests the premise beneath both branches | + +**Running the team:** + +| Page | One line | +|---|---| +| [[team-growth-ceiling]] | Company grows only as fast as its people; Keeper Test, public scoreboard, "values are what you tolerate" — `tentative`; **same author as [[marketing-system]]** | + +## Comparisons + +- [[solution-vs-staff-augmentation]] — pick one; never both under one brand — `tentative` + +## Queries + +| Page | Question | +|---|---| +| [[2026-07-17-best-method-first-client]] | What would be the best method to find the first client? | +| [[2026-07-26-eugene-90-day-plan]] | The corpus as [[eugene]]'s dated 90-day channel/niche plan — and does he work the in-person route or build a [[marketing-system]] early? | + +## Timelines / Lint Reports + +| Page | Scope | +|---|---| +| [[2026-07-18-lint]] | First lint — **sources only**; layer healthy, 2 fixes | +| [[2026-07-18-lint-full-wiki]] | **Full wiki** (all 40 pages) — healthy; 3 fixes (adversarial-source staleness), *referrals* page flagged as missing | + +_Timelines: none yet._ ✅ The full lint's top structural gap — a missing `referrals` page — was resolved 2026-07-18 ([[referrals]] created), and that page's own flagged "no adversarial source" gap was partially closed 2026-07-20. ✅ The long-standing next-query gap closed 2026-07-26: [[2026-07-26-eugene-90-day-plan]] is the dated plan, and it resolves the in-person-vs-[[marketing-system]] tension **by stage** (one-to-one is the engine; the system gets a small non-zero deposit because its lag is ~6 months). Natural next operation: a **lint** — the wiki has grown 40 → 62 pages since the last full one (2026-07-18), and several of the newest pages are single-source `tentative`. + +## Known Gaps + +- **Adversarial gap now partially closed.** [[ai-productivity-evidence]] (2026-07-18) tests the shared *AI-capability premise* with RCT/peer-reviewed evidence; [[2026-07-20-referrals-will-sink-your-business]] adds the first counter-*position* on a tactic (referral dependency) — and [[2026-07-26-how-to-build-a-billion-dollar-company-2027]] adds a second (partner-as-savior hope; whale-first clients), plus the corpus's first *failure cases* for a tactic (Pediant, Fab.com — war-story grade). All advocacy, not evidence. Still missing: a **failure-case source for the productization / sell-dear model itself** (where niching-down or value-pricing lose money) — and, for balance, a *pro-thesis rigorous* source showing AI does zero the cost for some real dev segment. +- **New unresolved conflicts (2026-07-20; updated 07-23):** pick 1 channel vs. pick 3 ([[client-acquisition-channels]]) — now further complicated by Martell's own $0 blueprint running inbound+outbound **in parallel**; explanation-gap vs. absent-relationships as the technical operator's real blocker ([[technical-founder-trap]] vs. [[relationships-as-moat]]) — the 07-22 ingest adds a possible *composition* (partner intros supply both the room and the vouching; [[partnerships]]) but no resolution. The formerly-open "unexplained partnerships lever" gap is closed ✅; its successor question is the **entry bar** (would a partner of consequence meet a no-name solo operator?). Resolved ✅ (2026-07-23): the "stop cold calling" position is **enterprise-scoped** — Martell himself prescribes SMB cold calling at $0. +- **Source-independence improved (2026-07-26) but the Martell share stands.** [[oskar-hartmann]] is the first substantial voice from a **third tradition** (VC/product world) and independently restates the vault's spine (selling beats building; founder sells; SOM>TAM; sell dear) — the biggest independence gain since the adversarial source. The single-voice problem itself has **worsened**: [[dan-martell]] confirms at **5 of 20 sources** (Branch A *and* Branch C — the 2026-07-29 Claude-Code short was owner-attributed to him the day it was ingested, vindicating the echo-grade discipline: no page had granted it independence weight), and the 07-23 ingest exposed two more: he is the near-certain author of [[2026-07-18-information-is-free-implementation-is-paid]] (verbatim mechanism reuse) and plausible author of [[2026-07-17-design-the-perfect-offer]] ("buy back 10 hours" = his book's frame) — **possibly 7 of 20, including one of the two "independent anchors."** Consequences applied: [[information-vs-implementation]]'s "independent second voice" claim withdrawn; [[offer-ladder]] and the $1K floor ([[pricing-from-value]]) may be one voice repeating itself. The vault's confidence signal is now almost entirely *cross-tradition* convergence (US coaching ↔ RU dev-sales — Rodenko, AB Analytics, Tony remain independent). **Cheap high-value owner action: confirm/refute the two suspected attributions.** One genuine cross-voice gain from 07-23: Martell's $50 paid-waitlist pre-sell independently matches the RU validate-before-build rule ([[productized-service]]). +- **Most quantitative claims are attributable but unverified** — the promotional sources' root material is YouTube videos. See [[overview]] Contradictions. Exception: [[ai-productivity-evidence]]'s figures trace to peer-reviewed / RCT primary sources and were adversarially verified — though they are early-2025-scoped, not current. +- **Unfilled by the corpus itself:** ~~B2B unit economics (CAC/LTV)~~ (general principles landed 2026-07-26 → [[unit-economics]]; the B2B-*services* version — lumpy project LTV — still missing), legal/SLA packaging, CIS/EU niches, the owner's own case studies, an objection-handling script — per [[2026-06-15-meta-analysis-selling-dev-in-ai-era]]. diff --git a/log.md b/log.md new file mode 100644 index 0000000..17a36c8 --- /dev/null +++ b/log.md @@ -0,0 +1,623 @@ +# Log + +Append-only chronological record of wiki operations. Newest entries at the bottom. + +--- + +## 2026-07-17 — init + +**Operation:** Initialize vault storage. + +**Changes:** + +- Created folder tree: `raw/sources`, `raw/assets`, `wiki/sources`, `wiki/entities`, `wiki/concepts`, `wiki/timelines`, `wiki/comparisons`, `wiki/queries`, `wiki/lint-reports`. +- Created `wiki/overview.md` (`#overview`). +- Created `index.md` catalog. +- Created `log.md` (this file). + +**State:** Empty wiki, no sources ingested. Awaiting first source in `raw/sources/`. + +**Open questions:** What is the first source to ingest? Which entities/concepts anchor this domain? + +--- + +## 2026-07-17 — ingest + +**Operation:** Ingest everything from `raw/sources/` (2 files, full folder). First content ingest. + +**Sources ingested:** + +- `Design The Perfect Offer in Under 10 Minutes.md` → [[2026-07-17-design-the-perfect-offer]] (undated video; ingestion date used for the filename prefix) +- `Принципы продажи услуг разработки в эпоху ИИ.md` → [[2026-06-15-selling-development-services-in-the-ai-era]] (dated 2026-06-15) + +**Changes:** + +- Created 2 source summaries in `wiki/sources/`. +- Created 10 concept pages: [[ai-market-shift]], [[niche-selection]], [[pain-discovery]], [[outcome-based-selling]], [[productized-service]], [[pricing-from-value]], [[methodology-as-moat]], [[offer-ladder]], [[sales-discipline]], [[cloning-over-originality]]. +- Created 1 comparison: [[solution-vs-staff-augmentation]]. +- Rewrote [[overview]] from scaffold to full synthesis (domain thesis + 8-step dependency chain + contradictions). +- Rewrote [[index]] catalog with source/concept tables and a Known Gaps section. +- No entity pages created — no attributable subjects in either source (rationale recorded in [[index]] and [[overview]]). + +**Findings:** + +- The two sources independently converge on one thesis: AI substitutes undifferentiated execution and raises the value of judgment → sell productized outcomes with accountability, not hours. 7 of 10 concepts carry evidence from both, which is the vault's main confidence signal. +- Both sources argue the same side. The vault has **no** adversarial material on productization; agreement here is unreplicated advocacy, not confirmation. +- Every quantitative claim across both sources is uncited (90% below-minimum-wage, 80%/5th-touch, 91% vs 11% referrals, 47% subject line, $1:$6 AI spend, 30–50% margin, 15–25% webinar). Flagged on each page and in [[overview]]; not to be repeated as fact. +- The RU source is a *second-order* distillation — its 5–7 upstream notes are outside this vault under `PARA/4. Archive/15-06-2026 Inbox/`, so no claim from it can be traced to origin. +- Recorded 3 live contradictions rather than resolving them: calls vs. chat ([[sales-discipline]]); "sound unique" vs. "buy a proven method" ([[methodology-as-moat]]); cloning vs. moat ([[cloning-over-originality]]). +- Marked `Status: tentative` on the 3 single-source pages: [[offer-ladder]], [[cloning-over-originality]], [[solution-vs-staff-augmentation]]. + +**Open questions:** + +- Import the 5–7 upstream notes from `PARA/4. Archive/15-06-2026 Inbox/` into `raw/sources/`? Highest-value next ingest — would let the RU claims be traced. +- Find an adversarial source: where does the productized model fail? +- Which market/currency do the $1K floor and $200/mo substitute assume, and do they transfer to the vault owner's market? +- When to productize: offer-first or after 2–3 identical projects? Unresolved across sources. +- Should Pabrai/Buffett/Munger/Graham get entity pages, or is the material too thin? + +--- + +## 2026-07-17 — ingest (batch 2) + +**Operation:** Pulled the eight `PARA/4. Archive/15-06-2026 Inbox/` notes into `raw/sources/` and ingested them alongside the Sebastian interview (already in the source folder). 9 new sources. + +**Raw changes:** copied 8 files from `D:\Projects\Notes\Vault\PARA\4. Archive\15-06-2026 Inbox` into `raw/sources/` (originals left intact; kept source filenames for provenance). No existing raw file modified. + +**Sources ingested (9):** Sebastian interview → [[2026-07-06-sebastian-interview-ai-and-software-engineering]]; and the June-15 batch → [[2026-06-15-rodenko-selling-development-expensively]], [[2026-06-15-17-ways-first-client]], [[2026-06-15-how-to-get-rich-cloning]], [[2026-06-15-more-clients-dev-agency]], [[2026-06-15-making-money-with-ai-2026]], [[2026-06-15-konspekt-aphorisms]], [[2026-06-15-linkedin-mail-template]], [[2026-06-15-meta-analysis-selling-dev-in-ai-era]]. + +**Wiki changes:** + +- +9 source pages; +6 entities ([[sebastian]], [[eugene]], [[virtido]], [[dmitry-rodenko]], [[mohnish-pabrai]], [[ab-analytics]]); +5 concepts ([[client-acquisition-channels]], [[relationships-as-moat]], [[product-ownership]], [[seniority-and-ai]], [[future-of-engineering-work]]). +- Updated all 10 prior concepts + the comparison: re-pointed "primary" citations from the distillation to the specific primary note; downgraded "uncited via distillation" hedges to "attributable but promotional/unverified." +- [[2026-06-15-selling-development-services-in-the-ai-era]] reclassified primary → secondary (derived index); its dead `PARA/...` links replaced with links to the now-ingested notes. +- [[cloning-over-originality]] and [[solution-vs-staff-augmentation]] gained real primary sources; the former's `tentative` relaxed, the latter's kept (still one source) but enriched (one valid combination, Squad-model). +- Broadened [[overview]] domain to two branches (selling services + engineering-work positioning); rewrote its navigation, open threads, and contradictions. + +**Findings / what changed in understanding:** + +- **Provenance resolved.** The June-15 distillation was second-order; its 7 upstream notes are now ingested, so statistics and claims trace to named speakers ([[dmitry-rodenko]], [[ab-analytics]], Tony, [[mohnish-pabrai]]) — but the roots are promotional YouTube videos, so figures are *attributable, not verified*. +- **New domain branch + new contradiction.** The Sebastian interview added engineering-work concepts and the vault's sharpest live conflict: **online outreach ("Big zero") vs. multi-channel outbound.** Recorded, not resolved; best current read is audience-dependent (enterprise vs SMB/startup). +- **Second moat.** Relationships-as-moat now competes with methodology-as-moat. +- **[[eugene]] is plausibly the vault owner** (his `insin` project + custom Claude Code harness match the owner's tooling) — recorded as tentative inference. + +**Open questions:** + +- Still no adversarial/failure-case source on productization — now the top gap. +- Which moat (method vs relationships) and which channels apply to [[eugene]]'s actual buyers? Candidate first durable query. +- Corpus-flagged gaps unfilled: unit economics, legal/SLA packaging, CIS/EU niches, own case studies, objection scripts. +- A first **lint** is now worthwhile (34 pages, multiple tentative/contradiction flags). + +--- + +## 2026-07-17 — query + +**Operation:** Answered durable query — "What would be the best method to find the first client?" (Workflow B). First page in `wiki/queries/`. + +**Question:** What would be the best method to find the first client? + +**Answer (synthesis):** No single magic channel; the corpus converges on a *sequence* — (1) pick one narrow niche (precondition), (2) for a literal first client favor a warm/repeat-contact in-person channel (Chamber of Commerce / local groups; 3×=regular, 6×=trusted) over cold online, (3) work it with discipline (3 channels × 90 days, 5+ touches Day 0→3→7→14→30, founder sells), (4) convert client #1 into referrals immediately. In-person is the low-variance bet because it is the one thing [[ab-analytics]] and [[sebastian]] independently endorse; cold online only if buyers are SMB/startup. Tailored note for [[eugene]] (likely owner): reallocate LinkedIn/articles effort to recurring in-person events. + +**Changes:** + +- Created [[2026-07-17-best-method-first-client]] (`#query`). +- Added inbound links from [[client-acquisition-channels]] and [[eugene]] (both had this exact question open in "Next Questions"; converted to "partially addressed → see query"). +- Updated [[index]]: new **Queries** section + page count 34→35 + status line. +- No source or concept *claim* changed — the answer is a synthesis of existing pages, not new evidence. + +**Findings / caveats carried into the answer:** + +- The online-vs-in-person split remains the governing uncertainty; the answer resolves it by audience (enterprise → in-person; SMB/startup → online viable), not by a universal law. +- All cited statistics remain attributable-but-unverified (promotional videos); flagged in the query page. +- Referrals are the highest-converting channel but cannot bootstrap client #1 — noted as a sequencing constraint. + +**Open questions:** + +- [[eugene]]'s actual niche/buyer type is still unchosen — it determines the online-vs-in-person call. Blocks a truly concrete plan. +- Is there a warm-intro path (existing content audience, embedded/CV contacts) faster than cold-in-person for the first engagement? +- Still no adversarial/failure-case source; a first **lint** remains the other worthwhile next operation. + +--- + +## 2026-07-18 — ingest + +**Operation:** Ingest single source — "Information Is Free, Implementation Is Paid" (Workflow A). 12th source; first on demand generation / content marketing as a discipline. + +**Source ingested:** `raw/sources/Information Is Free, Implementation Is Paid.md` → [[2026-07-18-information-is-free-implementation-is-paid]] (undated YouTube video, 08:45; ingestion date used for the filename prefix). No raw file modified. + +**Wiki changes:** + +- Created 1 source summary in `wiki/sources/`. +- Created 1 concept: [[information-vs-implementation]] (thesis + 5×10×4 content factory + scramble trick + pain→solution structure). Single-source, marked `Status: tentative`. +- Enriched 4 concepts: [[client-acquisition-channels]] (organic-content channel developed; added as a **fourth**, most-bullish position on online — "content *is* the engine" — sharpening the online-vs-in-person split), [[pain-discovery]] (the nuanced-observable-pain AI prompt added as a content-side pain-articulation tool), [[methodology-as-moat]] ("sequencing is the paid good" as the marketing-side moat framing), [[pricing-from-value]] (free content as an upstream price anchor). +- Updated [[overview]]: source count 11→12; added the content-marketing engine to the Branch-A channel step; new highest-signal bullet ("information is free / scramble"); widened the online-vs-in-person contradiction; noted the source reinforces (not tests) the "sell dear" school. +- Updated [[index]]: +1 source row, +1 concept row, page count 35→37, status line, "eleven of twelve" gap note. + +**Findings / what changed in understanding:** + +- **New domain surface: demand generation.** Prior sources listed "content marketing" only as one of 17 channels; this is the first to treat it as a system — give away every step, withhold the *sequence*, and let the giveaway anchor the price. +- **The online-vs-in-person split is now the vault's widest live contradiction**, spanning "content is the entire lead engine" ([[information-vs-implementation]]) to "content = Big zero" ([[sebastian]]) — still best read as audience-dependent, still untested. +- **Reinforcement, not confirmation.** Same US "sell dear / give-value" coaching school; anonymous speaker, zero results data. Does **not** close the standing adversarial-source gap. +- New moat wrinkle: "sequencing is the moat" agrees with [[methodology-as-moat]] but strains [[cloning-over-originality]] — a publicly-shown (if scrambled) sequence is more re-derivable than a private method. + +**Open questions:** + +- Does the scramble strategy actually convert (view→lead→sale), or do sophisticated viewers re-sequence and self-serve? No evidence in-source. +- For [[eugene]]: is a content engine faster than the in-person channels favored in [[2026-07-17-best-method-first-client]], or only viable at audience scale? Could content be the *trust layer under* outbound (Tony's model) rather than a standalone source? +- ICP-band mismatch: the source anchors to $500K–$2M-revenue buyers, larger than the vault's usual SMB framing — which buyers does the engine actually fit? +- Adversarial/failure-case source and a first **lint** remain the two highest-value next operations (12 sources, multiple tentative/contradiction flags). + +--- + +## 2026-07-18 — lint (sources) + +**Operation:** First lint (Workflow C), scoped to the 12 `wiki/sources/*` pages per user request ("run a lint on sources"). Report → [[2026-07-18-lint]]. + +**Checks run:** raw↔summary coverage · page-type tags · template-section completeness · outbound-link validity · inbound linking / orphans · cross-source contradiction coverage · stale/superseded claims · metadata completeness · evidence provenance. Inbound/outbound link health verified against a full-vault `[[…]]` link inventory. + +**Verdict:** source layer healthy. Complete 12-raw→12-summary coverage, no orphans, no broken links, all `#source` tags correct and first, all template sections present, provenance chain intact (distillation demotion + struck-through resolved question preserved as history). + +**Findings (5; all Low/Info):** + +- **F1 (fixed).** Content-marketing-timing contradiction was recorded two-way (Tony vs AB Analytics) but is now three-way — the 07-18 source makes content the *primary* engine. Upgraded the Contradictions bullet in [[client-acquisition-channels]] (rule #5). +- **F2 (fixed).** [[2026-06-15-linkedin-mail-template]]'s Change Impact claimed a link from [[sales-discipline]] that did not exist; template was inbound-linked from only one content page. Added the reciprocal link from [[sales-discipline]] — claim now true, weak link strengthened. +- **F3 (flagged).** [[2026-06-15-meta-analysis-selling-dev-in-ai-era]] is the most weakly inbound-linked source (only [[overview]] among content pages). Acceptable for a second-order map; optional future strengthening. +- **F4 (flagged).** Filename date-prefix convention is inconsistent for undated videos (ingestion date vs batch date vs file date). All documented in-page; suggest codifying "undated → ingestion date." No renames (link churn). +- **F5 (flagged, standing).** Corpus is 11/12 one school; all stats attributable-but-unverified. Adversarial source remains the top-value ingest. + +**Changes:** edited [[client-acquisition-channels]] (F1) and [[sales-discipline]] (F2); created [[2026-07-18-lint]]; updated [[index]] (new Lint Reports row, page count 37→38, status line). No source-page *content* changed — findings were about link/contradiction coverage, not claims. + +**Open questions / next:** + +- **Full-wiki lint** is the natural follow-up (this pass covered sources only) — concept/entity pages, plus high-mention concepts lacking pages (e.g. *referrals*). +- Adversarial/failure-case source (F5) still the highest-value next ingest. +- Optional tidy: F3, F4. + +--- + +## 2026-07-18 — ingest (first adversarial source) + +**Operation:** Ran `deep-research` (Workflow tool, user-requested) to locate and verify empirical AI-productivity evidence, then ingested it (Workflow A) as the vault's **first adversarial source**. Research run: 106 agents, 6 angles, 23 sources fetched, 104 claims → 25 adversarially verified (23 confirmed, 2 refuted). Task `ww05pcpxq`. + +**Raw created:** `raw/sources/AI Coding Productivity - Empirical Evidence (deep research 2026-07-18).md` — a new immutable synthesis file (no existing raw modified). It is second-order but built from peer-reviewed papers / RCTs / large surveys, so higher-provenance than any prior source. + +**Source ingested:** → [[2026-07-18-ai-productivity-adversarial-evidence]]. + +**Wiki changes:** + +- Created source page + 1 concept: [[ai-productivity-evidence]] (the durable home for the empirical counter-narrative). Both single-source → `Status: tentative`. +- Added explicitly-marked **counter-evidence** to [[ai-market-shift]] (substitute→complement), [[seniority-and-ai]] (novices gain most; now `Status: contested`), [[future-of-engineering-work]] ("coding cost → 0" qualified; DORA team-stability). Prior claims preserved, not overwritten (Update Policy); contradictions recorded explicitly (rule #5). +- [[overview]]: source count 12→13; added the foundational "AI capability — hype vs. measured evidence" contradiction; flipped the standing "no adversarial source" thread; added Branch-B caveat; new highest-signal item (perception ≠ measurement); navigation + concept list. +- [[index]]: +1 source row (flagged adversarial), +1 concept row, page count 38→40, status line, Known-Gaps rewrite, quantitative-claims exception noted. +- **No entity pages** for METR / Brynjolfsson / DORA / Stack Overflow — cited as evidence, not tracked subjects (consistent with the Buffett/Munger call on [[mohnish-pabrai]]). + +**Findings / what changed in understanding:** + +- **The premise beneath both branches is now contested, not settled.** Strongest developer-specific RCT (METR) found experts **19% slower** with early-2025 AI; best skill-distribution study (Brynjolfsson, *QJE* 2025) found **novices gain most (+34%)**, inverting "seniors up / juniors out." Perception-vs-reality gap (~39 pts) shows self-reported gains are unreliable. +- **Honest framing: qualifies, doesn't demolish.** Average effects are positive (14–15%); METR n=16 and "historical"; the strongest skill result is customer-support, not devs; all figures early-2025-scoped. Held to the same standard as the promotional sources. +- **It confirms a doubt the vault already held** — [[ai-market-shift]]'s "$200/mo substitute is asserted, not demonstrated" open question — rather than only contradicting. +- **The gap narrowed but didn't vanish:** this tests the *AI-capability* premise, not the *productization/sell-dear* tactics. A failure-case source for the selling model itself is now the top gap; a *pro-thesis* RCT-grade source would balance further. +- **Verification caught a real error** now avoided vault-wide: the widely-repeated "66% spend more time fixing AI code" conflates two SO-survey items; the correct debugging-time figure is **45%**. + +**Open questions:** + +- Does METR's −19% persist/reverse on mid-2026 agentic tools? (The source is explicitly historical.) +- Does "novices gain most" hold for real, complex codebases, or invert where juniors can't catch AI errors? +- Should [[dmitry-rodenko]]'s "$200/mo substitute / hourly dev is dead" now carry `Status: contested`? +- Next ingest candidates: (a) productization failure-case source; (b) pro-thesis rigorous source. Plus the still-pending full-wiki lint. + +--- + +## 2026-07-18 — lint (full wiki) + +**Operation:** Full-wiki lint (Workflow C) over all 40 pages — the follow-up to the sources-only lint. Every concept/entity/comparison/query page read in full; link health checked against a deduped inventory of all `[[…]]` targets. Report → [[2026-07-18-lint-full-wiki]]. + +**Verdict:** structurally healthy. **Tags 100%** (all 40 lead with the correct folder-matching type tag); **templates complete** (all 17 concepts + 6 entities carry the six required sections; query matches its template); **no broken links** (every target resolves; two `[[…]]` hits are code-span examples, one path-style `[[wiki/overview]]` normalized); **no orphans** (every page ≥7 inbound; new [[ai-productivity-evidence]] already at 26); **contradiction coverage thorough** (no unrecorded tension found). + +**Findings (6):** + +- **F1 (fixed, Medium).** [[productized-service]] still said "the vault needs an adversarial source" — stale after today's ingest. Updated Contradictions + Next Questions to acknowledge [[ai-productivity-evidence]] and sharpen the remaining gap (it tests the AI-capability premise, not the productization *model*); added a "substitution premise now contested" pointer + Related-Pages link. +- **F2 (fixed, Low).** [[2026-07-17-best-method-first-client]]'s "no adversarial source" caveat was imprecise; appended a dated lint note (original preserved) clarifying the new source addresses AI-capability, not the channel claims. +- **F3 (fixed, Low).** Normalized a path-style link `[[wiki/overview|Overview]]` → `[[overview|Overview]]` in [[index]]. +- **F4 (flagged, Medium).** **No `referrals` concept page** despite heavy cross-source mention (91%/11%, highest-converting, ask-immediately mechanics) across [[2026-06-15-17-ways-first-client]], [[sales-discipline]], [[client-acquisition-channels]], the query. The clearest structural gap — recommend creating it. +- **F5 (flagged, Low).** Guarantee/risk-reversal is a candidate concept, currently well-covered within [[pricing-from-value]] + [[outcome-based-selling]]. +- **F6 (flagged, Low).** Optional enrichment links from [[niche-selection]] / [[solution-vs-staff-augmentation]] to [[ai-productivity-evidence]]. + +**Note (not a defect):** today's adversarial ingest was correctly surgical — it added counter-evidence only to the three pages it truly contradicts and left [[relationships-as-moat]] / [[product-ownership]] alone, because "novices gain most" *corroborates* their "AI levels skill" premise rather than contradicting it. The vault records that contradiction but not the corroboration (optional future touch). + +**Changes:** edited [[productized-service]], [[2026-07-17-best-method-first-client]], [[index]] (link + Lint Reports table + counts 40→41); created [[2026-07-18-lint-full-wiki]]. No source or concept *claim* altered beyond the staleness corrections. + +**Open questions / next:** + +- Create the [[referrals]] concept page (F4) — top structural gap. +- Productization-failure-case source remains the top content gap; a pro-thesis rigorous AI source would balance further. +- Optional: F5, F6, and the corroboration note. + +--- + +## 2026-07-18 — create concept (referrals) + +**Operation:** Created the [[referrals]] concept page, resolving finding **F4** from the full-wiki lint ([[2026-07-18-lint-full-wiki]]). A synthesis/refactor of material already in the vault (no new source ingested). + +**Why:** referrals appeared as a distinct, high-value channel with its own statistics and mechanics across [[2026-06-15-17-ways-first-client]], [[sales-discipline]], [[client-acquisition-channels]], [[relationships-as-moat]], and [[2026-07-17-best-method-first-client]], but had no dedicated page — the clearest structural gap in the lint. + +**Wiki changes:** + +- Created [[referrals]] (`#concept #sales #outbound`), full template. Key content: the 91%-would / 11%-asked gap; ask-immediately / be-specific / frictionless discipline; the **two engines** (transactional ask vs. relational emergence); the **cold-start constraint** (referrals can't bootstrap client #1); referral *partners* as the one referral route not subject to cold-start. +- Wired inbound links (no orphan): [[client-acquisition-channels]] (taxonomy row + Related), [[sales-discipline]] (the ask bullet + Related), [[relationships-as-moat]] (the trust→referral chain + Related), [[2026-07-17-best-method-first-client]] (step 4). +- [[overview]]: added [[referrals]] to the selling-chain step 8 (flywheel/cold-start note) and the concept navigation list. +- [[index]]: +1 concept row, page count 41→42, concept count 17→18, status line; marked the lint's F4 gap ✅ resolved. + +**Findings / notes:** + +- Surfaced a **mild method tension** now recorded on the page: AB Analytics prescribes an explicit post-delivery *ask*; [[sebastian]]'s model has referrals *emerge* from repeated in-person trust. Treated as complementary (ask captures goodwill the relationship created), unreconciled by any source. +- The 91%/11% figures remain promotional/uncited (AB Analytics) — `Status: tentative` on the numbers, directionally corroborated by the relationship sources. + +**Open questions / next:** + +- Productization-failure-case source is now the top remaining gap (F5/F6 from the lint are optional). +- Candidate durable query: [[eugene]]'s concrete 90-day plan (the existing first-client query stops at method). + +--- + +## 2026-07-19 — ingest (Your Company Can't Outgrow Your Team) + +**Operation:** Ingested `raw/sources/Your Company Can't Outgrow Your Team.md` (US leadership video, 4:35, undated, speaker unnamed) — the only raw source not yet in the wiki (14/14 now ingested). + +**Wiki changes:** + +- Created [[2026-07-19-your-company-cant-outgrow-your-team]] (`#source #leadership #team`), full template. +- Created [[team-growth-ceiling]] (`#concept #leadership #team`, `Status: tentative` — single anecdotal source). Carries: growth-math thesis (company grows only as fast as its people), Business Athlete framework (2 of 7 practices captured), public scoreboard / private criticism, Netflix Keeper Test, values hire→inspire→fire ("values are what you tolerate", "complexity fails, simple scales"). +- [[overview]]: branches restructured two → **three** — added **Branch C: running the team** (explicitly thin/tentative); source count 13→14; navigation updated. +- [[future-of-engineering-work]]: Related-Pages link to [[team-growth-ceiling]] (team collapse to 2–3 makes per-person growth a larger share of the ceiling). +- [[index]]: +1 source row (anchors table), new "Running the team" concept group, counts 42→44, status line. + +**Findings / notes:** + +- This is the vault's **first internal-management source** — it doesn't touch selling (Branch A) or the AI labor shift (Branch B), so it opens a branch rather than reinforcing one. No contradictions with existing pages; recorded a *tension*: the Keeper Test presumes replaceability, which sits awkwardly with 2–3-person AI-era teams where each member is a single point of failure. +- Evidence quality is low (anecdotal talk, no data, speaker unnamed, framework only partially captured) — everything marked `tentative`; quotes attributed to the clip only. +- No new entities: the speaker is unnamed; Netflix is only the origin of the Keeper Test, not an actor here. + +**Open questions / next:** + +- Identify the speaker; recover the other 5 Business Athlete practices and the three values. +- Branch C is dormant for a solo operator — if [[eugene]] has no team yet, it matters only at first hire; note for the eventual 90-day-plan query. +- Standing gaps unchanged: productization-failure-case source (top), pro-thesis rigorous AI source. + +--- + +## 2026-07-20 — ingest (Referrals Will Sink Your Business) + +**Operation:** Ingested `raw/sources/Referrals Will Sink Your Business.md` (US coaching video, 6:47, undated; [[dan-martell]] coaching a founder stalled at ~$1.5M). 15/15 raw sources now ingested. + +**Wiki changes:** + +- Created [[2026-07-20-referrals-will-sink-your-business]] (`#source #marketing #content-marketing`), full template. +- Created [[marketing-system]] (`#concept #marketing #content-marketing`, `Status: tentative`) — money-in-at-top→money-out-at-bottom definition; the three levers (content / paid / partnerships), pick one × 90 days; "the new paid is organic" (organic is the *prerequisite* for paid, not an alternative); reps-not-views; the ~6-month lag. +- Created [[technical-founder-trap]] (`#concept #positioning #marketing`, `Status: tentative`) — solving ≠ explaining; explanation as the unlock. +- Created [[dan-martell]] (`#entity #person`). +- [[referrals]]: added a **Counter-position** subsection (dependency as a ceiling; referral flow has no throttle; "warning sign, not a badge") + Evidence/Related/Contradictions/Next-Questions revisions. Struck the page's standing "no adversarial source" bullet as **partially resolved**. +- [[client-acquisition-channels]]: added the three-lever taxonomy with its scope analysis, a 5th row to the content-position table, the pick-1-vs-pick-3 conflict, Evidence + Related + 2 Contradictions. +- [[sales-discipline]]: added reps-not-views as independent corroboration of consistency-over-intensity + the six-month patience budget. +- [[information-vs-implementation]]: Summary re-scoped (mechanism still single-source; the *bet* now has two voices), "what the second source adds" (publishing as practice; organic→paid bridge; patience budget) and where the two differ (scramble trick is unique to source 1). +- [[eugene]]: recorded the rival diagnosis of his networking blocker (articulation vs. relationships) + 2 Related links. +- [[2026-07-19-your-company-cant-outgrow-your-team]]: recorded the tentative speaker-attribution hypothesis. +- [[overview]]: source count 14→15; **selling chain extended to a 9th step** ([[marketing-system]]); 2 new highest-signal items; new Open Thread (first channel counter-position, with its evidence caveat); 3 new/revised Contradictions; navigation + single-source list updated. +- [[index]]: +1 source row, +1 entity row, +2 concept rows, counts 44→48, status line, Known Gaps. + +**Findings / notes:** + +- **First source in the vault to attack a *tactic* rather than a premise.** The prior adversarial source ([[ai-productivity-evidence]]) contested the AI-capability premise; this one contests a channel every other source rated highest. Precision matters: it does *not* dispute that referrals convert best — it disputes **dependency**, on the grounds that referral flow has no throttle. +- **Kept the evidence grades separate.** This is *advocacy against advocacy* — a coaching clip, no data, author sells the prescribed alternative — not evidence in the sense the adversarial dossier set. Recorded as such on [[referrals]], [[overview]], and [[index]] so the gap isn't logged as fully closed. +- **Its rhetorical high point is its logical low point.** The Tones and I / Oliver Anthony anecdotes are survivorship selection and cannot support "everyone is one creative project away"; the narrower claim they *do* support (be shipping when it lands) was kept, the broad one flagged. +- **Reconciled by stage, and said so.** The three levers exclude outbound and referrals entirely — they are all one-to-many motions aimed at a founder who already has clients. So the source succeeds rather than refutes the vault's first-client answer ([[2026-07-17-best-method-first-client]]). Flagged explicitly as the vault's inference, since that reading conveniently dissolves a conflict that may be real. +- **Recognised a merged claim rather than double-counting it.** "Can't bootstrap client #1" and "can't scale past a ceiling" are one structural property (referrals are *derived* demand) observed at two ends — noted on [[referrals]] so the vault doesn't read them as two independent findings. +- **Corroboration weighed, not counted.** Content-as-engine now has two voices ([[information-vs-implementation]] + this), but both are US coaching videos without conversion data — head-count moved, evidence didn't. Recorded on both pages and in [[overview]]'s channel contradiction. +- **Possible hidden dependency surfaced:** the unnamed speaker of the 07-19 leadership clip may be Dan Martell ("Business Athlete" framework, same genre). If true, two "independent" sources share an author. Logged as `tentative` inference in three places; **unverified** — no name appears in either raw note. + +**Open questions / next:** + +- Verify the Dan Martell attribution for [[2026-07-19-your-company-cant-outgrow-your-team]] before either source is treated as corroborating the other. +- Resolve pick-1 vs pick-3 channels, and the articulation-vs-relationships diagnosis for [[eugene]] — both now blocking a credible 90-day plan. +- Standing gaps unchanged: productization-failure-case source (top), pro-thesis rigorous AI source. New: nothing in the vault explains the *partnerships* lever. + +--- + +## 2026-07-20 — attribution fix (Dan Martell ↔ "Your Company Can't Outgrow Your Team") + +**Operation:** Resolved the open speaker question raised during the same-day ingest. The vault owner confirmed that [[2026-07-19-your-company-cant-outgrow-your-team]] — previously logged as "speaker unnamed" — is also [[dan-martell]]. Not a new ingest; a provenance correction with downstream consequences. + +**Wiki changes:** + +- [[2026-07-19-your-company-cant-outgrow-your-team]]: added a **Speaker** field to Source Metadata (with provenance: curator confirmation, not a documentary citation — the clip still names no one); resolved the Open Question; added [[dan-martell]] + [[marketing-system]] to Connections. +- [[team-growth-ceiling]]: status line now records the shared authorship; added a **cross-branch comparison table** (stall → misdiagnosis → real cause → mechanism, internal vs. external); Evidence re-sourced with the attribution; 2 new Contradictions; speaker question closed in Next Questions. +- [[dan-martell]]: extended from one source to two — added his Branch C positions, the **through-line** section, Evidence split by branch, sharpened the incentive caveat, 2 new Next Questions. Now the vault's only entity spanning two branches. +- [[2026-07-20-referrals-will-sink-your-business]]: Open Question closed ✅; Change Impact updated to record the same-day confirmation and what was applied. +- [[overview]]: the "possible hidden dependency" contradiction → **confirmed**, rewritten with the worldview/engine analysis; Branch C paragraph now names the author and flags the non-independence. +- [[index]]: status line, 07-19 source row, [[dan-martell]] one-liner, [[team-growth-ceiling]] row; replaced the "unverified attribution" gap with a **source-independence** gap. + +**Findings / notes:** + +- **The real cost is independence, and the real gain is coherence.** Branch C stops being an anonymous leadership talk (traceability up) but also stops being a voice independent of Branch A (corroboration down). Both recorded; the second matters more, because the vault's whole confidence method is convergence between unconnected traditions. +- **The attribution surfaced a synthesis that was invisible while the author was unknown.** Both clips diagnose a stalled founder and relocate the constraint inward — *the ceiling is never the market* — and both prescribe the same engine, **deliberate practice at volume**: "practice until we can't get it wrong" (people) and "the only thing you control is the volume of the reps" (marketing). Recorded as a table on [[team-growth-ceiling]] and a through-line on [[dan-martell]]. +- **Flagged the convenience of that frame.** A coach whose diagnosis is always "the constraint is internal and fixable" is describing a world in which coaching is by construction the answer — and *"have a coach"* is one of his own seven Business Athlete practices. Noted on both pages; not treated as disqualifying. +- **Kept the provenance grade honest.** This is curator testimony, not an external citation. Strong enough to act on, recorded as what it is. +- Recovering the full Business Athlete framework (5 of 7 practices + 3 values missing) is now a *findable* task rather than a dead end — the highest-value cheap win for Branch C. + +**Open questions / next:** + +- Recover the full Business Athlete framework from Martell's published material. +- Does "the ceiling is never the market" ever fail? Neither clip admits a genuinely small or shrinking market exists. +- Unchanged: productization-failure-case source (top gap); pick-1-vs-pick-3; articulation-vs-relationships for [[eugene]]; the unexplained *partnerships* lever. + +--- + +## 2026-07-22 — ingest (Stop Cold Calling, Do This Instead) + +**Operation:** Ingested `raw/sources/Stop Cold Calling, Do This Instead.md` (US sales video, 4:38, undated; **third [[dan-martell]] source**, named in the raw note itself). 16/16 raw sources now ingested. This one closes the standing "unexplained partnerships lever" gap. + +**Wiki changes:** + +- Created [[2026-07-22-stop-cold-calling-do-this-instead]] (`#source #sales #partnerships`), full template. +- Created [[partnerships]] (`#concept #sales #marketing`, `Status: tentative`) — borrowed credibility as the enterprise entry mechanism; the six reverse-engineering questions; the partner-archetype recruiting playbook; the **throttle distinction** vs. client referrals (recruited vs. derived demand); "ten good partners can replace an outbound sales team"; scope ~$10K+ ACV. +- [[marketing-system]]: Summary re-attributed (single *author*, now two sources); lever table row updated; new "third lever, filled in" paragraph; **one-to-many framing qualified** (partnerships is one-to-few-to-many); Evidence; Related; the partnerships Next Question closed ✅. +- [[client-acquisition-channels]]: three-lever bullet qualified; new **counter-position on cold outbound** paragraph (enterprise-scoped; Martell↔Sebastian convergence on trust-mediated entry); 2 new Contradictions; Evidence + Related. +- [[referrals]]: referral-partners paragraph now points to [[partnerships]]; the "referral variant with a throttle?" Next Question closed ✅ — including the resolution of Martell's apparent self-contradiction (anti-referral-dependency yet pro-partner-intros: control of the input differs, not the shape of the output). +- [[relationships-as-moat]]: new "convergence from the opposite pole" paragraph — **borrowed vs. built trust**; borrowed is faster but rented; Evidence + Related. +- [[dan-martell]]: Summary 2→3 sources; third-source positions block; through-line extended (**systematize what worked by luck** — every clip converts an accident into a machine); Contradictions updated (3 of 16 sources, largest single-voice share); partnerships Next Question closed ✅. +- [[eugene]]: networking blocker gains a *target* — recruit a partner archetype (for CV/embedded: industrial-equipment vendors / machine-builder integrators, flagged as untested inference); noted partner intros compose with *both* rival diagnoses (the room and the vouching). +- [[overview]]: source count 15→16; step-9 partnerships mechanism; new highest-signal item (borrowed credibility / throttle); new ✅ Open Thread; online-vs-in-person contradiction gains the enterprise-convergence nuance; Martell dependency updated to 3 sources; navigation + single-source list. +- [[index]]: +1 source row, +1 concept row, counts 48→50, status line, [[dan-martell]] one-liner, 2 Known-Gaps updates. + +**Findings / notes:** + +- **The gap this closes was flagged in three places** ([[marketing-system]], [[dan-martell]], [[referrals]] Next Questions) — all three now cite the answer, and all three answers carry the same caveat: the mechanism is single-author and anecdote-grade ($95K contracts, 7 pharma intros — war stories, no cohort). +- **The best finding is the throttle distinction.** Partner intros and client referrals produce the same output (a warm, trust-carrying intro), but partner *acquisition* is a controllable input while client goodwill is not. That is a structural claim that stands without any of the source's numbers, and it cleanly resolves what would otherwise be Martell contradicting himself across his own clips. +- **A genuine cross-voice convergence, from opposed poles.** Martell (content maximalist) and [[sebastian]] (content = "Big zero") independently agree that enterprise doors open on trust, not cold outreach — differing only on whose trust (borrowed vs. built). Recorded on [[relationships-as-moat]] and in [[overview]]'s channel contradiction as the strongest support yet for the audience-dependent reconciliation. This is the one place where the third Martell source adds weight *despite* the shared authorship, because the convergence is with a non-Martell voice. +- **Corrected an earlier vault characterization.** The 07-20 ingest described all three levers as "one-to-many motions" — the partnerships playbook (events, win the individual) shows that was overstated; the exclusion of the first-client toolkit is softer than it looked. Qualified on [[marketing-system]] and [[client-acquisition-channels]] rather than silently rewritten. +- **Named the title's overclaim.** "Stop cold calling" prescribes… approaching strangers at events — outbound redirected at a higher-leverage audience, not abolished. Recorded on the source page, [[partnerships]], and [[client-acquisition-channels]] so the anti-outbound position isn't over-read against Tony/AB Analytics, whose SMB segment this source never addresses. +- **Source-independence continues to thin:** Martell now authors 3 of 16 sources; [[team-growth-ceiling]], [[marketing-system]], and [[partnerships]] are one worldview. The restated three-lever taxonomy was logged as framework *stability*, not corroboration. + +**Open questions / next:** + +- **The entry bar is the new blocking question:** would a Tata-class (or any consequential) partner meet a no-name solo operator? Decides whether the lever is available to [[eugene]] at all. Related: what smaller-scale partners get paid, and the SMB partner archetype for dev services. +- The 90-day-plan query for [[eugene]] now has three unresolved inputs: pick-1-vs-pick-3, articulation-vs-relationships, and now content-vs-partnerships as *his* lever. +- Standing gaps unchanged: productization-failure-case source (top), pro-thesis rigorous AI source. Cheap win still open: recover the full Business Athlete framework. + +--- + +## 2026-07-23 — ingest (Make My First $100K in Month) + +**Operation:** Ingested `raw/sources/Make My First $100K in Month.md` (US blueprint video, 22:54, undated; **fourth confirmed [[dan-martell]] source**, named in the raw note). 17/17 raw sources ingested. His first material addressed to a $0 operator — and the ingest that exposed the vault's single-voice problem as larger than counted. + +**Wiki changes:** + +- Created [[2026-07-23-make-my-first-100k-in-month]] (`#source #offer-design #sales #demand-generation`), full template. +- [[dan-martell]]: 3→4 confirmed sources; fourth-source positions block ($0 protocol); through-line extended (**sequence over effort**); Contradictions — suspected authorship of 07-18 (near-certain, verbatim mechanism reuse) and 07-17 (plausible, "buy back 10 hours" = his book's frame), possibly 6 of 17; three within-author tensions logged (cold-call vs. stop-cold-calling; parallel engines vs. pick-one; $10K-dislike vs. $10K+ partnerships); pre-first-client Next Question closed ✅. +- [[information-vs-implementation]]: **"independent second voice" claim withdrawn** (superseded note — the founding anonymous source is near-certainly Martell too); Flowtown 350K→50K added as first (self-reported) outcome figure; scramble/prompt restatement recorded as stability, not corroboration. +- [[offer-ladder]]: second ladder ($500/$1K/$10K) with explicit **decoy rationale**; Summary re-scoped ("two examples, possibly one voice"); ratio instability (5× vs 10× top) and sellable-flanks vs. decoy-flanks disagreement recorded. +- [[productized-service]]: offer-first camp gains a source (marketing-before-building, Maritime-vs-Flowtown); format triage added ("customer cash funds the eventual product"); **$50 paid-waitlist pre-sell** — cross-tradition convergence with RU validate-before-build; when-to-productize weighting re-stated (3:2 by sources, maybe 3:1 by voices). +- [[pricing-from-value]]: money map added ($1K floor restated, sub-$10K ceiling, "investment" language); floor's "second assertion may be the same speaker" caveat. +- [[outcome-based-selling]]: time/money/status triad; five offer elements (outcome/deliverable/investment/risk-reversal/urgency); "features tell, outcomes sell." +- [[client-acquisition-channels]]: parallel-engines paragraph (outbound present at $0 → supports stage reading; within-author tension); phone-mining ladder; enterprise-scoping of "stop cold calling" **confirmed from inside the corpus** (he cold-calls SMB). +- [[sales-discipline]]: closing playbook (chat DM flow, cold-call qualify-and-book); **objections-vs-obstacles** (first concrete principle for the meta-analysis's objection-script gap); volume rules (100 no's/day, first-5 throwaways, 30-second callback, AI transcript review, spend-nothing-until-paid); calls-vs-chat contradiction softened (one source prescribes both). +- [[referrals]]: third engine added — **"ask past the person"** network mining (referral-shaped intros with no past client — dodges the cold-start constraint); Eugene next-question updated. +- [[marketing-system]]: scope note upgraded (same-author $0 protocol confirms the staged reading); pick-one contradiction gains the parallel-engines complication. +- [[partnerships]]: stage tension logged ($10K-dislike at $0 vs. $10K+ scope at scale). +- [[niche-selection]]: business-owners-at-$1K+ buyer default; Ikigai as first supply-side filter. +- [[eugene]]: two additions — a concrete day-one move (phone-mining/ask-past-the-person) and a stage/format mismatch (his CV/embedded deals are naturally few×$10K+, the shape Martell's blueprint avoids). +- Source pages [[2026-07-17-design-the-perfect-offer]] and [[2026-07-18-information-is-free-implementation-is-paid]]: speaker open-questions updated with the attribution evidence. +- [[overview]]: source count 16→17; convergence caveat (US pole is substantially one corpus); 3 new highest-signal items (ask-past-the-person, obstacles-not-objections, money map); new Open Thread ($0 blueprint + single-voice audit); hidden-dependency contradiction expanded (4 confirmed + 2 suspected); calls-vs-chat and channel-count updates; statistics list extended. +- [[index]]: +1 source row, counts 50→51, status line, Martell one-liner, Known Gaps rewrite (source independence), one conflict resolved ✅ (cold-call scoping). + +**Findings / notes:** + +- **The biggest finding is not in the source — it's about the corpus.** The video reuses the scramble trick, the "10 nuanced and observable problems" prompt, and the "describe their pain better than they can" line **verbatim** from the anonymous 07-18 content source — in a video that names Martell. That makes him its near-certain author, which retroactively deletes the "independent second voice" the vault granted content-as-engine on 07-20. The 07-17 anchor is also suspect ("buy back 10 hours of your time per week" — *Buy Back Your Time* is Martell's book; $997 core; chat-first close). If both hold: **6 of 17 sources are one coach**, including one of the two "independent anchors," and every intra-US-pole convergence (the $1K floor stated "twice," the three-tier ladder appearing "twice") is self-agreement. The RU side (Rodenko, AB Analytics, Tony) now carries nearly all of the vault's independence weight. +- **Martell contradicts Martell, three times, and the scope lines are never drawn.** Cold calling is "the hardest path" (07-22) yet a prescribed channel (07-23); pick one lever (07-20) yet run two engines in parallel (07-23); he dislikes 10×$10K (07-23) yet his partnerships play is $10K+ ACV (07-22). All three plausibly resolve as **stage/segment scoping** ($0-SMB start vs. $1.5M+ scale/enterprise) — and the parallel-engines protocol actually *supports* the vault's earlier staged-reading inference — but no clip states the boundary. Recorded without silent reconciliation. +- **One genuine cross-tradition gain:** the $50 paid-waitlist pre-sell (money as the validation signal) independently matches the RU "validate before writing code" rule — different tradition, same discipline, and the paid version is the stronger test. +- **First outcome number for content-as-engine, for what it's worth:** Flowtown 350K visitors → 50K customers — self-reported, blog-era, different business model. Until now the concept had zero numbers; now it has one bad one. +- **Most portable new tools:** objections-vs-obstacles (surface concerns pre-offer), and "ask past the person" (the one referral-shaped motion available with no past clients — directly relevant to [[eugene]]'s cold start). + +**Open questions / next:** + +- **Owner action, cheap and high-value: confirm or refute the two suspected attributions** (is the 07-18 content video Martell? is the 07-17 offer-design video Martell?). One answer settles whether the single-voice share is 4, 5, or 6 of 17 — and whether the vault still has two independent anchors or one. +- Does the 100×$1K sweet spot survive delivery load for a solo operator (100 concurrent customers vs. 10 heavier deals)? The video never costs out support. +- Where is the seam between Martell's start protocol (both engines, cold calls, SMB) and his scale protocol (one lever, partners, no cold calls)? Revenue, headcount, segment — unstated. +- Standing gaps unchanged: productization-failure-case source (top), pro-thesis rigorous AI source, Business Athlete framework recovery. +- The 90-day-plan query for [[eugene]] now has a fourth input: the $0 blueprint's *sequence* (offer → pre-sell → build; phone-mining first) fits him; its *format* (SMB × $1K chat/cold-call) does not — his domain implies few × $10K+, which pushes toward [[partnerships]] and the in-person route instead. + +--- + +## 2026-07-26 — ingest (Как Построить МИЛЛИАРДНУЮ КОМПАНИЮ в 2027) + +**Operation:** Ingested `raw/sources/Как Построить МИЛЛИАРДНУЮ КОМПАНИЮ в 2027.md` (RU YouTube video, 34:52, undated; speaker **Oskar Hartmann** — KupiVIP/ShoppingLive founder, Fab.com shareholder, identified by context in the raw note). 18/18 raw sources ingested. **The vault's first third-tradition voice** — VC/product-startup world, independent of both the Martell corpus and the RU dev-sales cluster. + +**Wiki changes:** + +- Created [[2026-07-26-how-to-build-a-billion-dollar-company-2027]] (`#source #gtm #strategy #pricing`), full template. +- Created [[oskar-hartmann]] (entity; identification `tentative` — by raw-note context, not on-camera statement). +- Created [[sales-channel-as-moat]] (`#concept`) — **moat candidate #3**: the repeatable, scalable channel with predictable CAC (Pediant vs FlatPay; FlatPay founder on business #6 through the same channel; LTV×⅓-CAC entry-barrier mechanism). +- Created [[unit-economics]] (`#concept`) — full-cost pricing (forgotten lines: distribution, *repeat* acquisition, amortization, write-offs; "cash gaps are real losses"), demand→cost→price sequence, buffer/best-year rule, $1,000 credit-card CAC. **Partially fills the CAC/LTV gap flagged by the meta-analysis since day one** — general principles present, B2B-services version still missing. +- Created [[venture-fit]] (`#concept`) — ~1% rule, venture stretch kills (Fab.com $1.5B round → bankruptcy), family-owned/slow-growth alternatives, ShoppingLive case, AI capital suction. +- [[partnerships]]: **first independent second voice on the page** — adversarial on partner-as-savior (46th-priority problem, gatekeeper margin capture, 100–200× shortfalls; his own $20M one-partner deal filed as boost-not-channel), convergent with Martell on many-partners-never-one; scope split recorded (referring partner vs distribution partner — the disappointment mechanism bites the latter harder); status upgraded from "single author" to "mechanism single-author, warning two-voice." +- [[pricing-from-value]]: **pricing power as the PMF test** (raise prices, watch the flow — the cheapest test in the vault; "simulation of entrepreneurship" for price-takers); "most sell below full cost" joins sell-dear from the *cost* side; convergence note upgraded — first out-of-school voice. +- [[niche-selection]]: SOM > TAM (HVAC-agent example, Manifest immigration-law unicorn); narrow-first now converged by **three independent traditions** — the vault's best-supported claim after the core thesis; beachhead nuance added. +- [[client-acquisition-channels]]: attention-economics hierarchy (search → banner → offline events → TV; "average loud beats better silent"; AI noise — 2,000 LinkedIn messages); whale-client counter-position (Pediant — org churn outlives long integrations); third position on channel count (**1 repeatable → then multichannel** — closest any source comes to stating the vault's staged reconciliation). +- [[marketing-system]]: the machine-vs-arriving-demand **core gains an independent second voice** (repeatable channel with predictable economics as the company-defining asset); three-lever framework remains Martell-only; pick-one contradiction gains Hartmann's both-ends position. +- [[sales-discipline]]: founder-sells now stated by **three traditions** — including as Hartmann's explicit investment criterion ("I don't invest where the founder doesn't sell"). +- [[technical-founder-trap]]: **feature-#26 syndrome** — the product-startup form of the trap (builds instead of sells vs can't explain); Hartmann's blunt behavioral fix vs Martell's skill-building one. +- [[ai-market-shift]]: vibe-coding product glut ("10–15 great products in Cloud Code"); attention as the scarcest resource; the ~$4B Anthropic/OpenAI PE land grab; AI labs sucking venture capital dry. +- [[methodology-as-moat]]: two-moat framing updated to **three**. +- [[eugene]]: two cheap self-tests (SOM question; pricing-power probe on the next quote); venture-fit seconding of his bootstrapped default; many-small-partner-bets caveat. +- [[overview]]: source count 17→18; third-tradition paragraph; step 10 added to Branch A (channel/unit-economics/venture layer); 3 new highest-signal items (pricing-power probe, channel-beats-technology, "46th priority"); three-moats contradiction; channel-count contradiction updated; statistics list extended; unit-economics gap marked partially filled; new ✅ Open Thread. +- [[index]]: +1 source row, +3 concept rows, +1 entity row, counts 51→56, status line, Known Gaps updates (independence improved; adversarial gap; unit-economics partial fill; 6-of-18 renumbering). + +**Findings / notes:** + +- **The headline is independence.** After the 07-23 single-voice audit shrank the US pole, this ingest materially rebuilds the vault's confidence base: a third tradition independently restates the spine — selling beats building, founder sells first, narrow beats broad, sell dear. Narrow-first (SOM>TAM) and founder-sells are now the vault's most broadly converged claims after the core thesis. +- **The partnerships page finally has a second voice, and it's a warning.** Not a flat contradiction: Hartmann's failure mode (single gatekeeper, partner-as-distribution-channel) and Martell's playbook (many recruited referring partners) overlap only partially, and both state the many-never-one rule. The vault's reconciliation — an intro costs the partner nothing, shelf space costs plenty — is recorded as `tentative` inference. +- **Pediant vs FlatPay is the source's best structural argument:** channel beats technology because the channel is *reusable across products* (business #6) while a product is not. It founds moat candidate #3 and independently corroborates [[marketing-system]]'s machine-vs-arriving-demand distinction. +- **Scope mismatch flagged throughout:** the source addresses product startups choosing venture vs bootstrapped growth; the vault's domain is dev services. Transfer judgments (which claims carry over) are marked per page as the vault's own inference. +- **Grade caution:** everything is stage-war-story grade — 100–200×, $1,000 CAC, $4B JVs, 12h/40GB, Apple-45× are uncited; the speaker sells a paid "unicorn creator" program (same incentive caution as Martell); the Tim Cook claim is factually contestable and recorded as a framing device. + +**Open questions / next:** + +- What is the **services analogue of FlatPay's door-to-door** — the one repeatable channel a dev-services operator could run to predictable closes? (Connects directly to the 90-day-plan query for [[eugene]].) +- Does the LTV×⅓-CAC rule mean anything for lumpy B2B-services LTV? The flagged unit-economics gap is narrowed, not closed — a B2B-services-specific economics source would close it. +- Do referring partners (Martell's kind) actually escape Hartmann's disappointment mechanism, or does the 46th-priority problem bite intros too once the novelty fades? +- For [[eugene]], two cheap owner actions now queued: the pricing-power probe on his next quote, and naming his SOM in one sentence. Standing owner action unchanged: confirm/refute the two suspected Martell attributions (decides 4/5/6 of 18). +- Standing gaps: productization-failure-case source (still top), pro-thesis rigorous AI source, Business Athlete framework recovery. + +--- + +## 2026-07-26 — query follow-up (create concept: TAM / SAM / SOM) + +**Operation:** User asked "what are SOM and TAM?" after the Hartmann ingest, then requested the definitions be turned into concepts. Created **one** canonical page rather than three stubs (merge-over-duplicates rule): [[tam-sam-som]]. + +**Wiki changes:** + +- Created [[tam-sam-som]] (`#concept #strategy #positioning`) — the three nested circles (table), the SOM > TAM directional rule, the beachhead reading (TAM stays behind the SOM as the growth story), and a terminology caveat. +- **Attribution honesty:** TAM/SOM usage and all examples trace to [[2026-07-26-how-to-build-a-billion-dollar-company-2027]]; **SAM is standard industry vocabulary from general knowledge, present in no ingested source** — marked as such in Evidence and Contradictions, with a rule that a future ingested source's definition wins. +- Linked from [[niche-selection]] (SOM>TAM paragraph), [[venture-fit]] (Related), the source page (Connections), [[overview]] (navigation). +- [[index]]: +1 concept row, counts 56→57, status line. + +**Findings / notes:** + +- The page's one non-obvious contribution: the **beachhead vs fortress distinction** — a SOM chosen as an entry point to a bigger market (Hartmann/venture logic) and a niche chosen for durable narrowness (Rodenko's AI-weak methodologies) are different strategies wearing the same circle. No source distinguishes them; flagged as an open contradiction. + +**Open questions / next:** + +- For [[eugene]]: is industrial-equipment CV/embedded a beachhead or a fortress? The answer changes what "winning the SOM" should lead to. +- No honest sizing method in the vault yet (all circles in pitch practice are constructed top-down) — worth capturing if a source supplies a bottom-up one. + +--- + +## 2026-07-26 — ingest (Главный Принцип УСПЕШНОГО БИЗНЕСА) + +**Operation:** Ingested `raw/sources/Главный Принцип УСПЕШНОГО БИЗНЕСА.md` (RU YouTube video, 17:52; **second [[oskar-hartmann]] source**, named in the raw note — which also effectively confirms the context-based attribution of the first). 19/19 raw sources ingested. Central thesis: **"Сначала продавай, потом строй"** — sell first, then build; only money votes. + +**Wiki changes:** + +- Created [[2026-07-26-main-principle-of-successful-business]] (`#source #validation #strategy`), full template. +- Created [[sell-before-build]] (`#concept`) — signal hierarchy (click < waitlist < payment < **pre-payment**); cheap-experiment toolkit as a cost-ordered table (AI-mockup blast, landing→payment screen, fake payment screen, fake-door buttons, Wizard-of-Oz, paid pre-order); acute-pain bridge; duration-without-revenue red flag. **Rule is three-tradition** (RU validate-first + Martell $50 paid waitlist + Hartmann toolkit); mechanics single-source `tentative`. +- [[productized-service]]: pre-sell paragraph upgraded to **three traditions**; sharpened bar recorded (unpaid waitlist doesn't count — makes Martell's *paid* slot the load-bearing detail); **when-to-productize dispute updated** — offer-first camp gains its first genuinely independent voice, but with the scope caveat that the camps may answer different questions (validate-before-build vs standardize-after-repetition; vault synthesis, would dissolve the dispute if right). +- [[pain-discovery]]: **acute-pain test** added ("good business = everything is bad and people still pay"; hospitals) — revealed preference at its purest; smallest-group-**by-name** targeting (a SOM statement → [[tam-sam-som]]). +- [[cloning-over-originality]]: **first independent second voice** — app studios that "forbid themselves from inventing," Samwer's fake-button eBay clone built in click-count order, robot-data founder copying 10 LLM-data playbooks; adds the clone-then-*measure* answer to the page's unobservable-details worry; status line updated. +- [[sales-discipline]]: duration-without-revenue red flag recorded as cross-tradition convergence with Rodenko's "год перепаковки — для тех, кто боится взять трубку" (same claim, seller's coach vs investor screening pitches); launch-ugly / endure-reality-early. +- [[unit-economics]]: **Zavent post-payment trap** ("a bank financing its clients" — payment timing as a unit-economics variable); $80–100 CAC-burn barrier restated (within-author consistency, flagged as such); status line now "single author, two sources." +- [[sales-channel-as-moat]]: CAC-burn restatement noted (stability, not corroboration). +- [[oskar-hartmann]]: second source; **framework-stability block** (prove-demand-first, money-as-signal, CAC-burn all restated consistently); one within-author tension logged (founder-sells-personally vs automated payment-screen tests — plausibly segment-scoped, unstated); attribution upgraded to confirmed; credibility note (two self-reported failures — coworking, Zavent — unusual among the vault's promotional voices). +- [[eugene]]: runnable pre-build checklist (10 named industrial prospects; deposit-backed audit/discovery sprint as the services analogue of a paid waitlist; semi-manual first CV-inspection delivery); composes with phone-mining. +- [[overview]]: source count 18→19; third-tradition thread expanded (two sources, framework stability, cloning corroboration, deception caveat); step 5 gains [[sell-before-build]]; 2 new highest-signal items (only-money-votes / coworking test; acute-pain test); when-to-productize contradiction updated; statistics list extended. +- [[index]]: +1 source row, +1 concept row, counts 57→59, status line, Hartmann one-liner. + +**Findings / notes:** + +- **Best structural gain: validate-before-build is now the vault's second three-tradition claim** (after narrow-first/SOM). RU dev-sales, Martell, and Hartmann all state it independently, and Hartmann resolves the apparent Martell-vs-Hartmann waitlist discrepancy himself: unpaid lists don't count, *paid* ones do — the two prescriptions agree at the money bar. +- **[[cloning-over-originality]] finally has a second voice** — it had been flagged since June as single-lineage. Hartmann's cases add the missing mechanism: where Pabrai clones judgment, Samwer clones the artifact and lets *instrumentation* pick priorities. +- **Ethics recorded, not endorsed:** two toolkit rows (fake payment screen, fake-door buttons) collect purchase intent under false pretenses; caveat placed on both the source page and [[sell-before-build]], with the honest variants (visible pre-order, paid waitlist, manual MVP) noted as carrying most of the same signal. +- **"Build.ai" flagged as almost certainly Builder.ai** (general-knowledge note, marked as such): the company collapsed into insolvency in 2025 amid allegations its AI was largely manual work — which makes Hartmann's "great way to start" framing half the story; the same case is the cautionary tale for never graduating from Wizard-of-Oz. +- **One new tension for the articulation thread:** "don't dictate what the customer should want" vs [[pain-discovery]]/[[outcome-based-selling]]'s name-the-pain-better-than-they-can. Likely scoped (product demand vs service framing); logged on [[sell-before-build]] and the source page. + +**Open questions / next:** + +- **What is the smallest *paid* test for a dev-services offer?** (Paid audit? Deposit-backed discovery sprint?) Feeds [[eugene]]'s 90-day-plan query directly — arguably its missing first step. +- Does the Zavent pre-pay rule survive B2B services reality, where net-60/90 post-payment is standard enterprise practice? If enterprise never prepays, is enterprise demand untestable by this method — or is a paid pilot the equivalent? +- Hartmann's two sources are consistent; a third would test whether the stability holds across formats (talk vs interview). +- Standing gaps: productization-failure-case source (still top — note the when-to-productize dispute may partially *dissolve* instead), pro-thesis rigorous AI source, Business Athlete recovery, the two Martell attribution checks. + +--- + +## 2026-07-26 — query (Eugene's concrete 90-day plan) + +**Operation:** Answered the standing next-query flagged on [[index]], [[eugene]], [[client-acquisition-channels]] and [[overview]] since 2026-07-17: turn the corpus into [[eugene]]'s **dated** channel/niche plan, and resolve the live tension inside it (in-person first-client route vs. building a [[marketing-system]] early). Read-only over 12 existing pages; no source claim altered. + +**Wiki changes:** + +- Created [[2026-07-26-eugene-90-day-plan]] (`#query #sales #planning`) — assumptions table (A1–A5, all `tentative`), the stage-based resolution, channel commitment, week-by-week plan 2026-07-26 → 2026-10-24, Day-90 gate, evidence trail, follow-ups. +- [[eugene]]: 90-day-plan Next Question closed ✅; new bullet on the two rival diagnoses now being cheaply testable; 2 Related Pages links. +- [[sell-before-build]]: its "smallest paid test for a dev-services offer" question struck through with a **proposed answer** (fixed-scope paid diagnostic) + its falsifier. +- [[client-acquisition-channels]]: the "which 3 channels for Eugene" question answered ✅, with the load-bearing assumption named. +- [[2026-07-17-best-method-first-client]]: successor callout — method vs. schedule; core recommendation explicitly preserved. +- [[overview]]: "Application is unstarted" → "Application has started — an experiment awaiting data"; stale `Timelines / Queries / Lint reports: empty` navigation line corrected (it had listed 3 existing pages as empty). +- [[index]]: +1 query row, counts 59→60, queries 1→2, status line, next-operation note. + +**Findings / notes:** + +- **The tension resolves by stage, not by compromise.** The three-lever map comes from a clip aimed at a stalled-$1.5M founder and omits outbound/referrals/in-person entirely; the same author runs one-to-one at $0; [[oskar-hartmann]] nearly states the staged rule outright. So: one-to-one is the engine. **But not to zero** — [[marketing-system]]'s ~6-month lag means "start it when you need it" starts it late, and publishing doubles as the articulation reps [[technical-founder-trap]] prescribes. Budgeted at ~2h/week, explicitly not measured on leads. +- **pick-1 vs pick-3 dissolves for this case** under the units reading the vault had already inferred: one *lever* (relationship-mediated one-to-one), three *venues*. Both rules satisfied at once — the conflict is not settled in general, only routed around here. +- **Four vault-original contributions, all inference and marked as such:** (1) the stage resolution with its non-zero-deposit exception; (2) the **Week-2 phone mine as the discriminator** between [[technical-founder-trap]] and [[relationships-as-moat]] — the vault has called those two diagnoses "testable against each other" since 07-20 without ever specifying the test; (3) the **paid diagnostic** as the smallest paid test for dev services; (4) a Day-90 gate scored on **inputs**, applying reps-not-views to the plan itself. +- **Honest weak joints, recorded in the plan rather than smoothed over:** the niche (A2) and the enterprise-lite buyer read (A5) are vault inferences that carry the entire channel decision; the industry room is unnamed; A4 (prior paid work to mine) is unverified; every threshold in the gate is invented, its function being pre-commitment, not accuracy. +- Evidence-quality caveat restated on the page: no failure-case source exists for the productized/sell-dear model, so nothing in the plan has been tested against a documented loss. + +**Open questions / next:** + +- Owner-answerable, and they unblock the plan's weakest joints: which machine-builder/automation association or trade fair meets often enough for the 3×/6× mechanic, and **will an industrial buyer pay for a diagnostic at all** (if free feasibility is the norm, Month 2 needs redesign). +- Standing owner actions unchanged: confirm/refute the two suspected [[dan-martell]] attributions (several rungs of this plan rest on his corpus — 4 vs 6 of 19 matters here); the pricing-power probe; naming the SOM in one sentence (now Week 1, step 1). +- **A lint is due.** Last full lint was 2026-07-18 at 40 pages; the wiki is now 60, with [[sales-channel-as-moat]], [[unit-economics]], [[venture-fit]] all single-source `tentative` and unlinted, and this query adding a page whose inbound links are all fresh. +- Standing gaps: productization-failure-case source (still top), pro-thesis rigorous AI source, Business Athlete framework recovery. + +--- + +## 2026-07-29 — ingest (Start a business with Claude Code) + +**Operation:** Ingested `raw/sources/Start a business with Claude Code.md` (conclusions note on a YouTube Short, 0:42, **author unnamed**, undated). 20/20 raw sources ingested. The vault's shortest and thinnest source: a $0→$1M playbook with [[claude-code]] as the full GTM stack — landing page + invented company + waitlist, scraped prospect list, cold-outbound script, close the sale, *then* build the product. + +**Wiki changes:** + +- Created [[2026-07-29-start-a-business-with-claude-code]] (`#source #validation #gtm #ai`), full template; evidence grade stated up front (42s, no cases, no figures, no named speaker — pure prescription). +- Created [[claude-code]] (`#entity #tool #ai`) — **the vault's first tool entity**: three corpus roles (build engine/commoditizer per Hartmann's "10–15 products in Cloud Code"; full GTM stack per this source; domain tutor/leveler), harness-market adjacency, capability counter-evidence linked. +- [[sell-before-build]]: fourth-voice echo noted in Summary (not counted toward independence until attributed); **AI-era compressed variant** paragraph — its unpaid waitlist fails the vault's money bar but its closed sale exceeds it; invented-company front filed with the deception-based toolkit rows; Evidence + Contradictions updated. +- [[ai-market-shift]]: **Leveler** row added to the roles table (domain knowledge on demand collapses the entry barrier); synthesis paragraph noting the odd alliance — [[ai-productivity-evidence]]'s novice-tilt cuts *against* expert-productivity hype but mildly *for* the leveler role, while still contesting the "then ask Claude to build it" step; [[claude-code]] added to Related Pages. +- [[client-acquisition-channels]]: **second $0-stage voice for cold outbound** — AI-scraped list + AI-written scripts as the entire first channel; matches Martell's $0 blueprint shape (caveat: if the author is Martell, the match is self-agreement); further supports the $0/SMB-vs-enterprise scoping of cold outbound. +- [[sales-channel-as-moat]]: slogan echo recorded ("distribution is the moat, not code") — second voice for the *priority claim*, zero corroboration of the repeatability/CAC mechanism; status explicitly unchanged. +- [[technical-founder-trap]]: Evidence bullet — the source's stated audience ("developers who over-invest in building and under-invest in selling"; blocker psychological, not technical) as a slogan-grade restatement of the build-instead-of-sell form. +- [[overview]]: source count 19→20; corpus paragraph and navigation updated; entities line gains a *tools* group. +- [[index]]: +1 source row, +1 entity row, counts 60→62, status line, Known Gaps updated (third unattributed source joins the two suspected Martell items; denominators refreshed to /20), lint note 60→62. + +**Findings / notes:** + +- **Nothing in this source is new to the vault as a claim — that is the finding.** Sell-first, distribution-over-product, cold outbound at $0, bias to action: each already held, with better support elsewhere. Its marginal contributions are (1) the **Leveler** role for AI (genuinely new to [[ai-market-shift]]'s table), (2) Claude Code named as the executor of the *entire* pre-product stack, and (3) an ultra-compressed confirmation that this playbook has reached mass short-form content — the vault's spine is now ambient advice. +- **Attribution discipline applied up front this time.** After the 07-23 audit (anonymous sources later unmasked as Martell), this source is held at **echo-grade** on every page it touches: it shifts no status lines, gains no independence credit, and each page notes the attribution condition explicitly. +- **The playbook passes the vault's own money bar — but not where it appears to.** Its waitlist is unpaid (fails the Hartmann/Martell bar); its actual validation event is the closed sale in step 5, which sits above mere payment in the signal hierarchy. Recorded on [[sell-before-build]]. +- **Ethics/compliance recorded, not endorsed:** the invented-company front is a fake *business* (kin to fake payment screens — same unmodeled reputational/legal cost), and scraped-list cold email carries GDPR/CAN-SPAM exposure. Neither cost appears in the source. +- **Contrast with the vault's own application:** [[2026-07-26-eugene-90-day-plan]] reaches the same sell-first conclusion but replaces the fake front with a paid diagnostic — the honest variant of the same discipline. + +**Open questions / next:** + +- **Who is the author?** Third unattributed short-form source (after the two suspected Martell items). No verbatim marker links it to any known voice; cheap owner action to check. +- Does "Claude will tell you how" survive regulated/physical domains (the owner's industrial CV niche), or only commodity digital services? +- **A lint is now overdue** — 40 pages at last full lint (2026-07-18), 62 now; this ingest also added a tool entity, a page *type* the lint conventions haven't seen. +- Standing gaps unchanged: productization-failure-case source (top), pro-thesis rigorous AI source, Business Athlete framework recovery, the two Martell attribution checks. + +--- + +## 2026-07-29 — attribution update (Start a business with Claude Code = Dan Martell) + +**Operation:** Vault owner confirmed the author of [[2026-07-29-start-a-business-with-claude-code]] is **[[dan-martell]]** (the short names no speaker; same provenance class as the 07-19 confirmation). His **5th confirmed source of 20** — possibly 7 with the two still-suspected. Propagated the relabel from "unattributed echo" to "within-author self-agreement" across every page the same-day ingest touched. + +**Wiki changes:** + +- [[2026-07-29-start-a-business-with-claude-code]]: metadata updated (author, provenance); author open question closed ✅; Connections rewritten (each link now names its relation — restatement vs new claim); Change Impact extended. +- [[dan-martell]]: 4→5 confirmed; **fifth-source positions block** (AI as the entire pre-product stack; the Leveler claim; distribution-is-the-moat slogan); **two within-author drifts logged** — the short's waitlist is *unpaid* against his own $50-paid-slot rule (07-23), and the invented-company front is deception-shaped with unmodeled cost; through-line updated to five sources; denominators refreshed (5 of 20, possibly 7); provenance note now covers both owner-confirmed clips; [[claude-code]] added to Related Pages. +- [[sell-before-build]]: "fourth voice" withdrawn — within-author restatement (Martell already counts among the rule's three traditions); the unpaid-waitlist nuance upgraded from cross-source observation to **within-author drift**. +- [[client-acquisition-channels]]: "independent match to the $0 blueprint" evaporated as predicted by the ingest's own conditional — relabeled framework stability; one genuine gain kept: the $0/SMB-vs-enterprise scoping of cold outbound now holds *across every format he publishes*. +- [[sales-channel-as-moat]]: the slogan echo folds into the already-recorded Martell/marketing-system convergence — no second voice; status explicitly unchanged. +- [[technical-founder-trap]]: Evidence bullet relabeled — same author as the page's founding source; restatement, not corroboration. +- [[ai-market-shift]]: Leveler attribution updated — Martell's first claim in the roles table; still single-source, slogan-grade. +- [[claude-code]]: roles table attributed; Contradictions sharpened — all promotional claims about the tool trace to exactly **two voices** (Martell, Hartmann). +- [[overview]]: Martell cluster four→five confirmed; hidden-dependency contradiction updated (5 of 20, possibly 7); corpus paragraph and navigation relabeled. +- [[index]]: source row, Martell one-liner, Known Gaps (single-voice problem **worsened**: 5 of 20), status line. + +**Findings / notes:** + +- **The echo-grade discipline paid for itself within a day.** Every page had recorded the source with an explicit attribution condition and zero independence weight — so the confirmation changed labels, not conclusions. No claim needs re-weighing; this is the cheapest possible outcome of an attribution reveal, and the direct payoff of the 07-23 audit's lesson. +- **Martell's share is now the vault's largest by a wide margin: 25% confirmed, possibly 35%.** The RU side (Rodenko, AB Analytics, Tony) and Hartmann now carry essentially all of the vault's independence weight. Practical consequence: any future US-coaching short-form ingest should be *presumed* Martell-adjacent until shown otherwise. +- **The two within-author drifts are the only new information.** Unpaid waitlist (vs his own load-bearing $50 paid slot) and the fake-company front (vs his "spend nothing until customers pay" — which at least is honest about money) — both plausibly short-form lossiness, but they show his compressed formats shed exactly the details his fuller protocols mark as critical. A caution for weighting any 42-second source, his or not. +- **One thing the attribution strengthens rather than weakens:** the enterprise-vs-$0/SMB scoping of cold outbound is now consistent across five Martell formats — within-author stability at that sample size is real evidence about *his* framework, if still none about the world. + +**Open questions / next:** + +- The two remaining attribution checks ([[2026-07-18-information-is-free-implementation-is-paid]] near-certain, [[2026-07-17-design-the-perfect-offer]] plausible) are the same cheap owner ask that just resolved this one — settling them decides 5, 6, or 7 of 20, and whether the vault has two independent anchors or one. +- **A lint is overdue** (40 pages at last full lint, 62 now) — and it should now also check every page still describing Martell as "4 confirmed" or using stale /17–/19 denominators. +- Standing gaps unchanged: productization-failure-case source (top), pro-thesis rigorous AI source, Business Athlete framework recovery. diff --git a/raw/assets/Dan Martell - Scale Your Business Workbook.pdf b/raw/assets/Dan Martell - Scale Your Business Workbook.pdf new file mode 100644 index 0000000..0eadf2f Binary files /dev/null and b/raw/assets/Dan Martell - Scale Your Business Workbook.pdf differ diff --git a/raw/sources/17 ways to get your 1st client as a developer in 2026.md b/raw/sources/17 ways to get your 1st client as a developer in 2026.md new file mode 100644 index 0000000..851ef82 --- /dev/null +++ b/raw/sources/17 ways to get your 1st client as a developer in 2026.md @@ -0,0 +1,204 @@ +# Conclusions + +**Source:** https://www.youtube.com/watch?v=mugDs0XaQ1A +**Title:** 17 ways to get your 1st client as a developer in 2026 +**Duration:** 40:49 +**Speaker:** founder of AB Analytics (B2B AI consulting, LA) and the *Code to CEO* startup accelerator — claims he went from ~$250k/yr as a dev to roughly double that since starting the consulting firm + +--- + +## Core thesis + +Most engineers can't land even one client on demand because they fight for scraps on the same overcrowded channels (Upwork, generic LinkedIn cold DMs, X). The win is to **fish where no one else is fishing.** The video stacks 17 channels in three tiers — common (everybody knows), low-key (most devs ignore), out-of-the-box (almost no devs do) — and the explicit advice is to **pick three methods, one from each tier, and run them daily for 90 days** before adding more. + +> "Consistency beats intensity every single time. 30 minutes a day beats five hours once a month." + +Two universal rules that apply to every channel below: +- **Follow up at least 5 times** — ~80% of sales happen after the 5th contact; most devs quit after one. +- **Niche specificity beats volume** — "Shopify developer for fashion brands" outsells "web developer" by a wide margin everywhere. + +--- + +## Tier 1 — Common methods (1-5) + +Everybody knows them, everybody competes here. Useful as a floor; do not stay here. + +### 1. Freelance platforms (Upwork, Fiverr, Toptal) +Built-in trust/payments/disputes, but ~18% take and a race-to-the-bottom on price. +- Recommended **only** if you're a true beginner in a third-world country (cost of living lets the rates work). +- First/second-world devs: skip — opportunity cost is too high. +- If you must: niche extremely hard, compete on value not price, push hard for 5-star reviews early. + +### 2. LinkedIn outreach (the B2B goldmine) +900M+ users, decision-makers active daily. + +Profile = resume + portfolio + sales page. Banner, featured work, endorsed skills, recommendations. + +**Who to connect with:** decision-makers (budget + authority) and referral partners (designers/marketers/agencies serving the same ICP). Quality, not quantity. + +**Cold-message anatomy that gets a response:** +> Hey, saw your post about *[specific post]* — *[short genuine comment]*. I help *[ICP]* with *[specific problem]*. I just helped *[prev company]* achieve *[specific result]*. If I can help you do the same, would you be open to a brief chat? + +Never sell in the first message. Never use templates blindly. + +**Follow-up cadence:** Day 0 initial → Day 3 friendly bump → Day 7 add value → Day 14 case study → Day 30 break-up email. (Tighter: every 2 business days.) One Code to CEO founder, Paul, closed a $10k + $1k/mo retainer this way. + +### 3. Content marketing (YouTube + X) +Teach what you know; build authority that attracts inbound. + +The speaker's contrarian take: **don't start content marketing until you're already making $10-15k/mo from outbound.** Otherwise it's slow and you starve. Content is a leverage layer on top of an already-working channel. + +### 4. Cold email +The most direct line to decision-makers — no gatekeepers, no algorithm. Snipe, don't spray. + +**Lead sources:** LinkedIn Sales Navigator, Apollo, Google Maps (local), AI research agents, company sites, industry directories. + +**Qualify on:** company size, urgent pain, decision-maker access, solvable problem. + +**Subject line carries 47% of the open** — spend 50% of your time here. + +| Quality | Example | Why | +|---|---|---| +| Bad | "Web development services — affordable rates" | Reads like a scam | +| Okay | "Ideas to improve your site load time" | Generic, no research evident | +| Great | "Quick question about [Company]'s checkout flow" | Specific, personal, implies you looked | + +**Body structure (< 100 words):** context → observation (proof of research) → value (how you help) → proof (credibility) → CTA (one clear next step). + +**Scaling stack:** Apollo (contacts) → Instantly/SmartLead (sending) → Clay (enrichment) → Claude (custom first lines). Automate process, not the human touch. Code to CEO founder John scaled this to ~1000 sends/day → $100k+/mo MRR. + +### 5. Referrals — highest converting, lowest cost +A happy client referring you ≈ 10 cold leads. 4× higher conversion, ~0 acquisition cost, pre-built trust. + +The gap: **91% of clients say they'd refer, only 11% of sellers ask.** + +**System:** +- Ask **right after delivery** when excitement is highest. +- Be specific: "Do you know anybody else who needs [exact thing]?" +- Make it frictionless: forward-ready email template + one-link portfolio. +- Offer incentives (commission, retainer credit, free maintenance month). +- Every project ends with: *"Who else should I talk to?"* + +--- + +## Tier 2 — Low-key methods (6-13) + +Most devs don't touch these. Less competition, better clients, higher rates. Local/in-person mostly. + +### 6. Chamber of Commerce — the speaker's most underrated channel +4000+ Chambers in the US alone; most European countries have equivalents. +- Business owners with budgets and **terrible websites / no automation**. +- The member directory alone is a pre-qualified lead list. +- Show up 3× → "regular." Show up 6× → trusted. Then you get invited to **speak**, which makes you the local tech expert. +- Membership ~$200-500/yr; one small project pays for a decade. +- When he joined the LA Chamber, he was the only software engineer in the room. + +### 7. Local business groups +Rotary, Lions, Kiwanis (service clubs); **BNI (Business Network International)** — one person per profession, weekly meetings, referrals tracked. BNI members average **$20k/yr in referred business**. + +### 8. Industry associations +National Association of Realtors, local Medical Society, etc. Hyper-targeted; everyone there is exactly your ICP. + +### 9. High-end hotels — the "sauna + hotel bar" strategy +Wherever the speaker travels (Vegas, Tokyo, LA), he stays at a top-tier hotel and: +- Morning: sauna/spa — calm, captive audience, make natural conversation. +- Evening: hotel bar/lounge — sit with laptop or phone, start conversations. +- Even **one client per year** from this single tactic justifies the cost if it's six figures. + +Plus business centers/executive lounges in hotels = high-value coworking. Conference hotels in Dubai/Vegas during big events = badge-hunting in common areas. One founder (Dom) sold a contract he started on a Dallas → Sydney flight. + +### 10. Car shows and expos (and boat shows, art fairs, food/wine expos, home & garden) +Speaker's framing: rich people own classic/exotic cars → most are business owners or top-company execs. +- Zero sales pressure → genuine connections. +- "What do you do?" → "I do software for [their industry]" → "We actually need that." +- Repeat attendance at the same shows builds trust. +- This is how he literally became known in LA as "the AI guy." + +### 11. Local conferences (not SXSW / TechCrunch / Web Summit) +- Local events are **begging for speakers** because they can't afford the big-name ones. +- Pick a practical topic, submit early to the call-for-speakers, bring case studies. +- Speak once → instant credibility. Speak regularly → you become *the* expert in the area. +- Follow-up rule: connect on LinkedIn within 24h, schedule an in-person follow-up within 1-2 weeks. + +### 12. Golf courses +He doesn't golf. Got 2 clients from ~40-50 hours of golfing → ~20× ROI on time. Driving ranges/clubhouses work even without playing. Charity tournaments and corporate scrambles are built-in networking. + +### 13. Gyms + country clubs (the 5am crowd + premium tier) +- **5am gym crowd = business owners, execs, disciplined professionals.** Same faces daily → casual relationship over weeks. +- He moved up from Crunch to **Equinox** — equipment isn't better, but members paying $200+/mo are his ICP. +- **Country clubs** ($50k-$200k+ in LA): nobody goes for the golf — they go to network. One project covers years of membership. + +--- + +## Tier 3 — Out-of-the-box methods (14-17) + +The 1% layer. Highest effort, highest reward, almost no competition. + +### 14. Strategic partnerships +Partner with businesses that serve your ICP. If you build for law firms → partner with vendors who sell to law firms. They get a referral fee or reciprocal leads; you get warm intros. + +### 15. Productize services +Fixed price, fixed scope, named packages. The speaker calls this the single biggest change to his client acquisition. + +Tiers (each step is more leverage): +| Tier | What | Price anchor | +|---|---|---| +| DIY | Templates / tools / course | Cheapest | +| DWY ("Done With You") | Coaching + frameworks | Mid | +| **DFY ("Done For You")** | We build it for you | Highest — his focus today | + +Friction down → buying easy. Clients know exactly what they get and what it costs. + +### 16. Workshop strategy — in-person, paid or free +- Run a free 2-hour workshop in your city (he ran Facebook ads to fill seats). +- Partner with libraries / co-working spaces / colleges — they often give space + promotion for free. +- Teach something genuinely valuable. End with a CTA for deeper engagement → some attendees can't get the help they need in 2h and convert into clients. + +### 17. Case studies + webinar funnel +Detailed case studies (problem → solution → process → ROI) feed a webinar funnel. + +**Webinar formula:** 60% teach · 20% case study · 20% offer. Expected conversion: **15-25%**. One webinar = 3-6 months of client work. Always follow up with non-buyers via email sequence. + +Webinars convert because of reciprocity + demonstrated authority + live trust (unedited). + +--- + +## Cross-cutting principles + +| Principle | Why it matters | +|---|---| +| Consistency > intensity | 30 min/day × 30 days = 15 hrs/mo; one big push won't land you clients | +| Pick 3 methods (1 common + 1 low-key + 1 creative) and run them 90 days minimum | Master a few channels before stacking more | +| Lifestyle integration | Hotels, gyms, car shows, golf — you'd do these anyway; do them deliberately and they double as pipeline | +| Always follow up ≥ 5 times | Follow until they say "stop." 80% of sales happen after the 5th touch | +| Niche specificity > volume | "Shopify dev for fashion brands" outperforms "web dev" everywhere | +| Track everything | Outreach, response, meeting, proposal, close rates — no feedback loop = no improvement | +| Client #1 is the hardest | #5 is easier, #10 comes to you. Momentum compounds | +| Start messy, today | Perfect time doesn't exist. The best method is the one you'll actually do | + +--- + +## Actionable 90-day plan (the explicit recipe) + +1. **Pick 3 methods** — one from each tier. Example combos: + - Cold email (common) + Chamber of Commerce (low-key) + Workshop strategy (creative) + - LinkedIn outreach + Premium gym + Productized DFY packages + - Referrals + Industry association + Strategic partnerships +2. **Run them daily for 90 days.** No new methods until these are mastered. +3. **Track:** outreach sent · responses · meetings booked · proposals sent · closes. +4. **Always follow up 5×** before giving up on any contact. +5. **Productize** as soon as you've delivered the same kind of work 2-3 times. +6. **Lifestyle-integrate** the in-person channels — gym, hotels, car shows — so the time spent has a second use. +7. **Once stable at $10-15k/mo**, layer in content marketing (YouTube/X) for leverage. + +--- + +## Who this is for + +Senior software engineers who are **business beginners** — strong technically, weak at sales. Particularly anyone stuck on Upwork or generic LinkedIn DMs and wondering why nothing converts. Not for total dev beginners and not focused on paid ads (deferred to a future video). + +## Caveats / promotional notes + +- Speaker plugs his Feb 22 ideation workshop and his *Code to CEO* accelerator throughout — examples ("Paul," "John," "Dom") are accelerator members, so treat the success metrics as marketing-flavored claims, not independent data. +- Several tactics (premium gyms, country clubs, sauna/bar networking) implicitly assume disposable income and a major US city. Adapt to your context. +- Door-knocking the "5am Equinox crowd" or country clubs is not legal/cultural advice — read the room. diff --git a/raw/sources/AI Coding Productivity - Empirical Evidence (deep research 2026-07-18).md b/raw/sources/AI Coding Productivity - Empirical Evidence (deep research 2026-07-18).md new file mode 100644 index 0000000..d49bc46 --- /dev/null +++ b/raw/sources/AI Coding Productivity - Empirical Evidence (deep research 2026-07-18).md @@ -0,0 +1,110 @@ +# AI Coding Productivity — Empirical Evidence (Deep-Research Synthesis) + +**Compiled:** 2026-07-18 by Claude Code `deep-research` harness (fan-out web search → source fetch → 3-vote adversarial verification → synthesis). +**Purpose:** A deliberately ADVERSARIAL evidence dossier commissioned to counterbalance a vault of promotional sources asserting AI has "zeroed the cost of commodity software development" and made "seniors more valuable while juniors become irrelevant." +**Provenance note:** This is a *second-order synthesis*, but unlike the vault's promotional videos its inputs are primary peer-reviewed papers, RCTs, and large-sample surveys. Verification stats: 6 search angles → 23 sources fetched → 104 claims extracted → 25 verified (23 confirmed, 2 refuted). Every quantitative figure below is time-scoped and caveated. + +--- + +## Bottom line + +Rigorous evidence **qualifies more than it demolishes** the popular narrative. No study shows AI has zero or negative value in general. What the evidence shows: AI's real productivity effect on developers is **modest (≈14–19% range), context-dependent, tilted toward NOVICES rather than experts, and systematically overstated by self-report.** Two of the popular thesis's load-bearing claims are directly inverted by the best available data: + +1. **"AI zeroed the cost of skilled dev work"** → the strongest developer-specific RCT found experienced devs **19% SLOWER** with early-2025 AI. +2. **"Seniors up, juniors irrelevant"** → the best skill-distribution study found the **least-experienced workers gain most** (34% vs. ~0 for experts). + +--- + +## Finding 1 — METR RCT: experienced devs were 19% SLOWER with AI (confidence: HIGH, 3-0) + +**Claim:** METR's 2025 randomized controlled trial found experienced open-source developers took **19% LONGER** to complete real tasks when allowed to use early-2025 AI coding tools — AI slowed the most-skilled population down. + +**Evidence:** Verbatim from primary source (METR blog 2025-07-10; arXiv:2507.09089): *"When developers are allowed to use AI tools, they take 19% longer to complete issues—a significant slowdown"* / *"allowing AI actually increases completion time by 19%—AI tooling slowed developers down."* + +- **Design:** genuine RCT (gold standard). 16 experienced OSS developers (avg ~5 yrs on their OWN mature repos, ~1,500 commits; repos avg 22k+ stars, 1M+ LOC). 246 real tasks (~2h each), Feb–June 2025, randomly assigned AI-allowed vs AI-disallowed. Tools: Cursor Pro + Claude 3.5/3.7 Sonnet. +- **Caveats (qualify, don't refute):** (1) small n=16; (2) narrow population — experts on codebases they know deeply, the cohort *least* likely to benefit → does NOT generalize to juniors or greenfield work; (3) non-peer-reviewed preprint; (4) authors concede experimental-artifact risk "cannot be entirely ruled out." +- **On the Feb 2026 follow-up:** METR does NOT retract the 19% figure; it labels it "historical" (scoped to early-2025 tools) and only redesigns FUTURE experiments after finding selection bias (30–50% of devs refused no-AI conditions) in a *separate* Aug-2025 trial. Secondary blogs calling this "backtracking" overstate it. + +**Sources:** metr.org/blog/2025-07-10-early-2025-ai-experienced-os-dev-study · arxiv.org/abs/2507.09089 · x.com/METR_Evals/status/1943360399220388093 · metr.org/blog/2026-02-24-uplift-update + +--- + +## Finding 2 — Perception vs. reality gap (~39 points) (confidence: HIGH, 3-0) + +**Claim:** Developers' subjective perception of AI's benefit is badly miscalibrated. In the METR RCT they **forecast a 24% speedup** beforehand and **still estimated a 20% speedup afterward** — despite being measured **19% slower**. A ~39-point perception-vs-reality gap, which is exactly the evidence base ("it feels faster") that most "AI makes devs faster" claims rest on. + +**Evidence:** All three figures verbatim from arXiv:2507.09089 abstract (developers' own forecast 24%; post-hoc estimate 20%; measured −19%). This within-study perception gap is the study's most robust, uncontested takeaway — critiques target the external validity of the 19% *magnitude*, not the perception gap. **Survey parallel:** Stack Overflow 2025 reports 69% self-report a personal-productivity increase from AI agents *even while* majorities report time lost fixing flawed AI output — self-report on both sides, so a looser "parallel," not objective measurement. + +**Sources:** arxiv.org/abs/2507.09089 · metr.org/blog/2025-07-10… · stackoverflow.blog/2025/12/29/… + +--- + +## Finding 3 — Brynjolfsson/Li/Raymond: AI gains tilt to the LEAST-skilled (confidence: HIGH, 3-0) + +**Claim:** "Generative AI at Work" found gains distributed INVERSELY with skill: least-experienced workers improved most (~34%, in speed AND quality); most-experienced workers saw only small speed gains and **small quality DECLINES**. Overall average a modest 14–15% — not a cost-to-zero collapse. This is the direct inverse of "seniors more valuable, juniors irrelevant." + +**Evidence:** Verbatim (NBER w31161, Apr 2023; published *Quarterly Journal of Economics* 140(2):889–942, 2025 — a top-5 econ journal; authors Brynjolfsson/Stanford, Li/MIT, Raymond): *"increases productivity, as measured by issues resolved per hour, by 14% on average, including a 34% improvement for novice and low-skilled workers but with minimal impact on experienced and highly skilled workers"* and *"Less experienced and lower-skilled workers improve both the speed and quality of their output while the most experienced and highest-skilled workers see small gains in speed and small declines in quality."* (QJE version: 15% / 5,172 agents; NBER WP: 14% / 5,179 — both correct to their version.) + +- **MANDATORY SCOPE CAVEAT:** population is **customer-support agents, NOT software developers.** "No software developers were studied." Strong *analogous/directional* counter-evidence to the general "seniors up, juniors out" thesis — not same-population proof about coding. +- **Design:** quasi-experimental staggered rollout (difference-in-differences, small RCT component), single Fortune 500 firm. +- Direction aligns with the developer-specific METR and Copilot findings (no directional contradiction). A Brookings follow-up ("Borrowed expertise") qualifies: AI disseminates senior expertise; gains may not persist long-run. + +**Sources:** nber.org/papers/w31161 · arxiv.org/pdf/2304.11771 · gsb.stanford.edu/faculty-research/publications/generative-ai-work · ssrn.com/abstract=4426942 · ideas.repec.org/a/oup/qjecon/v140y2025i2p889-942 + +--- + +## Finding 4 — GitHub Copilot RCT: 55.8% faster on a TOY task; novices benefit more (confidence: MEDIUM) + +**Claim:** A GitHub/Microsoft-authored RCT found less-experienced developers benefited more (also heavier-coding-load and age-25–44 devs) — reinforcing "novices gain most." Its large headline (**55.8% faster**) came from a single narrow toy task; the gulf vs. METR's −19% is largely task realism (standardized benchmark vs. real PRs on familiar codebases). + +**Evidence:** arXiv:2302.06590 (Peng, Kalliamvakou, Cihon, Demirer, 2023). Treated group "completed the task 55.8% faster" (95% CI 21–89%, p=0.0017; 71.17 vs 160.89 min) on a *toy* task (implement a JS HTTP server), n=70 analyzed (Upwork freelancers), NOT real collaborative development. + +- **Honest caveats:** the programming-EXPERIENCE coefficient — the centerpiece of "novices benefit more" — is NOT significant at 0.05 (p=0.0629); only hours/day and age-25–44 clear 0.05. Paper hedges "If this result persists…". Subgroups underpowered (~35/group); sample skews young, lower-income, India/Pakistan. Authors are Copilot's makers (COI — though this cuts toward credibility for an anti-hype "novices benefit more" result they had no incentive to manufacture). + +**Sources:** arxiv.org/pdf/2302.06590 (critique: blueoptima.com/post/debunking-githubs-claims…) + +--- + +## Finding 5 — DORA 2024: AI hurt team delivery stability/throughput (confidence: MEDIUM) + +**Claim:** DORA's 2024 research: AI adoption raised individual productivity/satisfaction but **negatively impacted software delivery stability and throughput** at the team level — individual speed gains did not translate to better team delivery. + +**Evidence:** Verbatim (dora.dev/research/2024): *"AI adoption significantly increases individual productivity, flow, and job satisfaction. However, it also negatively impacts software delivery stability and throughput."* Magnitudes (corroborated by RedMonk/InfoQ/GetDX): a 25% increase in AI adoption ≈ 1.5% throughput decrease, 7.2% stability reduction; mechanism = AI inflating batch/changeset size. Independent primary research (Google/DORA), not vendor marketing. + +- **Two mandatory caveats:** (1) observational/self-reported cross-sectional survey → CORRELATION not causation. (2) **PARTIALLY SUPERSEDED** — DORA's OWN 2025 report REVERSED the throughput finding (AI now positively correlates with throughput); the negative STABILITY relationship persisted. Only the stability half remains current. + +**Sources:** dora.dev/research/2024/dora-report + +--- + +## Finding 6 — Stack Overflow 2025: trust low and falling; debugging tax (confidence: HIGH, 3-0) + +**Claim:** SO 2025 Developer Survey (~49,000 respondents): developer trust in AI output accuracy is low and eroding, with a documented "debugging tax." Only **~3% "highly trust"** AI accuracy while **~46% actively distrust** (up from 31% in 2024; now exceeding the ~33% who trust), even as adoption climbed to 84%; **~45% report debugging AI-generated code is time-consuming.** + +**Evidence:** Verbatim (survey.stackoverflow.co/2025/ai, n=33,244 on trust; Dec 2025). Highly trust 3.1%, somewhat 29.6%, somewhat distrust 26.1%, highly distrust 19.6% → ~46% distrust vs 32.7% trust. *"Trust in the accuracy of AI has fallen from 40% in previous years to just 29% this year."* Press release: "Trust in AI at an All Time Low." Adoption rose to 84% (from 76%); 51% daily among pros. + +- **Caveats:** all self-reported perception/trust, not direct output-reliability measures. SO has mild business interest in AI skepticism. +- **⚠ Data-hygiene note (verification caught this):** two claims asserting "66% spend more time fixing almost-right AI code" were **REFUTED** — the 66% item measures *encountering* "almost right, but not quite" solutions; the cleanest "more time" figure is **45%**. Cite 45%, not 66%. Several secondary summaries conflate them. + +**Sources:** survey.stackoverflow.co/2025/ai · stackoverflow.co/company/press/archive/stack-overflow-2025-developer-survey · stackoverflow.blog/2025/12/29/… + +--- + +## Overall caveats (the adversarial source held to its own standard) + +- **TIME-SENSITIVITY (biggest limit):** every figure is tied to a fast-moving tool generation. METR's −19% is explicitly "historical"/early-2025 (Cursor Pro + Claude 3.5/3.7 Sonnet); the Copilot RCT uses 2022-era Copilot; DORA's 2024 throughput finding was reversed by DORA in 2025. None represents the live 2026 state of the art. +- **STATISTICAL POWER/SAMPLE:** METR n=16 (though significant across 246 tasks); its population is precisely the cohort least likely to gain, so it does NOT show AI slows juniors/greenfield/most devs (METR is explicit about these non-conclusions). Copilot heterogeneity subgroups underpowered; key experience coefficient not significant at 0.05. +- **SCOPE/DOMAIN MISMATCH:** the strongest skill-distribution result (Brynjolfsson, 34% novice gain) is customer-support agents, not developers — directional, not same-population proof. +- **DESIGN LADDER:** RCTs (METR, Copilot) > quasi-experiment (Brynjolfsson) > observational surveys (DORA, SO). "Zeroed cost" is undercut by inference, not a direct cost measurement. +- **SOURCE BIAS:** GitHub/Microsoft authored the pro-Copilot RCT (COI); SO has mild commercial interest in AI skepticism; DORA/Google is independent of the tool vendors. + +## Open questions + +1. Does METR's −19% persist/reverse with mid-2026 agentic tools? Its own Feb-2026 update hints at possible speedup but calls it "very weak evidence"; a properly powered follow-up RCT on current tools is the key missing piece. +2. Does "novices gain most" hold for REAL software work, or invert on complex/unfamiliar codebases where juniors lack judgment to catch AI errors (the mechanism behind experts' small quality declines)? +3. All findings measure task SPEED/productivity — the "seniors up/juniors out" thesis is about labor-market VALUE (wages, hiring, headcount), which no source here measures. Directional counter-evidence, not same-metric refutation. +4. Are AI's negative team-level effects (larger batches, debugging burden, low trust) a transient learning-curve cost or a durable tax? DORA's 2025 partial reversal suggests some are transitional; persistent stability decline and falling trust suggest others may not be. + +## Refuted during verification (recorded for honesty) + +- "66% report spending MORE time fixing almost-right AI code" (0-3 and 1-2) — conflates SO's 66% "encounter almost-right solutions" item with the 45% "debugging is time-consuming" item. Use 45%. diff --git a/raw/sources/Design The Perfect Offer in Under 10 Minutes.md b/raw/sources/Design The Perfect Offer in Under 10 Minutes.md new file mode 100644 index 0000000..1b5de62 --- /dev/null +++ b/raw/sources/Design The Perfect Offer in Under 10 Minutes.md @@ -0,0 +1,111 @@ +# Conclusions + +**Source:** https://www.youtube.com/watch?v=19QYlpGvcLo +**Title:** Design The Perfect Offer in Under 10 Minutes +**Duration:** 09:35 + +--- + +## Core thesis + +Stop selling "I do X for you" as an hourly-labor service — **productize the offer**: sell a specific *outcome* with your time invested behind it. A productized service lets you charge more, deliver on a repeatable methodology, and escape the sub-minimum-wage trap most service businesses fall into. + +The 10-minute exercise: pick a revenue target → do backwards math on price × clients → let the market tell you what to sell → let AI generate the offer deck/doc. + +--- + +## 1. Why generic "I do AI" businesses lose + +- Selling "Do you need AI? Yes. $1,000/mo, I do AI for you." forces every engagement into custom work. +- ~90% of service businesses operate this way — they get paid for time, not outcomes. +- If you net out real revenue per hour, most owners earn **less than minimum wage** — "could make more cash working at McDonald's". +- Fix: **productize** — same delivery, but framed and sold as a specific outcome with a repeatable method. + +## 2. Backwards math to a revenue target + +The speaker's rule-of-thumb pricing model, worked live against a $10K/mo target: + +| Step | Rule | Example | +|---|---|---| +| Price floor | Sell for ≥ $1,000/mo | Enough "meat on the bones" to reinvest in delivery | +| Why $1K works for AI/biz | One new client is worth ~$1K to the buyer | Worst case, they recoup the fee with a single client | +| Client math | Target ÷ price = clients needed | $10,000 ÷ $1,000 = **10 clients** | + +Under $100/mo there's no margin to fund the work that would make the service any good — pricing itself constrains quality. + +## 3. Finding the offer: hungry crowd beats best burger + +- Don't invent a novel service — **listen to what the market is already asking for**. +- Analogy: "Is it better to have the best burger in town, or be around a bunch of hungry people?" Hungry crowd wins every time. +- Fitness coaching example: the problem is never "there's too much fitness coaching already" — it's putting the *right offer* in front of the *right people*, framed in a way that sounds unique even if the underlying service isn't. + +Discovery step: talk to prospects, find the bottleneck, name it back to them as the offer. In this session: "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." + +## 4. Turn the bottleneck into a productized offer + +Reframe from service → outcome: + +| Weak (service framing) | Strong (productized outcome) | +|---|---| +| "I'll audit your calendar and set up some automations" | "I guarantee I'll buy back 10 hours of your time per week using AI, for $1,000/mo — every month." | + +10 hours/week × 4 = **40 hours/month** of the client's time returned, repeating monthly. That's a concrete, defensible, priceable outcome. + +## 5. The three-tier offer ladder (built live) + +The guest's ladder, refined on-camera: + +| Tier | Price | What it is | What the 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 per month | +| Top | **$5,000/mo** ("AI Ecosystem") | Full deployment | Rolled out across the business + team training + monthly call | + +Key structural advice from the coach: +- **Anchor on the core tier first** ($997), then design entry and top around it. Easier to move a prospect up or down from a defined middle than to build up from scratch. +- The AI-generated recommendation (workflow + dashboard + agent) matched the actual best-practice structure — the tool is a legitimate co-designer. + +## 6. Language rules for the sales conversation + +Small wording changes that materially change willingness-to-pay: + +| Never say | Say instead | Why | +|---|---|---| +| "3 hours per month **with me**" | "3 hours of training **with my team**" (or "me or my team") | Buyers don't want your time — they want the standard/method. If you promise you and don't show up, they're upset; if you promise your team and you show up, that's a bonus. | +| "I do AI for you" | "This is my specific methodology for [outcome]" | People buy **methodology**, not labor. That's what "productized" means. | + +Core principle: **"People don't buy your time. They buy your standards."** + +## 7. Ship two artifacts, not one + +Once the core offer exists, have AI generate both: + +| Artifact | Used for | +|---|---| +| **Pitch deck** | Walking a prospect through the offer on a sales call | +| **Offer doc** | Selling in chat, without a call | + +Rationale: **the market is fatigued by sales calls**. Educated buyers often already know more about what you sell than you do — forcing them onto a discovery call to buy is friction, not qualification. "You can literally make a million dollars a month over chat." + +## 8. Cross-cutting principles + +- **Sell outcomes, not deliverables** — nobody wants "a workflow, a dashboard, and an agent"; they want hours of their week back and their business running without them. +- **Backwards math first** — pick the revenue number, derive price × clients, then design the offer to fit. +- **Middle-out ladder design** — nail the core tier, then bracket it above and below. +- **Methodology is the moat** — a thousand people can do "the thing"; only you have *your way* of doing it. +- **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. + +## 9. Actionable checklist + +1. Write down your monthly revenue target. +2. Divide by $1,000 → that's your minimum client count. Adjust price up if the count feels unrealistic. +3. Ask 5–10 prospects in your niche: "what's your biggest bottleneck around [your domain]?" +4. Reframe the top answer as a **guaranteed, recurring outcome** priced at ≥$1K/mo — that's your core offer. +5. Build a 3-tier ladder around that core (entry ≈ 40–50% of core, top ≈ 5× core). +6. Have AI generate both a pitch deck *and* a text offer doc. +7. Scrub sales language of "with me" / "my time" — replace with "me or my team" / "methodology". +8. Default to selling in chat; only escalate to a call when the buyer asks. + +## Who this is for + +Solo operators or small agencies stuck in custom-hourly work — especially anyone selling AI, marketing, coaching, or consulting services — who want to move to a recurring $1K–$5K/mo productized model without inventing a new category. diff --git a/raw/sources/How to Get Rich So Fast It Feels Like CHEATING.md b/raw/sources/How to Get Rich So Fast It Feels Like CHEATING.md new file mode 100644 index 0000000..a452ff2 --- /dev/null +++ b/raw/sources/How to Get Rich So Fast It Feels Like CHEATING.md @@ -0,0 +1,72 @@ +# Conclusions + +**Source:** https://www.youtube.com/watch?v=KJSSvOY1UOk +**Title:** How to Get Rich So Fast It Feels Like CHEATING +**Duration:** 12:31 + +--- + +## Core thesis + +The fastest path to success is **shameless, total cloning** of someone who already won — not "inspiration", not "my own twist", but copying the entire system, including the boring parts. Almost nobody does it. The blocker is always ego, not information. + +## Why nobody clones (the two ego traps) + +1. **The originality trap.** From childhood, schools call copying "cheating". Adults inherit the belief that copied work is shameful. In reality, nearly every successful person started by copying — they just don't advertise it (e.g. Sam Walton walked into competitor stores with a notepad to copy shelf layouts and signage). +2. **Half-hearted cloning.** Even people who try to copy "dip a toe in for a week" and quit. Pabrai's rule: **10,000% or nothing.** Picking single ideas to try out is not cloning; it's tasting. + +The gas-station parable: two stations across the street, identical product. One wipes windshields and checks tires for free and is packed; the other watches it happen daily and refuses to copy it. The losing station goes bankrupt — not from lack of information, from ego. + +## The Pabrai → Buffett case study + +| Move | Detail | +|---|---| +| Trigger | Picked up *One Up on Wall Street* at Heathrow, read Buffett returned 31%/year for 40+ years (most investors don't clear 10%) | +| Decision | "Copy everything. Don't try to be smarter than Buffett. Don't add my own twist." | +| Execution | Read every letter Buffett wrote; watched every interview; attended the Berkshire annual meeting 20+ years in a row; copied morning routine, business structure, 5–6 hrs of daily reading, working alone | +| Outcome | ~$154M | +| Coda | In 2007 paid **$650,000** for a charity lunch with Buffett — framed it as *guru dakshina*, the Hindu gift to a teacher when education is complete | + +## Cloning ≠ becoming a mindless copycat + +Pabrai cloned from **multiple sources**: Buffett for investing, Munger for thinking, Graham for principles, philosophers for life decisions. By combining proven systems from several teachers, he ended up original — because **nobody else stacked those exact pieces the same way.** Originality is an emergent property of deep, multi-source cloning, not a starting condition. + +## The beginner mistake (food-channel story) + +A friend ran a short-form recipe channel — polished, well-edited, growing slowly. The top channel in her niche had: + +- No subtitles +- No music +- No on-screen recipe text +- ~30-second videos +- Topics already proven to perform in the niche + +She was doing the opposite of every single one, "to make it more useful" and "to be original". The lesson: + +> When a creator has millions of views, every choice they make — including what they *don't* do — is the result of testing. Beginners assume omissions are oversights. They're usually deliberate. + +She stopped, cloned the format exactly: **first video 100K views, next 500K.** Only after that did she start experimenting again. + +## The barber analogy + +Nobody walks into a barbershop on day one and says "I've never cut hair but I'll figure out my own way." You'd stand behind the best barber for weeks — watch the wrist, the grip, the head tilts, the small talk — copy everything, *then* experiment. People skip this exact step the moment they start a business or YouTube channel. + +## How to actually clone (practical) + +1. **Pick ONE.** Not five inspirations. The single best person/channel/business in your niche. Pabrai didn't sample five investors and average them — he went all-in on Buffett before branching. +2. **Go deep, not surface.** Don't summarize. Try to understand *how* they think and what principles drive each decision. Pabrai didn't watch one interview; he read every letter and went to meetings for 20+ years. +3. **Clone the boring parts.** Success is not one golden insight — it's ~1,000 small decisions stacked: morning routine, how distractions are handled, how time is protected. You can't pick only the exciting parts; you have to do the whole program, gym-style. +4. **Adjust only after.** Once your hands understand the craft, then experiment — never before. + +## Cross-cutting principles + +- **Ego is the cost of not cloning.** Every "I want to do it my way" before mastery is an unpaid tuition bill. +- **Letter of the rules > spirit of the rules — at the start.** Spirit-of-the-rules thinking is for masters; beginners use it to justify skipping discipline. +- **Originality is downstream of cloning, not upstream of it.** +- **Information is rarely the bottleneck.** The winning formula is usually visible across the street. The blocker is the willingness to use it. + +## Who this is for + +- Anyone building a side business, YouTube channel, or new skill where "I tried for months and nothing worked" — the diagnostic question is *"Am I copying what already works, or trying to be original before I've mastered the basics?"* +- New investors who waste years trying to outsmart proven systems. +- Anyone who feels embarrassed about following a template — the embarrassment is the tax you're paying for slow growth. diff --git a/raw/sources/How to get more clients as a software development agency.md b/raw/sources/How to get more clients as a software development agency.md new file mode 100644 index 0000000..6dc3552 --- /dev/null +++ b/raw/sources/How to get more clients as a software development agency.md @@ -0,0 +1,86 @@ +# Conclusions + +**Source:** https://www.youtube.com/watch?v=sqSg0cM9xzE +**Title:** How to get more clients as a software development agency? +**Duration:** 5:20 +**Speaker:** Tony + +--- + +## Core thesis + +Software dev shops live in a feast-or-famine cycle: deliver a custom project → scramble for the next client → repeat. Three steps break that cycle and turn client acquisition into a predictable engine: **(1) niche down so you can do outbound at all, (2) run a deliberate outbound motion, (3) back it with a social-media presence that builds trust.** + +--- + +## Step 1 — Niche down (the precondition for everything else) + +Without a clear target audience, outbound is inefficient and projects stay one-off custom builds. + +| Generalist dev shop | Niched dev shop | +|---|---| +| No clear target → can't outbound | Clear ICP → outbound is crisp, can be outsourced to a VA | +| Every project custom → long delivery, troubleshooting, lower margins | Same problem repeated → productize delivery, faster turnaround | +| Sales cycle breaks every project | Pipeline runs on autopilot | +| Growth = stress about the next deal | Predictability enables team growth | + +**How to find the niche:** +1. Look back at your most profitable clients — is there a pattern in problem solved, industry, or software type? Double down on it. +2. Run experiments across target audiences and messaging; keep what gets responses. +3. Once chosen, actively target those people — but don't reject other paying work while the niche ramps. Bills first. + +## Step 2 — Outbound strategies + +Pick a posture that matches your audience. Both work; mixing is fine. + +| Approach | Examples | When it fits | +|---|---|---| +| High-touch, low-volume | Podcast inviting CXOs, exclusive roundtables, lunches | Local or executive audiences; few, high-value targets | +| High-volume, low-touch | LinkedIn conversational prospecting, cold email | Larger ICP; you can produce personalization at scale | + +**Sweeping rule:** Software development is a **high-trust, high-relationship** business. Even high-volume outbound has to feel personalized and relationship-building, or it doesn't convert. + +## Step 3 — Social-media presence (the trust layer) + +Outbound alone is fragile: vacation, illness, anything that stops sends also stops the pipeline. Social presence keeps you in prospects' minds and warms up everyone your outbound touches. + +- **Platform:** LinkedIn for most dev shops (B2B audience concentration). Instagram is the second option. +- **Cadence:** 3 posts/week on LinkedIn is enough to move the needle. +- **What it actually does:** Posts rarely generate direct leads. They **grease the wheels** of outbound — the difference between a profile with no activity and one posting regularly is, per Tony, sometimes the difference between signing the deal and not signing it. + +--- + +## Three mistakes that kill dev-shop sales + +| # | Mistake | Why it backfires | Do this instead | +|---|---|---|---| +| 1 | Marketing the tech stack ("excellent .NET developer") | Buyers don't know what the stack means | Target the audience the stack implies (e.g., .NET → Microsoft-environment buyers) | +| 2 | "We do everything for everybody" | Alienates the niche, fails to convince the actual prospect in front of you | Pick a problem and a buyer; say no to the rest in messaging | +| 3 | Using price as an incentive (undercutting) | Devalues your service permanently — clients keep pushing until you can't serve them; fastest path to bankruptcy | Compete on outcomes, fit, and trust — not price | + +--- + +## Cross-cutting principles + +- **Niche is upstream of everything.** Outbound efficiency, delivery speed, margins, and the ability to outsource sales work all flow from having a clear ICP. +- **Productization follows niche.** Same problem repeatedly → process, templates, faster delivery, more clients in parallel. +- **Trust > volume.** Even at high volume, every touch must feel personal. +- **Social + outbound > either alone.** Posts make cold messages convert; cold messages give posts an audience. + +--- + +## Actionable takeaways + +For a dev-shop owner watching this: + +1. **Today:** Pull your last 12-24 months of clients, sort by profit. Look for a repeating problem/industry/software-type pattern. Write down the niche hypothesis. +2. **This week:** Pick one outbound posture (high-touch or high-volume) that matches your ICP. Define the channel (LinkedIn DMs, cold email, podcast invites, …) and the offer. +3. **This week:** Audit your LinkedIn profile and start a 3x/week posting cadence aimed at your niche. Stop posting about your stack; post about your buyer's problems. +4. **Audit messaging for the three mistakes:** stack-talk, "we do everything," price-as-hook. Rewrite the website and outbound copy accordingly. +5. **Next:** Tony's follow-up video covers pricing strategy — explicitly flagged as the lever that can wipe out profits even with a full pipeline. + +--- + +## Who this is for + +Owner-operators of small/medium custom software dev agencies stuck in the feast/famine loop, especially those who haven't yet niched and rely on referrals + sporadic outbound. Not aimed at product companies or freelancers. diff --git a/raw/sources/Information Is Free, Implementation Is Paid.md b/raw/sources/Information Is Free, Implementation Is Paid.md new file mode 100644 index 0000000..02f3e30 --- /dev/null +++ b/raw/sources/Information Is Free, Implementation Is Paid.md @@ -0,0 +1,114 @@ +# Conclusions + +**Source:** https://www.youtube.com/watch?v=knrSj8t2L9U +**Title:** Information Is Free, Implementation Is Paid +**Duration:** 8:45 + +--- + +## Core thesis + +**Give away everything you know for free. Charge for implementation and sequencing.** + +The best marketing content a service business can create is *exactly what they do in-house for paying clients* — the internal playbooks, the step-by-step how-to. The trick is that giving away the *know-how* does not remove demand for the *how* (i.e., the sequenced, done-with-you or done-for-you delivery). Done right, it *creates* demand and makes your paid offer feel cheap by comparison. + +--- + +## The content-idea factory (the "5 × 10 × 4 = 200" formula) + +A repeatable system for never running out of expert-sounding short-form content: + +| Layer | Count | What it is | +|---|---|---| +| **Hot buttons** | 5 | Big pain areas your ideal customer feels (e.g. "AI agents") | +| **Nuanced pains per hot button** | 10 | Specific, observable problems inside each hot button | +| **Total pain-point ideas** | **50** | 5 × 10 — enough for **50 days** of content, then loop | +| **Content formats per idea** | 4 | e.g. clone, talking head, green screen, etc. | +| **Total pieces of content** | **200** | 50 × 4 — nearly a full year, near-daily | + +### How to generate the 10 nuanced pains (AI prompt template) + +Ask the AI (verbatim structure from the video): + +> *"Make a list of 10 nuanced but observable problems business owners who are between $500,000 and $2 million in revenue have around [HOT BUTTON]."* + +Why this works: the modifiers do the heavy lifting. + +- **"nuanced but observable"** → forces specifics, not clichés +- **"business owners between $500K and $2M"** → anchors to your ICP so the pains sound like *their* world +- **"around [hot button]"** → keeps the output scoped + +Example outputs the AI produced live in the video (around "AI agents"): + +- *"They have AI tabs open and personal subscriptions but zero AI doing recurring workflows."* +- *"They bought the automation and built a co-pilot that added work."* +- *"Every agent still runs through them — they're the bottleneck."* + +These are the difference-makers: they describe the viewer's world **better than they can describe it themselves** → you sound like an expert on sight. + +--- + +## The pain → solution content structure + +Every piece of content follows the same 1-2 punch: + +1. **Open on the nuanced pain** — "Do you have a bunch of AI tabs open but nothing's actually automating your business?" → viewer thinks *"how do you know?"* +2. **Teach them how to not do that** — give the actual solution. + +Do this across all 50 pains and every video reinforces expert status. + +--- + +## The scramble trick (the whole reason this works) + +**Problem:** If you post your 10 videos on AI agents *in order*, viewers watch them back-to-back and think "cool, I can just do this myself" — no reason to hire you. + +**Solution:** Scramble the order across hot buttons. + +- Don't post: A1, A2, A3 … A10, then B1, B2 … +- Instead post: **A1, B1, C1, D1, E1, A2, B2, C2 …** + +Each individual video still teaches something valuable — so you look like an expert on every swipe — but the **sequence** the viewer would need to actually implement the whole system is missing. + +> *"You could literally create a course on how to do everything from point A to point Z, put the videos on YouTube in a completely out-of-whack order, and people would still pay you for the same content put in the right order."* + +**What you demonstrate:** know-how. +**What you withhold:** the how (sequencing + implementation). + +--- + +## Why this doesn't cannibalize sales — it creates them + +The instinct is "if I give away my best stuff, no one will buy." The video argues the opposite mechanism: + +| Instinct | Reality (per speaker) | +|---|---| +| Give away best stuff → lose demand | Give away best stuff → *increase* demand | +| Hold best stuff in-house → look valuable | Hold best stuff in-house → nobody knows you have it | +| Scrambled free content = leaks | Scrambled free content = proof of expertise without a shortcut around you | +| A high price feels expensive | A $997 offer feels **cheap** after the viewer has seen 50 free expert videos | + +**The line:** +> *"Information is free. People pay for implementation and sequencing. That's why they pay you."* + +--- + +## Actionable takeaways + +For a service business owner / consultant / agency: + +1. **List your 5 hot buttons.** The big pain areas your ICP feels. +2. **For each, generate 10 nuanced pains** using the AI prompt above with your ICP's revenue band and the hot button plugged in. +3. **Pick 4 formats** you're willing to shoot in (clone, talking head, green screen, one more). +4. **Batch content in pain→solution pairs** — never open on a solution, always open on the observable pain. +5. **Publish in scrambled order** across hot buttons, not sequentially within one. +6. **Rotate at day 51** — start again from pain #1 in a fresh format. +7. **Stop hoarding your internal playbook.** If you have a 27-step doc for building the perfect AI agent, splinter each step into its own piece of free content — out of order. + +--- + +## Who this is for + +- Service-business owners who "hold their best stuff in-house" and can't figure out why content isn't converting. +- Coaches / consultants / agency operators worried that teaching = losing clients. +- Anyone trying to feed a daily short-form content calendar without running out of ideas by week 2. diff --git a/raw/sources/Linked In mail template.md b/raw/sources/Linked In mail template.md new file mode 100644 index 0000000..dc53001 --- /dev/null +++ b/raw/sources/Linked In mail template.md @@ -0,0 +1,9 @@ +Hi [Name], + +Saw your post about [specific detail]. [Thoughtful comment about it]. + +I help [target audience] with [specific problem]. Just helped [similar company] achieve [specific result]. + +If I could help you do the same, would you be open to a brief chat? + +[Your name] \ No newline at end of file diff --git a/raw/sources/Make My First $100K in Month.md b/raw/sources/Make My First $100K in Month.md new file mode 100644 index 0000000..808f65a --- /dev/null +++ b/raw/sources/Make My First $100K in Month.md @@ -0,0 +1,223 @@ +# Conclusions + +**Source:** https://www.youtube.com/watch?v=xj5gZq159lM +**Title:** If I Wanted to Make My First $100K/Month, I'd Do This +**Duration:** 22:54 +**Speaker:** Dan Martell (built and sold 3 multi-million-dollar companies; coaches business owners) + +--- + +## Core thesis + +Going from $0 to $100K/month is not a grinding problem — it is a **sequence** problem. Follow a five-step blueprint: (1) do the money math to pick a price, (2) design a productized service, (3) build a three-tier offer, (4) generate demand with inbound + outbound in parallel, (5) close by chat or call. Do the marketing **before** you build the thing. + +--- + +## Step 1 — The money map: pick your price × customer count + +Five ways to reach $100K/month. Only the middle option is sane: + +| Model | Customers | Price | Verdict | +|---|---|---|---| +| Whale | 1 | $100,000 | Concentration risk, requires elite skills | +| **Enterprise-lite** | **10** | **$10,000** | Dan personally dislikes it — still heavy per-deal | +| **Sweet spot** | **~100** | **~$1,000/mo** | **Recommended starting point** | +| Prosumer | 1,000 | $100 | Too many conversations to close | +| Mass-market | 10,000 | $10 | Impossibly wide reach for a new founder | + +**Rule of thumb:** minimum offer size = **$1,000/month**, staying **below $10K/month**. Every conversation should be worth having. + +--- + +## Step 2 — What to sell: the three buyer motivations + Ikigai + +People pay for exactly three things: + +1. **Time** — buy back my hours → unlimited capital available +2. **Money** — the easiest thing to sell (that's why sales training is easy: pay money → get more money) +3. **Status** — luxury brands, front-row seats, cars, watches, associations — routinely ignored, hugely underpriced + +**Pro tip:** at $1K+/month, sell to **business owners** (especially small business owners) — all three motivations matter to them and they decide fast. + +**Ikigai filter** for what you offer: + +- What do you **love**? (if you don't, you'll quit) +- What are you **good at**? — reframe as "what do people tell me I'm good at" (we discount our own skills) +- What does the **world need**? — look at search trends, what's discussed online +- What will they **pay for**? — nice-to-haves die; must-haves get bought + +Sweet spot = all four overlap. + +**Service vs. product — the productized-service play:** + +| Format | Problem | Verdict | +|---|---|---| +| Custom services | Selling hours, no leverage | Avoid | +| Products (apps, SaaS, courses) | Expensive, slow, risky to build | Avoid at start | +| **Productized service** | Fixed package, repeatable steps 1-2-3, price like a product | **Start here — customer-cash funds the eventual product** | + +--- + +## Step 3 — Build the offer + +**Sell the outcome, not the work.** Don't say "I do marketing for $1K/month" — say "I'll get you 10 new clients a month." Features tell; outcomes sell. + +**Three-tier pricing (decoy structure):** + +| Tier | Price (relative to core) | Delivery | Purpose | +|---|---|---|---| +| Low — DIY | ½× ($500/mo) | Give them the playbooks, they execute | Anchors low end | +| **Core** | **1× ($1,000/mo)** | **Productized service — you do it** | **Sell this one — 100× per month = $100K** | +| High — Done-for-you | 10× ($10,000/mo) | Everything managed, includes training their team | Decoy; makes core look like a steal | + +Both flanking tiers are **decoys** — they exist so the middle tier prints. + +**Every offer must contain:** + +- **Outcome** — the business improvement they get +- **Deliverable** — what shows up weekly/monthly +- **Investment** — the price (called "investment", not "cost") +- **Risk reversal** — a specific guarantee ("10 leads/month", "save 10 hours/week") +- **Urgency** — "only 5 slots this month, 20 calls this week, lock it in with a $1K deposit" + +**AI prompt to draft it:** feed your Ikigai answers + time/money/status + the target buyer, then ask AI to write "the offer with all elements above, plus a premium and entry-level tier that make my core offer look like an absolute steal, output as an offer doc I can send as a link **and** a pitch deck for sales calls. Then ask me any question you need to get total clarity." — that last line is "reverse prompting." + +**Offer doc vs. pitch deck:** + +| Artifact | Job | +|---|---| +| Offer doc | Copywritten — sells on its own via reading | +| Pitch deck | High-level bullets — you speak the words during the call | + +**Do NOT email the pitch deck** to a prospect for "team review." They will forward it to their friend Bob and hire Bob with your plan. + +--- + +## Step 4 — Create demand (inbound + outbound in parallel) + +Nobody is waiting for you. Two engines, run both. + +### Inbound (long-term) + +Give away everything. Take every deliverable in your offer doc, feed each to AI with this prompt: + +> "Give me 10 **nuanced and observable** problems your customer [HVAC owners / SMBs / etc.] has around each of these pains." + +That yields an infinite content backlog. Create hook-first content that solves those specific, observable problems. **"If I can describe my customer's pain better than they can, I'm the expert."** + +What do you still get paid for if you give everything away? — The **sequence of implementation**. Step 1 (audit) → Step 100 (fully automated). In content, you *scramble* the steps (A1, B2, C1…); the ordered checklist is what customers pay to have executed. + +Personal example: Dan's second company **Flowtown** got 350K unique visitors → 50K customers off blog content. His first company (Maritime Vacation) failed because he built product first, marketed later. → **Crickets.** + +### Outbound (short-term) + +Order of operations: + +1. **Mine your phone** — count contacts; usually 100-200, sometimes 20K +2. **Ask past the person** — "Do you know anyone with this problem?" → often answers "yeah, me"; otherwise gets you warm intros +3. **Use referral names** — "Bob suggested I reach out — I do X for people like you, is that a problem?" +4. **AI backfill** — "Build me a list of 100 people who need my service, with phone + email" +5. **Tools** — SocialSweep (mentioned) auto-extracts contacts from email history + +**Build a funnel:** outbound → follow-up → ask → close. Track it in a spreadsheet. + +--- + +## Step 5 — Close the deal + +Two channels only: **sell by chat** or **cold call**. Sell by chat is easier to start. + +### Sell by chat (Dan has done 8-figures this way) + +The DM flow: + +1. Every new follower gets a message: *"Are you here for [content] or [help growing your business]?"* +2. End with the second option — that primes the yes +3. Ask **pain-awareness questions** +4. Present the solution +5. Send the **offer doc link** +6. If interested → send **Stripe payment link** + +### Cold call + +Real transcript from the video (paraphrased): + +> "Hi, David — quick question. Have you looked into using AI to answer your calls so you can book appointments while working on jobs? I've got nothing to sell, just curious." +> "Not yet — been busy." +> "Most folks in your space aren't answering calls anymore because AI does it for them and makes more money. If I could show you how, would that interest you?" +> "Yeah, 15 minutes." +> "Tomorrow at [time]? I'll send a Zoom link and demo the software live." + +**Rule:** the cold call's job is **not** to sell. It is to qualify + book a meeting from a meeting. + +### Objections vs. obstacles + +- **Obstacles** = concerns raised **before** you present the offer +- **Objections** = concerns raised **after** + +Rule: **surface objections up-front so they become obstacles.** ("Do you have a budget to solve this?") If they surface after the offer, you're playing defense. + +### Volume + persistence rules + +- **First 5 calls are throwaways** — don't judge yourself on them +- **If they don't answer, call right back within 30 seconds** — most phones ring through on the second call because "urgent" +- **Feed transcripts to AI** — it will show you where you're stumbling +- **Goal: 100 no's per day** — this level of rejection buys the yes +- **Do not spend money** (equipment, software, tools) until customers have paid. Offer starts 2 weeks out; use that gap to prep delivery. + +--- + +## Step 6 — Only *then* build the thing + +You've done marketing → chats/calls → paying customers. Now build. + +**Pre-sell + waitlist mechanic** (Dan's playbook for every product launch): + +1. Ship a landing page with a waitlist — before writing a line of code +2. Market the waitlist; take signups +3. Offer a **$50 "top of the waitlist" spot** — a paid signal that they actually want it solved your way +4. If money doesn't come in → no proof of demand → don't build +5. If it does → you have both **validated demand** and **build capital** + +AI now makes the landing page + waitlist + payment collection buildable with no coding. + +--- + +## Cross-cutting principles + +- **Sequence, not effort.** Every failure Dan describes is doing the right steps in the wrong order (build before marketing, custom before productized, calls before scripts). +- **Sell outcomes; deliver services; monetize the sequence.** The value is in *knowing the order*, not the individual steps. +- **Productize > custom.** Same three steps every time = leverage. +- **Give the information, sell the implementation.** Content is not what you're paid for — it's what earns the right to be paid. +- **Marketing before manufacturing.** Waitlist + pre-sell every time. +- **Decoys sell the core.** Never launch with only one price. +- **Volume beats polish early.** 100 no's/day > perfect script. +- **Two engines, always in parallel.** Inbound (long tail) + outbound (this week's cash). + +--- + +## Actionable checklist + +- [ ] Set a price at **$1,000/month** (or higher, below $10K) and target **100 customers** +- [ ] Fill in the four Ikigai quadrants; find the intersection +- [ ] Identify which of **time / money / status** you're selling and to which buyer +- [ ] Package your service into a **repeatable 3-step productized offer** +- [ ] Draft the **offer doc + pitch deck** with AI, using the "outcome / deliverable / investment / risk reversal / urgency" template +- [ ] Add **$500 DIY** and **$10K done-for-you** decoy tiers +- [ ] For each deliverable, generate **10 observable customer pains** via AI → convert each to hook-driven content +- [ ] Mine your phone contacts, run **"ask past the person"**, AI-build a fallback list of 100 prospects +- [ ] Set up a simple **spreadsheet funnel** (outreach → follow-up → ask → close) +- [ ] Write your **DM flow** for sell-by-chat + your **15-second cold-call opener** +- [ ] Surface likely objections up-front; script them as pre-emptive questions +- [ ] Commit to **100 no's/day**; first 5 calls are throwaways; call back within 30 seconds +- [ ] Collect payment via **Stripe** link at close; **don't spend a dollar until customers have paid** +- [ ] For any product build: launch a **paid waitlist** first ($50 = proof); build only after validation + +--- + +## Who this is for + +- Aspiring founders at $0 who want a concrete playbook rather than motivation +- Existing service providers stuck on hourly/custom work who want to productize +- SMB-focused agencies, AI-automation builders, consultants, coaches — the offered example (AI voice agent for local businesses) fits this profile +- Anyone who already has some revenue and wants a repeatable process to scale to $100K/month or beyond diff --git a/raw/sources/Referrals Will Sink Your Business.md b/raw/sources/Referrals Will Sink Your Business.md new file mode 100644 index 0000000..fe2b691 --- /dev/null +++ b/raw/sources/Referrals Will Sink Your Business.md @@ -0,0 +1,116 @@ +# Conclusions — Referrals Will Sink Your Business + +**Source:** https://www.youtube.com/watch?v=50CTmoSuCYE +**Title:** Referrals Will Sink Your Business +**Duration:** 6:47 +**Speaker:** Dan Martell (coaching a founder stuck at ~$1.5M revenue) + +--- + +## The main thesis + +**Growing a business only on referrals is a failed primary strategy.** It feels good ("look at us, all word-of-mouth!") but it's evidence you skipped the real work: building a marketing system where **money in at the top produces more money out at the bottom**. Founders who did that work are hitting the same revenue in ~18 months that the referral-only founder took years to reach — and, unlike him, they can keep going. + +The ceiling ("I can't grow past $1.5M") is not a market problem. It's a missing system. + +--- + +## The only three ways to grow (pick one, own it) + +There are exactly three levers to get more people aware of your business: + +| Lever | What it is | Note | +|---|---|---| +| **Publish content** | Organic reels, lives, shorts, posts | Cheapest to start, hardest skill to build | +| **Paid ads** | Meta / Google / etc. | See below — the best paid ads *are* organic content | +| **Partnerships** | Get in front of other people's audiences | Requires relationships and reciprocity | + +All three cost something. All three are different skills. You pick the one you're most compelled to do — but you actually do it. + +--- + +## Why start with organic content (even if the goal is paid) + +> "The new paid is organic." + +- The best-performing ads on Meta right now **look like content**, not like ads. +- The platform *wants* content-shaped ads. +- Most founders never build the **creative pipeline** required to feed paid ads at volume — because they aren't content creators yet. +- Rule: take an organic post that already worked → run *that* as an ad. Skip this step and paid ads burn cash. + +So: 90 days on organic content isn't a detour from paid — it's the prerequisite. + +--- + +## The 90-day organic sprint — what "attack it" means + +- **Volume** — daily output, not weekly. +- **Experimentation** — new hooks, new formats, new angles. +- **Intensity** — treat it like a job, not a side task. +- **Feedback loops** — read the response, adjust. +- **New shots, new creative, new ideas** — keep firing. + +Concrete cadence Dan runs himself: + +- **Go live every day.** Why? To *practice*. (He repeats "go live every day, why? you got to practice" three times — that's the whole answer.) +- **Two reels a day.** No gear. Just a phone. Talk into it. Publish to Facebook, Instagram, YouTube Shorts. +- Learn to **answer questions**, **add value**, and — most importantly — **explain what you do**. + +--- + +## The technical-founder trap + +> "You and I are the same guy — software people, systems thinkers. 'Give me your problem and I'll go.' You don't want to explain, you just want to do it." + +- Technical founders are great at **solving** problems for customers. +- Technical founders are terrible at **explaining** how they solve those problems. +- **Communication and explanation is the big unlock.** Once that's in place, paid ads become "so amazing" — because you now have something to say and know how to say it. + +--- + +## The mindset shift: measure reps, not views + +| 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 which piece of content goes viral. The **only** thing you control is the **volume of reps** you do so that eventually something hits. + +> "Most of you get bored with your marketing before the market ever does — and you just stop." + +### Two viral proof points he cites + +- **Tones and I — "Dance Monkey"**: busker outside a closed store in Byron Bay. One recording. Billion+ streams. One song made her. +- **Oliver Anthony — "Rich Man North of Richmond"**: broke, got sober, sang in a backyard, someone filmed on a crappy phone. Went viral. Now a touring multi-millionaire. + +The lesson isn't "get lucky." It's: **everyone is one creative project away from being a superstar** — but only if you're still shipping when it lands. + +--- + +## The 6-month math + +| Month | What happens | +|---|---| +| 0–3 | 90-day attack on organic publishing. Skill building, no marketing system yet. | +| 3–6 | Another 90 days. Now the pipeline exists. | +| 6+ | **Beginning of a marketing system** — leads start flowing. | +| 6–18 | $1.5M business becomes $10M "no problem." | + +--- + +## Actionable takeaways (if this is you) + +1. **Stop being proud of "we grew on referrals."** It's a warning sign, not a badge. +2. **Pick one lever** — content, paid, or partnerships — and commit for 90 days. Don't dabble in all three. +3. If you pick content (the recommended start): **go live daily + 2 reels/day, on a phone**. No gear, no excuses. +4. **Track reps and improvement**, not views. Views are lagging output; reps are the leading input. +5. **Practice explaining what you do** as a first-class skill. If you can't explain it, you can't scale it. +6. Assume it takes **6 months** before the system produces leads. Budget the patience up front so you don't quit at day 60. +7. When an organic piece works, **turn it into a paid ad**. That's your bridge from organic to paid. + +--- + +## The one line to remember + +> "You don't decide what you create that's gonna go viral. The only thing you control is the volume of the reps." diff --git a/raw/sources/Start a business with Claude Code.md b/raw/sources/Start a business with Claude Code.md new file mode 100644 index 0000000..c923d55 --- /dev/null +++ b/raw/sources/Start a business with Claude Code.md @@ -0,0 +1,50 @@ +# Conclusions + +**Source:** https://youtube.com/shorts/JpLgVf8Alys +**Title:** Stop pretending not to know how to start a business with Claude Code +**Duration:** 0:42 + +--- + +## Core thesis + +**Sell first, build second.** If you want to go from $0 → $1M with AI, use Claude Code to fake a real business first, close paying customers via cold outbound, and only *then* have Claude build the actual product. The bottleneck isn't skill or code — it's willingness to start. + +--- + +## The 5-step "$0 → $1M" playbook + +| # | Step | Tool doing the work | +|---|---|---| +| 1 | Pick a service to sell (video editing, AI automation — anything) | You | +| 2 | Have Claude Code build a landing page, invent a company name, wire up a waitlist | Claude Code | +| 3 | Have Claude Code scrape the web for prospects' contact info | Claude Code | +| 4 | Have Claude Code write a cold-outbound sales script for that ICP | Claude Code | +| 5 | Email / call, book the meeting, close the sale — **then** ask Claude to actually build the product | You + Claude Code | + +Order matters: demand is validated (money on the table) *before* engineering effort is spent. + +--- + +## The point most people miss + +- Step 5 (**"ask it to build it for you"**) is the one everyone underestimates. +- Whatever business you want to be in, Claude will also **tell you how to do it** — you don't need pre-existing deep expertise. +- The blocker is psychological, not technical: *"Stop pretending not to know."* + +--- + +## Underlying principles + +1. **Sales precedes product.** A signed customer is cheaper validation than a built MVP. +2. **AI collapses the "I don't know how" excuse.** Domain knowledge is now on-demand. +3. **Distribution is the moat, not code.** Landing page + outbound = go-to-market; the product is the last step. +4. **Bias to action.** The gap between "aspiring founder" and "founder" is one cold email away. + +--- + +## Who this is for + +- Aspiring solo founders sitting on ideas without acting. +- Developers who over-invest in building and under-invest in selling. +- Anyone using "I don't have experience in that industry" as a reason not to start. diff --git a/raw/sources/Stop Cold Calling, Do This Instead.md b/raw/sources/Stop Cold Calling, Do This Instead.md new file mode 100644 index 0000000..3c1673d --- /dev/null +++ b/raw/sources/Stop Cold Calling, Do This Instead.md @@ -0,0 +1,85 @@ +# Conclusions + +**Source:** https://www.youtube.com/watch?v=wk5MpA2ckTI +**Title:** Stop Cold Calling, Do This Instead +**Speaker:** Dan Martell +**Duration:** 4:38 + +--- + +## Core thesis + +Every business either has a **repeatable pipeline** (attention → conversion → customer) or it stops growing. There are only **three ways** to build one — and most founders should stop cold-calling and lean into **partnerships** instead, because it is the fastest and gives you *borrowed credibility*. + +--- + +## The only three pipeline sources + +| # | Channel | What it is | Examples | +|---|---|---|---| +| 1 | **Publish** | You create content that pulls attention in | Social content, PR, a book | +| 2 | **Paid** | You interrupt people where they already are | Meta ads, billboards, stadium sponsorships | +| 3 | **Partners** | Someone with credibility walks you into their customer base | System integrators, referral partners, alliances | + +Rule: **pick one and go all in.** Trying all three at once is why most founders never build a real pipeline. + +--- + +## Why partnerships beat cold outbound (especially in enterprise) + +- Enterprise sales without a partner is brutal — "you might as well go run an ultra marathon." Dan spent four years in a suit-and-tie at age 24 selling to Fortune 2000 companies and got PTSD from it (why he now refuses to wear button-up shirts). +- Procurement, getting the meeting, getting the deal signed *before someone gets fired or the board reshuffles* — the friction is enormous. +- A single partner walked him into **7 pharmaceutical companies in New Jersey** (Novartis, Johnson & Johnson, etc.) in one shot. +- Partners give you **borrowed credibility** — the buyer is already pre-sold because someone they trust brought you in. + +## The economics of the play + +- Dan signed **$95K contracts** three weeks after being introduced. +- The **partner (system integrator)** had a **multi-million-dollar contract** with the same account. +- Both sides win — that's why the partner keeps introducing you. + +--- + +## The insight: turn one lucky partner into a system + +The mistake most founders make: they treat partners as **one-off relationships** instead of reverse-engineering the pattern. + +Dan's move: he became a **"professional recruiter of system integrators"** — targeting firms like Tata Consulting and IBM Global Services. + +### Reverse-engineering questions to ask about any partner that works + +1. Where did we actually meet? (e.g. LinkedIn) +2. What was true about them — role, company type, buyer profile? +3. **How many more people like them exist** on that same channel? +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**? + +Answer those and you have a repeatable partnership pipeline — not a lucky introduction. + +--- + +## How Dan built the machine (playbook) + +1. Identify who *inside the partner org* makes the "who do we bring in" decision. +2. Go to the **events they attend** — not the events your peers attend. +3. Introduce yourself and win the individual over first. +4. Let the partner bring you into their accounts. +5. Deliver — the partner keeps recycling you into more deals. +6. Systematize: content, offer, and story all engineered to attract more of that same partner archetype. + +--- + +## Takeaways for founders + +- If you can't describe your pipeline in one sentence, you don't have one — you have hope. +- Cold outbound into enterprise is the hardest path. A partner shortcuts months of procurement pain. +- Don't optimize the *deal*; optimize the *partner acquisition system*. +- Ten good partners can replace an outbound sales team. +- Whatever pipeline channel you pick — publish, paid, or partner — commit fully. Half-effort across three channels beats no channel. + +--- + +## Who this is for + +Founders selling into mid-market or enterprise, agencies, B2B service businesses, and anyone whose deal size justifies a relationship-driven motion (typically $10K+ ACV). Not directly applicable to low-ticket DTC. diff --git a/raw/sources/Your Company Can't Outgrow Your Team.md b/raw/sources/Your Company Can't Outgrow Your Team.md new file mode 100644 index 0000000..9afb9c7 --- /dev/null +++ b/raw/sources/Your Company Can't Outgrow Your Team.md @@ -0,0 +1,107 @@ +# Conclusions + +**Source:** https://www.youtube.com/watch?v=wE3TwzH-XCE +**Title:** Your Company Can't Outgrow Your Team +**Duration:** 4:35 + +--- + +## Core thesis + +**A company can only grow as fast as its people.** If the business is targeting 100% growth, every person on the team has to grow ~100% too — otherwise the company hits a ceiling made of humans, not markets. Leadership's job is to make that expectation explicit, make each person's performance visible, and hold the line against tolerance drift. + +> *"Good got you on the team. Great keeps you on the team, because 100% requires greatness."* + +--- + +## The "Business Athlete" framework + +The speaker teaches a **philosophy**, not a task list, so that people who want to climb have a model to climb toward. It's the difference between operational management (what to do) and leadership training (how you show up for the work). + +Two of the seven athlete practices called out: + +| Practice | What it means | +|---|---| +| **Have a coach** | *"I'm not your coach."* Team members must own their own development — books they read for their industry, external coaches, deliberate learning. | +| **Have a practice schedule** | *"We practice until we can't get it wrong. We don't practice to get it right."* Repetition to the point of unconscious competence, not to first success. | + +The other five aren't named in this clip, but the pattern is clear: they're behaviors, not skills. + +--- + +## Making performance public + +Everyone's numbers/status are posted where the whole team can see them. + +- Each person has their name and their standing on display. +- *"They know where they sit."* +- **Praise in public, criticize in private** — the 1-on-1 is where hard conversations happen, not the wall. + +Publicness creates self-driven accountability without the manager having to constantly enforce it. + +--- + +## The Keeper Test (borrowed from Netflix) + +The single question every leader should ask about every team member: + +> *"If this person came to me tomorrow and said they had an offer for 30% more money, would I fight to keep them?"* + +- **Yes** → they belong on the team. +- **No** → they shouldn't be on the team. Have the conversation. Turn it into a **development plan**: here's where you are, here's what I'm not seeing, here's why — grounded in the Business Athlete framework. + +The point isn't to fire people quickly; it's to force honesty. Silent tolerance of "no" answers is what rots a team. + +--- + +## "Shining a light" — using bright spots as leadership content + +Instead of top-down lectures, the speaker grabs a team member who thinks about their work differently and asks them to teach the rest: + +- Age, tenure, seniority don't matter — a rising star gets the spotlight. +- Others hear a peer articulate a way of thinking they'd never have arrived at alone. +- Message to the room: *"be more like that person."* + +Leadership training becomes peer-generated, not manager-generated. + +--- + +## Values: hire → inspire → fire + +Three-step integration so values are operational, not decorative: + +| Stage | What it looks like | +|---|---| +| **Hire with the values** | Screen for them in recruiting — before skills. | +| **Inspire with the values** | Tie every internal decision, praise, and initiative back to the three values. | +| **Fire against the values** | When someone goes, name the specific value they violated. | + +Examples of value-based firings from the clip: +- A leader who didn't develop their team (didn't build people). +- Someone who added complexity to a process. *"Complexity fails, simple scales."* + +**The punchline:** +> *"Values aren't what you say they are. They're what you tolerate."* + +If you say "we value simplicity" and keep someone who ships complex processes, your real value is complexity. Firing is how you tell the team what the values actually are. + +--- + +## Actionable takeaways + +For a founder / team leader: + +1. **State the growth math out loud.** If the company is doubling, the team is doubling too — that message can't be implicit. +2. **Adopt a Business Athlete philosophy** (or your own equivalent framework) so "how to show up" is teachable, not vibes. +3. **Post the scoreboard.** Make each person's standing visible; use 1-on-1s (not the wall) for the hard talk. +4. **Run the Keeper Test on every direct report** — turn every "no" into a documented development plan or a departure. +5. **Weekly, pick a bright spot** and have them teach the team their thinking. Never let leadership training all come from you. +6. **Audit your last three fires** — did you name the value each violated? If not, your team can't tell what your values actually are. + +--- + +## Who this is for + +- Founders whose company growth is stalling and who suspect (correctly) it's a people ceiling, not a market one. +- Managers who feel they're "doing all the coaching" and getting no leverage. +- Leadership teams whose stated values don't match the behavior they tolerate. diff --git a/raw/sources/sebastian interview - conclusions and insights.md b/raw/sources/sebastian interview - conclusions and insights.md new file mode 100644 index 0000000..d57bc52 --- /dev/null +++ b/raw/sources/sebastian interview - conclusions and insights.md @@ -0,0 +1,150 @@ +#ai #interview #development #webinar + +# Sebastian Interview — Conclusions & Insights + +**Participants:** Sebastian (founder of *Virtido*, a ~11-year-old software outsourcing/engineering company) and Eugene (the interviewer — a computer-vision & embedded/firmware developer, content creator, and builder of his own AI "harness"). +**Length:** ~56 minutes · **Topic:** How AI is reshaping software engineering — teams, tooling, careers, enterprise reality, and business development. +**Context:** Appears to be a pre-webinar conversation. Casual, candid, two practitioners comparing notes. + +> **Sourcing note:** Built from an automatically generated (Whisper large-v3) and speaker-diarized transcript. Quotes are lightly cleaned for readability and obvious speech-to-text errors are corrected (e.g. "Claude Code," "COBOL," "RAG," "Virtido"). A few rapid-crosstalk moments may be mis-attributed. + +--- + +## Executive Summary + +The debate is over *whether* AI can write software — it can. The whole game is now *how you use it*. That single shift cascades into everything else in the interview: + +- **Teams shrink and roles merge.** The 8-person scrum team collapses to 2–3 people who share coordination and agent-wrangling. +- **Tooling becomes personal ("bring your own harness") — except where it can't.** Individual developers get maximum leverage from custom harnesses on top of Claude Code; regulated enterprises can't allow that, which creates a real business opportunity. +- **The value of pure coding skill collapses; the value of judgment, ownership, and relationships rises.** Claude "levels" a 20-year veteran and a fresh grad to similar output — so the differentiator moves to understanding problems and, above all, human connection. +- **The durable human skills are product ownership and real-world networking.** These are the two things AI doesn't commoditize. + +--- + +## Who's Who + +| | **Sebastian** (SPEAKER_01) | **Eugene** (SPEAKER_00) | +| -------------------- | --------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- | +| **Role** | Founder/owner of *Virtido*, a software outsourcing company | Hands-on developer & content creator; the interviewer | +| **Vantage point** | Running a services business, client/compliance/sales lens | Building tooling, embedded/firmware & computer vision, individual-leverage lens | +| **Signature stance** | "Bring-your-own-harness won't survive enterprise; connections win business" | "Build your own harness; get closer to the client's real problem" | +| **Notable work** | 11 yrs in business, 10–15 engineers on big teams, enterprise clients | Custom Claude-Code harness, projects like *insin* (apt-get-style edge updater) & *Keller* | + +--- + +## Key Themes & Insights + +### 1. The question changed: not "can AI code?" but "how do you use it?" +The cost of writing code trends toward zero, so the leverage moves entirely to *how* AI is directed. +> "It's not a question *if* AI can write software anymore — it's just a question of *how* you use it." + +### 2. Team structure collapses from ~8 people to 2–3 +No more scrum master + PM + requirements engineer + a big dev team. Instead: one coordination/ownership role plus one or two people managing coding agents, sharing responsibilities. +> "Teams will be two or three people and they will share these roles… one person with a coordination role and one or two who manage the coding agents. That's it." + +### 3. "Bring your own harness" — but it hits a wall in the enterprise +Eugene's thesis (echoed by many practitioners he cites): every developer should build a personal *harness* on top of Claude Code because knowing every detail makes it far more effective. He demoed his own: a Telegram-like UI with one agent per project, inter-agent messaging, per-agent memory, and a "done thinking" signal so you don't babysit the console. Tools referenced: **Conductor** (isolates a git worktree per chat, automates PRs/merges), plus "open clock, Hermes, paperclip." + +Sebastian's crucial counterpoint: this **does not scale to large or regulated organizations**. Compliance and liability make ad-hoc, per-developer setups impossible. +> "From a compliance perspective I can guarantee you that bring-your-own-harness will not be the way forward… it has to be a company-managed resource. We cannot let everyone pick their own setup." + +**→ Business opportunity identified:** *scalable, manageable, company-standard harnesses for larger engineering teams.* Sebastian explicitly frames this as "the interesting market." + +### 4. Enterprise reality is far more locked-down than the indie world +Sebastian's biggest clients: engineers can't use their own laptops — only a centrally managed VM, **zero ability to install their own tools.** Reference points: a Roche SAP transformation ran ~1,200 engineers for years; banks first banned AI outright and are now cautiously adopting it "because it's just so good." + +### 5. Seniors are now *more* valuable; juniors are being squeezed out +Counter-intuitively, AI has raised demand for seniors and made juniors "completely irrelevant" in the market, even though a junior + Claude could in theory produce the same output. +- **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." +- **The junior risk (a security argument):** the habit of 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; 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." + +### 6. Ownership & product thinking is the durable human skill +The recurring "profile picture" story: an engineer implemented "change your photo," ticked every acceptance criterion, but shipped it *ugly* (visible in the corner) because they never looked at the actual result. That's the absence of **ownership**. +- Ownership = putting yourself in the user's/customer's shoes and understanding what they'll expect — a mindset/personality trait, not a task list. +- Reframe the work: **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." +- AI forces the issue: 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). + +### 7. The planning/waterfall debate: coordination overhead can exceed the work +A colleague (Daniel) floated returning to waterfall. Sebastian disagrees — with AI, "we don't have time for planning." Concrete evidence: +- On a small two-person project (each ~1 day/week), Sebastian is **faster alone**: the effort to synchronize who-does-what and how-it-integrates exceeds the speed of just prompting it himself. +- **Printer anecdote:** a new printer had to work in 2 days via an unfamiliar direct-printing protocol in Java (which he'd never written). Explaining it to a remote engineer wouldn't have made the deadline; he went on-site and Claude Code solved it in ~30 minutes. His edge wasn't coding — it was *knowing how to instruct and verify* the result. + +### 8. Connections are everything — the standout insight +Eugene's core unsolved problem (stuck ~6 months): how to build a professional network. The framing that lands: +- Claude **levels pure programming skill.** 20 years of experience vs. a fresh grad, same Claude subscription → similar output. The *only* real differentiator becomes the ability to communicate with clients and understand their problems. +- **Real, in-person connection is the one thing AI can't commoditize** — and it gets more valuable as AI floods everything else. Soon you won't be able to tell bots from humans on LinkedIn, or even on a phone call. "In 10 years… zero" ability to tell. +- **What actually works for winning business:** showing up in person 2–4 days/week (business lunches, networking events, conferences, open days). **What doesn't:** sales agencies, cold calling, email marketing, LinkedIn campaigns, content, SEO — "Big zero." Every real long-term customer came through personal network. +> "The only way to get a real connection is to stand face to face in the same room with someone, shake their hand, and have a conversation." +- **Mechanics of a connection:** it forms not on the first meeting but when you meet the *same* person in *different* circumstances → recognition value → trust → referrals. ("Oh, 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, a dog) — not "I run a software company," which everyone forgets. Because everyone now uses the same AI tools, *everything online looks identical*; humanity is the differentiator. (Virtido's playful `humans.verti.com` / "human badge on LinkedIn" is a riff on exactly this.) + +### 9. Decouple identity from profession (the philosophical turn) +Older generations tie identity to their job ("I *am* a doctor"). As many professions collapse into "prompt the AI," they'll lose obvious societal value. The advice: learn to separate *who you are* from *what you do professionally*, or "we will feel worthless in a couple of years." +> "Fundamentally I'm Eugene — I'm not a programmer. But I need to work on that." + +### 10. AI's value extends well beyond programmers +Non-technical, high-leverage uses discussed: profile ~2,000 LinkedIn/HR contacts into Obsidian, build RAG/search over your own collected information, spot who's hiring and pitch as a contractor. "You can put your whole life into a RAG." You don't need to be a programmer to benefit. + +### 11. Two smaller-but-sharp side points +- **Open source will grow because of AI.** When writing code costs ~nothing and most code isn't high-value, people will give it away. (Eugene's more cynical read: OSS is largely marketing; every OSS dev cites *The Cathedral and the Bazaar*.) +- **Legacy/hobby niches persist.** A few holdouts survive (e.g., COBOL engineers in banks — no training data for AI), plus people who code for the love of it "like driving an old-timer car" — but not where time, quality, and money matter. +- **On outsourcing economics (opening exchange):** great engineers exist everywhere (India has as many as Ukraine/Russia); the problem is that a *low-cost expectation* selects for bad code. Pay $10k/month and you get excellent people; an $800/month hire won't beat a good, well-paid engineer. + +--- + +## Points of Tension / Disagreement + +- **Personal vs. company-managed harness:** Eugene champions bring-your-own; Sebastian says compliance kills it at scale (and that gap *is* the business). +- **Planning:** Daniel (absent) wants waterfall back; Sebastian says coordination overhead now outweighs the work itself. +- **Open source motivation:** Eugene sees it mostly as marketing/"gambling for questionable results"; Sebastian expects *more* OSS as code becomes nearly free to produce. +- **Networking channels:** Eugene is invested in LinkedIn/articles; Sebastian bluntly calls online outreach a "waste of time" versus in-person. + +--- + +## Standout Conclusions + +1. **Move up the value chain — from writing code to owning outcomes.** The engineer's job is shifting from "produce the solution" to "understand and frame the problem, then direct and verify the AI." +2. **Seniority = risk reduction.** The senior's real product is judgment: preventing expensive mistakes and catching dangerous agent actions. +3. **The enterprise-harness market is wide open.** Someone will make money providing compliant, centrally managed AI tooling for large regulated teams. +4. **Relationships are the last non-commoditized asset.** When skill and online presence are equalized by AI, in-person trust becomes the scarce, decisive edge. +5. **Protect your identity.** Tie your sense of self to *who you are*, not a job title that AI may hollow out. + +--- + +## Memorable Quotes + +- "It's not a question *if* AI can write software anymore — it's just a question of *how* you use it." +- "No one ever needed a programmer… people have problems that you are solving." +- "Give a junior… access to this almighty Claude and then access to the codebase — they will [wreck] it in two days." +- "The only way to get a real connection is to stand face to face in the same room with someone, shake their hand, and have a conversation." +- "We tried sales agencies, cold calling, email marketing, LinkedIn campaigns, content, SEO. Zero. Big zero… Every real long-term customer has come through [personal network]." +- "We need to learn to decouple our identity from the thing we do professionally." + +--- + +## Actionable Takeaways + +**For Eugene (his stated problem — building a network):** +- Reallocate time from LinkedIn posts/articles to **recurring in-person events** (aim for the same circles repeatedly to build recognition value). +- Prepare a **memorable, human self-introduction** that isn't your job description. +- Treat the network as the moat, not the code — the coding is already commoditized. + +**For engineers generally:** +- Practice **product ownership**: always look at the actual result a user sees, not just the acceptance criteria. +- Shift vocabulary from "tasks/tickets" to "problems and desired outcomes." +- Build (or learn) a **harness** for personal leverage — but expect a company-standard one at any regulated employer. +- **Read what you approve.** Don't reflexively "allow all"; that habit is a security incident waiting to happen. + +**For businesses / founders:** +- The **compliant enterprise-harness** space is an underserved market. +- Assume digital outreach converges to noise; **invest in face-to-face relationship-building** as the durable channel. + +--- + +## Open Questions Raised (Unresolved in the Interview) + +- How does AI actually transform *huge* enterprise programs (the ~1,200-engineer, multi-year kind)? Sebastian is candid that he doesn't know. +- How do you unify wildly different personal workflows into one company process? (Eugene and his collaborator spent a month and couldn't.) +- Concretely, how does an individual engineer *build* a connections network from a standing start? (Sebastian offers principles; the step-by-step remains open.) diff --git a/raw/sources/Главный Принцип УСПЕШНОГО БИЗНЕСА.md b/raw/sources/Главный Принцип УСПЕШНОГО БИЗНЕСА.md new file mode 100644 index 0000000..72ea51d --- /dev/null +++ b/raw/sources/Главный Принцип УСПЕШНОГО БИЗНЕСА.md @@ -0,0 +1,212 @@ +# Выводы по видео + +**Источник:** https://www.youtube.com/watch?v=pHoWRl7MVwE +**Название:** Главный Принцип УСПЕШНОГО БИЗНЕСА +**Длительность:** 17:52 +**Спикер:** Оскар Хартманн + +--- + +## Главный тезис + +**Сначала продавай, а потом строй.** + +Всё видео — вариации одного принципа: строительство продукта — самое ответственное, дорогое и необратимое решение предпринимателя. До того как вложить время и деньги в постройку, нужно **дешёвыми экспериментами доказать, что боль клиента настолько острая, что он готов заплатить деньги вперёд**. Всё остальное — «списки ожидания», лайки, «интересно» — не считается. + +--- + +## Личный анти-кейс автора: коворкинг для владельцев бизнеса + +- Оскар был на 100% убеждён в идее коворкинга для крупных владельцев бизнеса. +- Уже готов был сделать большую инвестицию. +- Остановил себя и сделал минимальный тест: + 1. Сгенерировал через AI **самую красивую картинку** идеального пространства в лучшей локации. + 2. Разослал в 7-8 бизнес-клубов с оффером: «Я, Оскар, буду работать в этом офисе. Есть 20 мест. Вот цена. Кто со мной?» + 3. Сообщение получили **~5000 человек**. + 4. Ответило **< 5**. Из них 3 — «у меня всё решено, но может быть». 2 — «не эта локация». + 5. **Настоящих покупателей — 0.** +- Проект похоронен до постройки. Стоимость проверки — копейки. Стоимость ошибки, если бы построил — миллионы. + +--- + +## Как работают лучшие app-студии + +Крупные utility-app студии **запрещают себе придумывать**. Они запускают сразу 20 приложений и смотрят на голосование деньгами. + +**Механика теста:** + +- Собирается полнофункционально выглядящее приложение (страницы, тексты, обещания). +- Пользователь доходит до экрана оплаты. +- Показывается сообщение: *«Ошибка, извините, платёж не прошёл.»* +- Человек забывает — но у студии остаются **реальные данные о готовности платить**. + +Инсайты из этой волны тестов: + +| Гипотеза | Результат | +|---|---| +| «Бросить казино» | Провалилась — люди не хотят бросать азартные игры | +| «Бросить порно» | Сработала — есть спрос | +| «Похудение / счётчик калорий» | Классически работает | + +Стоимость одного эксперимента — **< $1000**. Стоимость нормальной постройки приложения — на порядки больше. + +--- + +## Признаки настоящей боли (что мы ищем) + +Оскар: *«Если бизнес работает, только когда всё идеально — это плохой бизнес. Хороший бизнес — когда всё плохо, а люди всё равно приходят и платят.»* + +**Признак острой боли:** + +- Сервис плохой, продукт ломается — а клиенты всё равно платят. +- Пример: **больницы**. Никто не оставляет хорошие отзывы, ждёшь 1.5 часа с болью 10/10, но альтернатив нет — заплатишь и ещё поблагодаришь. + +Когда боль такая острая — люди платят **за концепт**, не за отполированный продукт. + +--- + +## Идеальный тестовый бизнес — трафиковый + +Оскар всем молодым рекомендует начинать с трафикового бизнеса: + +- **Максимально быстрый отклик** — покупаешь трафик → гонишь на оффер → смотришь, что сработало. +- Даже **одно слово** в оффере меняет конверсию в 3-5 раз («мы помогаем снизить концентрацию портфеля» vs «мы уменьшаем …»). +- Всё это до того, как начал строить. + +**Правило:** просто лендинг не годится. Нужен **экран оплаты**. Записать в список ожидания — не считается. Только деньги — голос. + +--- + +## Кейс Илона Маска — тот же принцип на триллионном уровне + +- Tesla Model 3: собрал **100 000 предзаказов** — люди заплатили — и только после этого начал строить. +- Cybertruck: сначала **100 000 предзаказов** — потом стройка. +- «Компания стоит $1.5T, зачем ей проверять спрос?» — **всё равно проверяет.** Принцип не зависит от размера. + +--- + +## Кейс парня из Таджикистана — $5M предоплаты без продукта + +- Выпускник MIT, работает в Кремниевой долине. +- Ниша: продажа данных для тренировки хуманоид-роботов. +- Стратегия (скопирована с 10 компаний, которые так же выросли на данных для LLM): + 1. Обошёл все компании, делающие роботов. + 2. Спросил: «Какие данные вам нужны?» + 3. Получил ответы: «Складывать шорты + датчики + видео.» + 4. Продал контрактов на **$5M предоплаты**. + 5. **Только теперь** начал собирать данные под конкретные требования. +- Итог: «делается что-то из ничего» — компания сразу с положительной юнит-экономикой. + +--- + +## Кейс наставника Оливера Самвера — eBay для Германии + +Оскару 20 лет назад Самвер показал контр-интуитивный приём: + +- Скопировал eBay: 100 функций, не знал, какие приоритизировать. +- Сделал **все кнопки** в UI — но кнопки **не работали**. +- Смотрел логи: сколько кликов по какой кнопке. +- **Строил в порядке количества нажатий.** + +Приоритеты оказались неочевидными — интуиция обманывает всегда. + +**Иерархия силы сигнала:** + +1. Клик по кнопке — слабый сигнал +2. Оставить email / записаться в список — сильнее, но обманчив +3. **Оплата** — единственный настоящий сигнал + +--- + +## Портфельный контр-пример: две команды за 12 недель + +Свежий кейс из портфеля Оскара — две AI-компании, разные географии, похожая идея, одинаковые инвестиции. + +| Метрика | Команда A | Команда B | +|---|---|---| +| Тестов запущено | **10** (уже) | 0 | +| Продукт | Много раз обновлён, ищет | Ещё нет | +| Клиентские сигналы | Постоянные | Ноль | +| Потрачено денег | Почти ноль | Почти ноль | +| Разница | — | — | + +**Единственная разница — мышление.** Готовность запуститься с уродливой первой версией и «выглядеть глупо» побеждает. Успех обычно **не там, где вы думали** — а найти это можно только частыми дешёвыми тестами. + +--- + +## Красный флаг — «Мы работаем над проектом с 2016 года» + +Каждую неделю Оскара питчат командой с подводкой типа: *«Мы работаем над этим с 2016 года, выручки пока нет»* — как будто длительность = ценность. + +**Это жирнейший минус.** Оскар: «Лучше поговорю с командой, которая работает неделю, чем с той, что 9 лет без выручки.» + +Отсутствие выручки при длительном проекте = отсутствие доказательств. + +--- + +## Ручной MVP — «Wizard of Oz» до продукта + +Когда цифровой продукт нельзя дёшево смакетировать — **делай ценность вручную для 10 клиентов.** + +- Свежий пример: **Build.ai** — оценивалась в $2 млрд, а выяснилось, что «AI» — это **500 индийских специалистов**, которые притворяются моделью. Оскар: «Так начинать классно. Но при оценке $2B, наверное, уже стоило продукт сделать.» +- Идея — та же: сначала руками довести до ценности → доказать спрос → **затем** автоматизировать. + +--- + +## Анти-кейс автора: Zavent (бронирование переговорок) + +- Классный спрос, компания росла. +- Клиенты платили **только с постоплатой через 3 месяца**. +- Zavent превратился в **банк**, финансирующий клиентов. +- Продукт стал непонятен: удобство бронирования или финансирование ивентов? +- Когда включили только предоплату — **конверсия резко упала**. +- Урок: если клиенты **готовы платить вперёд** — это сильнейший сигнал спроса. Если только постоплата — модель другая, и бизнес другой. + +--- + +## Барьер входа через выжигание CAC + +Когда система уже работает и юнит-экономика положительная — можно **тратить много на клиента** ($80-$100 CAC), чтобы: +- Ни один новый конкурент не мог себе этого позволить. +- Заблокировать вход в рынок. + +Это работает **только** после доказанного PMF, но именно так строятся долгие моаты. + +--- + +## Сквозные принципы + +1. **Сначала продавай, потом строй.** Работает на любом уровне — от MIT-студента до Tesla. +2. **Экспериментировать, пока это дёшево.** Ошибиться за $1000 → безопасно. Ошибиться за 6 месяцев постройки → фатально. +3. **Голос деньгами** — единственный настоящий сигнал. Клик, лайк, список ожидания — иллюзия. +4. **Интуиция обманывает.** Клиенты голосуют не за то, что ты ожидаешь. Всегда удивляешься. +5. **Ищи «острую боль».** Признак — плохой продукт, а всё равно покупают. +6. **Готовность выглядеть глупо** > идеальный релиз через 6 месяцев. +7. **Предоплата = высший знак спроса.** Клиент авансирует твою постройку. +8. **Ручная ценность до автоматизации.** Wizard-of-Oz для первых 10 клиентов. +9. **Терпи боль реальности быстро.** Умный предприниматель радуется плохому отклику раньше, а не позже. +10. **Не пытайся диктовать клиенту, что он должен хотеть.** Строй то, что уже востребовано. + +--- + +## Чек-лист для собственной гипотезы + +- [ ] Какой **самый маленький эксперимент** докажет или опровергнет мою гипотезу? +- [ ] Что конкретно я могу сделать, чтобы **клиент проголосовал деньгами** сейчас, до постройки? +- [ ] Есть ли **лендинг → экран оплаты** (не «записаться», а именно платёж)? +- [ ] Можно ли собрать **предоплату** (даже частичную) до начала работы? +- [ ] Что говорит **самая маленькая группа с самой острой болью**? Кто эти люди по именам? +- [ ] Готов ли я **обойти 10 конкретных потенциальных клиентов** и спросить, за что они прямо сейчас готовы заплатить? +- [ ] Могу ли я **вручную** доставить обещанную ценность первым 10 клиентам, пока продукта нет? +- [ ] Если я «работаю над проектом» дольше 3 месяцев без выручки — что реально мешает мне запуститься с уродливой версией завтра? +- [ ] Мой бизнес работает, только когда всё идеально — или **работает даже когда всё плохо**? + +--- + +## Кому это видео полезно + +- Основателям, которые «уже 6 месяцев допиливают» продукт без клиентов +- Тем, кто путает список ожидания / лайки / комментарии с реальным спросом +- Предпринимателям, влюблённым в свою идею и не смеющим её проверить +- Всем, кто собирается делать «большую маркетинговую компанию, дайте $5M» — вместо десяти конкретных встреч с покупателями +- Командам, у которых «мы работаем над этим с …» ≥ 1 года и всё ещё нет выручки diff --git a/raw/sources/Как Построить МИЛЛИАРДНУЮ КОМПАНИЮ в 2027.md b/raw/sources/Как Построить МИЛЛИАРДНУЮ КОМПАНИЮ в 2027.md new file mode 100644 index 0000000..1129e98 --- /dev/null +++ b/raw/sources/Как Построить МИЛЛИАРДНУЮ КОМПАНИЮ в 2027.md @@ -0,0 +1,227 @@ +# Выводы по видео + +**Источник:** https://www.youtube.com/watch?v=GE5qmn7M7lo +**Название:** Как Построить МИЛЛИАРДНУЮ КОМПАНИЮ в 2027? +**Длительность:** 34:52 +**Спикер:** Оскар Хартманн (по контексту — KupiVIP, ShoppingLive, Fab.com как акционер, программа «Создатель единорога») + +--- + +## Главный тезис + +**Хороший продукт сам себя не продаёт.** В эпоху вайб-кодинга и ИИ у каждого в Cloud Code лежит 10-15 «отличных» продуктов, но кладбище мёртвых стартапов растёт быстрее, чем число реально успешных компаний. Product-Market Fit — это не финиш, а старт. Настоящее отличие миллиардной компании от опухоли — **повторяемый, масштабируемый канал продаж** с предсказуемой экономикой. + +> «Тим Кук создал больше ценности, чем Стив Джобс. 45-кратный рост Apple — без единого нового продукта.» + +--- + +## Ключевые ошибки и как их избегать + +### Ошибка 1. Продолжать пилить фичи вместо построения GTM + +- Свежий пример у автора: команда ИИ-стартапа делает 26-ю фичу в Jira, выручка < 1 млн руб/мес. +- **Самое ценное сейчас — не фича №26, а повторяемый Go-to-Market.** +- Разовые всплески («Майкл Джексон из гроба сказал приходите») не считаются — нужен канал с предсказуемой стоимостью привлечения и масштабируемостью. + +### Ошибка 2. Фаундер не продаёт сам + +- «Найму продажника» — детская идея. **Фаундер = главный продавец компании. Точка.** +- Во всех крупных компаниях первую партию клиентов пробивал сам основатель, «как продавец пылесосов». Некомфортно, но необходимо. +- Оскар: «Я лично не инвестирую в компанию, где фаундер не занимается продажами сам.» + +### Ошибка 3. Целиться сразу в весь TAM + +Инвесторы любят большой TAM, но начинать нужно с SOM — маленького рынка, где ты можешь **уже сейчас** взять значимую долю. + +| Плохо | Хорошо | +|---|---| +| «AI-агенты для всех профессий мира» | «AI-агент, принимающий звонки для HVAC/сантехников/крышников» | +| «AI-юрист» | Manifest (Дэн Мишин) — стартовали с **иммиграционного права**, стали единорогом только на этом сегменте | +| «Amazon для дома» (Fab.com) | Fab на пике: $100M на дизайнерских товарах для дома с лояльной базой | + +Правило: **большой рынок + маленький выигрываемый субрынок + MVP, а не фантастический продукт.** + +### Ошибка 4. Гигантские клиенты как «спасение» + +Кейс **Pediant** (QR-платежи, продали Walmart и Best Buy): +- Интеграция длится вечно → откладывается → через 1.5 года купивший тебя менеджер ушёл → новый не берёт ответственность → отменяют / начинают заново. +- Для корпорации это «рассмотрим на следующем инвесткомитете», для стартапа — **стенка, финиш**, деньги кончились. + +### Ошибка 5. Надежда на партнёрства («один договор — и всё полетит») + +- **Партнёры почти всегда разочаровывают.** У банка уже 15 своих продуктов, которые он не может продать по плану, + 30 партнёрских — твой где-то в этой каше. +- Если один партнёр = gatekeeper — он заберёт всю маржу. +- Партнёрство работает, только если партнёров **много** (не одна компания-охранник ворот), и продукт хорошо садится сверху их услуг. +- Оскар видел, как компании входили в «огромные партнёрские каналы» — результат был в **100-200 раз ниже ожиданий**. + +--- + +## Контрастный кейс — Pediant vs FlatPay + +| | Pediant | FlatPay | +|---|---|---| +| Продукт | QR-платежи | Платёжный терминал | +| Ценностное предложение | Технология | «1% комиссия. Всё. Никаких звёздочек» | +| Канал продаж | Огромные корпорации (Walmart, Best Buy) | **Door-to-door** — обученные продажники стучатся в двери предпринимателей в Голландии и Германии | +| Один продажник | Ждёт годовые интеграции | Продаёт **10-20 терминалов в месяц** | +| Исход | Опухоль → банкротство | Миллиардная компания | +| Основатель | — | Уже **шестой** бизнес по этому же playbook — может брать любой продукт в ту же дистрибуцию | + +**Мораль:** уникальный, масштабируемый, повторяемый канал ценнее уникальной технологии. + +--- + +## Мир стал невыносимо шумным — сколько стоит внимание + +- **12 часов экрана в день, ~40 ГБ информации в голову.** +- ИИ сделал мир ещё шумнее: LinkedIn — 2000 непрочитанных сообщений за месяц (агенты рассылают за всех). +- Email забит, все каналы забиты. Внимание — **самый дорогой ресурс на планете**. + +### Иерархия рекламных каналов (по эффективности внимания) + +| Канал | Логика | Цена входа | +|---|---|---| +| Поисковая реклама (Google Ads) | Клиент **уже выразил желание** — купить обувь, купить билеты | Средне | +| Баннерная реклама (Meta) | Клиент рекламу **не просил** — читает новости, показываем | Дороже за результат | +| Событийный маркетинг (offline events) | Возвращается — компаниям стало выгоднее делать оффлайн-ивенты | Дорого | +| Super Bowl / TV | Массовая, без таргетинга, но эффективнее многих таргетированных | **~$10M за 30-секундный ролик** | + +- Google обошёл Meta по обороту — «средний продукт, который кричит, вытесняет лучший продукт, который молчит». + +### Бизнесы, которые находят канал, знают Lifetime Value + +- Готовы отдать **треть пожизненной прибыли клиента** за одного клиента в день №1. +- Пример: клиент кредитной карты в США стоит **$1000 CAC**. 1000 клиентов = $1M. Дешевле не бывает. Это барьер входа — новые стартапы просто не могут конкурировать. +- Так рождаются убыточные, огромные венчурные раунды: покрыть отрицательную юнит-экономику, пока LTV не соберётся. + +--- + +## Land Grab — что происходит прямо сейчас в AI + +- Anthropic и OpenAI сделали **joint-ventures по $4 млрд** с private-equity-фирмами, у которых сотни тысяч компаний в портфеле. +- Цель — внедрить технологию сразу в тысячи клиентов. +- Это классический **land grab**: свободное поле, кто быстрее себе кусок отрисует — тому и рынок. +- Задействованы **все каналы одновременно**: партнёрские, собственные, телефонные, door-to-door. + +**Устойчивая система = мультиканальная**, где каналы взаимно усиливают друг друга. + +--- + +## Венчур vs остальной мир — важное отрезвление + +- **Только ~1% бизнесов** подходят для венчура. В Европе VC уже не смотрят стартапы, которые не могут вырасти в $100B+. +- «Растяжка на венчурные ожидания» **убивает** нормальные компании. + +### Кейс Fab.com + +- Прекрасная ниша, лояльные клиенты, $50M → $100M выручки, «дизайнерские интерьерные вещи». +- Подняли раунд на **$1.5B оценку** → ожидание $10B выручки. +- Одновременно: маркетинг-бюджет вверх, международная экспансия, +страны, +продукты, бесплатная доставка везде. +- **Единственное, что росло — убытки.** Даже не смогли вернуться к $100M. Обанкротилась. + +### Альтернативы венчуру + +- Топ-20 крупнейших **частных** компаний США делают по $30B+ оборота — до сих пор принадлежат основавшим их семьям. +- Медленный, «мид-маркет» рост от $10M до $100M — вполне себе бизнес, просто не венчурный. +- Собственный кейс автора: ShoppingLive построен на «пару сотен тысяч долларов» — стал №1 телемагазином в России, один из лучших ROI в его карьере. + +--- + +## AI высасывает весь свободный капитал + +- Anthropic, SpaceX, OpenAI в этом году **высосут почти весь свободный кэш** из мирового венчурного рынка. +- «Приехала Анечка» (AI) — всё остальное вытесняется. +- Ты либо в топовой AI-лабе, либо на венчурном рынке **тебя не существует**. +- Что делать остальным? Строй свои «парки аттракционов» с окупаемостью 9 месяцев, реинвестируй прибыль, расти медленно. + +--- + +## Юнит-экономика — где почти все ошибаются + +Оскар: **большинство предпринимателей продают своё дешевле, чем это реально стоит.** + +Что забывают учитывать в цене: +- Стоимость дистрибуции и продаж +- Стоимость **повторного** привлечения / удержания +- Стоимость транспорта, амортизации +- Списание остатков + +Это создаёт «кассовые разрывы», которые на самом деле — **настоящие убытки**. + +### Что делать + +1. Сначала доказать, что продукт **нужен**. +2. Затем — что можешь производить его **сильно дешевле**, чем клиент готов платить. +3. Разница должна покрывать **всё**: маркетинг, дистрибуцию, продажи, склад — **с запасом**. + +### Правило запаса + +- Лучший год ≠ норма. Лучший год = аномалия раз в 10 лет. +- Не бери лучший год за базу: тогда все остальные годы будут «кризисом», хотя это нормальная реальность. +- В ритейле — оптимизация «копейка в копейку», в остальном должна быть буферная маржа. + +--- + +## Pricing Power — настоящий тест на Product-Market Fit + +- Если ты **поднимаешь цены**, а поток клиентов не падает — вот тогда есть PMF. +- Если не можешь ставить цену (маркетплейс её ставит, скидки не в твоих руках) — **ты не предприниматель**, а участник «симуляции предпринимательства». +- Цена — часть позиционирования и часть PMF. + +### Маркетплейсы — самый удивительный бизнес-модель + +- Начинают как «всё бесплатно» → потом невероятно прибыльны, потому что у них **власть в ценообразовании**. +- Даже в мире AI маркетплейсы **никуда не денутся**. + +--- + +## Что ещё раскрыл автор о своём собственном бизнесе + +- Его личный первый интернет-магазин вырос до **$20M** за счёт одной предпринимательской сделки: партнёр делал баннеры, приходил трафик, автор платил **10% выручки** постфактум с открытыми книгами. +- Но такие сделки — один разовый подъём. Потом всё равно нужно строить системные каналы, потому что «менеджмент партнёра меняется, они делают аудит, приходят и говорят: теперь платишь за 1000 показов». К этому моменту у тебя должна быть статистика для аукционов. + +--- + +## Что действительно делает предприниматель (если убрать всё лишнее) + +**Строить и продавать.** + +Всё остальное — производные. + +--- + +## Практические вопросы к своему бизнесу (автор просит ответить в комментариях) + +- [ ] Насколько у тебя **действительно** есть Product-Market Fit — а не приятная иллюзия? +- [ ] Какой у тебя **узкий сегмент**, в котором ты можешь выигрывать **уже сейчас**? +- [ ] Какую **зубную, острую боль** ты лечишь? (Не «делаю AI для всего», а конкретно.) +- [ ] Подходит ли твоя бизнес-модель под **венчур** — или лучше реинвестировать свои и расти медленно? +- [ ] Есть ли у тебя **pricing power** — можешь ли ты поднять цену и не потерять клиентов? +- [ ] Какой канал дистрибуции позволит тебе **повторять** одно и то же снова и снова? +- [ ] Учитываешь ли в цене **всю** стоимость: дистрибуцию, повторное привлечение, амортизацию, списание? +- [ ] Готов ли ты стать **первым продавцом** своей компании — или ждёшь чуда от найма? + +--- + +## Сквозные принципы + +1. **Продукт → продавать → повторять.** Всё остальное — производные. Не путать эти три стадии. +2. **SOM > TAM на старте.** Маленький выигрываемый сегмент важнее большого рынка «в теории». +3. **Один канал = концентрационный риск.** Устойчивая система мультиканальна. +4. **Партнёры — плохой первый канал.** Ты — их 46-й приоритет. +5. **Внимание — самый дорогой ресурс.** Средний громкий вытесняет лучший тихий. +6. **Венчур ≠ бизнес.** Fundraising — не успех, а обязательство. За каждым раундом стоят ожидания. +7. **Растяжка на венчурные ожидания убивает** нормальные компании (Fab.com). +8. **Кто продаёт слишком дёшево — не имеет PMF.** Pricing power = реальный тест. +9. **Sales channel is a moat.** LTV × 1/3 CAC — вот почему стартапы «сжигают каналы» и создают барьер входа для других. +10. **Фаундер продаёт первый. Всегда. Без исключений.** Или ставь свою жизнь на то, что ты — исключение из закона природы. + +--- + +## Кому это видео полезно + +- Основателям AI-стартапов, которые «уже 26-я фича», а выручки нет +- Предпринимателям, которые ждут, что «партнёр» / «крупный клиент» / «инвестор» их спасёт +- Тем, кто путает fundraising с успехом +- Владельцам бизнеса, стоящим перед выбором: венчур или медленный органический рост +- Всем, кто до сих пор считает, что «хороший продукт сам себя продаст» diff --git a/raw/sources/Как продавать услуги по разработке дорого.md b/raw/sources/Как продавать услуги по разработке дорого.md new file mode 100644 index 0000000..428b5d2 --- /dev/null +++ b/raw/sources/Как продавать услуги по разработке дорого.md @@ -0,0 +1,184 @@ +# Выводы по видео + +**Источник:** https://www.youtube.com/watch?v=mnQX-JLi_oA +**Название:** Как продавать услуги по разработке дорого +**Длительность:** 58:22 +**Спикеры:** Дмитрий Роденко (SaaS Founders), Натан + +--- + +## Главный тезис + +Эпоха почасовой разработки заканчивается: у заказчика появилась альтернатива за $200/мес (ИИ), поэтому война «мы vs дешёвые регионы» по часовой ставке — это путь в обнуление маржи. Дорого продаётся только **результат и ответственность за него**; всё остальное — себестоимость, которую заказчик быстро посчитает. + +Две формулы, которые повторяются весь эфир: + +- **«Дорого» не существует. Существует «не вижу, за что».** +- **Ваш value = то, что заказчики сами называют, когда вы спрашиваете «за получение какого результата вы мне платили». Всё остальное — ваши косты.** + +--- + +## 1. Тест на commodity + +Уберите из вашего оффера слово «разработка» и название технологии. Что осталось? + +- Ничего осмысленного → вы **commodity**, конкурируете по часовой ставке. Гарантия тут не лечит: «commodity с бантиком — всё равно commodity». +- Осталась конкретная боль и результат → есть шанс уйти из ценовой гонки. + +> «Если вас можно сравнить с индусами, вы и есть индус, просто дороже.» + +--- + +## 2. Категория важнее услуги + +Категория описывается **болью + результатом**, не названием технологии. Рынок сам категоризирует вас, если вы не сделали это первыми — обычно по часовой ставке. + +Пример из продуктового мира: + +| Старая категория | Новая категория | +|---|---| +| Sales Automation (красный океан, CRM/outreach) | Sales Enablement | +| Вы 240-й в списке скидок | Вы 5-й в новой категории | + +На уровне одной услуги — то же: «мы делаем X для таких-то компаний, чтобы закрыть Y боль и получить Z результат», а не «мы разрабатываем». + +--- + +## 3. ИИ не прячьте — используйте как фильтр квалификации + +Кейс одного фаундера: + +- На первом созвоне даёт **готовый AI-скилл бесплатно**, «попробуйте 30 дней». +- Из 10 первых созвонов 5 возвращаются за second call, 1 закрывается в проект на $100k. + +Три типа ответа после тестирования (и что они значат): + +| Ответ клиента | Что это значит | +|---|---| +| «Работает» | Ваш value не нужен — задачу уже закрыл AI. Не клиент. | +| «Не взялись» | Задача, за которую не готовы платить. Не клиент. | +| «Слабовато, много абстракции, не хватает конкретики» | Увидели value, готовы говорить. **Целевой клиент.** | + +--- + +## 4. Zendesk-story: канонический оффер + +Заказчик платил $30k/мес ($360k/год) на Zendesk. Команда сделала кастомное решение за $2k/мес. Проект на $100k окупился клиенту примерно за 4 месяца. + +**Outreach сводится к двум вопросам:** + +1. «Сколько вы тратите на Zendesk?» +2. «А если бы тратили не 300, а 30 — это интересно обсудить?» + +Принцип: спрашиваете про **реальные траты на конкретное операционное действие** и обещаете **сократить в 10 раз**. + +> «Даже если вы наполовину ошибаетесь, вы всё равно в 5 раз вывели.» + +Не уходите искать «ещё один Zendesk» — ищите похожие операционные боли в той же индустрии. + +--- + +## 5. От часов к результату — за неделю, а не за год + +> «Год переупаковки нужен тем, кто боится поднять трубку и позвонить заказчику.» + +Алгоритм на неделю: + +1. Позвонить 3-5 лучшим заказчикам. +2. Спросить **за получение какого результата** вы им платили (не «почему выбрали» — на это отвечают «хорошая команда, удобный процесс»). +3. Свести ответы к паттерну — это ваш реальный оффер. +4. Дальше: 20% времени и маркетинговых усилий вкладываете в нишевое продуктивизированное предложение, остальное пока продолжает кормить команду. +5. Через 3-4 месяца переоценить, что работает. + +Продуктивизированные офферы всегда выигрывают и по циклу сделки, и по марже — потому что покупатель понимает уникальность и готов переплачивать. + +--- + +## 6. Где искать клиентов: смотрите, на что тратят, а не что говорят + +Типовая структура расходов даёт точку входа: + +| Тип компании | Самая большая статья затрат | Куда бить оффером | +|---|---|---| +| Сервисные | Фонд оплаты труда | Снижение FOT в конкретных функциях | +| Производство | Сырьё и переработка → затем оплата труда | Оптимизация цепочки | +| Узкие индустрии (финтек/медтек/cyber) | Специфика отрасли | Узкие SaaS-затраты на интерпрайсе | + +И принципиально: **продавайте руководству, а не исполнителям**. Исполнителям ваш AI отбирает рабочее место (для них вы — риск). Руководству вы выполняете KPI — от них уже ждут предложений по эффективности. + +--- + +## 7. Squad-model: пример успешной перепозиционировки + +Бывший outstaffing-шоп, чьи сеньоры лежали на прилавке рядом с индусами по $25/час: + +- Перестали продавать людей вообще. +- Собрали скводы по 4 человека: 2 инженера + QA + PM. +- ICP: **стартапы, только что поднявшие раунд** (у всех одна и та же боль — через полгода показать инвестору результат). +- Оффер: «Стартуем за 7 дней. По цене двух американских программистов. К месяцу 6 у тебя есть, что показать инвесторам. Не получилось — доделываем за свой счёт.» +- Сейчас ~19 скводов × $15-18k/мес ≈ $7M годовой оборот, команда 90 человек. + +> «С индусом это просто невозможно сравнить.» + +Цена позиционирования: они сами учат своих стартаперов, помогают находить инвесторов — то есть выстроили «банду стартаперов» вокруг себя. + +--- + +## 8. Solution vs Staff Augmentation + +| | Solution | Staff Augmentation | +|---|---|---| +| Что продаёте | Результат + ответственность за него | Людей; клиент управляет проектом | +| Маржа | 30-50% | Низкая, гонка по цене | +| Замена клиентом | Сложно | За неделю | +| Совмещение под одним брендом | Скатится в staff aug | — | + +Единственная валидная комбинация: **сначала продали и внедрили solution → дальше оставили сотрудника на поддержку**. Это даёт длинный кэшфлоу и продолжение контакта. + +Если продавать обе модели — то под разными брендами и сайтами. + +--- + +## 9. «Дорого» vs «не вижу за что» — как отличить + +Скрипт-различитель: **«А если бы мы гарантировали этот результат — цена остаётся проблемой?»** + +- «Да, остаётся» → у клиента просто нет денег (нет такого Zendesk). Не клиент, торгуется ради торговли. +- «Нет» → цена была отговоркой; вопрос был в доверии к value. + +И — **бизнес покупает не уникальность, а проверенный способ**. + +> «Уникально — это «боюсь, не экспериментируйте на мне».» + +--- + +## 10. Нулевой бюджет, команда 15 человек — тактика + +Что делать в эту неделю: + +1. **Аудит закрытых проектов:** позвонить и спросить «за что вы мне платили». Деньги лежат на столе у заказчиков. +2. **Снять «нам нужна команда 15 человек»** как догму. Век больших команд ушёл; кейс выше показывает, что 4 человека закрывают тот же чек. +3. **Идти через нетворк/партнёров** — но не с «у меня команда 15 по $30/час», а с критерием: «знаешь кого, кто тратит $100k/год на helpdesk?» — это перенастраивает мозг собеседника. +4. **Founder = главный sales.** Не закрепились на следующем уровне — нормально, но продавать снова идёт фаундер. + +> «Лучший маркетинг при нулевом бюджете — перестать продавать дешево. Это бесплатно.» + +--- + +## Сквозные принципы + +- **80% успеха в продажах = КОМУ говорите, а не ЧТО.** Если оффер не продаётся — почти всегда не та аудитория. +- **Не лезть в каждый ринг.** Профессионалы выбирают только те бои, где есть шанс выиграть, чтобы не расходовать силы на commodity-войны. +- **Узкие ниши = там, где AI бессилен.** LLM не знает узких отраслевых методологий — потому что их «не выгодно кормить». Туда и идите. +- **AI продаёт не продукт, а обслуживание.** На каждый $1 в ИИ компания тратит ~$6 на специалистов, которые это настраивают — это новая воронка продаж. +- **Заказчик — не приз.** Сделка — обмен экспертизы на деньги, не благотворительность с вашей стороны и не одолжение с его. +- **Вы продаёте ответственность, а не часы.** Готовы взять ответственность — AI-эпоха озолотит. Не готовы — AI подписал приговор на 12 месяцев. + +--- + +## Кому полезно + +- Фаундерам IT-сервисных компаний и аутстаффинговых студий, которым прижимают по цене и сравнивают с дешёвыми регионами. +- Командам на T&M, у которых маржа сжимается из-за AI-альтернатив. +- Тем, кто думает «надо переупаковать оффер» — здесь чёткие шаги на неделю, а не на год. +- Тем, кто пытается продать solution и staff augmentation одновременно с одного сайта — статья объясняет, почему это не работает и как разделить. diff --git a/raw/sources/Конспект.md b/raw/sources/Конспект.md new file mode 100644 index 0000000..768279f --- /dev/null +++ b/raw/sources/Конспект.md @@ -0,0 +1,25 @@ +если ты с индусом на одном уровне, то ты не дал ничего больше, чем тот самый индус, чтобы попасть в другую категорию людей + +знание, где находятся подводные камни - это и есть твоя экспертиза + +останутся спецы, которые знают свою узкую нишу и пишут скилы + +нужно продавать РЕШЕНИЯ, а не работу. решения стоят дороже. а на работе ты конкурируешь с индусами + +самое важное в вашем предложении - это ТОТ, кому вы делаете предложение + +если есть один человек, котороый купил продукт, то нет никакой причины, чтобы другие его не купили. значит проблема не в продукте. + +спортсмеры профессионалы не идут участвовать в соревнованиях. они идут выигрывать. + +полководец не заходит в битву, если он не видит условия для победы + +деньги лежат у твоих старых заказчиков, проэкты которых ты давно закрыл + +возьмите 2-3 кейса с цифрами До и ПОСЛЕ, которые служат доказательством вашей экспертизы и идите конкурировать + +ИИ создал возможность озолотится, а вы всё ходите и продаёте часы + +офер начинается с критерия: что у вас сейча есть? а вот что мы вам може предложить чтобы это улучшить: ... + +https://www.youtube.com/watch?v=mnQX-JLi_oA \ No newline at end of file diff --git a/raw/sources/Метаанализ Inbox - продажи разработки в эпоху ИИ.md b/raw/sources/Метаанализ Inbox - продажи разработки в эпоху ИИ.md new file mode 100644 index 0000000..303c037 --- /dev/null +++ b/raw/sources/Метаанализ Inbox - продажи разработки в эпоху ИИ.md @@ -0,0 +1,139 @@ +#meta #sales #development #ai #clients + +# Мета-анализ заметок Inbox: продажа услуг разработки в эпоху ИИ + +Семь заметок (5 конспектов видео + 1 шаблон письма + 1 россыпь тезисов) фактически описывают **одну и ту же картину мира с разных углов**. Это не разрозненные темы — это связный учебник по тому, как разработчику/агентству выжить и заработать в 2026, когда ИИ обнулил почасовую разработку. + +## Карта заметок + +| Файл | Угол зрения | Уровень | +|---|---|---| +| [[Конспект]] | Афоризмы-выжимки | Принципы | +| [[Как продавать услуги по разработке дорого]] | Перепозиционирование сервисной компании | Стратегия | +| [[как реально зарабатывать на ИИ в 2026 году]] | Три пути монетизации ИИ (B2C/B2B/житейский) | Стратегия | +| [[How to Get Rich So Fast It Feels Like CHEATING]] | Метод обучения через тотальное клонирование | Мета-метод | +| [[How to get more clients as a software development agency]] | 3 шага для дев-шопа: ниша + outbound + соцсети | Тактика | +| [[17 ways to get your 1st client as a developer in 2026]] | 17 каналов привлечения клиентов в 3 уровнях | Каналы | +| [[Linked In mail template]] | Готовый шаблон первого касания | Инструмент | + +## Сквозные тезисы (повторяются у разных авторов) + +### 1. Эпоха почасовой разработки закончилась +- **Роденко:** «у заказчика появилась альтернатива за $200/мес — ИИ. Война по часовой ставке = путь в обнуление маржи» +- **Конспект:** «если ты на уровне индуса — ты и есть индус» +- **Tony (агентство):** «цена как инструмент = быстрый путь к банкротству» +- **AB Analytics:** Upwork = race to the bottom, забудьте, если вы не из третьего мира + +Согласие на 100%: продавать часы и стек = коммодити. + +### 2. Продавай результат и ответственность, а не работу +- **Роденко:** Solution vs Staff Aug — маржа 30-50% vs гонка по цене +- **Конспект:** «продавайте РЕШЕНИЯ, а не работу» +- **Конспект:** «вы продаёте ответственность, а не часы» +- **AB Analytics:** Productize услуги — DIY → DWY → **DFY** (Done For You) как высшая ступень + +### 3. Категория = боль + результат, не технология +- **Роденко:** «уберите слово «разработка» из оффера — что осталось?» +- **Tony:** «маркетинг стека (.NET-developer) не работает — продавайте аудитории, которую этот стек подразумевает» +- **AB Analytics:** «Shopify dev for fashion brands» бьёт «web developer» везде + +### 4. Ниша — это upstream всего остального +Без ниши не работает ни outbound, ни продуктизация, ни продакшн. +- **Tony:** ниша → продуктизация → масштабирование команды +- **AB Analytics:** «нишевая специфичность бьёт объём» +- **Видео про ИИ:** «решай конкретную боль, не делай платформу» + +### 5. Деньги лежат у старых заказчиков +Самый недооценённый канал во всех источниках: +- **Конспект:** «деньги лежат у твоих старых заказчиков» +- **Роденко:** позвонить 3-5 лучшим клиентам и спросить «за получение какого результата вы мне платили» +- **AB Analytics:** 91% клиентов готовы рекомендовать, спрашивают только 11% + +### 6. ИИ — это не угроза, а **фильтр квалификации** +- **Роденко:** даёте бесплатный AI-скилл на 30 дней. «Работает» = не клиент. «Слабовато, нужна конкретика» = **целевой клиент**. +- **Конспект:** «ИИ создал возможность озолотиться, а вы всё ходите часы продаёте» +- **Видео про ИИ:** на каждый $1 в LLM компания тратит ~$6 на спецов, которые это настраивают + +### 7. КОМУ важнее ЧЕГО +- **Конспект:** «самое важное в предложении — ТОТ, кому вы делаете предложение» +- **Роденко:** «80% успеха в продажах = КОМУ говорите, а не ЧТО» +- **Видео про ИИ:** выбор целевого сегмента — отдельный шаг ДО реализации +- **Роденко:** продавайте руководству, а не исполнителям (для исполнителя ваш ИИ = угроза рабочему месту) + +### 8. Дисциплина follow-up'а +- **AB Analytics:** «~80% сделок закрываются после 5-го касания; большинство сдаётся после первого» +- **AB Analytics:** каденс Day 0 → 3 → 7 → 14 → 30 +- **Конспект** косвенно: «полководец не заходит в битву, если не видит условия для победы» — методичность бьёт энтузиазм + +## Конфликты между источниками + +**Где источники расходятся:** + +1. **Контент-маркетинг (YouTube/X) — когда?** + - Tony: 3 поста в неделю на LinkedIn с самого начала + - AB Analytics: **не начинай**, пока не делаешь $10-15k/мес на outbound — иначе голодаешь + - Разрешение: LinkedIn-присутствие как «слой доверия» под outbound (Tony) ≠ контент как основной канал (AB Analytics) + +2. **Уникальность vs клонирование** + - *How to Get Rich* (Pabrai): «клонируй на 10 000%, оригинальность приходит после» + - Роденко: «бизнес покупает не уникальность, а проверенный способ» — **согласуется** + - Но видео про ИИ: «у тебя должна быть узкая ниша, куда ИИ не дотянулся» — это уже про дифференциацию + - Синтез: клонируй **операционную систему успешных** (Pabrai), но позиционируйся в **узком сегменте, где никто не воюет** (Роденко + AB Analytics) + +3. **Размер команды** + - Старая модель: 15+ человек на T&M + - Новая (Squad-model Роденко): 4 человека × ~$15-18k/мес = $7M годового оборота + - ИИ-путь: соло-фаундер с $293k/мес (Rezi) + - Тренд: **размер команды больше не сигнал серьёзности** + +## Где у тебя пробелы (что НЕ покрыто заметками) + +- **Юнит-экономика B2B-проекта:** все говорят про оффер, никто — про CAC/LTV +- **Юридическая упаковка solution-контракта** (где ответственность подкреплена SLA/неустойками — Роденко это упоминает, но без шаблонов) +- **Конкретные ниши для AI-консалтинга в СНГ/EU:** все примеры — US (Чамберы, Equinox, country clubs) +- **Кейс-стади собственной работы:** «возьмите 2-3 кейса с цифрами До/ПОСЛЕ» (Конспект) — у тебя их в Inbox нет +- **Процесс квалификации лида:** что отвечать на «мы подумаем» + +## Синтез: один план действий из всех 7 заметок + +Если свернуть всё в одну дорожную карту: + +### Неделя 1 — Аудит и позиционирование +1. Прозвонить 3-5 последних/лучших заказчиков: «за получение какого результата вы мне платили?» (Роденко) +2. Найти паттерн в самых прибыльных проектах: индустрия / тип проблемы / стек (Tony) +3. Сформулировать оффер по формуле: **«мы делаем X для [ICP], чтобы закрыть Y боль и получить Z результат»** (Роденко) +4. Применить тест на commodity: убрать слово «разработка» и название технологии — что осталось? (Роденко) + +### Месяц 1 — Первый поток +5. Выбрать **3 канала**: 1 common + 1 low-key + 1 creative (AB Analytics) + - Пример: cold email + индустриальная ассоциация / профильный чат + продуктизированный DFY-пакет +6. Использовать [[Linked In mail template]] как стартовый шаблон, но кастомизировать каждое первое касание (никаких массовых шаблонов) +7. Дисциплина follow-up: 5 касаний минимум на каждом лиде (AB Analytics) +8. Если есть знакомые с бизнесом — упрощённый B2B путь (видео про ИИ): встретился → услышал боль → решил → деньги + +### Месяцы 2-3 — Продуктизация +9. После 2-3 однотипных проектов — превратить в фиксированный DFY-пакет с именем и ценой (AB Analytics) +10. Найти свой «Zendesk-моtion»: спросить «сколько вы тратите на X?» → «а если в 10 раз меньше — обсудим?» (Роденко) +11. Когда стабильно $10-15k/мес — начать LinkedIn-контент 3×/неделю как слой доверия (Tony + AB Analytics) + +### Сквозной мета-принцип +Клонировать на 10 000% того, кто уже сделал это в твоей нише (Pabrai). **Не пытаться придумать своё до того, как освоил чужое.** Оригинальность — следствие глубокого копирования из нескольких источников, не стартовая точка. + +## TL;DR в одной фразе + +Все 7 заметок сводятся к одной мысли: +**Перестань продавать часы и стек. Найди узкую группу людей с конкретной болью, упакуй результат + ответственность в продуктизированный оффер, и стучись методично — 5 касаний, через 3 канала, 90 дней без переключений.** + +ИИ — это не то, что отнимает работу, а то, что делает старую модель невозможной, а новую — десятикратно прибыльной. Если ты не категоризировал себя сам — рынок категоризирует тебя по часовой ставке. + +--- + +## Куда это разнести (CODE → Organize) + +- Принципы → `PARA/2. Areas/` (длинная зона ответственности «продажи/позиционирование») +- Конкретный план на 90 дней → `PARA/1. Projects/` если возьмёшься делать +- Список 17 каналов и таблица сравнения подходов → `PARA/3. Resources/` как справочник +- Афоризмы из [[Конспект]] — кандидаты на отдельную атомарную заметку в Resources + +--- +*Мета-анализ от 15.06.2026 по 7 заметкам Inbox* diff --git a/raw/sources/Принципы продажи услуг разработки в эпоху ИИ.md b/raw/sources/Принципы продажи услуг разработки в эпоху ИИ.md new file mode 100644 index 0000000..046e38e --- /dev/null +++ b/raw/sources/Принципы продажи услуг разработки в эпоху ИИ.md @@ -0,0 +1,106 @@ +#sales #marketing #development #ai #positioning #pricing #outbound + +# Принципы продажи услуг разработки в эпоху ИИ + +Дистилляция из 5 источников (Конспект, Роденко/Натан, AB Analytics, Pabrai/cloning, Tony/dev-agency, видео про ИИ-монетизацию). Только timeless-принципы — без конкретных каналов и тактик. + +--- + +## 1. Природа рынка + +- **Почасовая разработка мертва.** У заказчика есть альтернатива за ~$200/мес (ИИ). Конкурировать ставкой = обнуление маржи. +- **«Дорого» не существует. Существует «не вижу, за что».** Если клиент возражает по цене, тест: «А если бы мы гарантировали результат — цена остаётся проблемой?» Да → нет денег. Нет → не было доверия к value. +- **Бизнес покупает не уникальность, а проверенный способ.** Уникально = «боюсь, не экспериментируйте на мне». +- **На каждый $1 в ИИ компания тратит ~$6 на спецов настроить.** ИИ не отнимает работу — открывает новую воронку. + +## 2. Что продавать + +- **Продавай результат и ответственность за него, а не часы.** Готов взять ответственность — эпоха ИИ озолотит. Не готов — приговор на 12 месяцев. +- **Категория = боль + результат, не технология.** Тест на commodity: убери из оффера слово «разработка» и название стека. Что осталось? Ничего → ты коммодити. +- **Solution vs Staff Augmentation: выбирай одно.** Solution — маржа 30-50%, сложно заменить. Staff aug — гонка цены, замена за неделю. Одновременно под одним брендом = всё скатится в staff aug. +- **Продуктизируй после 2-3 одинаковых проектов.** Фикс-цена, фикс-скоуп, имя пакета. DIY → DWY → **DFY** (Done For You) = высший рычаг. +- **Польза → потом фича.** Не наоборот. MVP за 7-14 дней. + +## 3. Кому продавать + +- **80% успеха в продажах = КОМУ говоришь, а не ЧТО.** Если оффер не продаётся — почти всегда не та аудитория. +- **Самое важное в предложении — ТОТ, кому его делаешь.** +- **Продавай руководству, а не исполнителям.** Для исполнителя твой ИИ = угроза рабочему месту, ты для него риск. Руководству ты выполняешь KPI. +- **Узкая ниша = там, где ИИ бессилен.** LLM не знает узких отраслевых методологий — туда и иди. +- **«Shopify dev for fashion brands» бьёт «web developer» везде.** Нишевая специфичность побеждает объём. + +## 4. Как находить боль + +- **Смотри, на что тратят, а не что говорят.** Найди операционную статью затрат → предложи сократить в 10 раз. «Сколько вы тратите на X?» → «А если бы тратили в 10 раз меньше — обсудим?» Даже если ошибся наполовину — всё равно вывел в 5×. +- **«Боль с деньгами»:** частая, стоит бизнесу денег, уже решается костылями, фаундер понимает её ценность. Без этих 4-х — не клиент. +- **Деньги лежат у твоих старых заказчиков.** Прозвон 3-5 лучших: «За получение какого результата вы мне платили?» (не «почему выбрали» — на это отвечают «хорошая команда»). + +## 5. ИИ как фильтр + +- **Не прячь ИИ — используй как тест квалификации.** Дай готовый AI-скилл бесплатно на 30 дней. Реакции: + - «Работает» → твой value не нужен. Не клиент. + - «Не взялись» → задача без бюджета. Не клиент. + - «Слабовато, нужна конкретика» → **целевой клиент**. + +## 6. Дисциплина исполнения + +- **Консистентность бьёт интенсивность.** 30 минут в день > 5 часов раз в месяц. +- **5 касаний минимум.** ~80% сделок закрываются после 5-го контакта. Большинство сдаётся после 1-го. +- **3 канала × 90 дней.** Не добавляй новые методы, пока не освоил эти. Перепрыгивание = ноль. +- **Спрашивай рекомендации сразу после доставки.** 91% клиентов готовы рекомендовать. Спрашивают только 11%. Окно энтузиазма короткое. +- **Год переупаковки нужен тем, кто боится поднять трубку.** Real-feedback за неделю > планирования за год. +- **Founder = главный sales.** Не закрепился на следующем уровне — нормально, продавать снова идёт фаундер. + +## 7. Клонирование > оригинальность + +- **Originality is downstream of cloning, not upstream.** Сначала копируй на 10 000%, потом адаптируй. +- **Клонируй скучные части.** Успех = ~1 000 мелких решений, не одно гениальное. Утренний рутин, как обрабатываешь отвлечения, как защищаешь время — копируй всё. +- **Letter of the rules > spirit of the rules — в начале.** «Дух правил» — для мастеров. Новички этим оправдывают пропуск дисциплины. +- **Парабол газовых станций:** одна вытирает лобовое и проверяет шины бесплатно, у неё очередь. Другая видит это каждый день и не повторяет. Проигравшая банкротится — не от нехватки информации, от эго. +- **Pabrai-метод:** копируй из **нескольких источников** (Buffett для инвестиций, Munger для мышления, Graham для принципов). Оригинальность = emergent property комбинации, никто не сложил те же куски тем же способом. + +## 8. Психология сделки + +- **Заказчик — не приз.** Сделка = обмен экспертизы на деньги. Не благотворительность с твоей стороны, не одолжение с его. +- **Профессионалы выбирают, в какие бои идти.** Спортсмен не «участвует в соревнованиях», он идёт **выигрывать**. Полководец не заходит в битву, если не видит условия победы. +- **Если есть один человек, купивший продукт — нет причины, чтобы другие не купили.** Проблема не в продукте, проблема в КОМ и КАК. +- **Если ты на уровне индуса — ты и есть индус, просто дороже.** +- **Знание, где подводные камни — это и есть твоя экспертиза.** + +## 9. Тактическая оснастка (минимум) + +- **Кейсы с цифрами До/ПОСЛЕ:** 2-3 штуки. Без них продавать результат нечем. +- **Шаблон первого касания:** см. [[PARA/4. Archive/15-06-2026 Inbox/Linked In mail template|Linked In mail template]] — но не используй массово, кастомизируй каждое. +- **Сабжект cold-email несёт 47% открытия.** Трать 50% времени на него. Specifically > generically: «Quick question about [Company]'s checkout flow» >> «Ideas to improve your site». +- **Webinar formula:** 60% обучение + 20% кейс + 20% оффер. Конверсия 15-25%. + +--- + +## Антипаттерны + +| Делать | Не делать | +|---|---| +| Продавать результат | Продавать часы или стек | +| Категория по боли+результату | Категория «мы разрабатываем X на Y» | +| Solution или Staff Aug под разными брендами | Обе модели на одном сайте | +| Кастомизировать каждое первое касание | Массовая рассылка одного шаблона | +| Цена через ценность | Цена как инструмент конкуренции (= банкротство) | +| Узкая ниша, где ИИ слаб | «Мы делаем всё для всех» | +| Запрашивать рекомендации сразу | Ждать «удобного момента» | +| 5 follow-up'ов до «стоп» | Один заход и забыл | +| 3 канала × 90 дней | Менять каналы каждую неделю | + +--- + +## Источники (архив) + +- [[PARA/4. Archive/15-06-2026 Inbox/Метаанализ Inbox - продажи разработки в эпоху ИИ|Метаанализ Inbox]] — связка всех 7 заметок +- [[PARA/4. Archive/15-06-2026 Inbox/Конспект|Конспект]] +- [[PARA/4. Archive/15-06-2026 Inbox/Как продавать услуги по разработке дорого|Как продавать услуги по разработке дорого]] +- [[PARA/4. Archive/15-06-2026 Inbox/как реально зарабатывать на ИИ в 2026 году|как реально зарабатывать на ИИ в 2026 году]] +- [[PARA/4. Archive/15-06-2026 Inbox/How to Get Rich So Fast It Feels Like CHEATING|How to Get Rich So Fast It Feels Like CHEATING]] +- [[PARA/4. Archive/15-06-2026 Inbox/How to get more clients as a software development agency|How to get more clients as a software development agency]] +- [[PARA/4. Archive/15-06-2026 Inbox/17 ways to get your 1st client as a developer in 2026|17 ways to get your 1st client as a developer in 2026]] + +--- +*Дистилляция от 15.06.2026 из заметок Inbox (заархивированы в `PARA/4. Archive/15-06-2026 Inbox/`)* diff --git a/raw/sources/как реально зарабатывать на ИИ в 2026 году.md b/raw/sources/как реально зарабатывать на ИИ в 2026 году.md new file mode 100644 index 0000000..c38dd4a --- /dev/null +++ b/raw/sources/как реально зарабатывать на ИИ в 2026 году.md @@ -0,0 +1,63 @@ +# Выводы по видео + +**Источник:** https://www.youtube.com/watch?v=o7c4XdtzU30 +**Название:** как реально зарабатывать на ИИ в 2026 году (пошаговый гайд) +**Длительность:** 19:20 + +--- + +Видео — практический гайд по заработку на AI в 2026 году. Автор выделяет **три пути** и для каждого даёт пошаговый пайплайн. + +## Главный тезис +Большинство AI-проектов умирают, потому что их делают по схеме «идея → закодил в Claude/GPT → запустил». Правильный путь — **сначала проверить рынок и боль, потом писать код**. + +## 1. B2C — продукт для конечного пользователя +Чек низкий ($10–50), но рынок массовый. Примеры: Rezi (резюме), StoryShort (короткие видео), Postiz (соцсети). + +Пайплайн из 6 шагов: +1. Гипотеза +2. Денежная оценка рынка (готовы ли вообще платить) +3. Масштабный ресёрч в Reddit / X / YouTube / Telegram + deep research через GPT +4. Проверка данных вручную (GPT может приврать) +5. Выбор целевого сегмента (не для всех — для конкретной аудитории) +6. И **только теперь** реализация + +## 2. B2B — продукт для бизнеса +Прибыльнее: чек $100 – $100 000+. Пайплайн проще, но требует ручной работы: + +0. Выбрать нишу, в которой комфортно (онлайн-школы, HR-агентства, юристы и т.п.) +1. Найти **много** компаний (Telegram, X, LinkedIn, Google Maps, 2GIS, HH) +2. **«Прощупать почву»** — писать в личку, задавать 3–4 вопроса о ручных задачах. Ответят ~10%. +3. Найти «боль с деньгами»: частая, стоит бизнесу денег, уже решается костылями, фаундер понимает её ценность +4. Сделать MVP за 7–14 дней — **польза важнее фич**, потом докручиваешь + +**Упрощённый вариант B2B**: если есть знакомые с бизнесом — встретился, услышал боль, решил, получил деньги. Поэтому связи важны. + +## 3. Житейский AI — услуги обычным людям +Самый простой путь: курсовые, лабораторные, презентации, тексты — всё с помощью AI. + +Пайплайн: +1. Выбрать 2–3 услуги +2. Собрать примеры работ (для друзей дёшево/бесплатно) +3. Найти клиентов +4. Завести Telegram-канал, собирать отзывы (фильтровать на положительные) +5. Шаблонизировать решения → собирать «библиотеку» + +Этот путь можно потом масштабировать в полноценный B2C или B2B продукт. + +## Реальные цифры (доказательная база автора) + +| Продукт | Тип | Доход/мес | +|---|---|---| +| Rezi | B2C | $293 256 | +| Postiz | B2C | $109 000 | +| ChatSEO | B2B (стартовал в ноябре 2025) | $16 000 | + +## Сквозные принципы +- **Решай конкретную боль**, а не «делай платформу» +- **Польза → потом фича**, не наоборот +- Хороший продукт **встраивается в существующую привычку**, а не ломает её (мысль из Postiz) +- Связи и сарафан важнее, чем выглядит + +## Кому это полезно +Тем, кто умеет работать с LLM, но застревает на этапе «что делать дальше». Это не туториал по нейронкам — это методичка по продуктовому мышлению поверх них. diff --git a/wiki/comparisons/solution-vs-staff-augmentation.md b/wiki/comparisons/solution-vs-staff-augmentation.md new file mode 100644 index 0000000..88b5ebf --- /dev/null +++ b/wiki/comparisons/solution-vs-staff-augmentation.md @@ -0,0 +1,64 @@ +# Solution vs. Staff Augmentation + +#comparison #positioning #pricing + +## Summary + +The two business models a development shop can sell, and the claim that you must pick exactly one. Primary source is now [[2026-06-15-rodenko-selling-development-expensively]] (which lays out the full table and the one valid combination); [[2026-06-15-selling-development-services-in-the-ai-era]] condenses it. The [[2026-07-17-design-the-perfect-offer]] method doesn't discuss the choice but presupposes the Solution side. + +## Side-by-Side + +| | **Solution** | **Staff Augmentation** | +|---|---|---| +| What's sold | An outcome and accountability for it | Bodies/hours slotted into the client's process | +| Margin | **30–50%** | Race to the bottom on rate | +| Replaceability | Hard to replace | **Replaced within a week** | +| Priced against | Value of the result | Competitors' hourly rates | +| Direction under AI pressure | Defensible — the buyer needs judgment | Directly substituted by the ~$200/mo alternative | +| Compatible with | [[productized-service]], [[outcome-based-selling]], [[pricing-from-value]] | Hourly billing, commodity positioning | + +## The Core Claim + +**Choose one — running both under a single brand collapses everything into staff augmentation.** + +*"Solution vs Staff Augmentation: выбирай одно… Одновременно под одним брендом = всё скатится в staff aug."* ([[2026-06-15-selling-development-services-in-the-ai-era]]) + +The anti-patterns table restates it as: Solution or Staff Aug **under separate brands** — never both models on one site. So the claim isn't that staff aug is illegitimate; it's that the two can't share a brand, because the cheaper, more legible offer wins every comparison a prospect makes. A buyer who can see an hourly rate will anchor on it, and no outcome pitch survives contact with a visible cheaper unit price. + +**The one valid combination** ([[2026-06-15-rodenko-selling-development-expensively]]): sell and deploy a **solution first**, *then* leave a person on support afterward. That gives long cash flow and continued contact — the sequence matters (solution → staff), because the relationship is anchored on the outcome before any hourly work appears. + +**Worked example — the Squad-model.** A former outstaffing shop whose seniors sat "on the shelf" next to $25/hr Indian devs stopped selling people entirely; assembled 4-person squads (2 engineers + QA + PM); chose an ICP of *startups that just raised a round*; and offered "Start in 7 days, price of two US programmers, something to show investors by month 6, or we finish at our expense." Result claimed: ~19 squads × $15–18k/mo ≈ **$7M/yr**, 90 people. It's the Solution model in one case — outcome + accountability + narrow ICP + productized package — and evidence that "you need a big T&M team" is a dogma ([[future-of-engineering-work]]: team size is no longer a signal). + +## Why It Matters Here + +This is the structural precondition for most of the vault: + +- [[pricing-from-value]] is unavailable to a staff-aug brand — rate comparison is the buyer's default frame. +- [[methodology-as-moat]] can't develop when you're supplying bodies to someone else's method. +- [[ai-market-shift]] makes the choice urgent rather than academic: staff aug is precisely the undifferentiated execution the ~$200/mo substitute attacks, while Solution work is the "$6 spent per $1 of AI" side of the same shift. + +## Evidence + +- **Primary:** the full Solution vs Staff-Aug table, the "collapses into staff aug" claim, the one valid combination (solution → support), and the Squad-model example — [[2026-06-15-rodenko-selling-development-expensively]] +- Condensed: "выбирай одно… Solution — маржа 30-50%… Одновременно под одним брендом = всё скатится в staff aug" — [[2026-06-15-selling-development-services-in-the-ai-era]] +- Implicit: the entire offer-design method assumes Solution — [[2026-07-17-design-the-perfect-offer]] + +## Related Pages + +- [[productized-service]] — the Solution model's delivery form +- [[pricing-from-value]] — the margin consequence +- [[ai-market-shift]] — why staff aug is the exposed side +- [[outcome-based-selling]] — what Solution actually sells +- [[overview]] + +## Contradictions / Uncertainty + +- **Stated as a law, with no counter-example examined.** `Status: tentative`. Firms plausibly do run both under separate brands or business units — the source allows this — but the claim that a single brand *always* collapses is asserted from experience, not demonstrated. +- The 30–50% margin figure and the $7M Squad-model numbers are the speaker's ([[dmitry-rodenko]]) own anecdotes — attributable now, still uncorroborated. +- **The transition is partly addressed after all:** the "solution → then leave a person on support" combination is exactly a staged path, but the source doesn't cover a shop currently *living on* staff-aug revenue funding the switch to Solution — where the choice actually bites for a small operator. + +## Next Questions + +- Is there a documented case of both models coexisting under one brand successfully? +- What's the sequence for a shop currently living on staff-aug revenue — how do you fund the switch? +- Does the collapse mechanism depend on the two offers being visible to the *same* buyers? diff --git a/wiki/concepts/ai-market-shift.md b/wiki/concepts/ai-market-shift.md new file mode 100644 index 0000000..bb60dba --- /dev/null +++ b/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? diff --git a/wiki/concepts/ai-productivity-evidence.md b/wiki/concepts/ai-productivity-evidence.md new file mode 100644 index 0000000..08d9514 --- /dev/null +++ b/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)? diff --git a/wiki/concepts/client-acquisition-channels.md b/wiki/concepts/client-acquisition-channels.md new file mode 100644 index 0000000..fdb6703 --- /dev/null +++ b/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? diff --git a/wiki/concepts/cloning-over-originality.md b/wiki/concepts/cloning-over-originality.md new file mode 100644 index 0000000..66c38ca --- /dev/null +++ b/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? diff --git a/wiki/concepts/future-of-engineering-work.md b/wiki/concepts/future-of-engineering-work.md new file mode 100644 index 0000000..945848b --- /dev/null +++ b/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? diff --git a/wiki/concepts/information-vs-implementation.md b/wiki/concepts/information-vs-implementation.md new file mode 100644 index 0000000..d152dcc --- /dev/null +++ b/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? diff --git a/wiki/concepts/marketing-system.md b/wiki/concepts/marketing-system.md new file mode 100644 index 0000000..40b782f --- /dev/null +++ b/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. diff --git a/wiki/concepts/methodology-as-moat.md b/wiki/concepts/methodology-as-moat.md new file mode 100644 index 0000000..c7daebb --- /dev/null +++ b/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? diff --git a/wiki/concepts/niche-selection.md b/wiki/concepts/niche-selection.md new file mode 100644 index 0000000..17ac01d --- /dev/null +++ b/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? diff --git a/wiki/concepts/offer-ladder.md b/wiki/concepts/offer-ladder.md new file mode 100644 index 0000000..00e18a1 --- /dev/null +++ b/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? diff --git a/wiki/concepts/outcome-based-selling.md b/wiki/concepts/outcome-based-selling.md new file mode 100644 index 0000000..243f33c --- /dev/null +++ b/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? diff --git a/wiki/concepts/pain-discovery.md b/wiki/concepts/pain-discovery.md new file mode 100644 index 0000000..a181085 --- /dev/null +++ b/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? diff --git a/wiki/concepts/partnerships.md b/wiki/concepts/partnerships.md new file mode 100644 index 0000000..511fd4b --- /dev/null +++ b/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? diff --git a/wiki/concepts/pricing-from-value.md b/wiki/concepts/pricing-from-value.md new file mode 100644 index 0000000..a3d21f8 --- /dev/null +++ b/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.) diff --git a/wiki/concepts/product-ownership.md b/wiki/concepts/product-ownership.md new file mode 100644 index 0000000..69edd2c --- /dev/null +++ b/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? diff --git a/wiki/concepts/productized-service.md b/wiki/concepts/productized-service.md new file mode 100644 index 0000000..18a721c --- /dev/null +++ b/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. diff --git a/wiki/concepts/referrals.md b/wiki/concepts/referrals.md new file mode 100644 index 0000000..916b767 --- /dev/null +++ b/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. diff --git a/wiki/concepts/relationships-as-moat.md b/wiki/concepts/relationships-as-moat.md new file mode 100644 index 0000000..023cf13 --- /dev/null +++ b/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? diff --git a/wiki/concepts/sales-channel-as-moat.md b/wiki/concepts/sales-channel-as-moat.md new file mode 100644 index 0000000..079452d --- /dev/null +++ b/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? diff --git a/wiki/concepts/sales-discipline.md b/wiki/concepts/sales-discipline.md new file mode 100644 index 0000000..7e01f8e --- /dev/null +++ b/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? diff --git a/wiki/concepts/sell-before-build.md b/wiki/concepts/sell-before-build.md new file mode 100644 index 0000000..2ab92fd --- /dev/null +++ b/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? diff --git a/wiki/concepts/seniority-and-ai.md b/wiki/concepts/seniority-and-ai.md new file mode 100644 index 0000000..1674b5d --- /dev/null +++ b/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? diff --git a/wiki/concepts/tam-sam-som.md b/wiki/concepts/tam-sam-som.md new file mode 100644 index 0000000..7b5e974 --- /dev/null +++ b/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? diff --git a/wiki/concepts/team-growth-ceiling.md b/wiki/concepts/team-growth-ceiling.md new file mode 100644 index 0000000..b2b7095 --- /dev/null +++ b/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. diff --git a/wiki/concepts/technical-founder-trap.md b/wiki/concepts/technical-founder-trap.md new file mode 100644 index 0000000..fb0f82a --- /dev/null +++ b/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.) diff --git a/wiki/concepts/unit-economics.md b/wiki/concepts/unit-economics.md new file mode 100644 index 0000000..ee07072 --- /dev/null +++ b/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?)? diff --git a/wiki/concepts/venture-fit.md b/wiki/concepts/venture-fit.md new file mode 100644 index 0000000..2a4d729 --- /dev/null +++ b/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? diff --git a/wiki/entities/ab-analytics.md b/wiki/entities/ab-analytics.md new file mode 100644 index 0000000..5e84ffd --- /dev/null +++ b/wiki/entities/ab-analytics.md @@ -0,0 +1,35 @@ +# AB Analytics (and Code to CEO) + +#entity #organization + +## Summary + +A B2B AI-consulting firm in LA, run by the (unnamed) speaker of [[2026-06-15-17-ways-first-client]], who also runs the *Code to CEO* startup accelerator. The source of this vault's client-acquisition channel taxonomy, follow-up statistics, and the DIY→DWY→DFY productization ladder. + +## Current Understanding + +- **Positioning:** the founder claims he went from ~$250k/yr as a developer to roughly double that after starting the consulting firm, and became known in LA as "the AI guy" via in-person channels (car shows, premium gyms, Chamber of Commerce). +- **Signature methodology:** *fish where no one else is fishing* — 17 channels in three tiers (common / low-key / out-of-the-box); pick 3 (one per tier) and run them 90 days; follow up ≥5 times; niche specificity beats volume. → [[client-acquisition-channels]], [[sales-discipline]]. +- **Productization as "the single biggest change to his client acquisition"** — DIY → DWY → **DFY** (his current focus). → [[productized-service]]. +- **Code to CEO:** the accelerator through which his named example founders ("Paul," "John," "Dom") appear. + +## Evidence + +- Firm, accelerator, channels, statistics, and ladder — [[2026-06-15-17-ways-first-client]] + +## Related Pages + +- [[client-acquisition-channels]] — the channel taxonomy this org originates +- [[sales-discipline]] — the follow-up cadence and consistency rules +- [[productized-service]] — the DFY ladder +- [[relationships-as-moat]] — its heavy Tier-2 in-person channels partly agree with [[sebastian]], while its Tier-1 online channels contradict him + +## Contradictions / Uncertainty + +- **Promotional context.** The speaker plugs Code to CEO throughout, and the success stories are accelerator members. The raw note explicitly says to treat the metrics as marketing-flavored claims, not independent data. +- Tactics assume disposable income and a major US city (Equinox, country clubs, high-end hotels) — geographically/economically specific. + +## Next Questions + +- What is the firm's actual name/track record beyond the video's self-report? +- Which of the 17 channels does the founder actually rely on now, vs. which are content filler? diff --git a/wiki/entities/claude-code.md b/wiki/entities/claude-code.md new file mode 100644 index 0000000..8008e7d --- /dev/null +++ b/wiki/entities/claude-code.md @@ -0,0 +1,42 @@ +# Claude Code + +#entity #tool #ai + +## Summary + +Anthropic's agentic coding tool (CLI/agent). The vault's first *tool* entity — created 2026-07-29 because the corpus has begun assigning it roles well beyond writing code, and because it is the harness this vault itself runs on. + +## Current Understanding + +Three distinct roles the corpus gives it: + +| Role | Claim | Source | +|---|---|---| +| **Build engine / commoditizer** | "Everyone has 10–15 great products sitting in Cloud Code" — products become cheap, distribution becomes the scarcity | [[2026-07-26-how-to-build-a-billion-dollar-company-2027]] ([[oskar-hartmann]]) | +| **Full GTM stack** | Landing page, invented company identity, scraped prospect list, cold-outbound script, then the product — the human only picks the service and closes | [[2026-07-29-start-a-business-with-claude-code]] ([[dan-martell]]) | +| **Domain tutor / leveler** | "Whatever business you want to be in, Claude will also tell you how to do it" — collapses the no-expertise barrier to starting | [[2026-07-29-start-a-business-with-claude-code]] ([[dan-martell]]) | + +Adjacent, not about the product itself: the [[2026-07-06-sebastian-interview-ai-and-software-engineering|Sebastian interview]]'s enterprise-harness thesis (companies will pay for compliant, managed wrappers around exactly this class of tool — [[future-of-engineering-work]]), and [[eugene]]'s bring-your-own-harness practice. + +## Evidence + +- Vibe-coding product glut ("Cloud Code" = this tool, near-certainly) — [[2026-07-26-how-to-build-a-billion-dollar-company-2027]] +- The 5-step $0→$1M playbook with Claude Code executing steps 2–4 and the build — [[2026-07-29-start-a-business-with-claude-code]] ([[dan-martell]], owner-attributed 2026-07-29) +- Capability counter-evidence: measured AI coding gains are modest and novice-tilted; experts slowed in RCT — [[2026-07-18-ai-productivity-adversarial-evidence]] via [[ai-productivity-evidence]] + +## Related Pages + +- [[ai-market-shift]] — the roles table there is the market-side generalization of this page +- [[sell-before-build]] — the playbook this tool is cast as executing +- [[future-of-engineering-work]] — the harness market it anchors +- [[eugene]], [[dan-martell]], [[oskar-hartmann]], [[overview]] + +## Contradictions / Uncertainty + +- The corpus's claims about the tool trace to exactly **two voices** — [[dan-martell]] (GTM stack, leveler) and [[oskar-hartmann]] (build engine/commoditizer) — both promotional, zero demonstrated cases; the one empirical page in the vault ([[ai-productivity-evidence]]) qualifies the capability premise. The leveler claim, however, targets novices-in-a-domain — the segment the same evidence says gains *most* — so the evidence cuts less against it than against expert-productivity claims. +- "Cloud Code" in the Hartmann source is a transcription of this product's name — near-certain, marked as an inference. + +## Next Questions + +- Is there any documented (non-promotional) case of a business whose GTM assets were substantially Claude-Code-generated and which reached revenue? +- Where is the line between "Claude tells you how" and regulated/physical domain knowledge it can't stand behind? diff --git a/wiki/entities/dan-martell.md b/wiki/entities/dan-martell.md new file mode 100644 index 0000000..717406b --- /dev/null +++ b/wiki/entities/dan-martell.md @@ -0,0 +1,85 @@ +# Dan Martell + +#entity #person + +## Summary + +Founder coach behind **five confirmed** vault sources: [[2026-07-20-referrals-will-sink-your-business]] (coaching a founder stalled at ~$1.5M), [[2026-07-22-stop-cold-calling-do-this-instead]] (the partnerships lever, from his own enterprise-sales history), [[2026-07-23-make-my-first-100k-in-month]] (the $0→$100K/month blueprint — named in the raw note; self-described as having built and sold 3 multi-million-dollar companies), and two previously-unattributed clips confirmed by the vault owner — [[2026-07-19-your-company-cant-outgrow-your-team]] (confirmed 2026-07-20) and [[2026-07-29-start-a-business-with-claude-code]] (confirmed 2026-07-29; a 42-second compression of his $0 protocol with [[claude-code]] executing every pre-close step). He is also the **near-certain author of [[2026-07-18-information-is-free-implementation-is-paid]]** and a plausible author of [[2026-07-17-design-the-perfect-offer]] (see Contradictions), which would make him the voice behind up to **7 of the vault's 20 sources**. He is the vault's first named voice arguing that **organic content is the growth engine** and that **referral dependency is a symptom, not an achievement**, which puts him in direct opposition to [[sebastian]] on channels and makes him the primary voice behind [[information-vs-implementation]]. + +He is also **the only source spanning two branches** of the vault — Branch A (selling) and Branch C (running the team) — which is what makes the attribution consequential: [[team-growth-ceiling]] and [[marketing-system]] stop being independent pages and become two applications of one worldview. + +## Current Understanding + +Martell's positions as captured (see the source page for detail): + +- **Referral-only growth is a failed primary strategy** — proof a marketing system was never built. The ceiling is the missing system, not the market. → [[referrals]], [[marketing-system]] +- **Three levers only — content, paid ads, partnerships. Pick one, own it 90 days.** → [[client-acquisition-channels]] +- **"The new paid is organic."** Content-shaped ads win; promote an organic piece that already worked; without a creative pipeline, paid ads burn cash. → [[marketing-system]] +- **Technical founders can solve but can't explain**, and explanation is the unlock. → [[technical-founder-trap]] +- **Measure reps, not views** — you control volume, not virality. *"Most of you get bored with your marketing before the market ever does."* → [[sales-discipline]] +- **Six months before the system produces leads**; 6–18 months to take $1.5M to $10M. +- Practises what he prescribes: daily live, two reels a day, phone only. + +From the third source ([[2026-07-22-stop-cold-calling-do-this-instead]], Branch A — added 2026-07-22): + +- **Pipeline or hope** — a business either has a repeatable pipeline (attention → conversion → customer) or it stops growing; if you can't state yours in one sentence, you have hope. +- **Three pipeline sources — Publish, Paid, Partners** — the same taxonomy as the referrals clip, restated; pick one and go all in. +- **Partnerships is the fastest lever for enterprise** — borrowed credibility walks you in pre-sold; cold enterprise outbound is "the hardest path" (his own four years of it). → [[partnerships]] +- **Systematize the lucky partner** — reverse-engineer the one that worked, recruit the archetype ("professional recruiter of system integrators"); *ten good partners can replace an outbound sales team*. +- Self-reported: one integrator → 7 NJ pharma companies; $95K contracts three weeks post-intro. Unverified. + +From the fourth source ([[2026-07-23-make-my-first-100k-in-month]], Branch A — added 2026-07-23; his only material addressed to a **$0 operator** rather than a stalled scaler): + +- **$0→$100K/month is a sequence problem** — money math → productized service → three-tier decoy offer → demand → close. Marketing before building, always (his first company died building-first; his second, Flowtown, rode blog content to a claimed 350K visitors / 50K customers). +- **The money map:** ~100 customers × ~$1K/month is the sweet spot; $1K/mo minimum, below $10K; he *dislikes* the 10×$10K model. → [[pricing-from-value]], [[offer-ladder]] +- **People buy time, money, or status**; at $1K+/mo sell to business owners. → [[outcome-based-selling]] +- **Inbound + outbound in parallel from day zero** — phone-mining, "ask past the person," then chat-DM or cold-call close; 100 no's/day; spend nothing until customers pay. → [[sales-discipline]], [[referrals]] +- **Pre-sell waitlist ($50 top-of-list) before building anything.** → [[productized-service]] + +From the fifth source ([[2026-07-29-start-a-business-with-claude-code]], Branch A — attributed 2026-07-29; his shortest format, the $0 protocol compressed to 42 seconds with [[claude-code]] as the executor): + +- **AI as the entire pre-product stack** — landing page, invented company name, waitlist, scraped prospect list, cold-outbound script; the human's residual jobs are picking the service and closing. → [[client-acquisition-channels]], [[sell-before-build]] +- **"Whatever business you want to be in, Claude will also tell you how to do it"** — domain knowledge on demand; the blocker is psychological ("stop pretending not to know"). → [[ai-market-shift]] (the Leveler role — his first claim in that table) +- **Distribution is the moat, not code** — the product is the *last* step; consistent with his marketing-system machine framing. → [[sales-channel-as-moat]] +- Two compressions against his own fuller protocol, recorded as within-author drift: the waitlist here is **unpaid** (his 07-23 rule makes the $50 *paid* slot the load-bearing detail), and the front is an **invented company** (deception-shaped, cost unmodeled). Likely short-form lossiness, but the drift is his, not a transcription artifact. + +From the second source ([[2026-07-19-your-company-cant-outgrow-your-team]], Branch C): + +- **A company can only grow as fast as its people** — state the growth math out loud; *"Good got you on the team. Great keeps you on the team."* → [[team-growth-ceiling]] +- **Teach a philosophy, not a task list** — his "Business Athlete" framework (only 2 of 7 practices captured: *have a coach*, *have a practice schedule*). +- **Public scoreboard, private criticism**; the Netflix **Keeper Test**; **values as hire → inspire → fire** (*"Values aren't what you say they are. They're what you tolerate."*). + +**The through-line across all five.** His diagnosis is always that **the ceiling is never the market** — a stalled company is stalled on its people, a stalled revenue line is stalled on a missing system. The fixes run on one engine: **deliberate practice at volume** (*"practice until we can't get it wrong"* internally, *"the volume of the reps"*, "100 no's per day" externally), **systematize what worked by luck** (a good partner isn't a relationship to keep, it's a pattern to reverse-engineer and recruit at scale), and — made explicit by the fourth source — **sequence over effort** (*every failure he describes is right steps, wrong order*). Every clip converts an accident into a machine. Coherent worldview; see Contradictions for why the coherence isn't evidence. + +## Evidence + +- Branch A positions — [[2026-07-20-referrals-will-sink-your-business]], [[2026-07-22-stop-cold-calling-do-this-instead]], [[2026-07-23-make-my-first-100k-in-month]] (the latter two name him in the raw notes — documentary attribution) +- Branch C positions — [[2026-07-19-your-company-cant-outgrow-your-team]]; authorship confirmed by the vault owner 2026-07-20 (the clip names no speaker) +- Claude-Code playbook — [[2026-07-29-start-a-business-with-claude-code]]; authorship confirmed by the vault owner 2026-07-29 (the short names no speaker) +- Self-reported personal cadence (daily live + 2 reels), enterprise war stories (7 pharma intros, $95K contracts), and track record (3 companies built/sold; Flowtown 350K visitors → 50K customers; "8 figures sold by chat") — his own clips; unverified +- Suspected authorship of [[2026-07-18-information-is-free-implementation-is-paid]]: the 07-23 source reuses its scramble trick, its "nuanced and observable problems" AI prompt, and its "describe their pain better than they can" line **verbatim** — three distinctive mechanisms, same wording, in a source that names him. Inference, not confirmation; `Status: tentative` + +## Related Pages + +- [[marketing-system]] · [[partnerships]] · [[technical-founder-trap]] · [[referrals]] · [[client-acquisition-channels]] · [[information-vs-implementation]] · [[sales-discipline]] · [[claude-code]] +- [[team-growth-ceiling]] — his Branch C material; the internal-facing half of the same worldview +- [[sebastian]] — his direct opposite on whether online content works at all +- [[overview]] + +## Contradictions / Uncertainty + +- **Five confirmed sources, one voice — do not treat them as corroboration.** All are his own coaching clips. Restatements across clips (three levers, scramble trick, $1K price point, sell-first/build-last) confirm the frameworks are stable for him and add zero independent weight. Every figure ($1.5M→$10M, ~18 months, six-month lag, $95K/7-pharma, 350K→50K, 8-figures-by-chat, "$0→$1M") is unsourced. He authors **5 of the vault's 20 sources** — the largest single-voice share; see [[index]] Known Gaps on source independence. `Status: tentative` throughout. +- **The single-voice share may really be 7 of 20.** Near-certain: [[2026-07-18-information-is-free-implementation-is-paid]] (verbatim mechanism overlap — see Evidence). Plausible: [[2026-07-17-design-the-perfect-offer]] — its signature offer is *"buy back 10 hours of your time per week"* (Buy Back Your Time is Martell's book and flagship frame), its core price ($997/mo) matches his $1K sweet spot, and its chat-first close matches his "8 figures by chat." If both hold, the vault's *entire US-coaching pole* on offers/content is substantially one person, and "cross-source" agreement inside that pole (e.g. the $1K floor appearing in both 07-17 and 07-23) is self-agreement. Awaiting owner confirmation, as with the 07-19 clip. +- **He contradicts himself across clips, scope unstated.** (1) Cold calling: "the hardest path" for enterprise (07-22) vs. a prescribed closing channel for SMB (07-23). (2) Channel count: pick **one** lever for 90 days (07-20/07-22) vs. inbound + outbound **in parallel** from day zero (07-23). (3) Deal size: "personally dislikes" 10×$10K (07-23) vs. a $10K+ ACV partnerships playbook (07-22). All three plausibly resolve by **stage/segment** ($0 SMB start vs. $1.5M+ scale, SMB vs. enterprise buyer) — but no clip states the boundary, so the reconciliations are the vault's inference. Recorded on [[client-acquisition-channels]], [[marketing-system]], [[partnerships]]. +- **Incentive alignment, and it runs deeper than the usual caveat.** He sells founder coaching, and his diagnosis is *always* that the constraint is internal and fixable — people who stopped growing, a system never built. That is a worldview in which coaching is by construction the answer. It may still be right; it is not disinterested. Note too that *"have a coach"* is one of his seven Business Athlete practices. Held to the same standard the vault applies to [[ab-analytics]] and [[dmitry-rodenko]]. +- **His strongest rhetorical evidence is his weakest logical evidence** — the Tones and I / Oliver Anthony viral anecdotes are survivorship selection (see the source page). +- **Attribution provenance.** The 07-19 and 07-29 authorships rest on the vault owner's confirmation, not documentary citations; neither clip names a speaker. Solid enough to act on, worth remembering if it ever matters. + +## Next Questions + +- Is the pick-*one*-lever rule reconcilable with [[ab-analytics]]'s pick-*three*-channels rule, or is one of them wrong? Both use the same 90-day unit. +- ✅ ~~He names *partnerships* as a lever and never explains it~~ — answered 2026-07-22: [[2026-07-22-stop-cold-calling-do-this-instead]] → [[partnerships]]. It *does* overlap with referral partners ([[referrals]]) — same warm-intro output, but recruited rather than derived, which is what gives it a throttle. +- ✅ ~~Does his advice have anything to say to a pre-first-client operator?~~ — answered 2026-07-23: [[2026-07-23-make-my-first-100k-in-month]] is addressed squarely at $0 (phone-mining, ask-past-the-person, chat/cold-call close, pre-sell before building). The open question is now the **seam** between his start protocol and his scale protocol: at what point do "run both engines" and "cold-call SMBs" hand over to "pick one lever" and "partners, not cold calls"? +- **Confirm or refute the suspected authorship** of [[2026-07-18-information-is-free-implementation-is-paid]] (near-certain) and [[2026-07-17-design-the-perfect-offer]] (plausible) — one owner check settles whether he holds 5, 6, or 7 of 20 sources. (The 07-29 short shows the owner *can and does* resolve these on request — the two standing checks are the same ask.) +- **Recover the full Business Athlete framework** (5 of 7 practices and the three values are missing) — now sourceable, since the author is known. It would fill out Branch C from one clip to a framework. +- Does the "ceiling is never the market" frame ever fail? A founder in a genuinely small or shrinking market is the obvious counter-case, and neither clip admits one exists. diff --git a/wiki/entities/dmitry-rodenko.md b/wiki/entities/dmitry-rodenko.md new file mode 100644 index 0000000..109db54 --- /dev/null +++ b/wiki/entities/dmitry-rodenko.md @@ -0,0 +1,39 @@ +# Dmitry Rodenko (Дмитрий Роденко) + +#entity #person + +## Summary + +Speaker (with co-host Nathan) of the video [[2026-06-15-rodenko-selling-development-expensively]], associated with "SaaS Founders." He is the single most-cited source behind this vault's sales methodology — the origin of the guarantee test, the Zendesk canonical offer, the commodity test, and the Solution-vs-Staff-Aug framing. + +## Current Understanding + +Rodenko's core methodology (see the source page for detail): + +- **Hourly development is ending; sell result + accountability.** A ~$200/mo AI alternative makes rate wars a path to zero margin. +- **"Expensive" doesn't exist — "I don't see what for" does**, tested by the guarantee question. → [[pricing-from-value]]. +- **Commodity test:** remove "development" and the stack name; if nothing meaningful remains, you compete on rate. **Category = pain + result.** → [[productized-service]], [[niche-selection]]. +- **The Zendesk motion:** ask real spend on a concrete operational action, promise a 10× cut. → [[pain-discovery]]. +- **Sell to leadership, not implementers; 80% of sales is WHO.** → [[niche-selection]]. +- **Business buys a proven method, not uniqueness.** → [[methodology-as-moat]]. +- **Founder = head of sales; "a year of repackaging is for people afraid to pick up the phone."** → [[sales-discipline]]. +- **Squad-model** repositioning example (~19 squads × $15–18k/mo ≈ $7M/yr). → [[solution-vs-staff-augmentation]]. + +## Evidence + +- All of the above — [[2026-06-15-rodenko-selling-development-expensively]] and its terse companion [[2026-06-15-konspekt-aphorisms]] +- His claims propagate through the derived [[2026-06-15-selling-development-services-in-the-ai-era]] and [[2026-06-15-meta-analysis-selling-dev-in-ai-era]] + +## Related Pages + +- [[pricing-from-value]] · [[outcome-based-selling]] · [[pain-discovery]] · [[niche-selection]] · [[methodology-as-moat]] · [[solution-vs-staff-augmentation]] · [[sales-discipline]] + +## Contradictions / Uncertainty + +- His anecdotes (a $100k close from 10 calls; the $7M squad shop) are self-reported in a talk — plausible, uncorroborated. +- The distillation attributes some cross-cutting statistics to "Роденко" that actually belong to other notes (e.g. follow-up rates trace to [[2026-06-15-17-ways-first-client]]); attributions in second-order notes are imperfect. + +## Next Questions + +- What is "SaaS Founders" and how does Rodenko's own business validate the methodology? +- How does Nathan's contribution differ from Rodenko's? The notes don't separate them. diff --git a/wiki/entities/eugene.md b/wiki/entities/eugene.md new file mode 100644 index 0000000..3a0e1b4 --- /dev/null +++ b/wiki/entities/eugene.md @@ -0,0 +1,52 @@ +# Eugene + +#entity #person + +## Summary + +The interviewer in [[2026-07-06-sebastian-interview-ai-and-software-engineering]]: a hands-on computer-vision & embedded/firmware developer, content creator, and builder of a custom Claude Code "harness." His lens is individual leverage and getting closer to the client's real problem. He appears likely to be the owner of this vault (see Contradictions / Uncertainty). + +## Current Understanding + +Eugene's signature positions: + +- **"Build your own harness."** Every developer should build a personal harness on top of Claude Code; knowing every detail makes it far more effective. He demoed his own: a Telegram-like UI, one agent per project, inter-agent messaging, per-agent memory, a "done thinking" signal so you don't babysit the console. Tools he references: **Conductor** (git-worktree-per-chat, automated PRs/merges). See [[future-of-engineering-work]]. +- **His stated unsolved problem (stuck ~6 months): how to build a professional network.** Sebastian's "connections are everything" answer is aimed squarely at this — see [[relationships-as-moat]]. Eugene had been investing in LinkedIn/articles; the interview's takeaway for him is to reallocate to recurring in-person events. + - **A target for the networking itself (added 2026-07-22).** [[partnerships]] reframes "build a network" — vague, and stuck for 6 months — as **recruit a specific partner archetype**: identify who already holds trust with his target buyers (for CV/embedded work, plausibly industrial-equipment vendors and machine-builder integrators — untested inference), find the events *they* attend, win individuals. This composes with both diagnoses below rather than competing: it supplies the criterion that makes showing up purposeful, and a partner intro partially substitutes for self-articulation because the partner does the vouching. Same-author, anecdote-grade source ([[dan-martell]]). + - **A concrete day-one outbound move (added 2026-07-23).** [[2026-07-23-make-my-first-100k-in-month]] supplies the cheapest test of the network blocker: mine existing phone contacts and **"ask past the person"** ("do you know anyone with this problem?") — warm, referral-shaped intros that require no past clients and no publishing ([[referrals]]). Costs an afternoon; would also produce the first real data on whether his network is thin or merely unasked. + - **A stage/format mismatch worth naming (added 2026-07-23).** The same source's recommended shape — ~100 SMB customers × ~$1K/mo, closed by chat-DM and cold calls — fits CV/embedded work poorly: his natural deals look like few × $10K+ (the "enterprise-lite" shape Martell dislikes at $0 but serves with [[partnerships]] at scale). Applying the blueprint to him likely means keeping its *sequence* (offer → pre-sell → build; phone-mining outbound) while rejecting its price×count sweet spot. Vault inference, untested. + - **A pre-build validation checklist he can run this week (added 2026-07-26).** [[sell-before-build]] ([[2026-07-26-main-principle-of-successful-business]]) turns the vault's validate-first rule into concrete moves for his situation: name the smallest group with the most acute pain **by name** (10 concrete industrial-equipment/machine-builder prospects), walk to them and ask what they'd pay for *right now*, and structure the first offer so some payment lands **before** the build (deposit-backed audit or discovery sprint — the services analogue of a paid waitlist). Wizard-of-Oz applies directly: deliver the first CV-inspection value semi-manually before automating the pipeline. Composes with the phone-mining/ask-past-the-person move below — that supplies the prospect list, this supplies what to test on it. + - **Two cheap self-tests from the vault's newest voice (added 2026-07-26).** [[2026-07-26-how-to-build-a-billion-dollar-company-2027]] ([[oskar-hartmann]]) supplies founder-facing checks that apply to him directly: (1) the **SOM question** — not "CV/embedded services" but the narrow segment he can win *now* (his industrial-equipment/machine-builder direction is exactly the "AI agent for HVAC contractors" shape Hartmann endorses); (2) the **pricing-power probe** — raise the price on the next quote and watch, the cheapest PMF test available ([[pricing-from-value]]). The same source also seconds his implicit funding default: a niched services operation is in the 99% venture doesn't fit, and per [[venture-fit]] that is a sound place to be, not a failure. Caveat for the partnerships route he's been pointed at: Hartmann's warning that partner hopes disappoint (and whale clients stall past a solo operator's runway) argues for *many small partner bets* over one anchor partner — see [[partnerships]]. + - **A rival diagnosis of the same blocker (added 2026-07-20).** [[technical-founder-trap]] proposes that the missing skill for a technical operator is not networking but **explaining what you do** — solving comes free, articulating doesn't. On this reading his LinkedIn/articles effort failed less because the channel is wrong than because the message wasn't yet legible to a non-engineer. The two diagnoses are testable against each other and imply different fixes (show up in rooms vs. get reps at explaining); the vault has no evidence to choose. Note also that a referral only travels if the referrer can *repeat* what you do in a sentence — which makes articulation upstream of the relational engine too, not an alternative to it ([[referrals]]). +- **Skeptical of open source** as mostly marketing ("gambling for questionable results"). + +Notable work named in the interview: **insin** (an apt-get-style edge/device updater) and **Keller**. + +## Evidence + +- Role, background, harness demo, and the networking problem — [[2026-07-06-sebastian-interview-ai-and-software-engineering]] +- "Fundamentally I'm Eugene — I'm not a programmer. But I need to work on that." (agreeing with the identity-decoupling point) + +## Related Pages + +- [[sebastian]] — his interlocutor +- [[future-of-engineering-work]] — the BYO-harness thesis +- [[relationships-as-moat]] — the connections problem he's trying to solve +- [[client-acquisition-channels]] — his LinkedIn/content investment vs Sebastian's in-person rule +- [[technical-founder-trap]] — the rival diagnosis of that same blocker +- [[marketing-system]] — whether his acquisition should be a machine he can turn up, and when +- [[partnerships]] — the lever that may fit him best: networking with a partner-archetype criterion instead of publishing +- [[sell-before-build]] — the validation checklist runnable against his offer before any build +- [[2026-07-26-eugene-90-day-plan]] — the dated plan assembled from all of the above +- [[2026-07-17-best-method-first-client]] — its undated predecessor (method, not schedule) + +## Contradictions / Uncertainty + +- **Likely the vault owner.** `Status: tentative`. Internal evidence: the interview names his project **insin** (apt-get-style edge updater) and his custom Claude Code harness; the owner's environment includes `insin` tooling and this vault is maintained through a Claude Code harness. Strong but circumstantial — recorded as inference, not asserted as fact. +- Surname not given; "Eugene" is the only handle available. + +## Next Questions + +- ✅ **Resolved 2026-07-26** — the dated 90-day plan now exists: [[2026-07-26-eugene-90-day-plan]] (one lever / three venues, warm mining → recurring industry room → partner archetype; paid diagnostic as the smallest paid test; Day-90 gate on inputs). It supersedes the undated method answer in [[2026-07-17-best-method-first-client]] without replacing it. **The plan's own weakest joints are now his open questions:** which specific association/trade fair meets often enough for the 3×/6× mechanic, and whether an industrial buyer pays for a diagnostic at all. +- **The two rival diagnoses of his blocker are now testable, cheaply.** The 90-day plan's Week 2 phone mine doubles as the discriminator: contacts who engage but can't restate what he does ⇒ [[technical-founder-trap]]; contacts who restate it but know nobody ⇒ [[relationships-as-moat]]. Vault synthesis, no source proposes it — but it costs an afternoon and the vault has had no way to choose between the two diagnoses since 2026-07-20. +- Did the in-person-networking advice change his channel allocation? (No follow-up source yet.) diff --git a/wiki/entities/mohnish-pabrai.md b/wiki/entities/mohnish-pabrai.md new file mode 100644 index 0000000..776a734 --- /dev/null +++ b/wiki/entities/mohnish-pabrai.md @@ -0,0 +1,38 @@ +# Mohnish Pabrai + +#entity #person + +## Summary + +Investor cited as the central case study in [[2026-06-15-how-to-get-rich-cloning]] and the namesake of the "Pabrai method" behind [[cloning-over-originality]]. Presented as living proof that shameless, total, multi-source cloning — not originality — is the fast path to mastery. + +## Current Understanding + +Per the source (claims as presented, not independently verified here): + +- **Cloned Warren Buffett wholesale** after reading, at Heathrow, that Buffett returned 31%/yr for 40+ years: read every letter, watched every interview, attended the Berkshire annual meeting 20+ years, copied the morning routine, business structure, 5–6 hrs daily reading, and working alone. Outcome ~**$154M**. +- **Guru dakshina:** in 2007 paid **$650,000** for a charity lunch with Buffett, framed as the Hindu gift to a teacher when education is complete. +- **Multi-source cloning:** Buffett for investing, **Charlie Munger** for thinking, **Benjamin Graham** for principles, philosophers for life decisions — originality emerged from stacking proven systems nobody else combined the same way. +- **"10,000% or nothing"** — sampling single ideas is tasting, not cloning. + +Buffett, Munger, and Graham appear here only as the sources Pabrai cloned; they are recorded on this page rather than as separate entities. + +## Evidence + +- Case study, figures, and the multi-source method — [[2026-06-15-how-to-get-rich-cloning]] + +## Related Pages + +- [[cloning-over-originality]] — the concept he anchors +- [[methodology-as-moat]] — the tension between a cloned method and a defensible one +- [[2026-06-15-how-to-get-rich-cloning]] — source + +## Contradictions / Uncertainty + +- All figures (31%/40yr Buffett return, ~$154M, $650k lunch) are stated by an advocacy video without citation. Broadly consistent with public accounts of Pabrai, but treat as claimed, not verified in this vault. +- The video is the only source; the framing is deliberately motivational. + +## Next Questions + +- Would a primary Pabrai source (his book/letters/talks) confirm the "clone the boring parts" emphasis, or is that the video creator's gloss? +- Does the cloning thesis survive in a field (unlike investing) where the cloned combination becomes public the moment you sell it? See [[cloning-over-originality]]. diff --git a/wiki/entities/oskar-hartmann.md b/wiki/entities/oskar-hartmann.md new file mode 100644 index 0000000..74d2744 --- /dev/null +++ b/wiki/entities/oskar-hartmann.md @@ -0,0 +1,47 @@ +# Oskar Hartmann + +#entity #person + +## Summary + +Russian-German serial entrepreneur and investor; speaker of [[2026-07-26-how-to-build-a-billion-dollar-company-2027]] and [[2026-07-26-main-principle-of-successful-business]] (**two sources** — named outright in the second, context-identified in the first). Founder of KupiVIP and ShoppingLive, shareholder of Fab.com, runs a "Создатель единорога" (Unicorn Creator) program. The vault's first voice from the **VC/product-startup tradition** — independent of both the [[dan-martell]] coaching corpus and the RU dev-sales cluster — which makes his convergences with the vault's core thesis unusually valuable and his divergences (multichannel, partner skepticism) genuine counter-positions rather than in-family variation. + +## Current Understanding + +Signature positions across his two ingested sources: + +- **"Sell first, then build"** ([[2026-07-26-main-principle-of-successful-business]], his second source): prove acute pain with cheap experiments ending at a **payment**, not a waitlist; pre-payment is the supreme demand signal; deliver value by hand (Wizard-of-Oz) before automating; launch ugly, endure reality early; duration without revenue is a disqualifying red flag → [[sell-before-build]]. +- **Framework stability across the two sources** — the second restates the first's core commitments rather than contradicting them: prove-demand-first (source 1's unit-economics step 1 → source 2's whole thesis), pricing/payment as the only honest signal (pricing-power test → money-vote hierarchy), CAC-burning as a post-PMF entry barrier (⅓-of-LTV → $80–100 CAC). One tension to watch: source 1's *founder-sells-personally* vs source 2's automated payment-screen tests — resolvable as segment/stage difference (B2B sales motion vs consumer-product demand testing), unstated. + +- **"Build and sell" is the whole job**; PMF is a start line, and the differentiating asset is a **repeatable, scalable sales channel** with predictable economics ([[sales-channel-as-moat]]). "A good product does not sell itself." +- **Founder sells first, always** — he states he does not invest in companies where the founder doesn't sell personally ([[sales-discipline]]). +- **SOM over TAM** at the start ([[niche-selection]]); whale clients and single-partner hopes kill startups ([[partnerships]], [[client-acquisition-channels]]). +- **Full-cost unit economics with a buffer**; pricing power as the real PMF test ([[unit-economics]], [[pricing-from-value]]). +- **Venture fits ~1% of businesses**; stretching a normal company onto venture expectations destroys it (Fab.com — he was a shareholder); slow reinvested growth is a legitimate alternative ([[venture-fit]]). +- Speaks from cases he claims first-hand stakes in: Fab.com (shareholder, watched the venture stretch fail), ShoppingLive (low-capital #1 TV shop in Russia), his first store ($20M via one 10%-of-revenue partner deal). + +## Evidence + +- Channel/moat/venture positions — [[2026-07-26-how-to-build-a-billion-dollar-company-2027]] +- Sell-first/validation positions; Zavent and coworking anti-cases — [[2026-07-26-main-principle-of-successful-business]] + +## Related Pages + +- [[sales-channel-as-moat]] — his central thesis, now a vault concept +- [[unit-economics]], [[venture-fit]], [[sell-before-build]] — concepts his sources founded +- [[cloning-over-originality]] — where his second source supplies the first independent corroboration +- [[partnerships]] — where he supplies the first independent second voice +- [[dan-martell]] — the other prolific voice; contrast in tradition and incentive +- [[overview]] + +## Contradictions / Uncertainty + +- Identification: the second source names him outright; the first was context-identified — the attribution is now effectively confirmed (the two raw notes describe the same speaker and cases). +- His self-reported cases now include **two own failures** (the coworking test, Zavent) — unusual among the vault's promotional voices and a mild credibility positive, though still self-selected stories. +- Incentive: sells a paid founder program; "you lack GTM discipline" is also the shape of his offer — same standing caution the vault applies to [[dan-martell]]. +- All his numbers are stage war stories — attributable, unverified ([[2026-07-26-how-to-build-a-billion-dollar-company-2027]] Open Questions). + +## Next Questions + +- Do his other talks/materials repeat these frameworks (stability) or contradict them (opportunism)? +- What does his "unicorn creator" program actually teach — and does the paid material match the free advice? diff --git a/wiki/entities/sebastian.md b/wiki/entities/sebastian.md new file mode 100644 index 0000000..1ce0c55 --- /dev/null +++ b/wiki/entities/sebastian.md @@ -0,0 +1,41 @@ +# Sebastian + +#entity #person + +## Summary + +Founder and owner of [[virtido]], a ~11-year software outsourcing/engineering company with enterprise clients. The interview subject in [[2026-07-06-sebastian-interview-ai-and-software-engineering]]. His vantage point is a services business with a client/compliance/sales lens, and he supplies the vault's most contrarian sales claim and its clearest enterprise-reality reporting. + +## Current Understanding + +Sebastian's signature positions: + +- **"Bring-your-own-harness won't survive enterprise; connections win business."** Compliance and liability make per-developer AI setups impossible at scale → he frames compliant, company-managed harnesses as "the interesting market." See [[future-of-engineering-work]]. +- **Online outreach is "Big zero"** — every real long-term Virtido customer came through personal, in-person network; sales agencies, cold calling, email, LinkedIn campaigns, content, and SEO produced nothing. This is the pole against the outbound taxonomy in [[client-acquisition-channels]]. See [[relationships-as-moat]]. +- **Seniors up, juniors out; the senior's product is risk reduction.** See [[seniority-and-ai]]. +- **Ownership and problem-framing are the durable skills** — "no one ever needed a programmer; people have problems you solve." See [[product-ownership]]. +- **Decouple identity from profession.** + +He runs 10–15 engineer teams on big programs and reports enterprise lockdown first-hand (managed VMs, no self-installed tools; a Roche SAP program of ~1,200 engineers; banks moving from banning AI to adopting it). + +## Evidence + +- Role, tenure, stances, and all quotes — [[2026-07-06-sebastian-interview-ai-and-software-engineering]] +- "From a compliance perspective… bring-your-own-harness will not be the way forward… it has to be a company-managed resource." +- "We tried sales agencies, cold calling, email marketing, LinkedIn campaigns, content, SEO. Zero. Big zero." + +## Related Pages + +- [[virtido]] — his company +- [[eugene]] — his interlocutor, who holds the opposite view on harnesses and channels +- [[relationships-as-moat]] · [[seniority-and-ai]] · [[product-ownership]] · [[future-of-engineering-work]] · [[client-acquisition-channels]] + +## Contradictions / Uncertainty + +- His "online = Big zero" is **one founder's experience in enterprise services** and directly contradicts [[2026-06-15-17-ways-first-client]] and [[2026-06-15-more-clients-dev-agency]], which treat online channels as live. Likely audience-dependent (enterprise vs SMB/startup), but unresolved — see [[client-acquisition-channels]]. +- Surname/company spelling ("Virtido", `verti.com`) comes from a cleaned auto-transcript; treat as approximate. + +## Next Questions + +- Does the in-person-only rule hold outside large-enterprise buying, or is it specific to Virtido's ICP? +- What would a "compliant enterprise harness" product actually look like — is Sebastian building one, or only naming the gap? diff --git a/wiki/entities/virtido.md b/wiki/entities/virtido.md new file mode 100644 index 0000000..58c1239 --- /dev/null +++ b/wiki/entities/virtido.md @@ -0,0 +1,35 @@ +# Virtido + +#entity #organization + +## Summary + +A ~11-year-old software outsourcing/engineering company founded and owned by [[sebastian]], serving enterprise clients with 10–15-engineer teams on large programs. Its experience anchors the vault's enterprise-reality reporting and its in-person-relationships sales claim. + +## Current Understanding + +- **Client base:** large, regulated enterprises. Reported constraints: engineers work on centrally managed VMs, cannot use personal laptops, cannot install their own tools. +- **Go-to-market:** per Sebastian, **every real long-term customer came through personal network / in-person relationships**; online outreach produced "Big zero." See [[relationships-as-moat]], [[client-acquisition-channels]]. +- **Brand voice:** a playful `humans.verti.com` "human badge on LinkedIn" riff — leaning into "we're actual humans" as differentiation now that AI makes everything online look identical. +- **Strategic read:** Virtido's constraints are exactly what makes Sebastian identify the **compliant, company-managed enterprise harness** as an open market ([[future-of-engineering-work]]). + +## Evidence + +- Company age, team sizes, enterprise constraints, GTM, and the human-badge riff — [[2026-07-06-sebastian-interview-ai-and-software-engineering]] + +## Related Pages + +- [[sebastian]] — founder/owner +- [[relationships-as-moat]] — its GTM is the primary evidence +- [[future-of-engineering-work]] — enterprise lockdown and the harness opportunity +- [[client-acquisition-channels]] — the in-person pole of the channel debate + +## Contradictions / Uncertainty + +- Company name and the `verti.com` domain come from a cleaned auto-transcript; spelling is approximate. +- All claims about Virtido are the founder's own account in a pre-webinar conversation — self-reported, uncorroborated. + +## Next Questions + +- Is `humans.verti.com` a live product/campaign or a rhetorical device in the interview? +- What is Virtido's actual ICP and deal size — needed to judge whether its "in-person only" GTM generalizes. diff --git a/wiki/lint-reports/2026-07-18-lint-full-wiki.md b/wiki/lint-reports/2026-07-18-lint-full-wiki.md new file mode 100644 index 0000000..7744baa --- /dev/null +++ b/wiki/lint-reports/2026-07-18-lint-full-wiki.md @@ -0,0 +1,66 @@ +# Lint Report — Full Wiki (2026-07-18) + +#lint-report + +## Scope + +Full-wiki health check of all **40 pages** (1 overview · 13 sources · 17 concepts · 6 entities · 1 comparison · 1 query · 1 lint report), the follow-up to the sources-only lint ([[2026-07-18-lint]]). Every concept, entity, comparison, and query page was read in full; link health was checked against a deduped inventory of all `[[…]]` targets across the vault. + +Checks: page-type tags · template-section completeness · broken links · orphans / weak linking · cross-page contradiction coverage · stale claims superseded by newer sources · missing evidence links · high-mention concepts lacking pages. + +## Verdict + +**The wiki is in good structural health.** Tags, templates, links, and orphan-coverage all pass cleanly. The only real findings are **staleness introduced by today's adversarial-source ingest** — three pages still say "the vault has no adversarial source," which is no longer true. Two fixes + one clarification applied; one structural gap (a missing *referrals* page) flagged. + +## Passing Checks + +- **Page-type tags: 100%.** All 40 pages lead with the correct folder-matching type tag (`#source`/`#concept`/`#entity`/`#comparison`/`#query`/`#overview`/`#lint-report`), topical tags after. No mismatch. +- **Template sections: complete.** All 17 concepts and 6 entities carry the required Summary / Current Understanding / Evidence / Related Pages / Contradictions-Uncertainty / Next Questions. The query matches the Query template; sources verified in the prior lint. +- **No broken links.** Every `[[…]]` target resolves to an existing page. (Two `[[…]]` hits are illustrative text inside code spans; one `[[wiki/overview|Overview]]` is a path-style link — resolvable but inconsistent, fixed below.) +- **No orphans; linking is strong.** Every page has ≥7 inbound references (busiest: [[client-acquisition-channels]] 46, [[methodology-as-moat]] 43, [[2026-07-17-design-the-perfect-offer]] 42; lowest are the query at 7 and this-day's lint at 4 — both expected for their type). The new [[ai-productivity-evidence]] already has 26 references — well-integrated on arrival. +- **Evidence links present** on every concept/entity page. +- **Contradiction coverage is thorough.** Every live tension is recorded on the relevant page(s): productize-immediately-vs-after-2–3 ([[productized-service]]), one-package-vs-price-ladder ([[offer-ladder]]), cloning-vs-moat ([[cloning-over-originality]]), online-vs-in-person ([[client-acquisition-channels]]), two-moats ([[methodology-as-moat]]/[[relationships-as-moat]]), and now the foundational AI-capability contradiction ([[ai-productivity-evidence]]). No unrecorded contradiction found. + +## Findings + +### F1 — `productized-service` still says the vault has no adversarial source (Medium) — ✅ fixed + +The page's Contradictions and Next Questions read "still no true adversarial view" / "the vault needs an adversarial source," now contradicted by the day's ingest of [[ai-productivity-evidence]]. It also leans on the "~$200/mo AI substitute" premise that the new evidence contests. +**Fix:** updated both sections to acknowledge the adversarial source exists and to sharpen the *remaining* gap — the new source tests the **AI-capability premise**, not the **productization model itself**, so a *productization-failure* source is still genuinely missing. Added a "now contested" pointer on the substitution bullet and [[ai-productivity-evidence]] to Related Pages. + +### F2 — Query snapshot's "no adversarial source" caveat is now imprecise (Low) — ✅ fixed (dated note) + +[[2026-07-17-best-method-first-client]] states "the vault also has no adversarial or failure-case source on any of this." True for its *channel/sales* topic, but the blanket phrasing is now misleading. +**Fix:** appended a dated lint note (preserving the original per the Update Policy) clarifying that the new adversarial source addresses the AI-capability premise, not these channel claims — which remain un-countered. + +### F3 — Inconsistent path-style link in `index.md` (Low) — ✅ fixed + +`index.md` used `[[wiki/overview|Overview]]` (path-style) where the vault everywhere else uses the bare `[[overview]]`. Resolvable but inconsistent. **Fix:** changed to `[[overview|Overview]]`. + +### F4 — High-mention concept with no page: **referrals** (Medium) — flagged + +Referrals appear as a distinct, high-value channel with their own statistics and mechanics across [[2026-06-15-17-ways-first-client]] (91% would refer / 11% asked; highest-converting; ~0 cost; ask-immediately-after-delivery), [[sales-discipline]], [[client-acquisition-channels]], and the query — but have **no dedicated concept page**. This is the clearest structural gap. Recommend creating `wiki/concepts/referrals.md` (inbound from client-acquisition-channels, sales-discipline; the "can't bootstrap client #1" sequencing constraint is its key nuance). Not created in this lint pass (a lint reports; it doesn't author content). + +### F5 — Secondary concept candidate: **guarantee / risk-reversal** (Low) — flagged + +The guarantee mechanic recurs with an explicit open question across [[pricing-from-value]] (the guarantee test) and [[outcome-based-selling]] ("guarantee mechanics are undefined"). Currently well-covered within those two pages; a dedicated page is optional, lower priority than referrals. + +### F6 — Optional enrichment links to the new evidence page (Low) — flagged + +[[niche-selection]] ("'go where AI is powerless' assumes LLM capability is static") and [[solution-vs-staff-augmentation]] ("directly substituted by the ~$200/mo alternative") both make claims the new [[ai-productivity-evidence]] speaks to. Not errors — optional cross-links that would tighten the web. Left for a future pass to avoid over-editing during a lint. + +## Note — a nuance worth recording (not a defect) + +The adversarial ingest was appropriately *surgical*: it added counter-evidence only to the three pages it genuinely contradicts ([[ai-market-shift]], [[seniority-and-ai]], [[future-of-engineering-work]]). It did **not** touch [[relationships-as-moat]] or [[product-ownership]], which rest on the "AI levels skill" premise — correctly, because "novices gain most" *corroborates* leveling rather than contradicting it. So the same source contradicts one Sebastian claim (juniors irrelevant) while supporting another (skill is leveled); the vault currently records the contradiction but not the corroboration. Optional future touch. + +## Changes Made This Pass + +- [[productized-service]] — F1: adversarial-source acknowledgement + substitution-premise pointer + Related-Pages link. +- [[2026-07-17-best-method-first-client]] — F2: dated clarifying note. +- `index.md` — F3: path-style link normalized (plus this report added to the Lint Reports table and counts updated). + +## Recommended Next Operations + +1. **Create the `referrals` concept page** (F4) — the one real structural gap. +2. **Ingest a productization-failure-case source** — still the highest-value content gap (the AI-capability premise now has a counter; the *selling model* does not). +3. Optional tidy: F5 (guarantee page), F6 (enrichment links), the corroboration note above. diff --git a/wiki/lint-reports/2026-07-18-lint.md b/wiki/lint-reports/2026-07-18-lint.md new file mode 100644 index 0000000..2646923 --- /dev/null +++ b/wiki/lint-reports/2026-07-18-lint.md @@ -0,0 +1,57 @@ +# Lint Report — Sources (2026-07-18) + +#lint-report + +## Scope + +Health check of the **12 source summary pages** in `wiki/sources/*` (per user request "run a lint on sources"). Cross-page checks (inbound links, contradiction coverage) were run against the whole vault where a source page is one end of the relationship. This is the vault's **first lint**. + +Checks run: raw↔summary coverage · page-type tags · template-section completeness · outbound link validity · inbound linking / orphans · cross-source contradiction coverage · stale/superseded claims · metadata completeness · evidence provenance. + +## Verdict + +**The source layer is healthy.** No orphans, no broken links, no missing or mismatched tags, complete raw↔summary coverage, and provenance is well-maintained. Five findings, all Low/Info; two were fixed in this pass, three are flagged. + +## Passing Checks + +- **Coverage is complete and 1:1.** 12 raw files in `raw/sources/` → 12 summaries in `wiki/sources/`. No un-ingested raw source; no summary without a backing raw file. +- **Page-type tags correct.** All 12 pages open with `#source` as the first tag; topical tags follow. No folder/tag mismatch. +- **Template sections present.** All 12 carry Source Metadata, Core Claims, Key Evidence / Details, Connections, Open Questions, and Change Impact on Wiki. (`konspekt-aphorisms` uses "Core Claims (the aphorisms)" — compliant.) +- **No broken outbound links.** Every `[[…]]` target in every source page resolves to an existing page. +- **No orphan sources.** Every source has ≥1 inbound link from a content page (concept/entity/comparison/query/overview), plus index/overview catalog links. +- **Provenance chain intact.** The primary→secondary demotion of [[2026-06-15-selling-development-services-in-the-ai-era]] is recorded on the page and reflected in concept-page citations; its resolved open question is struck through, not deleted (history preserved). Primaries carry accurate "provenance role" notes. The `konspekt-aphorisms` "Indian dev" stereotype is quoted for fidelity with an explicit non-reuse caveat — compliant with the citation policy. + +## Findings + +### F1 — Content-marketing-timing contradiction was under-recorded (Low) — ✅ fixed + +The new source [[2026-07-18-information-is-free-implementation-is-paid]] makes organic content the *primary* lead engine from day one — a third, most-aggressive position on content timing. [[client-acquisition-channels]] still recorded the split as two-way (Tony vs AB Analytics). Non-negotiable rule #5 requires contradictions be recorded explicitly. +**Fix:** upgraded the Contradictions bullet in [[client-acquisition-channels]] to the three-way split, noting the "audience-dependent" escape is weaker here (all three are US SMB coaching sources). + +### F2 — Missing reciprocal link + inaccurate Change Impact on the LinkedIn template (Low) — ✅ fixed + +[[2026-06-15-linkedin-mail-template]]'s Change Impact claims it is "linked from [[client-acquisition-channels]] and [[sales-discipline]]," but `sales-discipline` did **not** link it — leaving the template inbound-linked from only one content page (its weakest link in the vault). +**Fix:** added the link from [[sales-discipline]] ("customize every first touch" → the concrete instance is the template), making the claim true and strengthening the weak link. + +### F3 — `meta-analysis` is the most weakly inbound-linked source (Low) — flagged + +[[2026-06-15-meta-analysis-selling-dev-in-ai-era]] is inbound-linked from only [[overview]] among content pages (plus index/log). Acceptable for a second-order map that mostly *points at* the primaries, but it is the least-connected source. Optional future strengthening: cite it from the concept pages whose contradictions it first surfaced (content-timing, team-size). + +### F4 — Filename date-prefix convention is inconsistent for undated videos (Info) — flagged + +Three conventions are in use for the date prefix: **ingestion date** for the two US anchors (`2026-07-17-design…`, `2026-07-18-information…`), **batch date** for the June-15 set, and **file date** for `2026-07-06-sebastian…`. Each page documents its own date in metadata, so nothing is misleading — but the naming rule doesn't specify which date to use when a source is undated. Consider codifying: "undated source → use ingestion date." No file renames recommended now (links would churn). + +### F5 — Corpus remains single-school and unverified (Info) — flagged (standing gap) + +The 12th source adds no statistics but also no verification and no dissent: 11 of 12 sources are the same "sell dear / give-value / productize" school; all quantitative claims across the corpus remain attributable-but-unverified (promotional videos). Already tracked in [[overview]] and [[index]]. The highest-value next ingest is still an **adversarial / failure-case** source; a warm partial-dissent already exists in [[sebastian]] (channels only). + +## Changes Made This Pass + +- [[client-acquisition-channels]] — content-timing contradiction upgraded to three-way (F1). +- [[sales-discipline]] — added reciprocal link to [[2026-06-15-linkedin-mail-template]] (F2). + +## Recommended Next Operations + +1. Ingest an **adversarial source** (F5) — the one gap that materially changes vault confidence. +2. A **full-wiki lint** (this pass covered sources only) — to check concept/entity pages for the same categories, plus high-mention concepts lacking pages (e.g. *referrals* is a high-value channel with metrics but no dedicated page). +3. Optional low-priority tidy: F3 (link meta-analysis from concept pages), F4 (codify the date-prefix rule). diff --git a/wiki/overview.md b/wiki/overview.md new file mode 100644 index 0000000..9f6d1e4 --- /dev/null +++ b/wiki/overview.md @@ -0,0 +1,100 @@ +# Overview + +#overview + +## Purpose + +Top-level synthesis and navigation for this vault. As sources are ingested, this page carries the current best understanding of the business domain and links to the canonical entity, concept, and comparison pages. + +## Current Understanding + +The vault covers **how a developer or agency earns in the AI era** — split into three linked branches: + +- **A. Selling services** in a market where AI substitutes undifferentiated execution (the original domain). +- **B. Positioning engineering work and careers** as AI restructures teams, roles, and where human value lives (added 2026-07-17 with the Sebastian interview). +- **C. Running the team** — leadership and people-development inside the delivery org (opened 2026-07-19 with a single source; thin branch, `tentative`). + +As of 2026-07-29 the vault holds **20 sources**: the seventeen below, the vault's shortest — [[2026-07-29-start-a-business-with-claude-code]], a 42-second [[dan-martell]] short (owner-attributed the day it was ingested) that compresses his $0 protocol (sell first, distribution over code, cold outbound) into a [[claude-code]]-executed playbook — plus a growing [[oskar-hartmann]] pair — [[2026-07-26-how-to-build-a-billion-dollar-company-2027]] and [[2026-07-26-main-principle-of-successful-business]] — the first voice from a **third tradition** (VC/product-startup world, Russian-language but independent of both the Martell corpus and the RU dev-sales cluster). It independently restates the vault's core inversion (*a good product does not sell itself; the founder sells; the repeatable channel is the asset; sell first, then build*), supplies the first genuine counter-voice on [[partnerships]], and the first independent corroboration of [[cloning-over-originality]]. Prior state: two anchors (a US offer-design video and the [[2026-07-06-sebastian-interview-ai-and-software-engineering|Sebastian interview]]), a growing [[dan-martell]] cluster — **five confirmed** ([[2026-07-19-your-company-cant-outgrow-your-team]], [[2026-07-20-referrals-will-sink-your-business]], [[2026-07-22-stop-cold-calling-do-this-instead]], [[2026-07-23-make-my-first-100k-in-month]], [[2026-07-29-start-a-business-with-claude-code]]) **plus two suspected** ([[2026-07-18-information-is-free-implementation-is-paid]] near-certainly; the 07-17 offer-design anchor plausibly — see Contradictions) — the eight "15-06-2026 Inbox" notes (six primary video-conclusions, a meta-analysis, a template), one distillation of them, and — since 2026-07-18 — the vault's **first adversarial source**, an empirical-evidence dossier ([[2026-07-18-ai-productivity-adversarial-evidence]] → [[ai-productivity-evidence]]) that tests the AI-capability premise the others assume. The core sales thesis is reached independently by an American coaching tradition and a Russian-language dev-sales tradition — that cross-tradition convergence, not any single source, is why it holds (the caveat since 2026-07-23: the American side of the convergence is substantially **one coach's corpus**, so the RU side carries more of the independence weight than the source count suggests): + +> **AI eats undifferentiated execution and creates demand for the judgment that directs it.** Stop selling hours, stack, or labor. Sell a named, repeatable *outcome* — and accountability for it — to a narrowly-chosen audience, priced against the value of the result, not competitors' rates. + +**Branch A — the selling chain, in dependency order:** + +1. **[[ai-market-shift]]** — a ~$200/mo AI alternative zeroes rate competition, but every $1 of AI spend reportedly pulls ~$6 of specialist spend: the funnel moves, it doesn't close. +2. **[[niche-selection]]** — WHO dominates WHAT. Go narrow, go where AI is weak, sell to leadership (to an implementer your AI is a job threat; to leadership it's a KPI). "Niche is upstream of everything." +3. **[[pain-discovery]]** — find pain with money: recurring, costly, already duct-taped, founder-understood. Watch what they *spend on*, not what they say. +4. **[[outcome-based-selling]]** — invert the pain into a countable outcome and take accountability for it. That accountability is the product. +5. **[[productized-service]]** — fix scope, fix price, name the package (DIY→DWY→DFY). Team size no longer signals seriousness. Upstream of packaging sits **[[sell-before-build]]** *(page added 2026-07-26)*: prove demand with *paid money* before building — signal hierarchy (click < waitlist < payment < pre-payment), cheap-experiment toolkit, Wizard-of-Oz manual delivery. Three traditions converge on the rule. +6. **[[pricing-from-value]]** — price from value, never cost or rate. "Expensive" doesn't exist; "I don't see what for" does. +7. **[[methodology-as-moat]]** — one candidate for the defensible asset: your proven way of doing it. "People don't buy your time. They buy your standards." *(Now one of **three** moat candidates — see [[relationships-as-moat]] and, since 2026-07-26, [[sales-channel-as-moat]]: the repeatable distribution machine itself, with the product as commodity.)* +8. **[[client-acquisition-channels]]** + **[[sales-discipline]]** — *where* to fish and *how* to work it: 5 touches, 3 channels × 90 days, founder sells. One online channel is now worked out in full — [[information-vs-implementation]]: give away the entire know-how as scrambled free content, charge for implementation and sequencing. The highest-converting channel, [[referrals]], is the *reward* for step 1's outcome (91% would refer, 11% are asked) but can't bootstrap the first client — hence the warm/in-person route above. +9. **[[marketing-system]]** *(added 2026-07-20)* — whether the channels add up to a **machine you can turn up**: money in at the top producing more money out at the bottom. Its diagnostic is the counter-position to step 8's best channel — **referral dependency is a ceiling, not an achievement**, because referral flow has no throttle. Three levers only (content / paid / [[partnerships]]), pick one, 90 days, ~6 months before leads. The partnerships lever — the one plausible fit for a technical operator who won't publish — got its mechanism 2026-07-22: **borrowed credibility** (a partner who already holds the buyer's trust walks you in pre-sold), scaled by recruiting the partner *archetype* rather than optimizing deals. Best read as **stage-successor, not rival**: one-to-one channels get you clients #1–#N; a system stops #N being the ceiling. Also supplies the vault's diagnosis of *why* developers stall at this step — [[technical-founder-trap]]: technical founders can solve but can't explain, and the explaining is what sells. +10. **[[sales-channel-as-moat]] + [[unit-economics]] + [[venture-fit]]** *(added 2026-07-26, all from [[oskar-hartmann]])* — the company-level view above the whole chain: the differentiating asset is a **repeatable channel with predictable acquisition economics** (Pediant vs FlatPay: channel beats technology); the price must cover the *full* cost stack with a buffer, and **pricing power is the real PMF test**; and only ~1% of businesses fit venture — stretching a sound company onto venture expectations kills it (Fab.com), while slow reinvested growth is a legitimate track. Partially fills the long-flagged unit-economics gap. All single-source, `tentative`. + +**Branch B — the engineering-work shift** ([[future-of-engineering-work]]): coding cost → 0, so teams collapse 8→2–3, [[seniority-and-ai|seniors appreciate and juniors are squeezed]], and human value migrates to [[product-ownership|owning outcomes not tickets]], judgment, and [[relationships-as-moat|in-person trust]]. This branch supplies the vault's second moat candidate (relationships) and a concrete niche opportunity: compliant, company-managed enterprise AI harnesses. **Caveat (2026-07-18):** Branch B rests on "coding cost → 0" and "seniors up / juniors out" — both now empirically contested by [[ai-productivity-evidence]] (AI's measured effect is modest and tilts to *novices*, not seniors). Read Branch B as a strong-form hypothesis the vault now holds *against* evidence, not a settled fact. + +**Branch C — running the team** ([[team-growth-ceiling]]): a company can only grow as fast as its people — the ceiling is human, not market. Mechanisms from the lone source ([[2026-07-19-your-company-cant-outgrow-your-team]], authored by [[dan-martell]] — identified 2026-07-20): state the growth math out loud, teach a philosophy not a task list ("Business Athlete"), public scoreboard / private criticism, the Netflix Keeper Test, and values enforced by hiring/firing ("values are what you tolerate"). One anecdotal source — read as a candidate frame, not a settled claim. It gains relevance if Branch B's team collapse holds: in a 2–3 person team, one non-growing person is a third of capacity. **Note the branch is not independent of Branch A:** its author also carries [[marketing-system]], and the two are the same "the ceiling is never the market" argument pointed inward and outward. + +**Supporting structure:** [[solution-vs-staff-augmentation]] (the model choice underneath the whole chain) and [[cloning-over-originality]] (where a method comes from — copy first, adapt second; originality is emergent from the combination). + +**Highest-signal single items:** + +- *The guarantee test* — "if we guaranteed the result, is price still the problem?" Yes → no money; No → no trust ([[pricing-from-value]], [[dmitry-rodenko]]). +- *AI as qualification filter* — give the AI skill away free 30 days; "works" and "never got to it" are non-clients, "weak, needs specifics" is your buyer ([[ai-market-shift]]). +- *Old-client mining* — ask your 3–5 best "what result were you paying me to get?", never "why did you choose us?" ([[pain-discovery]]). +- *Relationships compound in person* — you're trusted when someone meets you the *same* in *different* circumstances; online outreach may be noise ([[relationships-as-moat]], [[sebastian]]). +- *Information is free; implementation and sequencing are paid* — teach every step publicly but *scrambled* (A1, B1, C1, A2 …); each piece proves expertise, no feed hands over the working order ([[information-vs-implementation]]). +- *Perception ≠ measurement* — in the METR RCT, developers forecast AI would make them 24% faster, *felt* 20% faster, and were measured 19% *slower*. "It feels faster" is the evidence most AI-productivity hype rests on, and it is unreliable ([[ai-productivity-evidence]]). +- *Referrals have no throttle* — the channel that converts best is the one you cannot spend more to get more of. It can't start you (no prior client) and can't scale you (derived from demand you already created); "we grew on referrals" is a warning sign misread as a badge ([[referrals]], [[marketing-system]]). +- *Borrowed credibility beats cold outreach into enterprise* — a partner who already holds the account walks you in pre-sold; the play is recruiting the partner *archetype*, not treasuring the one lucky intro. "Ten good partners can replace an outbound sales team." Notably, partner intros are referrals **with a throttle** — you control partner recruitment — which is what client referrals lack ([[partnerships]], [[referrals]]). +- *Solving ≠ explaining* — the technical founder's actual bottleneck. Note this is the same disease as Rodenko's *"'expensive' doesn't exist — 'I don't see what for' does"*, seen from the buyer's side ([[technical-founder-trap]], [[pricing-from-value]]). +- *Ask past the person* — "do you know anyone with this problem?" asked of your existing contacts often lands on "yeah, me," and otherwise yields warm, name-carrying intros — the one referral-shaped motion that needs **no past client** ([[referrals]]). +- *Obstacles, not objections* — surface the concern **before** presenting the offer ("do you have a budget to solve this?") so it's an obstacle you address, not an objection you defend against ([[sales-discipline]]). +- *The money map* — ~100 customers × ~$1K/mo is the claimed sane route to $100K/mo; $1K/mo floor, sub-$10K ceiling, flanked by decoy tiers (½×, 10×) that exist so the core prints ([[pricing-from-value]], [[offer-ladder]]). +- *The pricing-power probe* — raise the price; if the customer flow doesn't fall, you have PMF. If someone else sets your price, "you're in a simulation of entrepreneurship." The cheapest PMF test in the vault ([[pricing-from-value]], [[oskar-hartmann]]). +- *Channel beats technology* — Pediant (QR payments, Walmart/Best Buy, dead) vs FlatPay (commodity terminal, door-to-door, billion-dollar; its founder is on business #6 through the same channel). The repeatable channel, not the product, is the reusable asset ([[sales-channel-as-moat]]). +- *"You are their 46th priority"* — a partner already has ~15 own + ~30 partner products they can't sell to plan; partner-as-savior plays land 100–200× below expectations. Works only with many partners, never one gatekeeper ([[partnerships]] — the first independent voice on that page, and it's a warning). +- *Only money votes* — click < waitlist signup < payment < **pre-payment**; "interesting!" is free and lies. Hartmann's coworking test: 5,000 reached, warm replies, **0 buyers** — project killed for pennies instead of millions ([[sell-before-build]]). +- *The acute-pain test* — "a good business is when everything is bad and people still come and pay" (hospitals). If demand survives bad service, people will pay for a concept before polish exists ([[pain-discovery]], [[sell-before-build]]). + +## Navigation + +- Content catalog: [[index]] +- Operation log: [[log]] +- Sources (20): Martell short [[2026-07-29-start-a-business-with-claude-code]]; third-tradition [[2026-07-26-how-to-build-a-billion-dollar-company-2027]] · [[2026-07-26-main-principle-of-successful-business]]; anchors [[2026-07-17-design-the-perfect-offer]] · [[2026-07-06-sebastian-interview-ai-and-software-engineering]] · [[2026-07-18-information-is-free-implementation-is-paid]] · [[2026-07-19-your-company-cant-outgrow-your-team]] · [[2026-07-20-referrals-will-sink-your-business]] · [[2026-07-22-stop-cold-calling-do-this-instead]] · [[2026-07-23-make-my-first-100k-in-month]]; **adversarial** [[2026-07-18-ai-productivity-adversarial-evidence]]; the June-15 batch [[2026-06-15-rodenko-selling-development-expensively]] · [[2026-06-15-17-ways-first-client]] · [[2026-06-15-how-to-get-rich-cloning]] · [[2026-06-15-more-clients-dev-agency]] · [[2026-06-15-making-money-with-ai-2026]] · [[2026-06-15-konspekt-aphorisms]] · [[2026-06-15-linkedin-mail-template]] · [[2026-06-15-meta-analysis-selling-dev-in-ai-era]] · [[2026-06-15-selling-development-services-in-the-ai-era]] +- Concepts — *selling:* [[ai-market-shift]] · [[niche-selection]] · [[pain-discovery]] · [[outcome-based-selling]] · [[productized-service]] · [[pricing-from-value]] · [[methodology-as-moat]] · [[offer-ladder]] · [[client-acquisition-channels]] · [[sales-discipline]] · [[referrals]] · [[partnerships]] · [[marketing-system]] · [[technical-founder-trap]] · [[cloning-over-originality]] · [[information-vs-implementation]] · [[sales-channel-as-moat]] · [[unit-economics]] · [[venture-fit]] · [[tam-sam-som]] · [[sell-before-build]]; *engineering work:* [[future-of-engineering-work]] · [[seniority-and-ai]] · [[product-ownership]] · [[relationships-as-moat]]; *running the team:* [[team-growth-ceiling]]; *evidence:* [[ai-productivity-evidence]] +- Comparisons: [[solution-vs-staff-augmentation]] +- Entities: people [[sebastian]] · [[eugene]] · [[dmitry-rodenko]] · [[mohnish-pabrai]] · [[dan-martell]] · [[oskar-hartmann]]; orgs [[virtido]] · [[ab-analytics]]; tools [[claude-code]] +- Queries: [[2026-07-17-best-method-first-client]] · [[2026-07-26-eugene-90-day-plan]] +- Lint reports: [[2026-07-18-lint]] · [[2026-07-18-lint-full-wiki]] +- Timelines: none yet + +## Open Threads + +- ✅ **Upstream notes imported (2026-07-17).** The seven notes behind the distillation are now ingested; claims trace to named primary sources. Their root sources remain promotional YouTube videos, so figures are *attributable, not verified*. +- ✅ **First adversarial source ingested (2026-07-18).** The vault's long-standing "no counter-evidence" gap is now *partially* closed: [[ai-productivity-evidence]] brings RCT/peer-reviewed evidence against the shared premise that **AI has zeroed the cost of commodity execution** (METR: experts 19% *slower*; Brynjolfsson: novices gain most, not seniors). Crucially, it targets the **AI-capability premise** (which underlies both branches), **not** the productization/sell-dear tactics themselves. So the remaining gap is narrower but real: **no source tests whether the *productized-outcome selling model* fails** — e.g. where niching-down or value-pricing lose money. That failure-case source is now the highest-value next ingest. The other dissonant voices are [[sebastian]] and [[dan-martell]], both only on *channels* — and, since 2026-07-26, [[oskar-hartmann]] on partner-hope and whale-first clients. +- ✅ **First counter-position on a channel (2026-07-20).** [[2026-07-20-referrals-will-sink-your-business]] attacks the one channel every prior source rated highest, and does it precisely: not referral *conversion* but referral *dependency* ([[referrals]] → [[marketing-system]]). Note what kind of gap this closes — it is **advocacy against advocacy**, a coaching clip with no data whose author sells the alternative, not evidence in the sense [[ai-productivity-evidence]] set. It is nonetheless the first time the vault holds two directly opposed positions on a *tactic* rather than a premise, and the structural half of the argument (referral flow has no throttle) stands without any of the source's unsourced numbers. +- ✅ **The partnerships lever is no longer unexplained (2026-07-22).** [[2026-07-22-stop-cold-calling-do-this-instead]] supplies the mechanism (borrowed credibility, partner-archetype recruiting → [[partnerships]]) and closes open questions on three pages, including [[referrals]]' "is there a referral variant with a throttle?" (yes — partner intros). Two caveats keep it modest: it is the **third source from the same author** ([[dan-martell]] held 3 of 16 sources at the time — 5 of 20 as of 2026-07-29, still the largest single-voice share), and it is anecdote-grade — his own war stories, no cohort. New question it opens: the **entry bar** — whether a partner of consequence takes a meeting with a no-name solo operator is exactly what the source skips, and exactly what decides if the lever is available to [[eugene]]. +- **The $0 start is no longer unaddressed by the Martell corpus (2026-07-23).** [[2026-07-23-make-my-first-100k-in-month]] is his first material for a pre-first-client operator: sequence over effort (offer → pre-sell → build), the money map (100×$1K sweet spot), inbound + outbound in parallel, phone-mining / ask-past-the-person, chat or cold-call close, $50 paid waitlist before building. It half-fills the "application unstarted" gap with a generic blueprint — but its sweet-spot shape (SMB, $1K/mo, chat/cold-call) fits [[eugene]]'s CV/embedded domain poorly (his natural deals are few × $10K+; see [[eugene]]). It also triggered the **single-voice audit**: its verbatim mechanism reuse exposed the 07-18 content source as near-certainly Martell's, and cast suspicion on the 07-17 anchor ("buy back 10 hours" = his book's frame). Confirming or refuting those two attributions is now a cheap, high-value owner action — **updated 2026-07-29:** it decides whether Martell holds **5, 6, or 7 of 20** sources (the 07-29 Claude-Code short was owner-attributed to him, taking the confirmed count from 4 to 5). +- ✅ **A third independent tradition arrived (2026-07-26) — now two sources deep.** [[2026-07-26-how-to-build-a-billion-dollar-company-2027]] and [[2026-07-26-main-principle-of-successful-business]] ([[oskar-hartmann]], VC/product world) are the first substantial voice outside both existing schools — and they independently restate the vault's spine: selling beats building (feature-#26 syndrome), founder sells first (as an *investment criterion*), SOM > TAM, sell dear (pricing power = PMF), **sell first, then build** (money is the only honest demand signal). After the single-voice audit shrank the US pole, this materially rebuilds the vault's independence base. The pair also delivers the first true counter-voice on [[partnerships]] (partner hope disappoints 100–200×; many partners or none), the first independent corroboration of [[cloning-over-originality]] (Samwer's fake-button clone; app studios that forbid inventing), and four new concept pages: [[sales-channel-as-moat]] (moat #3), [[unit-economics]] (the flagged CAC/LTV gap, **partially closed**), [[venture-fit]], [[sell-before-build]] (the validate-with-money discipline, three-tradition). The second source shows **framework stability** — it restates rather than contradicts the first. Caveats: one author, stage-war-story grade, a coach's incentive (paid "unicorn creator" program), a **scope mismatch** (product startups vs dev services — transfer flagged per page), and two of his test mechanics are deception-based (fake payment screens/buttons — recorded, not endorsed). +- **The adversarial source is time-scoped and one-sided too.** [[ai-productivity-evidence]] is 2023–2025 evidence (METR calls its own result "historical"), mostly non-developer for its strongest claim, and has its own incentives (a Copilot RCT by its makers; a survey firm with mild AI-skeptic interest). It is held to the same standard as the promotional sources: it *qualifies* the thesis, it does not demolish it. A **pro-thesis rigorous source** (RCT-grade evidence that AI *does* zero the cost for some real dev segment) would now balance the vault further. +- **When to productize** is disputed: offer-first (immediately) vs. delivery-first (after 2–3 identical projects). The offer-first camp gained its first independent voice 2026-07-26 ([[oskar-hartmann]]'s "sell first, then build") — though read precisely the camps may answer different questions (validate-before-build vs standardize-after-repetition), which would dissolve the dispute; vault synthesis, unstated by sources. See [[productized-service]], [[sell-before-build]]. +- **What the moat actually is** — proven *method* ([[methodology-as-moat]]) or in-person *relationships* ([[relationships-as-moat]])? Two credible answers, probably split by audience. +- **No market/currency context.** The $1K/mo floor, $200/mo substitute, and 30–50% margins assume a (mostly US) market. Sebastian suggests the $200 substitute may not even apply at locked-down enterprise scale. Untested for the owner's market. +- **Gaps flagged by the corpus's own meta-analysis** — one now partially filled: ~~B2B unit economics (CAC/LTV)~~ → general principles landed 2026-07-26 ([[unit-economics]]: full-cost pricing, LTV×⅓ CAC, buffer rule), though the *B2B-services* version (lumpy project LTV) is still missing. Still unfilled: legal packaging of a solution/SLA contract, concrete CIS/EU niches, the owner's own Before/After case studies, and a "we'll think about it" objection script — see [[2026-06-15-meta-analysis-selling-dev-in-ai-era]]. +- **Application has started (2026-07-26) — and is now an experiment awaiting data.** [[2026-07-26-eugene-90-day-plan]] maps the corpus onto [[eugene]]'s business for the first time: channels named (one lever, three venues — warm mining / one recurring industry room / partner archetype), a smallest paid test proposed (fixed-scope paid diagnostic), and a pre-committed Day-90 gate scored on **inputs**. It resolves the vault's in-person-vs-[[marketing-system]] tension **by stage** — one-to-one is the engine, the system gets a ~2h/week deposit because its lag is ~6 months and because publishing doubles as the articulation reps [[technical-founder-trap]] prescribes. What remains genuinely unstarted: the **niche is still a vault inference, not his choice** (assumptions A2/A5 carry the whole channel decision), the industry room is unnamed, and no case study exists yet. The plan's Week-2 phone mine is also the first proposed discriminator between the two rival diagnoses of his blocker. + +## Contradictions / Uncertainty + +- **AI capability — hype vs. measured evidence (the foundational one).** Every promotional source assumes AI has zeroed commodity execution ($200/mo substitute; coding cost → 0; seniors up / juniors out). The vault's first adversarial source ([[ai-productivity-evidence]]) brings RCT/peer-reviewed evidence that the real effect is *modest, novice-tilted, and overstated by perception* — experts measured 19% slower (METR), novices gaining most (Brynjolfsson), trust low and falling. It **qualifies rather than refutes**: average effects are still positive, and the evidence is early-2025-scoped. But it means the premise beneath *both branches* is contested, not settled — recorded on [[ai-market-shift]], [[seniority-and-ai]], [[future-of-engineering-work]]. +- **Online vs. in-person — the sharpest *channel* split.** [[sebastian]] rates all online outreach "Big zero" and says only in-person builds closing trust; [[ab-analytics]] and [[dmitry-rodenko]] run cold email / LinkedIn / outbound as live channels; [[information-vs-implementation]] and now [[dan-martell]] stake out the far end — organic content as the *entire* lead engine. Best read: **audience-dependent** (enterprise → in-person; SMB/startup → online still works), not a universal law. Note the *partial agreement* — AB Analytics' highest-value tier is also in-person. Unresolved; the content pole's "two voices" turned out to be almost certainly **one** ([[dan-martell]] — the 07-18 source's anonymous speaker is near-certainly him, 2026-07-23), and neither clip has conversion data, so the pole is one coach's corpus against Sebastian's one interview. **New nuance (2026-07-22):** on *enterprise* specifically, the poles converge — [[dan-martell]]'s own play there is trust-mediated, in-person entry (via partners: [[partnerships]]), differing from Sebastian only on whose trust (borrowed vs. built). The strongest support yet for the audience-dependent reconciliation: even the content pole doesn't prescribe content for enterprise doors — [[client-acquisition-channels]], [[relationships-as-moat]]. +- **How many channels — one or three?** [[dan-martell]]: pick **one** lever, 90 days. [[ab-analytics]]: pick **three** channels, 90 days. Same time unit, opposite N, both framed as *the* anti-dabbling discipline, neither with data. Possibly a units mismatch (broad lever vs. specific venue) — inferred, unstated, unresolved — and now complicated from inside: Martell's own $0 blueprint runs inbound + outbound **in parallel** (2026-07-23), so the pick-one rule is at best stage-scoped. **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 ("one channel = concentration risk") — the closest any source comes to stating the staged reconciliation the vault had inferred — [[client-acquisition-channels]], [[marketing-system]]. +- **Why a technical operator stalls — two rival diagnoses.** [[technical-founder-trap]]: you can solve but can't *explain*, so fix it with reps at explaining. [[relationships-as-moat]] / [[sebastian]]: explanation isn't the issue, *absent in-person trust* is, so fix it by showing up. Different causal claims about the same symptom, both single-source, no evidence to choose. They may compose (trust necessary, articulation sufficient) — untested. Directly relevant to [[eugene]]. +- **Three moats.** Is the defensible asset a proven *method* ([[methodology-as-moat]]), in-person *relationships* ([[relationships-as-moat]]), or the *repeatable sales channel* ([[sales-channel-as-moat]], added 2026-07-26)? All argued credibly, each by a different voice/tradition; likely split by [[niche-selection]] and stage. Unresolved. +- **Calls vs. chat.** The offer-design video says the market is call-fatigued (sell in chat); the June-15 sources say the founder picks up the phone. Possibly different funnel stages — and softened 2026-07-23: Martell's $100K blueprint prescribes **both** (chat-DM and cold calls side by side), and if he is also the 07-17 speaker the two "poles" were one person addressing different buyers — [[sales-discipline]]. +- **"Sound unique" vs. "don't be unique."** Video: frame it so it sounds unique; Rodenko: business buys a *proven method*, "unique" reads as "don't experiment on me." Tentatively reconciled as distinctive *packaging* + unremarkable *risk* — [[methodology-as-moat]]. +- **Cloning vs. moat.** A cloned method ([[cloning-over-originality]]) can't also be uniquely yours ([[methodology-as-moat]]); the implicit answer is that the *combination* is unclonable — asserted, not argued. +- **Statistics are now attributable but unverified.** 90% below minimum wage; ~80% of deals after touch 5; 91% vs 11% referrals; 47% subject-line open rate; $1:$6 AI spend; 30–50% Solution margin; 15–25% webinar; Rezi $293k/mo; Flowtown 350K visitors → 50K customers; "8 figures by chat"; and (2026-07-26) partner plays 100–200× under expectations; $1,000 credit-card CAC / ⅓-of-LTV rule; ~$4B AI-lab PE joint ventures; 12h screen / 40 GB/day; ~$10M Super Bowl spot; Apple 45× under Cook; FlatPay 10–20 terminals/rep/month; <$1K per app demand test; 100K Tesla preorders; $5M prepaid robot-data contracts; 3–5× one-word conversion swings. Each now traces to a named source, but those roots are promotional videos and stage talks. **Do not repeat as fact.** +- **Junior pipeline paradox.** If [[seniority-and-ai|juniors are frozen out]], seniors stop being produced — raised, unresolved. The adversarial evidence complicates it further: if AI's productivity gains actually accrue *most* to juniors ([[ai-productivity-evidence]]), "freeze juniors out" may be the wrong response to begin with — though whether that shows up in junior hiring/wages is unmeasured. +- **Single-source pages** marked `Status: tentative`: [[offer-ladder]] (the price ladder specifically), [[solution-vs-staff-augmentation]], [[team-growth-ceiling]], [[marketing-system]] (the three-lever framework; its machine-vs-arriving-demand core gained an independent second voice 2026-07-26), [[technical-founder-trap]], [[partnerships]] (single-*author* mechanism; the *warning* side is two-voice since 2026-07-26), [[sales-channel-as-moat]], [[unit-economics]], [[venture-fit]] (all three [[oskar-hartmann]]-only), and the four engineering-work concepts carried by the lone [[2026-07-06-sebastian-interview-ai-and-software-engineering|interview]] — two of which ([[seniority-and-ai]], [[future-of-engineering-work]]) now also carry adversarial counter-evidence and are marked `Status: contested`. [[ai-productivity-evidence]] is itself single-source (one deep-research dossier), also `tentative`. +- ✅ **A hidden dependency between sources — confirmed 2026-07-20; grown to five confirmed + two suspected 2026-07-29.** The unnamed speaker of [[2026-07-19-your-company-cant-outgrow-your-team]] is [[dan-martell]] (confirmed by the vault owner); [[2026-07-22-stop-cold-calling-do-this-instead]] and [[2026-07-23-make-my-first-100k-in-month]] name him outright; and the anonymous 07-29 Claude-Code short was owner-attributed to him the day it was ingested — **5 of 20 sources**, spanning Branch A and Branch C. The 07-23 ingest also exposed two more: [[2026-07-18-information-is-free-implementation-is-paid]] is **near-certainly** his (verbatim reuse of the scramble trick, the "nuanced and observable problems" prompt, and the describe-their-pain line in a named-Martell video), and [[2026-07-17-design-the-perfect-offer]] is **plausibly** his ("buy back 10 hours of your time" — *Buy Back Your Time* is his book; $997 ≈ his $1K sweet spot; chat-first close). If both hold he authors **7 of 20**, including one of the vault's two "independent anchors" — meaning Branch C, [[marketing-system]], [[partnerships]], [[information-vs-implementation]], and possibly [[offer-ladder]]/the $1K floor are **one worldview**, and intra-US-pole "convergence" is largely self-agreement. The cross-tradition RU↔US convergence survives (Rodenko, AB Analytics, Tony are independent), but it now carries nearly all the independence weight. One coherent engine runs the whole corpus: deliberate practice at volume, systematize the accident, sequence over effort. Standing caution: a coach whose diagnosis is always "the constraint is internal and fixable" describes a world where coaching is by construction the answer. diff --git a/wiki/queries/2026-07-17-best-method-first-client.md b/wiki/queries/2026-07-17-best-method-first-client.md new file mode 100644 index 0000000..670f279 --- /dev/null +++ b/wiki/queries/2026-07-17-best-method-first-client.md @@ -0,0 +1,101 @@ +# Best Method to Find the First Client + +#query #sales #outbound + +## Question asked + +> What would be the best method to find the first client? + +## Answer + +There is no single magic channel in the corpus, but the sources do converge on a +best *method* — a short sequence, not a one-off tactic. For a **literal first** +client (no case studies, no referrals yet): + +**Pick one narrow niche, then work a warm / repeat-contact (in-person) channel with +disciplined multi-touch follow-up — rather than leaning on cold online outreach.** + +This is the highest-confidence recommendation because it is the one prescription two +otherwise-disagreeing traditions in the vault independently endorse ([[ab-analytics]] +and [[sebastian]]). + +### The sequence + +1. **Niche first — it's a precondition.** "Niche is upstream of everything": without + an ICP you cannot outbound, productize, or delegate sales at all + ([[niche-selection]], [[2026-06-15-more-clients-dev-agency]]). Sell to leadership + not implementers; go where AI is weak; be specific ("Shopify dev for fashion + brands", not "web developer"). +2. **For client #1, favor a warm/in-person channel** where the audience is + pre-qualified and you can show up repeatedly. AB Analytics' most-underrated pick is + the **Chamber of Commerce** (member directory = pre-qualified list; show up 3× = + "regular", 6× = "trusted", then invited to speak); also BNI / local business groups + ([[2026-06-15-17-ways-first-client]]). [[sebastian]] describes the identical + mechanic — trust forms when someone meets you *the same in different circumstances* + → recognition → referrals ([[relationships-as-moat]]). +3. **Work it with discipline, not intensity.** 3 channels × 90 days; **5+ follow-up + touches** (Day 0→3→7→14→30) — ~80% of deals reportedly close after the 5th contact, + most quit after the first; the founder does the selling. "A year of repackaging is + for people afraid to pick up the phone." ([[sales-discipline]]) +4. **Convert client #1 into [[referrals]] immediately** — highest-converting, ~zero-cost, + but it cannot bootstrap you (needs an existing client). Exploits the gap: 91% would + refer, only 11% are asked. "Client #1 is hardest, #5 easier, #10 comes to you." + ([[2026-06-15-17-ways-first-client]]) + +### Why in-person over cold online for the *first* one specifically + +The vault's sharpest unresolved split is online-vs-in-person: [[sebastian]] rates all +online outreach "Big zero"; [[ab-analytics]] and Tony run cold email / LinkedIn as +live channels. Best current read: **audience-dependent** — enterprise buyers ignore +cold outreach (→ in-person), SMB/startup buyers still convert on it (→ online is a +legitimate lower tier). In-person is the low-variance bet *both* sides endorse (even +AB Analytics rates its in-person Tier 2 as the highest-value ground, with a +recognition-through-repetition mechanic identical to Sebastian's). Lean on cold online +only if the target buyer is SMB/startup. See [[client-acquisition-channels]]. + +### Application to the likely vault owner ([[eugene]]) + +Eugene's stated blocker (~6 months) is building a professional network, and he had +been investing in LinkedIn/articles. The corpus points squarely at **reallocating that +effort to recurring in-person events** — exactly Sebastian's advice to him in the +interview. This is the concrete, self-directed reading of "best method" for this vault. + +## Evidence trail + +- Channel taxonomy, Chamber of Commerce, 3×/6× recognition, referral 91%/11%, "client + #1 is hardest" — [[2026-06-15-17-ways-first-client]] ([[ab-analytics]]) +- Niche as precondition ("niche is upstream of everything") — [[2026-06-15-more-clients-dev-agency]], [[niche-selection]] +- 5 touches / Day 0→3→7→14→30 cadence, 3×90, founder sells, "afraid to pick up the + phone" — [[sales-discipline]] +- In-person trust as the AI-proof moat; recognition-through-repeat-contact — [[relationships-as-moat]], [[2026-07-06-sebastian-interview-ai-and-software-engineering]] ([[sebastian]]) +- Online-vs-in-person split and the audience-based reconciliation — [[client-acquisition-channels]] +- Eugene's networking blocker and channel reallocation — [[eugene]] + +**Caveat on evidence quality:** every quantitative claim (80% after 5th touch, +91%/11% referrals, 47% subject line) traces to promotional YouTube videos — +*attributable, not independently verified*. The vault also has **no adversarial or +failure-case source** on any of this. Treat the sequence as the corpus's best +consensus, not a proven playbook. + +> *Lint note (2026-07-18):* the vault's first adversarial source, [[ai-productivity-evidence]], has since been added — but it tests the **AI-capability premise**, not these channel/sales claims, which remain un-countered. This caveat still holds for the method above. + +> *Successor (2026-07-26):* this page answers **what method**; [[2026-07-26-eugene-90-day-plan]] +> answers **on what schedule**, with named venues, a Day-90 gate, and the +> in-person-vs-[[marketing-system]] tension resolved by stage. It keeps this page's core +> recommendation intact — warm/in-person first — and adds the parts left open below. + +## Follow-up questions + +- What is [[eugene]]'s actual niche and buyer type? The online-vs-in-person choice + hinges on it, and no niche has been selected yet. +- What is the minimum in-person cadence that builds "recognition value" for someone + operating largely remotely? +- Is there a warm-intro path faster than cold-in-person — e.g. mining Eugene's existing + content audience or embedded/CV professional contacts for the first engagement? + +## Whether this output changed existing pages + +Yes — added inbound links to this query from [[client-acquisition-channels]] and +[[eugene]] (both had this exact question open in their "Next Questions"). No concept or +source claim was altered; this page is a synthesis of existing pages, not new evidence. +Cataloged in [[index]] and logged in [[log]]. diff --git a/wiki/queries/2026-07-26-eugene-90-day-plan.md b/wiki/queries/2026-07-26-eugene-90-day-plan.md new file mode 100644 index 0000000..7a6d7d0 --- /dev/null +++ b/wiki/queries/2026-07-26-eugene-90-day-plan.md @@ -0,0 +1,244 @@ +# Eugene's Concrete 90-Day Plan + +#query #sales #planning + +## Question asked + +> Turn the corpus into [[eugene]]'s concrete 90-day channel/niche plan — the dated +> version [[2026-07-17-best-method-first-client]] stops short of — and resolve the live +> tension inside it: work the in-person first-client route, or build a +> [[marketing-system]] early? + +## Assumptions this plan rests on + +Stated up front so the plan is falsifiable rather than merely plausible. Each is a vault +inference, not a sourced fact: + +| # | Assumption | Status | +|---|---|---| +| A1 | [[eugene]] is the vault owner | `tentative` — circumstantial (insin, the harness) | +| A2 | His target buyers are industrial-equipment vendors / machine-builder integrators needing CV & embedded work | `tentative` — vault inference, never stated by him | +| A3 | His natural deal shape is few × $10K+, not 100 × $1K/mo | `tentative` — inferred from domain | +| A4 | He has *some* prior paid work to mine for a result-pattern | **unverified** — if false, Week 1 step 2 drops and Week 2 carries more load | +| A5 | Enterprise-lite industrial buyers behave closer to [[sebastian]]'s enterprise than to [[dan-martell]]'s SMB | `tentative` — this is the single assumption the channel choice hangs on | + +If A2 or A5 turn out wrong, the channel mix below is wrong and the online tier reopens. + +## Answer — the short form + +**One-to-one, in-person-weighted acquisition is the engine for these 90 days. The +[[marketing-system]] gets a small fixed time deposit — not because it produces leads in +this window (it won't), but because its clock is ~6 months long and because publishing +*is* the articulation practice that may be his actual blocker.** + +That is the resolution of the live tension, and it is not a compromise — it follows from +the vault's own stage reading. + +### Why the tension resolves this way + +The vault had already half-inferred it; [[oskar-hartmann]] nearly states it outright +(*one repeatable channel builds the company; multichannel is a resilience property of +scale*). Three supports: + +1. **The three-lever map is addressed to the wrong stage.** [[marketing-system]]'s + pick-one-lever rule comes from a clip aimed at a founder with a stalled $1.5M. It + omits outbound, [[referrals]], and in-person events entirely — i.e. the whole + first-client toolkit — because those aren't *scalable* levers, not because they don't + work ([[client-acquisition-channels]]). +2. **The same author runs one-to-one at $0.** His own $0→$100K blueprint prescribes + phone-mining and cold calls ([[2026-07-23-make-my-first-100k-in-month]]). The + pick-one-lever rule is stage-scoped by his own practice. +3. **The two poles agree about *this* buyer.** On enterprise specifically, + [[sebastian]] and [[dan-martell]] — who agree on nothing else about channels — + both say cold outreach doesn't open the door and trust does; they differ only on + built vs. borrowed trust ([[relationships-as-moat]], [[partnerships]]). + +**But the system isn't deferred to zero**, for one reason the stage reading alone misses: +[[marketing-system]]'s six-month lag means "start it when you need it" starts it six +months late. And publishing doubles as reps at explaining — the fix prescribed by the +*rival* diagnosis of Eugene's blocker ([[technical-founder-trap]]). A small deposit buys +both. It is budgeted below as ~2 h/week and explicitly **not** measured on leads. + +### The channel count, settled for this case + +[[ab-analytics]] says 3 channels × 90 days; [[dan-martell]] says 1 lever × 90 days +(`the vault's standing conflict`). Under the units reading the vault infers — a *lever* +is a discipline, a *channel* is a venue — both are satisfiable at once: **one lever +(relationship-mediated one-to-one), three venues.** + +| Venue | Tier ([[client-acquisition-channels]]) | Why this one | +|---|---|---| +| **1. Warm mining of existing contacts** | Common / [[referrals]] | The only referral-shaped motion that needs no past client; cheapest, fastest | +| **2. One recurring industry room** — machine-builder / automation association, regional trade fair, not a generic Chamber | Low-key (in-person) | The tier both [[ab-analytics]] and [[sebastian]] rate highest; "3× = regular, 6× = trusted" needs *recurring*, so pick by calendar not prestige | +| **3. Partner-archetype recruiting** — integrators & equipment vendors who already hold the buyer | Out-of-the-box | [[partnerships]]: borrowed credibility. Per [[oskar-hartmann]]'s warning, court **many small partners, never one anchor** | + +Deliberately excluded: cold email/LinkedIn campaigns at volume (A5 says this buyer +ignores them, and it is the effort that already failed him for ~6 months); the 100 × $1K/mo +money map (wrong deal shape, A3); building anything before payment. + +## The plan — 2026-07-26 → 2026-10-24 + +### Week 1 (Jul 26 – Aug 1) — Name the target, fix the words + +1. **Write the SOM in one sentence** and list **10 named prospects** — companies, not a + category ([[tam-sam-som]], [[sell-before-build]]). If the list can't reach 10, the + niche is wrong or too narrow; that failure is the week's most valuable output. +2. **Old-client mining** (per A4): call 3–5 past clients/employers — *"what result were + you paying me to get?"*, never *"why did you choose us?"* ([[pain-discovery]]). +3. **Offer formula:** *"we do X for [ICP] to close Y pain and get Z result."* +4. **Commodity test:** strip the words "development", "computer vision", and every + technology name. What's left? If nothing, there is no offer yet + ([[productized-service]]). +5. **The articulation rep:** say the offer to one non-engineer and have them repeat it + back. A [[referrals|referral]] only travels if the referrer can restate it in a + sentence — which is why this sits in Week 1 and not in the content bucket + ([[technical-founder-trap]]). + +### Week 2 (Aug 2 – Aug 8) — The diagnostic that costs an afternoon + +Run the **phone mine**: go through existing contacts and *ask past the person* — "do you +know anyone dealing with [the pain]?" Often lands on "yeah, me"; otherwise yields +warm, name-carrying intros ([[referrals]], [[2026-07-23-make-my-first-100k-in-month]]). + +**This is also the experiment that discriminates between the vault's two rival diagnoses +of his 6-month blocker** — a test the vault has flagged as needed but never specified: + +| What happens | Diagnosis | What to fix in Weeks 3+ | +|---|---|---| +| Contacts engage warmly but **can't restate** what he does | [[technical-founder-trap]] — articulation | Reps at explaining; the content deposit earns its keep | +| Contacts restate it fine but **know nobody** to send | [[relationships-as-moat]] — network reach | Weight venue 2 & 3 harder; the rooms are the work | +| Neither — low response | Relationship decay, not either diagnosis | Rebuild contact-by-contact before scaling any channel | + +Vault synthesis; no source proposes this test. + +### Weeks 3–4 (Aug 9 – Aug 22) — Open the three venues + +- Book the **recurring** industry room through December. Recurrence is the mechanic, not + attendance ([[relationships-as-moat]]). +- Identify 5–10 candidate **partner** organizations; approach as peers, not as a vendor + ([[partnerships]]). +- First touches on the 10 named prospects, **each customized** — the template is a + starting point, never a mass send ([[2026-06-15-linkedin-mail-template]]). +- **Follow-up cadence: Day 0 → 3 → 7 → 14 → 30**, 5 touches minimum, on every lead + ([[sales-discipline]]). +- Start the **~2 h/week content deposit**. Measured in reps, never views. Scrambled order + if published as know-how ([[information-vs-implementation]]). +- In every conversation, surface budget *before* presenting anything — obstacles, not + objections ([[sales-discipline]]). + +### Month 2 (Aug 23 – Sep 19) — Sell the smallest paid thing + +This answers the vault's own open question — *what is the smallest paid test for a +dev-services offer?* ([[sell-before-build]], flagged there as arguably this plan's +missing first step): + +> **A fixed-price, fixed-scope paid diagnostic** — a feasibility audit or discovery +> sprint on **one** inspection line / one device / one process. + +It satisfies four constraints at once: money lands **before** the build (the services +analogue of the paid waitlist — unpaid interest doesn't count); it is small enough to +clear without procurement (dodging the whale-client trap [[oskar-hartmann]] documents); +it manufactures the **Before/After case study** the corpus has flagged as missing for +him; and it is a legitimate entry rung of an [[offer-ladder]]. + +Also this month: + +- **Wizard-of-Oz the delivery.** First results produced semi-manually; automate only what + repeats ([[sell-before-build]]). +- **Pricing-power probe** on the second quote — raise it and watch. Cheapest PMF test in + the vault ([[pricing-from-value]]). +- **Ask for referrals immediately on delivery**, while the enthusiasm window is open — + 91% would, 11% are asked ([[referrals]]). + +### Month 3 (Sep 20 – Oct 24) — Standardize only what repeated + +- After **2–3 similar paid audits**, fix scope/price/name → a productized package + ([[productized-service]]). Not before: the offer-first vs delivery-first dispute is + unresolved, and this side of it costs nothing to obey. +- Write the case study as outcome + accountability, not scope + ([[outcome-based-selling]]). +- Try the Zendesk motion on the warmest prospect: *"how much do you spend on X?"* → + *"and if it were 10× less, would we talk?"* ([[2026-06-15-rodenko-selling-development-expensively]]). +- **Do not add a fourth venue.** Channel-hopping is the failure mode both rules agree on. + +## The Day-90 gate (2026-10-24) + +Review on **inputs**, decide on **outputs** — the reps-not-views substitution applied to +the plan itself ([[sales-discipline]], [[marketing-system]]). + +**Inputs — did the plan actually run?** (target: all four yes) + +- ≥ 10 named prospects worked to 5 touches each +- ≥ 6 appearances in the recurring room (the "trusted" threshold) +- ≥ 5 partner conversations opened +- ≥ 3 paid diagnostics *offered* (offered, not necessarily sold) + +**Outputs — what they mean for the next 90 days:** + +| Outcome | Read | Next | +|---|---|---| +| ≥ 1 paid diagnostic sold | Channel works | Repeat, productize, keep the system deposit small | +| 0 sold, but inputs all hit | The channel or A2/A5 is wrong | Change **one** variable — niche before channel | +| Inputs missed | No evidence either way | Re-run; nothing has been tested yet | +| Sold, but only via venue 1 | Warm network worked, cold rooms didn't | This is the [[referrals]] ceiling arriving early — *now* the [[marketing-system]] decision becomes live | + +Thresholds are vault-inferred, not sourced. Their function is to be pre-committed, not +to be correct. + +## Evidence trail + +- Stage reading (one-to-one starts, systems scale); three-lever map's omissions — [[client-acquisition-channels]], [[marketing-system]] +- One channel then multichannel; SOM > TAM; whale-client trap; partner-hope warning — [[2026-07-26-how-to-build-a-billion-dollar-company-2027]] ([[oskar-hartmann]]), [[tam-sam-som]], [[partnerships]] +- Signal hierarchy, Wizard-of-Oz, paid-waitlist analogue, duration-without-revenue red flag — [[sell-before-build]], [[2026-07-26-main-principle-of-successful-business]] +- 3-tier channel taxonomy, 3×90, 3×/6× recognition, Day 0→3→7→14→30, 91%/11% — [[2026-06-15-17-ways-first-client]] ([[ab-analytics]]), [[sales-discipline]] +- In-person trust mechanics; "Big zero" on online outreach — [[relationships-as-moat]], [[2026-07-06-sebastian-interview-ai-and-software-engineering]] ([[sebastian]]) +- Phone mining / ask past the person; obstacles-not-objections; offer → pre-sell → build — [[2026-07-23-make-my-first-100k-in-month]] ([[dan-martell]]) +- Six-month lag, reps-not-views, referral dependency as ceiling — [[2026-07-20-referrals-will-sink-your-business]] +- Borrowed credibility, partner-archetype recruiting — [[2026-07-22-stop-cold-calling-do-this-instead]], [[partnerships]] +- Week-1 sequence (old-client mining, offer formula, commodity test) — [[2026-06-15-meta-analysis-selling-dev-in-ai-era]]'s 90-day roadmap, [[pain-discovery]], [[niche-selection]] +- Pricing-power probe, guarantee test — [[pricing-from-value]] +- Predecessor query (method, undated) — [[2026-07-17-best-method-first-client]] +- Eugene's blocker, deal shape, prior LinkedIn/articles effort — [[eugene]] + +**Caveat on evidence quality.** Every channel and sales claim underneath this plan traces +to promotional YouTube videos and stage talks — *attributable, not verified* +([[overview]] Contradictions). The vault still holds **no failure-case source for the +productized / sell-dear model itself**, so nothing here has been tested against a +documented loss. The one adversarially-verified source in the vault +([[ai-productivity-evidence]]) touches the AI-capability premise, not these tactics. +Treat this as a pre-committed experiment design, not a playbook known to work. + +## Follow-up questions + +- **Which specific association / trade fair** serves machine-builders and industrial + integrators in his region, and does it meet often enough for the 3×/6× mechanic? The + plan's venue 2 is unnamed and that is its weakest joint. +- **Will an industrial buyer pay for a diagnostic at all**, or is a free feasibility + assessment the market norm? If free is the norm, the smallest paid test must move + downstream and Month 2 needs redesign. +- Does the net-60/90 enterprise payment reality break the pre-payment rule for services + buyers of this size? (Open on [[sell-before-build]].) +- Is industrial CV/embedded a **beachhead or a fortress** niche? Changes what winning + the SOM should lead to (open on [[tam-sam-som]]). +- Still outstanding and cheap: confirm/refute the two suspected [[dan-martell]] + attributions — several rungs of this plan rest on his corpus, and it matters whether + they are 5 or 7 of 20 sources. *(Updated by lint 2026-07-29: a third anonymous + source — the Claude-Code short — was owner-attributed to him that day, moving the + confirmed count 4 → 5 and making this plan's reliance on his corpus heavier, not + lighter.)* + +## Whether this output changed existing pages + +Yes — five pages updated, no source claim altered. This page is synthesis over existing +pages plus four vault-original contributions: the **stage-based resolution of the +one-to-one vs. system tension** (with the six-month-lag exception that keeps the deposit +non-zero), the **phone mine as the discriminating test between the two rival diagnoses** +of Eugene's blocker, the **paid diagnostic as the smallest paid test for dev services** +(an open question on [[sell-before-build]]), and the **pre-committed Day-90 gate**. All +four are inference, marked as such. + +Updated: [[eugene]] (Next Questions closed; Related Pages), [[sell-before-build]] (its +smallest-paid-test question now has a proposed answer), [[client-acquisition-channels]] +(its Eugene channel question now answered), [[2026-07-17-best-method-first-client]] +(forward link to its dated successor), [[overview]] ("Application is unstarted" thread). +Cataloged in [[index]], logged in [[log]]. diff --git a/wiki/sources/2026-06-15-17-ways-first-client.md b/wiki/sources/2026-06-15-17-ways-first-client.md new file mode 100644 index 0000000..3c5c962 --- /dev/null +++ b/wiki/sources/2026-06-15-17-ways-first-client.md @@ -0,0 +1,52 @@ +# 17 Ways to Get Your 1st Client as a Developer in 2026 (AB Analytics) + +#source #sales #outbound #marketing + +## Source Metadata + +- **Date:** batched 2026-06-15; underlying video undated. Duration 40:49. +- **Raw path:** `raw/sources/17 ways to get your 1st client as a developer in 2026.md` +- **Source type:** YouTube video conclusions — <https://www.youtube.com/watch?v=mugDs0XaQ1A> +- **Speaker:** founder of [[ab-analytics]] (B2B AI consulting, LA) and the *Code to CEO* accelerator. +- **Ingestion date:** 2026-07-17 +- **Provenance role:** Primary source for the "AB Analytics" citations in [[2026-06-15-selling-development-services-in-the-ai-era]] — the origin of the follow-up statistics, the 3-channels×90-days rule, the DIY→DWY→DFY ladder, and the webinar formula. + +## Core Claims + +1. **Fish where no one else is fishing.** Most engineers fight for scraps on the same crowded channels (Upwork, generic LinkedIn/X). 17 channels are stacked in three tiers: common, low-key, out-of-the-box. +2. **Pick 3 methods — one per tier — and run them daily for 90 days** before adding more. "Consistency beats intensity every single time. 30 minutes a day beats five hours once a month." +3. **Follow up ≥5 times** — ~80% of sales happen after the 5th contact; most devs quit after one. +4. **Niche specificity beats volume** — "Shopify developer for fashion brands" outsells "web developer" everywhere. + +## Key Evidence / Details + +**Tier 1 — common (do not stay here):** (1) freelance platforms — ~18% take, race to the bottom, only sensible for a true beginner in a low-cost country; (2) **LinkedIn** — profile = resume+portfolio+sales page; connect with decision-makers and referral partners; never sell in message one; (3) **content marketing** — the contrarian rule: *don't start until you already make $10–15k/mo from outbound*, else you starve; content is a leverage layer, not a first channel; (4) **cold email** — subject line carries **47%** of the open, spend 50% of your time there; body < 100 words: context → observation → value → proof → one CTA; (5) **referrals** — highest-converting, ~0 cost; the gap is **91% would refer, only 11% are asked** — ask right after delivery, be specific, make it frictionless. + +**Follow-up cadence:** Day 0 → 3 → 7 → 14 → 30 (break-up email). This is the origin of the "5 touches" and cadence claims elsewhere in the vault. + +**Tier 2 — low-key (local/in-person):** Chamber of Commerce (the speaker's most underrated — 4000+ in the US, member directory = pre-qualified list, show up 3× = "regular", 6× = trusted, then invited to speak); local business groups (BNI members average ~$20k/yr in referred business); industry associations; high-end hotels ("sauna + bar" strategy); car shows/expos (rich attendees = business owners); local conferences (begging for speakers → instant credibility); golf courses (2 clients from ~40–50 hrs ≈ 20× ROI); premium gyms + country clubs (5am crowd = execs; he moved Crunch → **Equinox** for the $200+/mo ICP). + +**Tier 3 — out-of-the-box:** strategic partnerships (vendors serving your ICP); **productize services** — "the single biggest change to his client acquisition" — DIY → DWY → **DFY** (his focus today); in-person workshops (paid or free, libraries/co-working give space); case-study → **webinar funnel** — formula **60% teach / 20% case study / 20% offer → 15–25% conversion**; one webinar = 3–6 months of work. + +**Cross-cutting:** lifestyle-integrate the in-person channels (gym/hotels/car shows you'd attend anyway); track every stage (outreach→response→meeting→proposal→close); "client #1 is hardest, #5 easier, #10 comes to you." + +## Connections + +- [[client-acquisition-channels]] — this is the primary source for the channel taxonomy +- [[sales-discipline]] — 5 touches, 3×90, consistency>intensity, cadence, webinar formula +- [[relationships-as-moat]] — the Tier-2 in-person channels *partially agree* with Sebastian, while Tier-1 online channels contradict him +- [[productized-service]] — the DIY→DWY→DFY ladder +- [[niche-selection]] — niche specificity beats volume +- [[ab-analytics]] — speaker/org + +## Open Questions + +- The speaker plugs the *Code to CEO* accelerator throughout; named successes ("Paul," "John," "Dom") are members → treat metrics as **marketing-flavored claims, not independent data** (the raw note flags this explicitly). +- Premium-gym/country-club/hotel tactics assume disposable income and a major US city. +- Direct conflict with [[relationships-as-moat]]: this source rates LinkedIn/cold-email as live channels; Sebastian rates online outreach "Big zero." Unresolved. + +## Change Impact on Wiki + +- Named primary source behind the follow-up statistics and cadence in [[sales-discipline]] (hedge downgraded from "uncited via distillation" to "attributable YouTube claim, promotional context"). +- Created [[client-acquisition-channels]] (channel taxonomy) and entity [[ab-analytics]]. +- Supplied the in-person-vs-online tension that anchors [[relationships-as-moat]]. diff --git a/wiki/sources/2026-06-15-how-to-get-rich-cloning.md b/wiki/sources/2026-06-15-how-to-get-rich-cloning.md new file mode 100644 index 0000000..8604827 --- /dev/null +++ b/wiki/sources/2026-06-15-how-to-get-rich-cloning.md @@ -0,0 +1,47 @@ +# How to Get Rich So Fast It Feels Like CHEATING (Cloning) + +#source #method + +## Source Metadata + +- **Date:** batched 2026-06-15; underlying video undated. Duration 12:31. +- **Raw path:** `raw/sources/How to Get Rich So Fast It Feels Like CHEATING.md` +- **Source type:** YouTube video conclusions — <https://www.youtube.com/watch?v=KJSSvOY1UOk> +- **Ingestion date:** 2026-07-17 +- **Provenance role:** The full primary source behind [[cloning-over-originality]] (previously single-sourced only through the distillation's "Pabrai/cloning" citation). Centers on [[mohnish-pabrai]]. + +## Core Claims + +1. **The fastest path is shameless, total cloning** of someone who already won — including the boring parts. Almost nobody does it; the blocker is **ego, not information**. +2. **Two ego traps:** the *originality trap* (schools call copying "cheating"; adults inherit the shame) and *half-hearted cloning* (dipping a toe for a week and quitting). Pabrai's rule: **10,000% or nothing** — sampling single ideas is tasting, not cloning. +3. **Originality is an emergent property of deep, multi-source cloning** — not a starting condition. +4. **Letter of the rules > spirit of the rules, at the start.** Spirit-of-the-rules thinking is for masters; beginners use it to skip discipline. + +## Key Evidence / Details + +**The gas-station parable (full form):** two stations across the street, identical product. One wipes windshields and checks tires free and is packed; the other watches daily and refuses to copy it, and goes bankrupt — from ego, not missing information. + +**Pabrai → Buffett case study:** picked up *One Up on Wall Street* at Heathrow; learned Buffett returned 31%/yr for 40+ years (most investors don't clear 10%); decided "copy everything, don't add my own twist"; read every Buffett letter, watched every interview, attended the Berkshire meeting 20+ years, copied the morning routine, business structure, 5–6 hrs daily reading, working alone; outcome ~**$154M**; in 2007 paid **$650,000** for a charity lunch with Buffett, framed as *guru dakshina*. + +**Multi-source cloning:** Buffett for investing, Charlie Munger for thinking, Benjamin Graham for principles, philosophers for life decisions — "nobody else stacked those exact pieces the same way." + +**Illustrations of the method:** the *food-channel story* — a friend's polished, edited, subtitled recipe channel grew slowly; the niche's top channel had no subtitles, no music, no on-screen text, ~30-sec videos, proven topics. She was doing the opposite "to be original." She cloned the format exactly → first video 100K views, next 500K, *then* experimented. The *barber analogy* — nobody invents their own haircut technique on day one; you stand behind the best barber for weeks, copy the wrist/grip/small-talk, then experiment. Beginners skip exactly this step when starting a business or channel. + +**Practical method:** (1) pick ONE (not five inspirations — Pabrai went all-in on Buffett before branching); (2) go deep, understand *how* they think; (3) clone the boring parts (success is ~1,000 small stacked decisions); (4) adjust only after your hands understand the craft. + +## Connections + +- [[cloning-over-originality]] — this is the concept's primary source +- [[methodology-as-moat]] — the tension: a cloned method vs. a defensible one (resolved via "the combination is unclonable") +- [[sales-discipline]] — discipline is precisely the "boring part" to clone +- [[mohnish-pabrai]] — central figure + +## Open Questions + +- Buffett's 31%/40yr and Pabrai's ~$154M / $650k lunch are stated as fact but uncited here; broadly consistent with public accounts of Pabrai, but not independently verified in this vault. +- Combination-as-originality is asserted, not argued — if a combination becomes public (as it does once sold), what stops it being cloned in turn? See [[cloning-over-originality]]. + +## Change Impact on Wiki + +- Upgraded [[cloning-over-originality]] from single-source-via-distillation to a fully-sourced page; the `Status: tentative` was relaxed to reflect a real primary source (though still one advocacy video). +- Created entity [[mohnish-pabrai]]; Buffett/Munger/Graham are recorded there and in [[cloning-over-originality]] rather than as separate pages (supporting cast). diff --git a/wiki/sources/2026-06-15-konspekt-aphorisms.md b/wiki/sources/2026-06-15-konspekt-aphorisms.md new file mode 100644 index 0000000..a48f064 --- /dev/null +++ b/wiki/sources/2026-06-15-konspekt-aphorisms.md @@ -0,0 +1,43 @@ +# Конспект (Aphorisms) + +#source #sales #positioning + +## Source Metadata + +- **Date:** batched 2026-06-15; note created ~2026-06-11. A bare list of aphorisms, no headers. +- **Raw path:** `raw/sources/Конспект.md` +- **Source type:** Distilled aphorisms from a video — <https://www.youtube.com/watch?v=mnQX-JLi_oA> (the same video as [[2026-06-15-rodenko-selling-development-expensively]], so this is a terse companion capture of the Rodenko talk). +- **Ingestion date:** 2026-07-17 +- **Provenance role:** The "Конспект" cited throughout the distillation and meta-analysis. Because it shares a source URL with the Rodenko video, its lines corroborate rather than add independent evidence. + +## Core Claims (the aphorisms) + +- **"If you're on the same level as an Indian dev, you gave nothing beyond what that Indian dev gave — to enter a different category of people."** (Recorded verbatim for fidelity; the point is about commoditized skill level, but the phrasing leans on a nationality stereotype and is **not** reused in this vault's own writing — see [[methodology-as-moat]].) +- **Knowing where the underwater rocks are — that is your expertise.** +- The survivors are specialists who know their narrow niche and write skills. +- **Sell SOLUTIONS, not work.** Solutions cost more; on "work" you compete with Indian devs. +- **The most important thing in your offer is WHO you make it to.** +- If one person bought the product, there's no reason others won't — the problem isn't the product. +- Professional athletes don't go to *participate*; they go to **win**. A commander doesn't enter a battle without seeing the conditions for victory. +- **The money is with your old clients**, whose projects you closed long ago. +- Take 2–3 case studies with Before/After numbers as proof of expertise, and go compete. +- AI created a chance to get rich — and you're still out there selling hours. +- An offer starts from a criterion: what do you have now? here's what we can offer to improve it. + +## Connections + +- [[methodology-as-moat]] — "expertise = knowing where the rocks are"; the "Indian dev" commodity line +- [[outcome-based-selling]] — "sell solutions, not work"; 2–3 Before/After case studies +- [[niche-selection]] — "the most important thing is WHO"; "if one bought, others will" +- [[pain-discovery]] — "the money is with your old clients" +- [[sales-discipline]] — the athlete/commander "choose your fights" psychology +- Same-source companion: [[2026-06-15-rodenko-selling-development-expensively]] + +## Open Questions + +- Being a same-video capture, this adds emphasis but no independent corroboration for the Rodenko claims. + +## Change Impact on Wiki + +- Confirmed the wording behind several quotes already on the concept pages (traced now to their video). +- No new concepts; reinforced [[methodology-as-moat]], [[outcome-based-selling]], [[niche-selection]], [[pain-discovery]]. diff --git a/wiki/sources/2026-06-15-linkedin-mail-template.md b/wiki/sources/2026-06-15-linkedin-mail-template.md new file mode 100644 index 0000000..a2d6f2b --- /dev/null +++ b/wiki/sources/2026-06-15-linkedin-mail-template.md @@ -0,0 +1,50 @@ +# LinkedIn Mail Template + +#source #outbound #sales + +## Source Metadata + +- **Date:** batched 2026-06-15. +- **Raw path:** `raw/sources/Linked In mail template.md` +- **Source type:** A reusable first-touch message template (tool, not an argument). +- **Ingestion date:** 2026-07-17 +- **Provenance role:** The "Linked In mail template" listed as note #7 in the meta-analysis and referenced by the distillation. It is the concrete instance of the cold-message anatomy taught in [[2026-06-15-17-ways-first-client]]. + +## Core Claims + +The template itself (verbatim structure): + +``` +Hi [Name], + +Saw your post about [specific detail]. [Thoughtful comment about it]. + +I help [target audience] with [specific problem]. Just helped [similar company] achieve [specific result]. + +If I could help you do the same, would you be open to a brief chat? + +[Your name] +``` + +Its structure encodes the vault's outbound rules: open with **specific** evidence you read their post (not a generic hook), state ICP + problem, offer one proof point with a concrete result, and end with a single low-friction CTA. It matches the AB Analytics cold-message anatomy almost line for line. + +## Key Evidence / Details + +- **Must be customized every time** — every source that mentions templates ([[sales-discipline]], the distillation, AB Analytics) warns against mass-mailing it. The blanks are load-bearing: "[specific detail]", "[specific problem]", "[specific result]" are the parts that make it not read as spam. +- **No selling in message one** — the CTA is a chat, not a pitch, consistent with [[client-acquisition-channels]]. + +## Connections + +- [[client-acquisition-channels]] — the LinkedIn/cold-email channel this instantiates +- [[sales-discipline]] — customize-every-touch; the 5-touch cadence this opens +- [[outcome-based-selling]] — "[specific result]" is where a Before/After case study goes +- [[2026-06-15-17-ways-first-client]] — the source that teaches this anatomy + +## Open Questions + +- Its usefulness depends entirely on the quality of the research filling the blanks; the template alone is inert. +- Sits inside the unresolved online-vs-in-person debate — see [[relationships-as-moat]] (Sebastian would rate this channel "Big zero"). + +## Change Impact on Wiki + +- Recorded as the concrete artifact behind the outbound copy rules; linked from [[client-acquisition-channels]] and [[sales-discipline]]. No new concepts. diff --git a/wiki/sources/2026-06-15-making-money-with-ai-2026.md b/wiki/sources/2026-06-15-making-money-with-ai-2026.md new file mode 100644 index 0000000..7a76a52 --- /dev/null +++ b/wiki/sources/2026-06-15-making-money-with-ai-2026.md @@ -0,0 +1,45 @@ +# Как реально зарабатывать на ИИ в 2026 году (Making Money with AI in 2026) + +#source #ai #product + +## Source Metadata + +- **Date:** batched 2026-06-15; underlying video undated. Duration 19:20. +- **Raw path:** `raw/sources/как реально зарабатывать на ИИ в 2026 году.md` +- **Source type:** YouTube video conclusions — <https://www.youtube.com/watch?v=o7c4XdtzU30> +- **Ingestion date:** 2026-07-17 +- **Provenance role:** The "видео про ИИ-монетизацию" cited by the distillation and meta-analysis. **Primary origin of the four-part "pain with money" filter** that appears on [[pain-discovery]]. + +## Core Claims + +1. **Most AI projects die from "idea → code it in Claude/GPT → launch."** The right order is **validate market and pain first, write code last.** +2. **Three monetization paths**, each with a pipeline: **B2C** (low ticket $10–50, mass market), **B2B** (ticket $100–$100k+, more manual), **everyday AI** (services to ordinary people — coursework, presentations, texts). +3. **Solve a concrete pain, don't "build a platform."** Benefit before feature. A good product **embeds into an existing habit** rather than breaking it. + +## Key Evidence / Details + +**B2C pipeline (6 steps):** hypothesis → monetary market check (will they pay at all) → large-scale research (Reddit/X/YouTube/Telegram + GPT deep research) → manual data verification (GPT may fabricate) → pick a target segment (not "for everyone") → **only now** build. + +**B2B pipeline:** (0) pick a comfortable niche (online schools, HR agencies, lawyers…) → (1) find *many* companies (Telegram, X, LinkedIn, Google Maps, 2GIS, HH) → (2) "test the ground" via DMs, 3–4 questions about manual tasks (~10% reply) → (3) find **"pain with money": frequent, costs the business money, already solved with crutches, founder understands its value** → (4) MVP in **7–14 days**, usefulness over features. **Simplified B2B:** if you know business owners — meet, hear the pain, solve it, get paid → "connections matter." + +**Everyday-AI pipeline:** pick 2–3 services → collect sample work (cheap/free for friends) → find clients → run a Telegram channel, collect (filtered-positive) reviews → templatize into a "library." Scalable later into B2C/B2B. + +**The author's proof figures (all as claimed):** Rezi (B2C) $293,256/mo; Postiz (B2C) $109,000/mo; ChatSEO (B2B, started Nov 2025) $16,000/mo. + +## Connections + +- [[pain-discovery]] — primary source of the four-part "pain with money" filter +- [[productized-service]] — MVP in 7–14 days; benefit-before-feature; templatize into a library +- [[niche-selection]] — pick a target segment before building; "solve a pain, not a platform" +- [[relationships-as-moat]] — the "simplified B2B" path (know owners → meet → solve → paid) rhymes with Sebastian's connections thesis +- [[ai-market-shift]] — the solo-founder revenue figures feed the "team size is no longer a signal" thread + +## Open Questions + +- Rezi/Postiz/ChatSEO revenue figures are stated without citation; Rezi's ~$293k/mo especially should be treated as a claimed headline number. +- Pipelines are generic; no unit economics (CAC/LTV) — a gap the meta-analysis also flags. + +## Change Impact on Wiki + +- Established the **named origin** of the four-part pain filter on [[pain-discovery]] (previously attributed only to the distillation). +- Reinforced [[productized-service]] (MVP cadence, library/templatization) and the "team size ≠ seriousness" thread in [[ai-market-shift]]/[[future-of-engineering-work]]. diff --git a/wiki/sources/2026-06-15-meta-analysis-selling-dev-in-ai-era.md b/wiki/sources/2026-06-15-meta-analysis-selling-dev-in-ai-era.md new file mode 100644 index 0000000..0150973 --- /dev/null +++ b/wiki/sources/2026-06-15-meta-analysis-selling-dev-in-ai-era.md @@ -0,0 +1,50 @@ +# Мета-анализ Inbox — продажа услуг разработки в эпоху ИИ (Meta-Analysis) + +#source #meta #sales #ai + +## Source Metadata + +- **Date:** 2026-06-15 (stated: "Мета-анализ от 15.06.2026"). +- **Raw path:** `raw/sources/Метаанализ Inbox - продажи разработки в эпоху ИИ.md` +- **Source type:** Second-order synthesis mapping the seven "15-06-2026 Inbox" notes into one worldview and one action plan. +- **Ingestion date:** 2026-07-17 +- **Provenance role:** Sibling to [[2026-06-15-selling-development-services-in-the-ai-era]] — both are derived from the same seven primary notes. This one keeps the source attributions and adds a 90-day roadmap; the distillation stripped tactics to keep only principles. **Neither is primary evidence**; the seven notes are. + +## Core Claims + +1. **All seven notes describe one worldview from different angles** — a coherent "textbook" for how a developer/agency survives and earns in 2026 once AI has zeroed hourly development. +2. **TL;DR:** *Stop selling hours and stack. Find a narrow group with a concrete pain, package result + accountability into a productized offer, and knock methodically — 5 touches, across 3 channels, 90 days without switching.* +3. **If you haven't categorized yourself, the market categorizes you by hourly rate.** + +## Key Evidence / Details + +**Note map (angle / level):** [[2026-06-15-konspekt-aphorisms|Конспект]] (principles) · [[2026-06-15-rodenko-selling-development-expensively|Как продавать дорого]] (strategy) · [[2026-06-15-making-money-with-ai-2026|как зарабатывать на ИИ]] (strategy) · [[2026-06-15-how-to-get-rich-cloning|How to Get Rich]] (meta-method) · [[2026-06-15-more-clients-dev-agency|more clients]] (tactics) · [[2026-06-15-17-ways-first-client|17 ways]] (channels) · [[2026-06-15-linkedin-mail-template|LinkedIn template]] (tool). + +**Eight cross-cutting theses** it identifies across authors: (1) hourly era over; (2) sell result + accountability; (3) category = pain + result; (4) niche is upstream of all; (5) money is with old clients; (6) AI is a qualification filter; (7) WHO > WHAT; (8) follow-up discipline (Day 0→3→7→14→30). + +**Conflicts it surfaces (useful):** +- *Content-marketing timing* — Tony (3 posts/wk from the start) vs AB Analytics (don't start until $10–15k/mo). Reconciliation: LinkedIn presence as a *trust layer under outbound* ≠ content as a *primary channel*. +- *Uniqueness vs cloning* — Pabrai (clone 10,000%) vs Rodenko ("buy a proven method, not uniqueness"): consistent. Synthesis: clone the operating system of the successful, but position in a narrow segment where nobody fights. +- *Team size* — old 15-person T&M vs Rodenko's 4-person squad (~$7M/yr) vs solo-founder Rezi ($293k/mo): **team size is no longer a signal of seriousness.** + +**Gaps it flags (not covered by any note):** B2B unit economics (CAC/LTV); legal packaging of a solution contract (SLA/penalties); concrete AI-consulting niches for CIS/EU (all examples are US); the reader's own Before/After case studies; a lead-qualification script for "we'll think about it." + +**Its 90-day roadmap:** Week 1 audit & positioning (call 3–5 clients, find the profit pattern, write the offer formula, run the commodity test) → Month 1 first flow (3 channels = 1 common + 1 low-key + 1 creative; customize each first touch; 5 touches) → Months 2–3 productize (fixed DFY package; the Zendesk "how much do you spend on X / 10× less?" motion; add LinkedIn content once at $10–15k/mo). + +## Connections + +- [[2026-06-15-selling-development-services-in-the-ai-era]] — sibling distillation of the same corpus +- All seven primaries (linked in the note map above) +- [[client-acquisition-channels]] — the content-timing and 3-channel material +- [[cloning-over-originality]] · [[niche-selection]] · [[productized-service]] · [[sales-discipline]] — the cross-cutting theses +- [[overview]] — the vault's synthesis mirrors this note's "one worldview" framing + +## Open Questions + +- Being second-order, it repeats the primaries' uncited statistics; not independent corroboration. +- Its gap list (unit economics, legal packaging, CIS/EU niches, own case studies, objection-handling) is a good agenda for future sources to fill — none are in this vault yet. + +## Change Impact on Wiki + +- Used as a cross-check that the vault's concept set matches the corpus's own self-analysis; its five identified gaps were carried into [[overview]]'s Open Threads. +- No new concepts of its own (it summarizes); reinforced provenance links across the batch. diff --git a/wiki/sources/2026-06-15-more-clients-dev-agency.md b/wiki/sources/2026-06-15-more-clients-dev-agency.md new file mode 100644 index 0000000..52ee863 --- /dev/null +++ b/wiki/sources/2026-06-15-more-clients-dev-agency.md @@ -0,0 +1,44 @@ +# How to Get More Clients as a Software Development Agency (Tony) + +#source #sales #outbound #positioning + +## Source Metadata + +- **Date:** batched 2026-06-15; underlying video undated. Duration 5:20. +- **Raw path:** `raw/sources/How to get more clients as a software development agency.md` +- **Source type:** YouTube video conclusions — <https://www.youtube.com/watch?v=sqSg0cM9xzE> +- **Speaker:** Tony. +- **Ingestion date:** 2026-07-17 +- **Provenance role:** Primary source for the "Tony (agency)" citations in [[2026-06-15-selling-development-services-in-the-ai-era]] and the meta-analysis. + +## Core Claims + +1. **Niche is upstream of everything.** Without a clear ICP you can't do outbound at all, projects stay one-off custom, margins stay low, and sales can't be delegated. "Niche → productization → team scaling." +2. **Run a deliberate outbound motion** — high-touch/low-volume (podcasts inviting CXOs, roundtables, lunches) or high-volume/low-touch (LinkedIn conversational prospecting, cold email). Both work; mixing is fine. +3. **Back it with a social presence (the trust layer).** LinkedIn, ~3 posts/week. Posts rarely generate direct leads — they **grease the wheels** of outbound; the difference between a dead profile and an active one is sometimes the difference between signing and not. +4. **Software dev is a high-trust, high-relationship business** — even high-volume outbound must feel personal or it won't convert. + +## Key Evidence / Details + +**Three mistakes that kill dev-shop sales:** (1) marketing the tech stack ("excellent .NET developer") — buyers don't know what the stack means; target the *audience the stack implies*; (2) "we do everything for everybody" — alienates the niche; (3) price as an incentive (undercutting) — "devalues your service permanently… fastest path to bankruptcy." + +**How to find the niche:** look back at your most profitable clients for a pattern (problem/industry/software type) and double down; run messaging experiments; target the chosen ICP but don't reject other paying work while it ramps ("bills first"). + +## Connections + +- [[niche-selection]] — Tony's "niche is upstream of everything" is a primary anchor for this concept +- [[client-acquisition-channels]] — the high-touch vs high-volume posture, and the social-as-trust-layer idea +- [[sales-discipline]] — social presence as a persistent complement to episodic outbound +- [[productized-service]] — productization follows niche +- [[pricing-from-value]] — price-as-hook = bankruptcy +- Cross-source: the "social greases outbound" claim sits between AB Analytics ("don't start content until $10–15k/mo") and Sebastian ("online = zero") — see [[client-acquisition-channels]] + +## Open Questions + +- Tony flags a follow-up video on pricing as "the lever that can wipe out profits even with a full pipeline" — not in this vault. +- "Social greases outbound" is asserted from experience, unquantified. + +## Change Impact on Wiki + +- Named primary source for [[niche-selection]]'s "niche is upstream" framing and the stack-marketing mistake. +- Contributed the middle position in the content-marketing timing debate recorded in [[client-acquisition-channels]]. diff --git a/wiki/sources/2026-06-15-rodenko-selling-development-expensively.md b/wiki/sources/2026-06-15-rodenko-selling-development-expensively.md new file mode 100644 index 0000000..3c6fc2e --- /dev/null +++ b/wiki/sources/2026-06-15-rodenko-selling-development-expensively.md @@ -0,0 +1,65 @@ +# Как продавать услуги по разработке дорого (Rodenko — Selling Development Services at a Premium) + +#source #sales #pricing #positioning + +## Source Metadata + +- **Date:** batched 2026-06-15 ("15-06-2026 Inbox"); underlying video undated. Duration 58:22. +- **Raw path:** `raw/sources/Как продавать услуги по разработке дорого.md` +- **Source type:** YouTube video conclusions — <https://www.youtube.com/watch?v=mnQX-JLi_oA> +- **Speakers:** [[dmitry-rodenko]] (SaaS Founders) and Натан (Nathan). +- **Ingestion date:** 2026-07-17 +- **Provenance role:** This is the **primary upstream source** for most of the sales principles in [[2026-06-15-selling-development-services-in-the-ai-era]] (the "Роденко" citations there resolve to this video). Ingesting it converts many previously-uncited claims into ones attributable to a named speaker. + +## Core Claims + +1. **Hourly development is ending** — the buyer has a ~$200/mo AI alternative, so a rate war against cheap regions zeroes margin. Only **result and accountability** sell at a premium; everything else is cost the buyer will quickly compute. +2. **"Expensive" doesn't exist — "I don't see what for" does.** (Origin of the guarantee test now on [[pricing-from-value]].) +3. **Your value = what clients name when you ask "what result were you paying me to get?" Everything else is your cost.** +4. **Category = pain + result, not technology.** The commodity test: remove "development" and the stack name — what's left? "A commodity with a bow on it is still a commodity." +5. **Sell to leadership, not implementers.** To an implementer your AI is a job threat (you're a risk); to leadership you deliver a KPI. +6. **Business buys a proven method, not uniqueness.** "Unique = I'm afraid, don't experiment on me." +7. **Founder = head of sales.** "A year of repackaging is for people afraid to pick up the phone." + +## Key Evidence / Details + +**The guarantee test (canonical form):** *"If we guaranteed this result — is price still the problem?"* "Yes, still" → no money (not a client, haggling for its own sake). "No" → price was an excuse; the real gap was trust in value. + +**AI-as-filter, quantified:** a founder gives a ready AI-skill free on the first call ("try 30 days"). Of 10 first calls, 5 return for a second call, 1 closes a **$100k** project. Reaction meanings: "works" → value not needed; "didn't get to it" → no budget; "weak, too abstract, needs specifics" → **target client**. + +**Zendesk story (the canonical offer):** a client paid $30k/mo ($360k/yr) for Zendesk; the team built a custom solution for $2k/mo; the $100k project paid back in ~4 months. Outreach reduces to two questions: *"How much do you spend on Zendesk?"* → *"And if it were 30 instead of 300 — worth discussing?"* Ask about **real spend on a concrete operational action** and promise a **10× cut**. "Even if you're half wrong, you still delivered 5×." Don't chase "another Zendesk" — find similar operational pains in the same industry. + +**Where clients hide (spend structure):** service firms → payroll; manufacturing → materials then labor; narrow industries (fintech/medtech/cyber) → industry-specific SaaS spend. Aim the offer at the biggest cost line. + +**Squad-model (successful repositioning):** a former outstaffing shop whose seniors sat "on the shelf" next to $25/hr Indian devs stopped selling people; assembled squads of 4 (2 engineers + QA + PM); ICP = **startups that just raised a round** (shared pain: show investors results in 6 months); offer = "Start in 7 days, price of two US programmers, by month 6 you have something to show investors; if not, we finish at our expense." Now ~19 squads × $15–18k/mo ≈ **$7M/yr**, 90 people. They also teach their startups and help them find investors — building a "gang of founders" around themselves. + +**Solution vs Staff Aug** — full table on [[solution-vs-staff-augmentation]]. The **one valid combination**: sell and deploy a solution first, *then* leave a person on support — long cash flow plus continued contact. Two models otherwise require separate brands/sites. + +**Zero-budget tactics (15-person team):** audit closed projects (call and ask "what were you paying me for?"); drop "we need a 15-person team" as dogma (4 people close the same check); go through network with a *criterion* ("know anyone spending $100k/yr on helpdesk?"), not "I have 15 devs at $30/hr"; founder sells. "The best zero-budget marketing is to stop selling cheap. That's free." + +## Connections + +- [[pricing-from-value]] — origin of the guarantee test and "expensive doesn't exist" +- [[outcome-based-selling]] — "sell result + accountability"; the Zendesk offer +- [[pain-discovery]] — the spend-based 10× opener; old-client mining +- [[niche-selection]] — 80% is WHO; sell to leadership; go where AI is weak +- [[methodology-as-moat]] — "buy a proven method, not uniqueness" +- [[solution-vs-staff-augmentation]] — primary source of the model comparison and the one valid combination +- [[productized-service]] — productized offers win on cycle and margin +- [[ai-market-shift]] — $200/mo substitute; $1:$6 AI-to-specialist spend; AI-as-filter +- [[sales-discipline]] — founder-led sales; "afraid to pick up the phone" +- [[dmitry-rodenko]] — speaker +- Derived-from-this: [[2026-06-15-selling-development-services-in-the-ai-era]], [[2026-06-15-meta-analysis-selling-dev-in-ai-era]] + +## Open Questions + +- The $100k close and $7M squad figures are the speaker's anecdotes — plausible, uncorroborated. +- "Solution + staff-aug on one brand always collapses" is stated as a law; only the one valid combination (solution → support) is examined. +- The Zendesk 10× framing assumes an order-of-magnitude-compressible cost line. When is a cost *not* 10×-compressible? +- Nathan's distinct contribution vs Rodenko's is not separated in the notes. + +## Change Impact on Wiki + +- Became the named primary source behind [[pricing-from-value]], [[outcome-based-selling]], [[solution-vs-staff-augmentation]], and much of [[niche-selection]]/[[pain-discovery]] — those pages' "uncited via distillation" hedges were downgraded accordingly (still YouTube-claim provenance, now attributable). +- Added the **one valid Solution+StaffAug combination** and the **Squad-model** example to [[solution-vs-staff-augmentation]]. +- Created entity [[dmitry-rodenko]]. diff --git a/wiki/sources/2026-06-15-selling-development-services-in-the-ai-era.md b/wiki/sources/2026-06-15-selling-development-services-in-the-ai-era.md new file mode 100644 index 0000000..60495a8 --- /dev/null +++ b/wiki/sources/2026-06-15-selling-development-services-in-the-ai-era.md @@ -0,0 +1,106 @@ +# Принципы продажи услуг разработки в эпоху ИИ (Principles of Selling Development Services in the AI Era) + +#source #sales #positioning #pricing #outbound + +## Source Metadata + +- **Date:** 2026-06-15 (stated distillation date) +- **Raw path:** `raw/sources/Принципы продажи услуг разработки в эпоху ИИ.md` +- **Source type:** Russian-language meta-distillation — a synthesis of 5–7 prior notes, deliberately stripped of channels and tactics to leave only timeless principles +- **Ingestion date:** 2026-07-17 +- **Upstream sources (now ingested — 2026-07-17):** the seven primary notes this was distilled from are now in the vault: [[2026-06-15-konspekt-aphorisms|Конспект]], [[2026-06-15-rodenko-selling-development-expensively|Роденко/Натан]], [[2026-06-15-17-ways-first-client|AB Analytics]], [[2026-06-15-how-to-get-rich-cloning|Pabrai/cloning]], [[2026-06-15-more-clients-dev-agency|Tony/dev-agency]], [[2026-06-15-making-money-with-ai-2026|AI-monetization video]], and the [[2026-06-15-linkedin-mail-template|LinkedIn template]]; a sibling synthesis is [[2026-06-15-meta-analysis-selling-dev-in-ai-era|the meta-analysis]]. +- **Format note:** This is a **second-order distillation** — for any claim, prefer citing the primary note above. Its attributions are imperfect (e.g. it credits "Роденко" with follow-up statistics that actually come from AB Analytics). + +## Core Claims + +1. **Hourly development is dead.** The buyer has a ~$200/mo alternative (AI). Competing on rate zeroes out margin. +2. **"Expensive" doesn't exist. "I don't see what for" exists.** Test the objection: *"If we guaranteed the result — is price still the problem?"* Yes → they have no money. No → they never trusted the value. +3. **Business doesn't buy uniqueness, it buys a proven method.** "Unique" reads to a buyer as *"I'm afraid — don't experiment on me."* +4. **AI expands the funnel rather than eating it.** For every $1 a company spends on AI it spends ~$6 on specialists to configure it. +5. **Sell the result and accountability for it, not hours.** Willing to take accountability → the AI era makes you rich. Unwilling → a 12-month death sentence. +6. **Category = pain + result, not technology.** Commodity test: remove the word "development" and the stack name from your offer. What's left? Nothing → you're a commodity. +7. **80% of sales success is WHO you talk to, not WHAT you say.** If the offer won't sell, it's almost always the wrong audience. +8. **Sell to leadership, not to implementers.** To an implementer your AI is a threat to their job and you are a risk. To leadership you deliver a KPI. +9. **Go where AI is powerless** — narrow industry methodologies LLMs don't know. +10. **Originality is downstream of cloning, not upstream.** Copy at 10,000% first, adapt second. +11. **Consistency beats intensity.** 30 min/day > 5 hours once a month. + +## Key Evidence / Details + +**Finding pain with money attached** — a pain qualifies only if all four hold: it recurs often; it costs the business money; it's already being solved with duct-tape workarounds; the founder understands its value. Missing any → not a client. + +**The spend-based opener:** watch what they *spend on*, not what they *say*. Find an operational cost line → *"How much do you spend on X?"* → *"And if you spent 10× less — would we talk?"* Even if you're off by half, you still delivered 5×. + +**AI as a qualification filter** — don't hide the AI, weaponize it. Give a working AI skill away free for 30 days: + +| Reaction | Meaning | +|---|---| +| "It works" | Your value isn't needed. Not a client. | +| "We never got to it" | Task has no budget. Not a client. | +| "Weak, needs specifics" | **Target client.** | + +**Mining existing clients:** the money is with your old customers. Call your 3–5 best and ask *"what result were you paying me to get?"* — **not** "why did you choose us?", which only ever returns "good team". + +**Numbers cited (all uncited by the distillation):** + +- ~80% of deals close after the 5th touch; most people quit after the 1st. +- 91% of clients are willing to refer; only 11% are ever asked. The enthusiasm window right after delivery is short. +- Cold-email subject line carries 47% of open rate — spend 50% of your time on it. *"Quick question about [Company]'s checkout flow"* >> *"Ideas to improve your site"*. +- Webinar formula: 60% teaching + 20% case study + 20% offer → 15–25% conversion. +- 3 channels × 90 days; don't add methods until these are mastered. + +**Productize after 2–3 identical projects** — fixed price, fixed scope, a package name. Ladder: DIY → DWY → **DFY (Done For You)** = highest leverage. Benefit first, then feature. MVP in 7–14 days. + +**On cloning (the Pabrai method):** clone from *multiple* sources (Buffett for investing, Munger for thinking, Graham for principles) — originality is an emergent property of the combination, because nobody assembled those same pieces the same way. Clone the *boring* parts: success is ~1,000 small decisions, not one brilliant one. **Letter of the rules > spirit of the rules — at the start**; "spirit of the rules" is for masters, and beginners use it to excuse skipping discipline. *Gas-station parable:* one station wipes windshields and checks tires free and has a queue; the one across the street watches this daily and never copies it, then goes bankrupt — not from missing information, but from ego. + +**Deal psychology:** the client is not a prize — a deal is expertise exchanged for money, not charity from you nor a favor from them. Professionals choose which fights to enter (an athlete doesn't "participate in competitions", they go to **win**; a commander doesn't enter a battle without seeing the conditions for victory). If even one person bought, there's no reason others won't — the problem is never the product, it's WHO and HOW. *"If you're at the level of an Indian dev, you are one — just more expensive."* Knowing where the underwater rocks are **is** your expertise. + +**Minimum tactical kit:** 2–3 case studies with Before/After numbers (without them you have nothing to sell a result with); a first-touch template, customized every time, never mass-mailed. + +**Anti-patterns table (verbatim structure):** + +| Do | Don't | +|---|---| +| Sell the result | Sell hours or the stack | +| Category by pain+result | Category "we build X on Y" | +| Solution or Staff Aug under separate brands | Both models on one site | +| Customize every first touch | Mass-mail one template | +| Price via value | Price as a competitive weapon (= bankruptcy) | +| Narrow niche where AI is weak | "We do everything for everyone" | +| Ask for referrals immediately | Wait for "the right moment" | +| 5 follow-ups before "stop" | One shot and forget | +| 3 channels × 90 days | Change channels weekly | + +## Connections + +- [[productized-service]] — the 2–3-identical-projects trigger and the DIY→DWY→DFY ladder +- [[outcome-based-selling]] — result *and accountability for it*, the sharpest framing in the vault +- [[pricing-from-value]] — "expensive doesn't exist" and the guarantee test +- [[niche-selection]] — WHO over WHAT; sell to leadership; go where AI is weak +- [[pain-discovery]] — the four-part "pain with money" filter and the spend-based opener +- [[methodology-as-moat]] — business buys a proven method, not uniqueness +- [[ai-market-shift]] — the $1:$6 ratio and AI-as-qualification-filter +- [[sales-discipline]] — 5 touches, 3 channels × 90 days, referral timing, founder as head of sales +- [[cloning-over-originality]] — the Pabrai method, sourced entirely from here +- [[solution-vs-staff-augmentation]] — the model choice laid out side by side +- Cross-source: [[2026-07-17-design-the-perfect-offer]] independently reaches the same productization conclusion from a different tradition + +## Open Questions + +- **Every statistic here is now traceable to a named primary note but still not independently verified** (80% / 5th touch, 91% vs 11% referrals, 47% subject line, 15–25% webinar → [[2026-06-15-17-ways-first-client]]; $1:$6 AI spend → [[2026-06-15-rodenko-selling-development-expensively]]). Their root sources are promotional YouTube videos. Attributable, not confirmed — do not repeat as fact. +- ~~The 7 upstream notes live outside this vault.~~ **Resolved 2026-07-17:** all seven are now ingested into `raw/sources/` and summarized in `wiki/sources/` (see Source Metadata). Claims can now be traced to their primary note. +- Is "hourly development is dead" true across the board, or only for commodity work? Regulated/legacy/high-liability domains plausibly still bill hourly at healthy rates. [[2026-07-06-sebastian-interview-ai-and-software-engineering]] adds partial counter-evidence (enterprise/COBOL holdouts). +- The ~$200/mo AI alternative: is that a real substitute for a dev contract, or only for the low end of it? The claim is asserted, not demonstrated. +- "Solution and staff aug under one brand will always collapse into staff aug" — stated as a law, with no counter-example examined. +- *"If you're at the level of an Indian dev, you are one — just more expensive"* — recorded as written for fidelity. The underlying point is about commoditized skill level, but the phrasing trades on a nationality stereotype and shouldn't be reused in this vault's own writing. + +## Change Impact on Wiki + +Co-first ingest into an empty vault (alongside [[2026-07-17-design-the-perfect-offer]]). + +- Primary evidence for [[cloning-over-originality]], [[sales-discipline]], and [[solution-vs-staff-augmentation]] — all three were sourced solely from this page at first ingest. +- Corroborating second stream for [[productized-service]], [[outcome-based-selling]], [[pricing-from-value]], [[niche-selection]], [[pain-discovery]], [[methodology-as-moat]], [[ai-market-shift]] — reached independently of the other source, which raises confidence in those. +- Its founder-led-outbound posture conflicts with the other source's chat-first posture; recorded under Contradictions in [[sales-discipline]]. +- Its "business buys a proven method, not uniqueness" tensions against the other source's "frame it so it sounds unique"; recorded in [[methodology-as-moat]]. + +**Update 2026-07-17 (second batch):** superseded as a *primary* source. With the seven upstream notes now ingested, this page is best treated as a **derived index** into them — concept pages that once cited it as primary now cite the specific note ([[2026-06-15-rodenko-selling-development-expensively]], [[2026-06-15-17-ways-first-client]], [[2026-06-15-how-to-get-rich-cloning]], [[2026-06-15-making-money-with-ai-2026]]). Its content is unchanged and still an accurate summary; only its citation status dropped from primary to secondary. diff --git a/wiki/sources/2026-07-06-sebastian-interview-ai-and-software-engineering.md b/wiki/sources/2026-07-06-sebastian-interview-ai-and-software-engineering.md new file mode 100644 index 0000000..1d8ce2c --- /dev/null +++ b/wiki/sources/2026-07-06-sebastian-interview-ai-and-software-engineering.md @@ -0,0 +1,68 @@ +# Sebastian Interview — AI and Software Engineering + +#source #ai #interview #positioning + +## Source Metadata + +- **Date:** 2026-07-06 (file date; the conversation itself is undated — described as a pre-webinar talk) +- **Raw path:** `raw/sources/sebastian interview - conclusions and insights.md` +- **Source type:** ~56-min recorded conversation, conclusions document. Built from a Whisper large-v3 auto-transcript, speaker-diarized; quotes lightly cleaned. A few rapid-crosstalk moments may be mis-attributed. +- **Ingestion date:** 2026-07-17 +- **Participants:** [[sebastian]] (founder of [[virtido]], ~11-yr software outsourcing firm) and [[eugene]] (interviewer; CV/embedded developer, content creator, builder of a custom Claude Code harness). +- **Format note:** A conclusions/insights write-up, one interpretive layer above the transcript. Distinct in origin from the other sources in this vault (which are the "15-06-2026 Inbox" batch) — this is an independent stream. + +## Core Claims + +1. **The debate is settled: AI *can* write software. The whole game is now *how* you use it.** Cost of writing code trends to zero, so leverage moves entirely to directing and verifying the AI. See [[future-of-engineering-work]]. +2. **Teams collapse from ~8 to 2–3.** Scrum master + PM + requirements engineer + big dev team → one coordination/ownership role plus one or two agent-wranglers. +3. **Bring-your-own-harness maximizes individual leverage but dies in the enterprise.** Compliance and liability forbid ad-hoc per-developer setups → **the business opportunity is compliant, company-standard managed harnesses** for large regulated teams. See [[future-of-engineering-work]], [[niche-selection]]. +4. **Pure coding skill is commoditized; judgment, ownership, and relationships appreciate.** Claude "levels" a 20-year veteran and a fresh grad to similar output. +5. **Seniors became *more* valuable; juniors "completely irrelevant."** A senior's real product is risk reduction. See [[seniority-and-ai]]. +6. **Product ownership is the durable human skill** — own the outcome a user sees, not the ticket. See [[product-ownership]]. +7. **Relationships are the last non-commoditized asset, and only in-person builds them.** Online outreach (agencies, cold call, email, LinkedIn, content, SEO) is "Big zero." See [[relationships-as-moat]] — this is the source's standout and most contrarian claim. +8. **Decouple identity from profession**, or "we will feel worthless in a couple of years." + +## Key Evidence / Details + +**Enterprise reality (Sebastian's lens):** biggest clients forbid personal laptops — engineers use a centrally managed VM with **zero** ability to install their own tools. Reference points: a Roche SAP transformation ran ~1,200 engineers for years; banks first banned AI outright, now adopt cautiously "because it's just so good." + +**Why seniors win / the junior security argument:** 20 years = knowing where things typically go wrong, so you don't let the AI make those mistakes ("AI does the same mistakes humans do because it's trained on our mistakes"). The junior risk is a *security* argument: reflexively clicking "allow for all future" is how "API keys are leaked, databases get dumped." A junior can't evaluate a 250-line bash script; a senior at least could. *"Give a junior fresh out of university access to this almighty Claude and then access to the codebase — they will [wreck] it in two days."* + +**The profile-picture story (ownership):** an engineer implemented "change your photo," ticked every acceptance criterion, shipped it ugly (visible in the corner) because they never looked at the result. Reframe: stop thinking "what needs to be done" (tickets); think "what problem needs to be solved." *"No one ever needed a programmer… people have problems that you are solving."* + +**Planning / the printer anecdote:** a colleague (Daniel) floated returning to waterfall; Sebastian disagrees — coordination overhead now exceeds the work. On a 2-person project (~1 day/week each) he is **faster alone**. A new printer needed a direct-printing protocol in Java (never written) working in 2 days; he went on-site and Claude Code solved it in ~30 min. His edge was knowing how to instruct and verify, not to code. + +**Connections — the mechanics:** a connection forms not at first meeting but when you meet the *same* person in *different* circumstances → recognition → trust → referrals. Be memorable in your humanness (renovating a house, two kids, a cat) — not "I run a software company," which everyone forgets, because everyone now uses the same AI tools and everything online looks identical. Virtido's playful `humans.verti.com` "human badge" riffs on this. What works: showing up in person 2–4 days/week. What doesn't: *"sales agencies, cold calling, email marketing, LinkedIn campaigns, content, SEO. Zero. Big zero."* + +**Side points:** open source will grow (code becomes nearly free to give away; Eugene's cynical read: OSS is largely marketing). Legacy/hobby niches persist (COBOL in banks — no training data; people who code "like driving an old-timer car") but not where time/quality/money matter. Outsourcing economics: great engineers exist everywhere, but a low-cost expectation selects for bad code — pay $10k/mo for excellent people; an $800/mo hire won't beat a good, well-paid engineer. AI helps non-programmers too: profile ~2,000 LinkedIn/HR contacts into Obsidian, build RAG over your own information — "you can put your whole life into a RAG." + +**Internal disagreements:** personal vs company-managed harness (Eugene vs Sebastian); planning/waterfall (Daniel vs Sebastian); OSS motivation (Eugene: marketing; Sebastian: expects more); networking channels (Eugene invested in LinkedIn/articles; Sebastian: online outreach is a waste vs in-person). + +## Connections + +- [[relationships-as-moat]] — the connections thesis, primary source +- [[product-ownership]] — ownership as the durable skill +- [[seniority-and-ai]] — senior/junior value inversion; risk reduction +- [[future-of-engineering-work]] — team collapse, harness, enterprise lockdown, identity, OSS, legacy +- [[client-acquisition-channels]] — Sebastian's "in-person only" is the sharp counter-pole to the outbound channel taxonomy +- [[methodology-as-moat]] — competing account of *what* the moat is (method vs relationship) +- [[ai-market-shift]] — the same AI shift, seen from the labor/enterprise side +- [[sebastian]], [[eugene]], [[virtido]] — entities + +## Open Questions + +- How does AI transform *huge* (~1,200-engineer, multi-year) enterprise programs? Sebastian is candid he doesn't know. +- How do you unify wildly different personal workflows into one company process? (Eugene + a collaborator spent a month, failed.) +- Concretely, how does an individual build a connections network from a standing start? Principles given; the step-by-step is open. +- Sebastian's "online outreach = Big zero" is one founder's experience in an enterprise-services context. Does it generalize, or is it audience-specific (big enterprise buyers vs. SMB/startup buyers, where the other sources' channels may work)? +- Is [[eugene]] the owner of this vault? Internal details (the `insin` project, a custom Claude Code harness) match the vault owner's tooling. Recorded as inference, not fact. + +## Change Impact on Wiki + +Second-batch ingest; the only source in this batch not from the "15-06-2026 Inbox" corpus. + +- Created 4 new concepts primarily from this source: [[relationships-as-moat]], [[product-ownership]], [[seniority-and-ai]], [[future-of-engineering-work]]. +- Created entities [[sebastian]], [[eugene]], [[virtido]]. +- Introduced the vault's sharpest live contradiction: **in-person-only (Sebastian) vs. multi-channel outbound incl. online (AB Analytics / Tony / Rodenko)** — recorded in [[client-acquisition-channels]], [[sales-discipline]], and [[overview]]. +- Introduced a second moat account (relationships) alongside the existing one (methodology) — tension recorded in [[relationships-as-moat]] and [[methodology-as-moat]]. +- Broadened the vault's domain in [[overview]] from "selling services in the AI era" to also include positioning engineering work/careers. diff --git a/wiki/sources/2026-07-17-design-the-perfect-offer.md b/wiki/sources/2026-07-17-design-the-perfect-offer.md new file mode 100644 index 0000000..49eea39 --- /dev/null +++ b/wiki/sources/2026-07-17-design-the-perfect-offer.md @@ -0,0 +1,76 @@ +# Design The Perfect Offer in Under 10 Minutes + +#source #offer-design #pricing + +## Source Metadata + +- **Date:** unknown (video publication date not recorded in raw file) +- **Raw path:** `raw/sources/Design The Perfect Offer in Under 10 Minutes.md` +- **Source type:** YouTube video conclusions/notes (09:35 runtime) — <https://www.youtube.com/watch?v=19QYlpGvcLo> +- **Ingestion date:** 2026-07-17 +- **Format note:** The raw file is a distilled conclusions document, not a verbatim transcript. Claims are therefore already one interpretive layer removed from the speaker. + +## Core Claims + +1. **Productize or stay poor.** Selling "I do X for you" forces every engagement into custom hourly work. ~90% of service businesses operate this way and net **less than minimum wage** per real hour worked. +2. **Backwards math sets the offer, not inspiration.** Pick a revenue target → divide by a ≥$1,000/mo price → that is your client count. $10,000 ÷ $1,000 = 10 clients. +3. **$1,000/mo is the floor.** Below ~$100/mo there is no margin to fund delivery quality — pricing itself constrains how good the service can be. $1K is defensible for AI/business services because one new client is typically worth ~$1K to the buyer, so a single win recoups the fee. +4. **Hungry crowd beats best burger.** Don't invent a novel service; listen to what the market already asks for and name its bottleneck back to it as an offer. +5. **Anchor the ladder on the core tier, then bracket it.** Design the middle offer first, then build entry (~40–50% of core) and top (~5× core) around it. +6. **People don't buy your time. They buy your standards.** Buyers want the methodology and the standard, not your presence. +7. **The market is fatigued by sales calls.** Ship both a pitch deck and a text offer doc; default to selling in chat and escalate to a call only when the buyer asks. + +## Key Evidence / Details + +**The ladder built live on-camera:** + +| Tier | Price | What it is | Client gets | +|---|---|---|---| +| Entry | $444 (AI Jumpstart) | 90-min working session | One workflow built with them | +| **Core** | **$997/mo** | The productized monthly | 1 personalized AI agent + dashboard + 1 new workflow/month | +| Top | $5,000/mo (AI Ecosystem) | Full deployment | Rolled out business-wide + team training + monthly call | + +**The reframe that carries the whole method:** + +| Weak (service framing) | Strong (productized outcome) | +|---|---| +| "I'll audit your calendar and set up some automations" | "I guarantee I'll buy back 10 hours of your time per week using AI, for $1,000/mo — every month." | + +10 hrs/week × 4 = **40 hours/month** returned, recurring. Concrete, defensible, priceable. + +**Language rules:** + +- Never "3 hours per month **with me**" → say "with my team" (or "me or my team"). If you promise yourself and don't show, they're upset; promise the team and show up anyway, that's a bonus. +- Never "I do AI for you" → say "this is my specific methodology for [outcome]". + +**On AI as co-designer:** the AI-generated recommendation (workflow + dashboard + agent) matched the coach's own best-practice structure. Claimed leverage: the deck-and-doc drudgery that used to require a paid coach is now free; what remains scarce is knowing which questions to feed it. + +**Audience:** solo operators and small agencies stuck in custom-hourly work (AI, marketing, coaching, consulting) wanting a recurring $1K–$5K/mo productized model without inventing a new category. + +## Connections + +- [[productized-service]] — this source is the primary evidence for the productization mechanic +- [[offer-ladder]] — the three-tier structure and middle-out design rule originate here +- [[outcome-based-selling]] — "buy back 10 hours/week" as the canonical outcome framing +- [[pricing-from-value]] — the $1K floor and backwards-math model +- [[niche-selection]] — hungry crowd over best burger +- [[pain-discovery]] — "what's your biggest bottleneck around [domain]?" +- [[methodology-as-moat]] — "people buy your standards" +- [[ai-market-shift]] — AI as free offer-design labor +- Cross-source: [[2026-06-15-selling-development-services-in-the-ai-era]] agrees on productization and outcome-selling, disagrees on sales-call posture + +## Open Questions + +- Who is the speaker/coach, and who is the guest whose ladder was built? The raw file names neither. **Update 2026-07-23: plausibly [[dan-martell]].** Evidence from [[2026-07-23-make-my-first-100k-in-month]] (named-Martell): this page's signature offer is *"buy back 10 hours of your time per week"* — *Buy Back Your Time* is Martell's book and flagship frame; the $997/mo core matches his $1K/mo sweet spot; the chat-first close matches his claimed 8-figures-by-chat channel; and the three-tier ~$1K-core ladder recurs there with a decoy rationale. Weaker than the 07-18 case (no verbatim mechanism reuse) — held as suspicion, not attribution. Owner confirmation would settle whether this "anchor" source is independent of the Martell corpus at all. +- Is the "<minimum wage for 90% of service businesses" figure sourced, or rhetorical? No citation given. +- Is "$1K is what one new client is worth" specific to lead-gen-adjacent buyers? It plausibly fails for buyers whose customer LTV is far below or above $1K. +- The $444 / $997 / $5,000 ladder is one worked example on one call. Is the 40–50% / 5× bracketing a real rule or a post-hoc description of this single case? +- "You can literally make a million dollars a month over chat" — unsupported, treat as motivational framing rather than evidence. + +## Change Impact on Wiki + +First ingest into an empty vault (alongside [[2026-06-15-selling-development-services-in-the-ai-era]]). + +- Created [[productized-service]], [[offer-ladder]], [[outcome-based-selling]], [[pricing-from-value]], [[niche-selection]], [[pain-discovery]], [[methodology-as-moat]], [[ai-market-shift]] — this source is a primary evidence stream for all eight. +- [[offer-ladder]] is sourced almost entirely from this page; it has no corroboration and is marked `Status: tentative`. +- Contributed the chat-first selling position that stands in tension with the founder-led outbound position in the other source; recorded under Contradictions in [[sales-discipline]] and [[overview]]. diff --git a/wiki/sources/2026-07-18-ai-productivity-adversarial-evidence.md b/wiki/sources/2026-07-18-ai-productivity-adversarial-evidence.md new file mode 100644 index 0000000..7509efe --- /dev/null +++ b/wiki/sources/2026-07-18-ai-productivity-adversarial-evidence.md @@ -0,0 +1,62 @@ +# AI Coding Productivity — Empirical Evidence (Adversarial) + +#source #ai #evidence #adversarial + +## Source Metadata + +- **Date:** 2026-07-18 (compilation date; underlying studies span 2023–2025) +- **Raw path:** `raw/sources/AI Coding Productivity - Empirical Evidence (deep research 2026-07-18).md` +- **Source type:** **Deep-research synthesis** — a Claude Code `deep-research` run (6 search angles → 23 sources fetched → 104 claims → 25 adversarially verified, 23 confirmed / 2 refuted). Not a single external artifact. +- **Ingestion date:** 2026-07-18 +- **Provenance role:** The vault's **first deliberately adversarial source** — commissioned (see [[2026-07-17-best-method-first-client]]'s lineage of open threads) to test the premise underlying both vault branches, that *AI has zeroed the cost of commodity software execution*. Second-order like the distillation, but its inputs are peer-reviewed papers, RCTs, and large-sample surveys rather than promotional videos — **higher-provenance than any prior source**, though still a synthesis. +- **⚠ Time-scope:** every figure is tied to a specific tool generation (early-2025 and earlier). This is **2023–2025 evidence, explicitly NOT the live 2026 state of the art** — METR itself labels its result "historical"; DORA reversed one 2024 finding in 2025. + +## Core Claims + +1. **The evidence QUALIFIES the hype, it does not demolish it.** No study shows AI has zero/negative value in general. It shows the real effect is **modest (≈14–19%), context-dependent, novice-tilted, and overstated by self-report.** +2. **"AI zeroed the cost of skilled dev work" is directly contradicted** by the strongest developer-specific RCT: experienced devs were **19% *slower*** with early-2025 AI ([METR]). +3. **"Seniors up, juniors irrelevant" is directly inverted** by the best skill-distribution study: the **least-experienced gain most** (34% vs ~0 for experts) — and a Copilot RCT independently found less-experienced devs benefit most. +4. **Self-reported productivity gains are unreliable evidence.** METR devs forecast +24%, felt +20%, measured −19% — a ~39-point perception gap. This is the exact "it feels faster" basis most promotional claims rest on. +5. **Individual speed ≠ team delivery.** DORA 2024: AI adoption correlated with *reduced* delivery stability (and, in 2024, throughput). Trust is low and falling (SO 2025: ~3% highly trust, ~46% distrust). + +## Key Evidence / Details + +| # | Finding | Design | Population | Headline | Confidence | +|---|---|---|---|---|---| +| 1 | Experienced devs **19% slower** with AI | RCT | 16 expert OSS maintainers, 246 real tasks, their own mature repos, early-2025 tools | −19% completion time | HIGH (3-0) | +| 2 | Perception ≫ reality | (within #1) | same | forecast +24%, post +20%, actual −19% | HIGH (3-0) | +| 3 | Gains tilt to **least-skilled** | quasi-exp (diff-in-diff) | **5,179 customer-support agents — NOT devs** | +34% novices vs ~0 experts (avg +14–15%) | HIGH (3-0) | +| 4 | Novices benefit more; toy-task speedup | RCT | 70 freelancers, one JS toy task, 2022 Copilot | +55.8% (toy); exp. coeff n.s. at 0.05 | MEDIUM | +| 5 | AI hurt team **stability/throughput** | observational survey | DORA 2024 respondents | −7.2% stability / −1.5% throughput per +25% adoption | MEDIUM (throughput reversed in 2025) | +| 6 | Trust low & falling; debugging tax | survey (~49k) | SO 2025 | ~3% highly trust, ~46% distrust; ~45% debugging is time-consuming | HIGH (3-0) | + +**Key primary sources:** METR (metr.org/blog/2025-07-10…, arXiv:2507.09089) · Brynjolfsson, Li & Raymond, "Generative AI at Work," *QJE* 140(2):889–942 2025 (NBER w31161) · GitHub Copilot RCT (arXiv:2302.06590) · DORA 2024 (dora.dev/research/2024) · Stack Overflow 2025 Developer Survey (survey.stackoverflow.co/2025/ai). + +**Verification honesty:** 2 claims were **refuted** during 3-vote checking — both versions of "66% spend more time fixing almost-right AI code" (the 66% actually measures *encountering* almost-right output; the real debugging-time figure is **45%**). Recorded so the error isn't silently repeated. + +## Connections + +- [[ai-productivity-evidence]] — the concept page this source anchors (measured vs. claimed AI productivity) +- [[ai-market-shift]] — **challenges** the premise that a ~$200/mo AI is a genuine *substitute* zeroing rate competition; substantiates a doubt the vault already flagged (the "$200 substitute is asserted, not demonstrated" open question) +- [[seniority-and-ai]] — **inverts** the productivity-gain direction of "seniors up, juniors irrelevant" (novices gain most) — while *not* settling the labor-market-value question, and partly supporting the "juniors can't catch AI's errors" risk mechanism +- [[future-of-engineering-work]] — **qualifies** "coding cost → 0, teams collapse 8→2–3": effect sizes are modest and team-level delivery can worsen +- Counter-pole to [[sebastian]]'s standout claims and to the whole "AI killed hourly dev" school ([[dmitry-rodenko]], [[ai-market-shift]]) +- [[overview]] — flips the standing "no adversarial source" gap + +## Open Questions + +- Does METR's −19% persist/reverse with **mid-2026 agentic tools**? The single most important missing piece; this source is explicitly historical. +- Does "novices gain most" hold for **real** software work, or invert on complex/unfamiliar codebases where juniors can't catch AI errors? +- The findings measure **speed**, not **labor-market value** (wages/hiring/headcount) — so they are directional counter-evidence to "juniors out," not a same-metric refutation. +- Transient learning-curve cost vs. durable tax for the team-level effects? DORA's 2025 partial reversal cuts both ways. +- Should [[dmitry-rodenko]]-style claims ("$200/mo AI substitute") now carry a stronger `Status: contested` given this evidence? + +## Change Impact on Wiki + +Thirteenth source; the vault's **first adversarial / empirical source** and its highest-provenance one. + +- Created concept [[ai-productivity-evidence]] as the durable home for the empirical counter-narrative. +- Added counter-evidence sections to [[ai-market-shift]], [[seniority-and-ai]], [[future-of-engineering-work]] — recording contradictions explicitly (rule #5), **not** overwriting the sources' prior claims (Update Policy). +- Flipped the long-standing gap in [[overview]] and [[index]] ("no adversarial source / 11-of-12 one school"). +- **No entity pages created** for METR / Brynjolfsson / DORA / Stack Overflow — they are cited as evidence rather than tracked as recurring subjects (consistent with the Buffett/Munger decision on [[mohnish-pabrai]]); revisit if a second study-based source arrives. +- Deliberately framed as *qualifying*, not inverting, the thesis — the honest reading of the evidence. diff --git a/wiki/sources/2026-07-18-information-is-free-implementation-is-paid.md b/wiki/sources/2026-07-18-information-is-free-implementation-is-paid.md new file mode 100644 index 0000000..113d214 --- /dev/null +++ b/wiki/sources/2026-07-18-information-is-free-implementation-is-paid.md @@ -0,0 +1,86 @@ +# Information Is Free, Implementation Is Paid + +#source #content-marketing #demand-generation + +## Source Metadata + +- **Date:** unknown (video publication date not recorded in raw file) +- **Raw path:** `raw/sources/Information Is Free, Implementation Is Paid.md` +- **Source type:** YouTube video conclusions/notes (08:45 runtime) — <https://www.youtube.com/watch?v=knrSj8t2L9U> +- **Ingestion date:** 2026-07-18 +- **Format note:** The raw file is a distilled conclusions document, not a verbatim transcript. Claims are one interpretive layer removed from the speaker; several tables in the raw are the note-taker's framing, not necessarily the video's wording. + +## Core Claims + +1. **Give away the know-how; charge for implementation and sequencing.** The best marketing content a service business can make is *exactly what it does in-house for paying clients* — the internal playbooks, step by step. Publishing the *what* does not remove demand for the *how* (the sequenced, done-with-you/done-for-you delivery); done right it *creates* demand. +2. **The paid good is sequencing, not information.** *"Information is free. People pay for implementation and sequencing. That's why they pay you."* Each free video teaches a real, valuable step; what is withheld is the **order** in which the steps combine into a working system. +3. **The scramble trick makes #1 and #2 compatible.** Post the pieces *out of order* across topics (A1, B1, C1, D1, E1, A2, B2 …), never in a runnable sequence within one topic. Every swipe shows expertise; no viewer can assemble the whole system from the feed, so the paid offer survives. +4. **A content-idea factory removes the "I ran out of ideas" excuse.** 5 hot buttons × 10 nuanced pains = 50 pain-ideas (≈50 days of content), × 4 formats = **200 pieces** (near-daily for most of a year), then loop from pain #1 in a fresh format. +5. **Precision-naming the buyer's pain is the whole conversion mechanism.** Open every piece on a *nuanced, observable* pain that "describes the viewer's world better than they can describe it themselves" → the viewer thinks *"how do you know?"* → you are an expert on sight. Then teach the fix. +6. **Free content makes the paid offer feel cheap.** A $997 offer reads as a bargain *after* the viewer has watched 50 free expert videos — the giveaway is the price anchor. + +## Key Evidence / Details + +**The "5 × 10 × 4 = 200" content factory:** + +| Layer | Count | What it is | +|---|---|---| +| Hot buttons | 5 | Big pain areas the ICP feels (e.g. "AI agents") | +| Nuanced pains per hot button | 10 | Specific, observable problems inside each hot button | +| Pain-point ideas | **50** | 5 × 10 — ≈50 days of content, then loop | +| Formats per idea | 4 | e.g. clone / talking head / green screen / +1 | +| Total pieces | **200** | 50 × 4 | + +**The pain-generation prompt (verbatim structure from the video):** + +> *"Make a list of 10 nuanced but observable problems business owners who are between $500,000 and $2 million in revenue have around [HOT BUTTON]."* + +The modifiers carry the weight: **"nuanced but observable"** forces specifics over clichés; **"business owners between $500K and $2M"** anchors to a concrete ICP so the pains sound like *their* world; **"around [hot button]"** scopes the output. Example outputs (around "AI agents"): *"They have AI tabs open and personal subscriptions but zero AI doing recurring workflows"*; *"They bought the automation and built a co-pilot that added work"*; *"Every agent still runs through them — they're the bottleneck."* + +**The pain → solution structure (every piece):** (1) open on the nuanced pain — "Do you have a bunch of AI tabs open but nothing's actually automating your business?" → *"how do you know?"*; (2) teach the fix. Never open on the solution. + +**The scramble, stated plainly:** + +> *"You could literally create a course on how to do everything from point A to point Z, put the videos on YouTube in a completely out-of-whack order, and people would still pay you for the same content put in the right order."* + +**Why it doesn't cannibalize sales** (the speaker's inversion of the hoarding instinct): + +| Instinct | Reality (per speaker) | +|---|---| +| Give away best stuff → lose demand | Give away best stuff → *increase* demand | +| Hold best stuff in-house → look valuable | Hold it in-house → nobody knows you have it | +| Scrambled free content = leaks your system | Scrambled free content = proof of expertise **without a shortcut around you** | +| A high price feels expensive | $997 feels **cheap** after 50 free expert videos | + +**Actionable sequence (as given):** list 5 hot buttons → generate 10 nuanced pains each via the prompt → pick 4 formats → batch in pain→solution pairs → publish scrambled across hot buttons → rotate at day 51 → splinter any internal N-step playbook into N out-of-order pieces. + +**Audience:** service-business owners/consultants/agencies who "hold their best stuff in-house" and can't see why content isn't converting; anyone afraid that teaching = losing clients; anyone who runs dry on content ideas by week 2. + +## Connections + +- [[information-vs-implementation]] — this source is the sole and primary evidence for the concept (thesis + factory + scramble) +- [[client-acquisition-channels]] — develops the organic-content channel that the 17-channel taxonomy only listed; adds a fourth, maximally pro-online-content position to the online-vs-in-person split +- [[pain-discovery]] — the "10 nuanced but observable problems" prompt is a concrete tool for the same skill (name the buyer's pain better than they can); note it targets *content*, not live sales discovery +- [[pricing-from-value]] — "free content makes $997 feel cheap" is an anchoring mechanism (giveaway as price anchor) +- [[methodology-as-moat]] — "sequencing is what's paid for" is a moat framing: the ordered method, not the steps, is the defensible asset +- [[cloning-over-originality]] — "splinter your internal playbook into out-of-order pieces" is a distribution corollary (share the parts, withhold the assembly) +- Cross-source: same US "sell dear / productize" school as [[2026-07-17-design-the-perfect-offer]] (both reach the $997 core price and "buy the standard/method, not the labor"); directly opposed to [[2026-07-06-sebastian-interview-ai-and-software-engineering]], which rates content marketing a "Big zero" + +## Open Questions + +- **Who is the speaker?** The raw file names no person or brand. **Near-certainly answered 2026-07-23: [[dan-martell]].** [[2026-07-23-make-my-first-100k-in-month]] — which names him — reuses this source's three distinctive mechanisms verbatim: the scramble trick ("out-of-whack order… pay you for the same content put in the right order" ↔ "scramble the steps; the ordered checklist is what customers pay to have executed"), the *"10 nuanced and observable problems"* AI prompt, and the *"describe their pain better than they can"* expertise claim. Inference from mechanism overlap, pending owner confirmation — but strong enough that this page's claims are treated as Martell's throughout the wiki (see [[information-vs-implementation]] for the downgrade this forced). +- **No results, only mechanism.** Zero data on whether the scramble strategy actually converts (view→lead→sale rates, examples). It is a plausible theory presented as fact. +- **The math is loose.** "200 pieces ≈ nearly a full year, near-daily" is really ~200 days (~⅔ of a year); "50 days then loop" and "200 pieces" describe different cadences depending on how many formats ship per day. Treat the numbers as illustrative, not a schedule. +- **ICP band mismatch.** The prompt anchors to **$500K–$2M revenue** businesses — a larger buyer than the rest of the vault's SMB/$1K-a-month framing. Whether the same engine works for the vault owner's likely buyers is untested. +- **Does the scramble survive a motivated viewer?** Anyone who searches the channel and sorts by topic can partially re-sequence. The moat is friction, not secrecy — unquantified. +- **Platform-blind.** Assumes a short-form feed (YouTube/TikTok/Reels) where discovery is per-video and non-linear. Weaker where audiences binge playlists or read in order. + +## Change Impact on Wiki + +Twelfth source; first on **demand generation / content marketing** as a discipline (prior sources listed "content marketing" only as one channel among 17). + +- Created [[information-vs-implementation]] — new concept; this source is its only evidence, so it is `Status: tentative`. +- Enriched [[client-acquisition-channels]] (organic-content channel now developed; added as the fourth and most pro-online voice, sharpening the online-vs-in-person contradiction with [[sebastian]]). +- Enriched [[pain-discovery]] (the nuanced-pain prompt added as a content-side tool for the "describe their world better than they can" skill). +- Added cross-link notes to [[pricing-from-value]] (free content as price anchor) and [[methodology-as-moat]] (sequencing as the paid, defensible good). +- Does **not** fill the vault's standing adversarial gap — it is another advocate of the same US "sell dear / give-value" school, so agreement here remains unreplicated advocacy. diff --git a/wiki/sources/2026-07-19-your-company-cant-outgrow-your-team.md b/wiki/sources/2026-07-19-your-company-cant-outgrow-your-team.md new file mode 100644 index 0000000..1b9d9bb --- /dev/null +++ b/wiki/sources/2026-07-19-your-company-cant-outgrow-your-team.md @@ -0,0 +1,50 @@ +# Your Company Can't Outgrow Your Team + +#source #leadership #team + +## Source Metadata + +- **Date of source:** undated (YouTube clip, 4:35) +- **Raw path:** `raw/sources/Your Company Can't Outgrow Your Team.md` +- **Source type:** US leadership/management video — conclusions note +- **Speaker:** [[dan-martell]] — the clip itself names no speaker; attribution confirmed by the vault owner 2026-07-20, after it was raised as a stylistic inference during the [[2026-07-20-referrals-will-sink-your-business]] ingest +- **Root URL:** https://www.youtube.com/watch?v=wE3TwzH-XCE +- **Ingested:** 2026-07-19 + +## Core Claims + +1. **A company can only grow as fast as its people.** Targeting 100% company growth means every team member must grow ~100% — otherwise the ceiling is human, not market. Leadership's job: make that expectation explicit and hold it. *"Good got you on the team. Great keeps you on the team, because 100% requires greatness."* +2. **Teach a philosophy, not a task list** — the speaker's "Business Athlete" framework gives climbers a model to climb toward. Two of its seven practices are named: *have a coach* ("I'm not your coach" — people own their own development) and *have a practice schedule* ("we practice until we can't get it wrong, we don't practice to get it right"). +3. **Make performance public.** Everyone's standing is posted where the team can see it — self-driven accountability without constant enforcement. Discipline: **praise in public, criticize in private** (hard talks in the 1-on-1, not on the wall). +4. **The Keeper Test** (borrowed from Netflix): *"If this person had an offer for 30% more tomorrow, would I fight to keep them?"* Yes → they belong. No → have the honest conversation and turn it into a development plan (or a departure). Silent tolerance of "no" answers rots the team. +5. **"Shine a light" on bright spots.** Have the team member who thinks differently teach the rest, regardless of age/tenure — leadership training becomes peer-generated, not manager-generated. +6. **Values must be operational: hire → inspire → fire.** Screen for values before skills; tie every decision back to them; when someone goes, name the value violated. *"Values aren't what you say they are. They're what you tolerate."* + +## Key Evidence / Details + +- Anecdotal only — a leadership talk, no data. Examples given: firing a leader who didn't develop their people; firing someone who added process complexity (*"Complexity fails, simple scales"*). +- Six actionable takeaways in the raw note: state the growth math out loud; adopt an athlete-style philosophy; post the scoreboard; run the Keeper Test on every direct report; weekly bright-spot teaching; audit your last three fires for value-naming. +- Five of the seven Business Athlete practices are *not* in the clip — the framework is only partially captured. + +## Connections + +- [[team-growth-ceiling]] — new concept page carrying this source's thesis and mechanisms. +- [[dan-martell]] — the speaker (identified 2026-07-20); his Branch A material is [[marketing-system]] and [[technical-founder-trap]]. +- [[marketing-system]] — same author, same argument aimed outward: the plateau is never the market. See the comparison table on [[team-growth-ceiling]]. +- [[future-of-engineering-work]] — complementary tension: if AI collapses teams to 2–3 people, each person's growth rate matters *more*, which strengthens this source's premise for small teams. +- [[methodology-as-moat]] — "philosophy, not task list" is the internal-facing sibling of selling a named methodology externally. +- [[sales-discipline]] — "practice until we can't get it wrong" echoes the consistency-over-intensity discipline on the sales side. + +## Open Questions + +- ✅ **Who is the speaker? — resolved 2026-07-20: [[dan-martell]]**, confirmed by the vault owner after the ingest of [[2026-07-20-referrals-will-sink-your-business]] surfaced it as a stylistic inference. Consequence recorded on [[team-growth-ceiling]]: this source and [[marketing-system]] are **one author**, so their shared "the ceiling is never the market" frame is a single worldview, not two independent findings. (Provenance note: curator testimony, not a documentary citation — the clip still names no one.) +- What are the other five Business Athlete practices and the three values referenced? Now findable — Martell's published material is the route. +- Does public-scoreboard accountability translate to small (2–3 person) senior teams, or is it a sales-floor/larger-org pattern? +- The Keeper Test's 30%-raise framing assumes replaceability is assessable — how does that interact with tiny AI-era teams where each member is a single point of failure? + +## Change Impact on Wiki + +- Created this page and [[team-growth-ceiling]] (new concept; first page in the vault about *running* the delivery org rather than selling or the AI labor shift). +- [[overview]]: added Branch C (running the team) note — one-source branch, marked tentative. +- [[future-of-engineering-work]]: added Related-Pages link to [[team-growth-ceiling]]. +- [[index]], [[log]] updated. diff --git a/wiki/sources/2026-07-20-referrals-will-sink-your-business.md b/wiki/sources/2026-07-20-referrals-will-sink-your-business.md new file mode 100644 index 0000000..1e78a3e --- /dev/null +++ b/wiki/sources/2026-07-20-referrals-will-sink-your-business.md @@ -0,0 +1,58 @@ +# Referrals Will Sink Your Business + +#source #marketing #content-marketing + +## Source Metadata + +- **Date of source:** undated (YouTube clip, 6:47) +- **Raw path:** `raw/sources/Referrals Will Sink Your Business.md` +- **Source type:** US coaching video — conclusions note; [[dan-martell]] coaching a founder stuck at ~$1.5M revenue +- **Root URL:** https://www.youtube.com/watch?v=50CTmoSuCYE +- **Ingested:** 2026-07-20 + +## Core Claims + +1. **Referral-only growth is a failed *primary* strategy.** It feels like validation ("all word-of-mouth!") but it is evidence the founder skipped building a marketing system. The $1.5M ceiling is *not* a market problem — it is a missing system. Founders who did the system work reach the same revenue in ~18 months **and can keep going**. +2. **A marketing system is defined by a single property: money in at the top produces more money out at the bottom.** Everything else is inbound luck you don't control. → [[marketing-system]] +3. **There are exactly three levers for making people aware of you: publish content, paid ads, partnerships.** All three cost something; all three are different skills. **Pick one and commit for 90 days** — don't dabble in all three. +4. **"The new paid is organic."** The best-performing Meta ads now *look like content*; the platform wants content-shaped ads. Most founders never build the **creative pipeline** paid ads need at volume, because they aren't content creators yet. Rule: take an organic post that already worked, then run *that* as an ad. Skip the step and paid burns cash. So 90 days of organic is not a detour from paid — it's the **prerequisite**. +5. **The technical-founder trap.** *"You and I are the same guy — software people, systems thinkers. 'Give me your problem and I'll go.' You don't want to explain, you just want to do it."* Technical founders are great at **solving** and terrible at **explaining**. Communication is the unlock; only after it exists do paid ads work, "because you now have something to say and know how to say it." → [[technical-founder-trap]] +6. **Measure reps, not views.** Wrong questions: *how many views? did it go viral?* Right questions: *am I getting better? how many reps this week?* You do not decide what goes viral; the only controllable variable is rep volume. *"Most of you get bored with your marketing before the market ever does — and you just stop."* +7. **Budget six months of patience.** Months 0–3: 90-day attack, skill-building, no system. Months 3–6: pipeline exists. Month 6+: the system begins producing leads. Months 6–18: $1.5M → $10M "no problem." + +## Key Evidence / Details + +- **Concrete cadence the speaker runs himself:** go **live every day** (stated reason, repeated three times: *"you got to practice"*); **two reels a day**; no gear, just a phone; publish to Facebook, Instagram, YouTube Shorts. Learn to answer questions, add value, and — most importantly — **explain what you do**. +- **What "attack it" means:** daily (not weekly) volume, active experimentation with hooks/formats/angles, job-level intensity, feedback loops, continuous new creative. +- **Evidence quality: anecdotal advocacy, zero data.** No conversion figures, no cost-per-lead, no cohort of founders who tried and failed. The $1.5M→$10M and "~18 months" numbers are unsourced coaching claims. +- **The two viral proof points are survivorship bias.** *Tones and I — "Dance Monkey"* (busker, one recording, billion+ streams) and *Oliver Anthony — "Rich Man North of Richmond"* (backyard, filmed on a bad phone, now touring millionaire) are used to support *"everyone is one creative project away from being a superstar."* Two selected winners cannot support that inference; the unobserved denominator is every person who shipped daily and never landed. The narrower claim the anecdotes *do* support — **you must still be shipping when it lands** — survives. +- The one line the speaker leaves it on: *"You don't decide what you create that's gonna go viral. The only thing you control is the volume of the reps."* + +## Connections + +- [[marketing-system]] — **new concept page** carrying this source's central thesis (owned system vs. inbound luck; three levers; organic→paid bridge; the 6-month lag). +- [[technical-founder-trap]] — **new concept page**: solving ≠ explaining, and why that gap is upstream of a founder's marketing problem. +- [[referrals]] — this source is the vault's **first counter-position on referrals**, which every prior source rated the highest-converting channel. It does not dispute referral *conversion*; it disputes referral *dependency*. Recorded there in full. +- [[client-acquisition-channels]] — a fourth, competing taxonomy (3 levers vs. the 17-channel/3-tier map), and a direct conflict on **how many channels to run** (pick 1 vs. pick 3). +- [[information-vs-implementation]] — a second source for content-as-primary-engine, adding "explain what you do" and the organic→paid bridge. **Independence withdrawn 2026-07-23:** the founding 07-18 source is near-certainly the same author, so this is framework consistency, not corroboration. +- [[partnerships]] — the third lever, named and dropped here; mechanism supplied by the same author 2026-07-22. +- [[sales-discipline]] — "reps not views" is a near-exact restatement of consistency-over-intensity, arrived at independently; the 6-month patience budget is the missing time dimension. +- [[dan-martell]] — new entity page. + +## Open Questions + +- ✅ **Same speaker as [[2026-07-19-your-company-cant-outgrow-your-team]]? — yes, confirmed by the vault owner 2026-07-20.** Raised here as a stylistic inference (same genre; the "Business Athlete" framework) and confirmed the same day. Consequences applied across the wiki: Branch C's lone source gains an author, and [[team-growth-ceiling]] + [[marketing-system]] are recorded as **one voice, not two** — their shared "the ceiling is never the market" frame is a worldview restated, not a finding replicated. See [[dan-martell]]. +- At what revenue does referral dependency actually become the binding constraint? The advice is aimed at ~$1.5M with an existing client base — it is silent on, and probably not addressed to, a pre-first-client operator. +- Does "pick one lever" survive contact with a solo operator who has no team to absorb daily-live + 2-reels-a-day? The cadence assumes marketing is the founder's job, not a slice of it. +- ✅ ~~No mechanism is given for *partnerships*, the third lever — it is named and dropped.~~ **Answered 2026-07-22** by the same author: [[2026-07-22-stop-cold-calling-do-this-instead]] supplies borrowed credibility + partner-archetype recruiting → [[partnerships]]. (Lint 2026-07-29: this page was the last one still showing the question open.) + +## Change Impact on Wiki + +- Created this page, [[marketing-system]], [[technical-founder-trap]], and [[dan-martell]]. +- [[referrals]]: added a **Counter-Position** section (referral dependency as a growth ceiling) and revised Contradictions — this closes the page's standing *"no adversarial source"* gap, though only partially (counter-*position*, not counter-*evidence*; see that page). +- [[client-acquisition-channels]]: added the three-lever taxonomy, the pick-1-vs-pick-3 conflict, and a fifth row to the content-position table. +- [[information-vs-implementation]]: upgraded from single-source; corroboration recorded, `tentative` narrowed. +- [[sales-discipline]]: added reps-not-views corroboration and the 6-month patience budget. +- [[eugene]]: added the technical-founder-trap lens on his stated networking blocker. +- [[2026-07-19-your-company-cant-outgrow-your-team]]: recorded the speaker-attribution hypothesis — **confirmed same day** by the vault owner, then applied: speaker added to that page's metadata, [[team-growth-ceiling]] re-scoped as same-author-as-[[marketing-system]] (with the cross-branch comparison table), [[dan-martell]] extended to cover both branches. +- [[overview]], [[index]], [[log]] updated. diff --git a/wiki/sources/2026-07-22-stop-cold-calling-do-this-instead.md b/wiki/sources/2026-07-22-stop-cold-calling-do-this-instead.md new file mode 100644 index 0000000..f1470c7 --- /dev/null +++ b/wiki/sources/2026-07-22-stop-cold-calling-do-this-instead.md @@ -0,0 +1,65 @@ +# Stop Cold Calling, Do This Instead + +#source #sales #partnerships + +## Source Metadata + +- **Title:** Stop Cold Calling, Do This Instead +- **Speaker:** Dan Martell — named in the raw note itself (documentary attribution, unlike the 07-19 clip) +- **Root source:** YouTube video, 4:38 — https://www.youtube.com/watch?v=wk5MpA2ckTI +- **Raw path:** `raw/sources/Stop Cold Calling, Do This Instead.md` +- **Source date:** undated (ingested 2026-07-22) +- **Type:** conclusions note from a US coaching video; **third [[dan-martell]] source** in the vault + +## Core Claims + +1. **Pipeline or hope.** Every business either has a repeatable pipeline (attention → conversion → customer) or it stops growing. *"If you can't describe your pipeline in one sentence, you don't have one — you have hope."* +2. **Exactly three pipeline sources — Publish, Paid, Partners** — and the rule to **pick one and go all in**. This restates the three-lever taxonomy from [[2026-07-20-referrals-will-sink-your-business]] verbatim in structure (publish/content, paid, partnerships), which confirms it is a stable framework for this author — and adds nothing to its evidence, since it is the same voice. +3. **Cold outbound into enterprise is the hardest path** — procurement, getting the meeting, closing *before someone gets fired or the board reshuffles*. Anecdote: four years in a suit at 24 selling to Fortune 2000 ("you might as well go run an ultra marathon"; the PTSD-and-button-up-shirts bit). +4. **Partnerships is the fastest lever, especially for enterprise, because of borrowed credibility** — someone the buyer already trusts walks you in, so the buyer arrives pre-sold. Anecdotes: one system integrator walked him into **7 New Jersey pharmaceutical companies** (Novartis, J&J, …) in one shot; **$95K contracts signed three weeks** after introduction. +5. **Both sides win, which is why it repeats.** The integrator held a multi-million-dollar contract on the same account; bringing in a vendor who delivers strengthens the partner's position. No revenue-share mechanics are described — the partner's payoff is account value, not commission. +6. **The insight is the system, not the intro.** Most founders treat a good partner as luck. The move is to **reverse-engineer the partner that worked** (six questions: where did we meet; what was true about them; how many more like them exist on that channel; can I make content for that audience; can I use their success story as bait; can I make my offer stupid-easy to say yes to) and become a *"professional recruiter of system integrators"* (his targets: Tata Consulting, IBM Global Services). +7. **The playbook:** find who inside the partner org makes the "who do we bring in" decision → go to the **events they attend, not the events your peers attend** → win the individual first → let them bring you into accounts → deliver → systematize content/offer/story to attract more of the same partner archetype. +8. **Ten good partners can replace an outbound sales team.** +9. **Scope, stated by the source:** mid-market/enterprise, agencies, B2B services, deal sizes justifying a relationship motion (~$10K+ ACV). Explicitly not low-ticket DTC. + +## Key Evidence / Details + +| Claim | Support offered | Grade | +|---|---|---| +| Partner → 7 pharma companies in one shot | Personal anecdote, companies named | Unverifiable, survivor-selected | +| $95K contracts 3 weeks post-intro | Personal anecdote | Unverifiable | +| Partner's multi-million contract (the both-win logic) | Personal anecdote | Unverifiable, but the *structural* point (partner is paid in account value) stands without the figure | +| Cold enterprise outbound is brutal | Personal experience, 4 years | Anecdote, though independently echoed by [[sebastian]] — see Connections | +| Ten partners replace an outbound team | Assertion | No cohort, no numbers | + +Evidence grade overall: **advocacy** — a coaching clip built on the author's own war stories, no data, from someone who sells the prescribed discipline. Same grade as the other two Martell sources. What survives without the figures is the **mechanism**: borrowed credibility lowers enterprise entry friction, and partner *acquisition* is a controllable input where client referrals are not. + +## Connections + +- **[[partnerships]]** — created from this source; the full mechanism lives there +- [[marketing-system]] — the third lever, previously "named and never explained," now explained; the standing open question there is closed +- [[referrals]] — answers that page's open question "is there a version of referrals *with* a throttle?" — yes: partner-sourced intros, because you control partner recruitment +- [[client-acquisition-channels]] — a new counter-position on **cold outbound** (the title's target), and a qualification to the "all three levers are one-to-many" reading +- [[relationships-as-moat]] — convergence from an unexpected direction: the content pole's own author prescribes **trust-mediated, in-person entry** for enterprise (events, win the individual), differing from [[sebastian]] only on *whose* trust — borrowed vs. built +- [[dan-martell]] — third source; extends the through-line (systematize the lucky win) +- [[sales-discipline]] — "commit fully to one channel" restated +- [[eugene]] — gives his networking blocker a *target*: recruit a partner archetype, not "network" generally + +## Open Questions + +- **What does the partner actually get?** The both-win logic here is account value (the integrator's multi-million contract benefits from a vendor who delivers). Is that generalizable, or do smaller-scale partner plays need explicit rev-share/referral fees? +- **What is the minimum credibility bar?** The anecdote comes from a funded SaaS founder with a product. Would a Tata-class integrator take a meeting with a no-name solo developer at all? The source doesn't say. +- **What is the SMB analogue?** If the buyer is SMB (Eugene's likely near-term market), the system-integrator archetype doesn't exist — are agencies, MSPs, accountants, or hardware vendors the equivalent partner class? +- Recruiting a partner still requires approaching a stranger (event, introduction) — outbound redirected at a higher-leverage audience, not eliminated. The title over-promises relative to the mechanism; does the source's own playbook step 3 ("introduce yourself and win the individual over") differ from warm-ish cold outreach in anything but target selection? + +## Change Impact on Wiki + +- Created [[partnerships]] — new concept page; the third lever now has a mechanism, an economics sketch, and a scope +- [[marketing-system]] — lever table updated (partnerships no longer unexplained); one-to-many characterization qualified; open question closed +- [[client-acquisition-channels]] — cold-outbound counter-position added; three-lever paragraph updated +- [[referrals]] — throttle question answered; referral-partners paragraph now points to [[partnerships]] +- [[relationships-as-moat]] — borrowed-vs-built trust convergence recorded +- [[dan-martell]] — third source added; partnerships question closed; through-line extended +- [[eugene]] — partner-archetype reading of his networking blocker added +- [[overview]], [[index]], [[log]] — counts, threads, contradictions updated diff --git a/wiki/sources/2026-07-23-make-my-first-100k-in-month.md b/wiki/sources/2026-07-23-make-my-first-100k-in-month.md new file mode 100644 index 0000000..57480f3 --- /dev/null +++ b/wiki/sources/2026-07-23-make-my-first-100k-in-month.md @@ -0,0 +1,83 @@ +# If I Wanted to Make My First $100K/Month, I'd Do This + +#source #offer-design #sales #demand-generation + +## Source Metadata + +- **Date:** unknown (video publication date not recorded in raw file) +- **Raw path:** `raw/sources/Make My First $100K in Month.md` +- **Source type:** YouTube video conclusions/notes (22:54 runtime) — <https://www.youtube.com/watch?v=xj5gZq159lM> +- **Speaker:** **[[dan-martell]]** — named in the raw note (fourth confirmed Martell source; "built and sold 3 multi-million-dollar companies") +- **Ingestion date:** 2026-07-23 +- **Format note:** Distilled conclusions document, not a transcript — claims are one interpretive layer removed from the speaker. + +## Core Claims + +1. **$0 → $100K/month is a sequence problem, not a grinding problem.** Five steps in strict order: money math → productized service → three-tier offer → demand (inbound + outbound in parallel) → close by chat or call. Marketing comes **before** building anything. +2. **The money map: ~100 customers × ~$1,000/month is the sweet spot.** Of five price×count routes to $100K/mo (1×$100K whale … 10,000×$10 mass-market), only the middle is sane. Floor: **$1,000/month minimum offer, below $10K/month** — "every conversation should be worth having." He *personally dislikes* the 10×$10K "enterprise-lite" model (still heavy per-deal). +3. **People pay for exactly three things: time, money, status.** Money is easiest to sell; status is routinely ignored and underpriced. At $1K+/month, sell to **business owners** — all three motivations apply and they decide fast. Filter what *you* offer through **Ikigai** (love / good at / world needs / will pay), with "good at" reframed as *what do people tell me I'm good at*. +4. **Productized service is the starting format** — custom services sell hours (no leverage), products are slow and risky to build; a fixed package with repeatable steps, priced like a product, funds the eventual product with customer cash. +5. **Three-tier decoy pricing:** ½× DIY ($500/mo) / **1× core productized ($1,000/mo — the one you sell)** / 10× done-for-you ($10,000/mo). Both flanking tiers are **decoys** whose job is to make the core print. Every offer contains: outcome, deliverable, investment (never "cost"), **risk reversal** (a specific guarantee — "10 leads/month"), urgency. +6. **Inbound: give everything away; monetize the sequence.** Per deliverable, AI-generate "10 **nuanced and observable** problems" the customer has → infinite hook-first content backlog. *"If I can describe my customer's pain better than they can, I'm the expert."* You still get paid for the **order of implementation** — in content you *scramble* the steps (A1, B2, C1…); the ordered checklist is what customers pay to have executed. +7. **Outbound: mine what you already have.** Phone contacts → **"ask past the person"** ("do you know anyone with this problem?" — often answers "yeah, me", otherwise yields warm intros) → referral-name openers → AI-built list of 100 as backfill. Track a spreadsheet funnel. +8. **Close by chat or cold call.** DM flow: content-or-help question → pain-awareness questions → offer-doc link → Stripe link (he claims 8 figures sold by chat). Cold call's job is **not to sell** — qualify + book a meeting from a meeting. **Surface objections before presenting so they become obstacles** ("do you have a budget to solve this?"). +9. **Volume discipline:** first 5 calls are throwaways; no-answer → call back within 30 seconds; feed call transcripts to AI to find where you stumble; goal **100 no's per day**; **spend nothing until customers have paid**. +10. **Build only after money arrives.** Pre-sell with a landing page + waitlist; a **$50 "top of the waitlist" payment** is the demand proof. No money in → don't build. + +## Key Evidence / Details + +**The money map:** + +| Model | Customers | Price | Verdict | +|---|---|---|---| +| Whale | 1 | $100,000 | Concentration risk, elite skills | +| Enterprise-lite | 10 | $10,000 | He dislikes it — heavy per-deal | +| **Sweet spot** | **~100** | **~$1,000/mo** | **Recommended start** | +| Prosumer | 1,000 | $100 | Too many closes | +| Mass-market | 10,000 | $10 | Reach a new founder can't get | + +**Personal track record offered as evidence (self-reported, unverified):** second company **Flowtown** — 350K unique visitors → 50K customers from blog content; first company (Maritime Vacation) built product before marketing → *"crickets"* → failed. The one before/after pair behind "marketing before manufacturing." + +**The cold-call opener (paraphrased transcript):** a curiosity question scoped to the prospect's world ("have you looked into AI answering your calls…?"), an explicit "I've got nothing to sell," a peer-behavior nudge, then a 15-minute Zoom with a live demo. Worked example niche: **AI voice agents for local businesses** (SMB, not enterprise). + +**Artifact discipline:** offer doc (copywritten, sells on its own via a link) vs. pitch deck (bullets you speak over). **Never email the pitch deck** for "team review" — it gets forwarded and your plan hired out to someone else. Drafting is delegated to AI via "reverse prompting" ("…then ask me any question you need to get total clarity"). + +**Audience:** aspiring founders at $0; service providers stuck on hourly/custom; SMB-focused agencies, AI-automation builders, consultants. + +## Connections + +- [[dan-martell]] — fourth confirmed source; see the within-author tensions below +- [[pricing-from-value]] — the money map is the backwards math restated; $1K/mo floor re-asserted (same voice as the suspected 07-17 origin, so convergence is weak) +- [[offer-ladder]] — a second three-tier ladder, now with an explicit **decoy** rationale and different ratios (½×/10× vs. 45%/5×) +- [[outcome-based-selling]] — "features tell, outcomes sell"; the time/money/status triad; the five offer elements incl. risk reversal +- [[productized-service]] — the custom/product/productized triage; **offer-first camp gains a source**; the $50 pre-sell waitlist converges with the RU validate-before-build rule +- [[information-vs-implementation]] — the scramble trick and the "nuanced and observable problems" prompt **verbatim from a named Martell source** — the key to the 07-18 authorship question; plus Flowtown, the first (self-reported) outcome number for content-as-engine +- [[client-acquisition-channels]] — inbound + outbound **in parallel**; cold calling prescribed for SMB; the phone-mining outbound ladder +- [[sales-discipline]] — objections-vs-obstacles; 100 no's/day; 30-second callback; chat DM flow; don't spend until paid +- [[referrals]] — "ask past the person" mines the personal network for warm intros **before any past client exists** +- [[marketing-system]] · [[partnerships]] — stage tensions with the same author's scaling material (see below) +- [[niche-selection]] — sell to business owners at $1K+; Ikigai as the supply-side filter +- [[eugene]] — the $0-start blueprint matches his stage; the sweet-spot format fits his domain poorly (see entity page) + +## Open Questions + +- **Does the sweet spot survive contact with delivery?** 100 concurrent $1K/mo customers is a support/ops load the video never costs out — for a solo operator that may be *harder* than 10 × $10K, the model he dislikes. +- **All numbers are self-reported.** Flowtown's 350K→50K, "8 figures by chat," and every rule of thumb ($1K floor, 100 no's/day, 30-second callback) carry no external verification. +- **Within-author tension 1 — cold calling.** [[2026-07-22-stop-cold-calling-do-this-instead]] (same author): cold outbound is "the hardest path." Here: cold calling is one of two prescribed closing channels. Reconciliation is scope — that clip was ~$10K+ ACV enterprise; this one is $1K/mo SMB/local — but neither video states the boundary. +- **Within-author tension 2 — parallel engines vs. pick one.** The three-lever material says pick **one** lever, 90 days. Here inbound and outbound run **in parallel** from day zero. Stage-scoped (start vs. scale)? Neither video says so. +- **Within-author tension 3 — the $10K deal.** He "personally dislikes" 10×$10K, yet [[partnerships]] — his flagship enterprise play — is scoped ~$10K+ ACV. Stage-dependent again, unstated. +- **The chat-vs-call posture blurs.** The suspected-same-author 07-17 video says the market is call-fatigued (chat-first); this one teaches cold calls alongside chat. If one speaker holds both, the positions are channel-by-buyer, not a doctrine. + +## Change Impact on Wiki + +Seventeenth source; fourth confirmed [[dan-martell]] — and the trigger for a **source-independence correction**: its verbatim reuse of the scramble trick and the "nuanced and observable problems" prompt makes Martell the near-certain author of the previously anonymous [[2026-07-18-information-is-free-implementation-is-paid]], and the "buy back 10 hours" signature makes him a plausible author of [[2026-07-17-design-the-perfect-offer]]. + +- Created this page. +- [[dan-martell]] — fourth source; money map; within-author tensions; suspected authorship of 07-18 (strong) and 07-17 (moderate). +- [[information-vs-implementation]] — **downgraded** its "independent second voice" claim (the first voice was probably Martell too); added Flowtown as first, self-reported outcome data. +- [[offer-ladder]] — second ladder + decoy rationale; no longer single-example, still possibly single-author. +- [[productized-service]] — offer-first trigger gains a source; pre-sell waitlist mechanic added (cross-tradition convergence with validate-before-build). +- [[pricing-from-value]] — floor restated; convergence caveat. +- [[outcome-based-selling]] — time/money/status; five offer elements. +- [[client-acquisition-channels]] · [[sales-discipline]] · [[referrals]] · [[marketing-system]] · [[partnerships]] · [[niche-selection]] · [[eugene]] — updated as described on each page. +- Source pages [[2026-07-17-design-the-perfect-offer]] and [[2026-07-18-information-is-free-implementation-is-paid]] — speaker open questions updated with the new attribution evidence. diff --git a/wiki/sources/2026-07-26-how-to-build-a-billion-dollar-company-2027.md b/wiki/sources/2026-07-26-how-to-build-a-billion-dollar-company-2027.md new file mode 100644 index 0000000..da4c040 --- /dev/null +++ b/wiki/sources/2026-07-26-how-to-build-a-billion-dollar-company-2027.md @@ -0,0 +1,61 @@ +# Как Построить МИЛЛИАРДНУЮ КОМПАНИЮ в 2027 (How to Build a Billion-Dollar Company in 2027) + +#source #gtm #strategy #pricing + +## Source Metadata + +- **Raw path:** `raw/sources/Как Построить МИЛЛИАРДНУЮ КОМПАНИЮ в 2027.md` +- **Source type:** Conclusions note from a Russian-language YouTube video (34:52), https://www.youtube.com/watch?v=GE5qmn7M7lo +- **Speaker:** [[oskar-hartmann]] (identified in the raw note by context: KupiVIP, ShoppingLive, Fab.com shareholder, "Создатель единорога" program) +- **Date:** undated (2026 context — "land grab happening right now in AI") +- **Ingested:** 2026-07-26 +- **Independence:** a genuinely new voice — **third tradition** in the vault (VC/product-startup world), independent of both the [[dan-martell]] corpus and the RU dev-sales cluster (Rodenko, AB Analytics, Tony) + +## Core Claims + +1. **A good product does not sell itself.** In the vibe-coding era everyone has "10–15 great products sitting in Cloud Code"; the startup graveyard grows faster than the list of successes. **Product-Market Fit is the start, not the finish.** What separates a billion-dollar company from a "tumor" is a **repeatable, scalable sales channel with predictable acquisition economics** ([[sales-channel-as-moat]]). Claimed illustration: "Tim Cook created more value than Steve Jobs — 45× growth of Apple without a single new product." +2. **Five founder mistakes:** (1) building feature #26 instead of a go-to-market machine; (2) not selling personally — "I'll hire a salesperson" is a childish idea; the founder is the company's chief salesperson, and Hartmann won't invest where the founder doesn't sell; (3) targeting the whole TAM instead of a small winnable SOM ("AI agent answering calls for HVAC/plumbers" beats "AI agents for every profession"; Manifest became a unicorn on **immigration law alone**); (4) betting on giant clients — Pediant sold QR payments to Walmart/Best Buy, integrations dragged 1.5 years, the champion left, the deal died, and with it the startup; (5) hoping a partnership will "make everything fly" — **partners almost always disappoint** (your product is lost among a bank's 15 own + 30 partner products; a single gatekeeper partner takes all the margin; observed results **100–200× below expectations**). Partnerships work only with **many** partners and a product that sits naturally on top of their services ([[partnerships]]). +3. **Channel beats technology — Pediant vs FlatPay.** FlatPay (payment terminal, "1% commission, no asterisks") built **door-to-door sales** in Holland/Germany: one rep sells 10–20 terminals/month → billion-dollar company; its founder is on his **sixth** business using the same distribution playbook — the channel, not the product, is the reusable asset. +4. **Attention is the most expensive resource on the planet.** 12 hours of screen time, ~40 GB of information per head per day; AI made it worse (2,000 unread LinkedIn messages — agents mail for everyone). Channel hierarchy by attention economics: search ads (intent already expressed) → banner/Meta (interruption, pricier per result) → offline events (returning) → TV/Super Bowl (~$10M per 30s). "The average product that shouts displaces the better product that stays silent." +5. **Businesses that find a channel know their LTV** and will pay up to **a third of a client's lifetime profit** to acquire them on day one (US credit-card client ≈ **$1,000 CAC**). Burned-in channels are an **entry barrier**; venture rounds exist to fund negative unit economics until LTV lands ([[unit-economics]]). +6. **Land grab in AI, right now:** Anthropic and OpenAI struck **~$4B joint ventures** with private-equity firms holding hundreds of thousands of portfolio companies — every channel at once (partner, direct, phone, door-to-door). A resilient system is **multichannel**, channels reinforcing each other. +7. **Only ~1% of businesses fit venture.** European VCs won't look below $100B+ potential. **Stretching a normal company onto venture expectations kills it** — Fab.com: $50M→$100M revenue on a loyal design niche, raised at $1.5B, chased $10B expectations, only losses grew, bankrupt. Alternatives: top-20 US **private** family-owned companies do $30B+ revenue; slow $10M→$100M mid-market growth is a fine business, just not venture; Hartmann's ShoppingLive was built on "a couple hundred thousand dollars" with ~9-month payback and became Russia's #1 TV shop ([[venture-fit]]). +8. **AI is sucking up all free capital:** Anthropic, SpaceX, OpenAI will absorb nearly all free cash in the venture market this year — "you're either in a top AI lab, or for the venture market you don't exist." The rest should build "amusement parks" with 9-month payback and reinvest profits. +9. **Most entrepreneurs sell cheaper than the real cost.** Forgotten cost lines: distribution and sales, *repeat* acquisition/retention, transport, amortization, inventory write-offs — the resulting "cash gaps" are actually **real losses**. Sequence: prove the product is needed → prove you can produce it far below willingness-to-pay → the spread must cover everything **with a buffer**. And never use your best year as the base — the best year is a once-a-decade anomaly ([[unit-economics]]). +10. **Pricing power is the real PMF test.** If you can raise prices and the client flow doesn't fall — that's PMF. If you can't set your price (a marketplace sets it, discounts aren't yours to give) — "you're not an entrepreneur, you're in a simulation of entrepreneurship" ([[pricing-from-value]]). Marketplaces themselves are the most striking model: start free, end enormously profitable, because they hold the pricing power — and they survive the AI era. +11. **One partner deal can boost, not build.** His own first store hit $20M via a single entrepreneurial deal (partner drove traffic, paid 10% of revenue post-factum, open books) — then the partner's management changes, audits arrive, terms flip to CPM; by then you must have the statistics to compete in auctions. One-off boosts don't replace systematic channels. +12. **The entrepreneur's job, stripped of everything else: build and sell.** All else is derivative. + +## Key Evidence / Details + +- Named cases: Pediant (QR payments, Walmart/Best Buy — died), FlatPay (door-to-door terminals — billion-dollar), Fab.com (venture stretch — bankrupt; Hartmann a shareholder), Manifest / Дэн Мишин (immigration-law niche — unicorn), ShoppingLive (low-capital, high-ROI), Apple/Tim Cook (45× without new product). +- Closing checklist the speaker poses to founders: real PMF or pleasant illusion? · narrow winnable segment? · which *aching* pain? · venture-fit or reinvest-and-grow-slow? · pricing power? · which channel lets you **repeat**? · full-cost pricing? · will you be the company's first salesperson? +- Through-principles as stated: product → sell → repeat; SOM > TAM at the start; one channel = concentration risk; partners are a bad *first* channel ("you are their 46th priority"); attention is the most expensive resource; fundraising is an obligation, not success; whoever sells too cheap has no PMF; **sales channel is a moat**; founder sells first, always. + +## Connections + +- [[sales-channel-as-moat]] — new page; the source's central thesis (moat candidate #3, next to [[methodology-as-moat]] and [[relationships-as-moat]]) +- [[unit-economics]] — new page; full-cost pricing, LTV×⅓ CAC, buffer margin (partially fills a long-flagged vault gap) +- [[venture-fit]] — new page; the 1% rule, venture stretch, the slow-growth alternative +- [[partnerships]] — **first independent voice on the page**: adversarial on partner-as-savior, convergent with Martell on "many partners, never one gatekeeper" +- [[pricing-from-value]] — pricing power as PMF test; "most sell cheaper than real cost" joins the sell-dear school from a *different* tradition +- [[niche-selection]] — SOM > TAM independently restates "niche is upstream of everything" (Manifest case) +- [[tam-sam-som]] — the sizing vocabulary itself (created 2026-07-26 from a follow-up Q&A) +- [[client-acquisition-channels]] — channel hierarchy by attention; whale-client warning; the multichannel position +- [[marketing-system]] — independent second voice for "a machine with predictable economics you can turn up"; FlatPay = one repeatable channel first, multichannel at scale +- [[sales-discipline]] / [[technical-founder-trap]] — founder-sells gets a third tradition; feature-#26 syndrome is the trap's product-startup form +- [[ai-market-shift]] — vibe-coding commoditizes the product artifact; attention scarcity; the AI land grab and capital suction +- [[oskar-hartmann]] — new entity + +## Open Questions + +- Almost every figure is war-story grade: 100–200× partner shortfall, $1,000 CAC, ~$4B JVs, 12h/40GB attention numbers, $10M Super Bowl, Apple 45× — quoted from memory on stage, uncited. Attributable, not verified. +- **Scope mismatch with the vault:** the address is to *product startups* choosing venture vs. bootstrapped growth; the vault's core domain is *dev services*. Which claims transfer (founder-sells, SOM>TAM, pricing power, full-cost pricing — plausibly all) and which don't (LTV×⅓ CAC math assumes recurring product LTV) is the reader's judgment, not the source's. +- Incentive: Hartmann runs a paid "unicorn creator" program — like every coaching source in the vault, the diagnosis ("you lack GTM discipline") is adjacent to what he sells. +- The Tim Cook claim ("45× without a single new product") is rhetorically effective and factually contestable (Watch, AirPods, services all shipped under Cook) — treat as a framing device, not a fact. +- Does the door-to-door FlatPay playbook say anything for B2B services, or is it consumer/SMB-product-specific? + +## Change Impact on Wiki + +- Created [[oskar-hartmann]] (entity), [[sales-channel-as-moat]], [[unit-economics]], [[venture-fit]] (concepts). +- Updated [[partnerships]] (first independent second voice — counter-position + partial convergence), [[pricing-from-value]] (pricing power test; cross-tradition convergence note), [[niche-selection]] (SOM>TAM, third-tradition convergence), [[client-acquisition-channels]] (multichannel position, whale-client warning, attention hierarchy), [[marketing-system]] (independent corroboration of the system idea; pick-one complication), [[sales-discipline]] (founder-sells third voice), [[technical-founder-trap]] (feature-#26 convergence), [[ai-market-shift]] (vibe-coding commoditization, attention scarcity, land grab), [[methodology-as-moat]] (third moat candidate cross-ref), [[eugene]] (pricing-power and SOM implications), [[overview]], [[index]], [[log]]. diff --git a/wiki/sources/2026-07-26-main-principle-of-successful-business.md b/wiki/sources/2026-07-26-main-principle-of-successful-business.md new file mode 100644 index 0000000..53c7c67 --- /dev/null +++ b/wiki/sources/2026-07-26-main-principle-of-successful-business.md @@ -0,0 +1,59 @@ +# Главный Принцип УСПЕШНОГО БИЗНЕСА (The Main Principle of a Successful Business) + +#source #validation #strategy + +## Source Metadata + +- **Raw path:** `raw/sources/Главный Принцип УСПЕШНОГО БИЗНЕСА.md` +- **Source type:** Conclusions note from a Russian-language YouTube video (17:52), https://www.youtube.com/watch?v=pHoWRl7MVwE +- **Speaker:** [[oskar-hartmann]] (named in the raw note) — his **second** vault source +- **Date:** undated (2026 context — AI mockups, humanoid-robot data market) +- **Ingested:** 2026-07-26 + +## Core Claims + +1. **Sell first, then build.** Building the product is the entrepreneur's most expensive and least reversible decision; before committing, prove with **cheap experiments** that the pain is acute enough that customers **pay money up front**. Waitlists, likes, "interesting" — none of it counts ([[sell-before-build]]). +2. **The signal hierarchy:** button click (weak) < email/waitlist signup (stronger but deceptive) < **payment — the only real signal**. "Голос деньгами" — voting with money. +3. **The cheap-experiment toolkit:** + - *AI-mockup blast* (his own anti-case): a beautiful AI-generated image of a coworking space for business owners, offered to ~5,000 people via 7–8 business clubs with named price and "20 seats, who's with me?" — **0 real buyers** despite his 100% conviction. Project killed for pennies instead of millions. + - *Fake payment screen*: top utility-app studios launch ~20 apps at once as full-looking shells; at the payment screen the user sees "Error, payment failed" — the studio keeps real willingness-to-pay data at **< $1,000 per experiment**. Findings: "quit casino" failed, "quit porn" worked, weight-loss always works. The studios **forbid themselves from inventing** — they let money vote. + - *Fake-door buttons* (Oliver Samwer's eBay clone for Germany, ~20 years ago): shipped all 100 buttons in the UI **non-functional**, watched click logs, built in click-count order. "Intuition deceives — always." + - *Wizard-of-Oz manual MVP*: when the product can't be cheaply mocked, deliver the value **by hand for the first 10 clients**, then automate. (His example: Build.ai [sic] — valued at $2B while "the AI" was 500 Indian specialists; "great way to *start* — at $2B you should probably have built the product.") + - *Pre-orders at any scale*: Tesla collected 100K paid Model 3 preorders, then built; same for Cybertruck — "a $1.5T company still tests demand; the principle doesn't depend on size." +4. **Pre-payment is the supreme demand signal.** The MIT-graduate case: sold **$5M in prepaid contracts** for humanoid-robot training data ("fold shorts + sensors + video") *before collecting any data* — strategy copied from 10 companies that grew the same way on LLM data. Positive unit economics from day one. Anti-case: his own Zavent (meeting-room booking) — customers would only pay 3 months post-delivery, turning the company into "a bank financing its clients"; when prepayment was required, conversion collapsed. **If customers will pay up front, demand is real; if only post-pay, you're in a different business.** +5. **The acute-pain test:** *"If the business only works when everything is perfect — it's a bad business. A good business is when everything is bad and people still come and pay."* Exemplar: hospitals — 1.5-hour waits, no good reviews, you pay anyway and say thank you. Acute pain means people pay **for the concept**, not for polish ([[pain-discovery]]). +6. **The recommended trainer business is traffic arbitrage:** fastest feedback loop — buy traffic → landing → payment screen; a **single word** in the offer can move conversion 3–5×. Rule: a plain landing page doesn't qualify — there must be a **payment screen**. +7. **The mindset differential:** two portfolio AI companies, 12 weeks, same money — team A ran 10 tests, updated the product repeatedly, constant customer signals; team B, still building, zero signals. Only difference: **willingness to launch ugly and look stupid**. "Success is usually not where you thought — and only frequent cheap tests find it." +8. **Red flag: duration without revenue.** "We've been working on this since 2016, no revenue yet" is pitched as dedication and is "the fattest minus" — no revenue over a long project = no evidence. "I'd rather talk to a team that started a week ago." +9. **CAC-burning as a moat, restated:** once PMF is proven and unit economics are positive, spend heavily per customer ($80–100 CAC) so no newcomer can afford to enter — consistent with his first source's ⅓-of-LTV entry-barrier logic ([[unit-economics]], [[sales-channel-as-moat]]). +10. Через-principles: experiment while it's cheap ($1K mistake safe; 6-month build fatal); intuition always deceives; endure the pain of reality **early**; don't dictate what the customer should want — build what is already demanded. + +## Key Evidence / Details + +- The self-test checklist (raw note): smallest experiment that would falsify the hypothesis · what makes a customer pay *now*, pre-build · landing → **payment screen** (not signup) · can I collect (partial) prepayment · who — by name — is the smallest group with the most acute pain · will I walk to 10 concrete potential buyers and ask what they'd pay for right now · can I deliver the value by hand to the first 10 · if >3 months with no revenue, what actually stops an ugly launch tomorrow · does my business survive when everything goes wrong? +- Named cases: coworking test (own, failed cheaply), utility-app studios, Samwer/eBay-Germany, Tesla Model 3/Cybertruck, humanoid-data founder ($5M prepaid), Zavent (own, post-pay trap), Build.ai [sic]. + +## Connections + +- [[sell-before-build]] — new page; the whole discipline (signal hierarchy + toolkit) lives there +- [[productized-service]] — validate-before-build gains a **third tradition**; the $50-paid-waitlist and RU validate-first rules now have a full toolkit behind them +- [[pain-discovery]] — the acute-pain test ("still pay when everything is bad") is a new, revealed-preference diagnostic +- [[cloning-over-originality]] — **first independent second voice**: Samwer's clone, app studios that forbid inventing, the data founder copying 10 LLM-data playbooks +- [[sales-discipline]] — "since 2016, no revenue" red flag converges with Rodenko's "a year of repackaging is for people afraid to pick up the phone"; welcome bad news early +- [[unit-economics]] — Zavent: post-payment = financing your customers (a forgotten cost line made vivid); CAC-burn barrier restated +- [[sales-channel-as-moat]] — within-author consistency on the CAC entry barrier +- [[oskar-hartmann]] — second source; framework stability +- [[eugene]] — the checklist is directly runnable against his CV/embedded offer + +## Open Questions + +- **Ethics/legality of the deception-based tests are never addressed.** Fake payment screens ("error, payment failed") and fake-door buttons collect purchase intent under false pretenses — consumer-protection exposure varies by jurisdiction, and the reputational cost of a discovered fake is unmodeled. The vault records the mechanics without endorsing them; the honest variants (visible pre-order, paid waitlist, manual MVP) carry most of the same signal. +- **"Build.ai" is almost certainly Builder.ai** (general knowledge, not from the source): the widely reported case matching the description — and that company **collapsed into insolvency in 2025 amid allegations its AI was largely manual work and its revenue overstated**. The source cites it as a quasi-positive "great way to start," which undercuts the example: the same case is also the cautionary tale for *never graduating* from Wizard-of-Oz (and for misrepresenting it to investors — the part Hartmann's framing skips). +- All figures are war-story grade: 5,000 recipients / <5 replies, <$1K per app test, 100K preorders, $5M prepaid, $80–100 CAC, 3–5× one-word conversion swings — attributable, unverified. +- The traffic-arbitrage recommendation sits oddly with the vault's services domain — a services operator can't A/B a payment screen as cheaply; the transferable core is "smallest paid test," not the mechanism. +- Tension worth watching: "don't dictate what the customer should want" vs the vault's [[outcome-based-selling]]/[[technical-founder-trap]] thread, where articulating an outcome the buyer couldn't name *is* the value-add. Likely scoped (product demand vs service framing), unstated. + +## Change Impact on Wiki + +- Created [[sell-before-build]] (concept). +- Updated [[productized-service]] (pre-sell now three traditions), [[pain-discovery]] (acute-pain test), [[cloning-over-originality]] (first independent second voice; status upgraded), [[sales-discipline]] (duration-without-revenue red flag convergence), [[unit-economics]] (Zavent post-pay trap; CAC-burn consistency), [[sales-channel-as-moat]] (consistency note), [[oskar-hartmann]] (second source), [[eugene]] (runnable checklist), [[overview]], [[index]], [[log]]. diff --git a/wiki/sources/2026-07-29-start-a-business-with-claude-code.md b/wiki/sources/2026-07-29-start-a-business-with-claude-code.md new file mode 100644 index 0000000..b8d3d51 --- /dev/null +++ b/wiki/sources/2026-07-29-start-a-business-with-claude-code.md @@ -0,0 +1,56 @@ +# Start a Business with Claude Code + +#source #validation #gtm #ai + +## Source Metadata + +- Date: undated (ingested 2026-07-29) +- Raw path: `raw/sources/Start a business with Claude Code.md` (conclusions note; root: https://youtube.com/shorts/JpLgVf8Alys — "Stop pretending not to know how to start a business with Claude Code", 0:42) +- Source type: US short-form video (YouTube Short); author **[[dan-martell|Dan Martell]]** — confirmed by the vault owner 2026-07-29 (the clip itself names no speaker); **fifth confirmed Martell source** +- Ingestion date: 2026-07-29 (attributed same day) +- Evidence grade: **the vault's shortest and thinnest source** — 42 seconds, no cases, no figures. Pure prescription; its value is compression: the Martell $0 protocol reduced to short-form, with [[claude-code]] as the executor. + +## Core Claims + +1. **Sell first, build second.** To go $0 → $1M with AI: use [[claude-code|Claude Code]] to stand up the *appearance* of a business, close paying customers via cold outbound, and only then have Claude build the product. Demand is validated with money before engineering effort is spent ([[sell-before-build]]). +2. **The 5-step playbook:** (1) pick a service to sell (anything — video editing, AI automation); (2) Claude Code builds a landing page, invents a company name, wires a waitlist; (3) Claude Code scrapes the web for prospect contacts; (4) Claude Code writes the cold-outbound script for that ICP; (5) you email/call, book, close — *then* ask Claude to build the product. +3. **Claude Code as the entire GTM stack**, not just the build engine: landing page, company identity, lead list, sales copy, and finally the product. The human's residual jobs are choosing the service and doing the close. +4. **AI collapses the "I don't know how" excuse.** "Whatever business you want to be in, Claude will also tell you how to do it" — domain knowledge on demand; pre-existing expertise not required ([[ai-market-shift]]). +5. **Distribution is the moat, not code.** Landing page + outbound = go-to-market; the product is the *last* step ([[sales-channel-as-moat]]). +6. **The blocker is psychological, not technical.** "Stop pretending not to know"; the gap between aspiring founder and founder "is one cold email away" ([[sales-discipline]]). + +## Key Evidence / Details + +- No evidence in the vault's sense is offered — no case, no number, no cohort. Every claim is asserted. +- Stated audience: aspiring solo founders sitting on ideas; **developers who over-invest in building and under-invest in selling** ([[technical-founder-trap]]); anyone using "no industry experience" as a reason not to start. +- Step 5 ("ask it to build it for you") is flagged by the source itself as the step people underestimate — i.e. the capability claim is load-bearing, and it is exactly the claim [[ai-productivity-evidence]] contests at the expert end (though the leveler claim targets *novices in a domain*, the segment the evidence says gains most). +- The internal waitlist (step 2) is **unpaid** — by the vault's own bar ([[sell-before-build]]: unpaid lists don't count) it is not the validation event. The playbook's actual validation event is the **closed sale** in step 5, which sits *above* mere payment in the signal hierarchy. The playbook passes the vault's money bar, just not where it appears to. + +## Connections + +- [[dan-martell]] — fifth confirmed source; every claim here restates his corpus (marketing-before-building, $0 cold outbound, AI-built lists), now compressed to 42 seconds +- [[sell-before-build]] — the rule restated in AI-era compression; **within-author restatement**, not a fourth voice (Martell already counts among the rule's three traditions) +- [[sales-channel-as-moat]] — "distribution is the moat, not code": Martell stating the priority claim; folds into his existing marketing-system convergence on that page (no mechanics added) +- [[ai-market-shift]] — new role for AI: the **leveler** (domain knowledge on demand) — his first claim in that page's roles table +- [[client-acquisition-channels]] — the $0 cold-outbound prescription, same author as the $0 blueprint it matches; framework stability, not a second voice +- [[technical-founder-trap]] — the stated audience is that page's patient, build-instead-of-sell form; same author as the page's founding source, so restatement not corroboration +- [[sales-discipline]] — bias to action; launch-ugly kinship +- [[claude-code]] — the tool itself, now an entity +- [[eugene]] — contrast case: his 90-day plan reaches the same sell-first conclusion but replaces the fake-company front with a paid diagnostic ([[2026-07-26-eugene-90-day-plan]]) + +## Open Questions + +- ✅ ~~**Who is the author?**~~ — **[[dan-martell|Dan Martell]]**, confirmed by the vault owner 2026-07-29. His 5th confirmed source (possibly 7 of 20 with the two still-suspected). Consequence: every echo this source lent — sell-first, distribution-over-code, $0 cold outbound, the build-over-sell audience — is **within-author self-agreement**. The echo-grade discipline held: no page had granted it independence weight, so the attribution changed labels, not conclusions. Two within-author drifts logged on [[dan-martell]]: unpaid waitlist (vs his own $50 *paid* rule) and the invented-company front. +- **Ethics/legality of the front.** An invented company name + landing page + waitlist before any capability exists is the deception-based end of the [[sell-before-build]] toolkit (kin to fake payment screens); web-scraped contact lists + cold email carry GDPR/CAN-SPAM exposure in the EU/US. The source models neither cost. +- Does "Claude will tell you how" survive contact with regulated or physical domains (the vault owner's industrial CV niche), or only with commodity digital services like the source's own examples? + +## Change Impact on Wiki + +- Created this page and [[claude-code]] (first tool entity). +- [[sell-before-build]]: fourth-voice echo recorded; the compressed services variant (close via outbound before building) and the fake-front caveat added. +- [[ai-market-shift]]: **Leveler** row added to the roles table, with the novice-tilt synthesis. +- [[client-acquisition-channels]]: second $0-stage cold-outbound voice noted under the Martell $0 protocol. +- [[sales-channel-as-moat]]: slogan-grade second voice recorded in Evidence; status unchanged. +- [[technical-founder-trap]]: audience-targeting bullet added to Evidence. +- [[overview]]: source count 19 → 20; navigation updated. +- **Attribution update (2026-07-29, same day):** owner confirmed Dan Martell as author. [[dan-martell]] updated to five confirmed sources (fifth-source positions block, within-author drifts); the echo/self-agreement relabel propagated to [[sell-before-build]], [[client-acquisition-channels]], [[sales-channel-as-moat]], [[technical-founder-trap]], [[ai-market-shift]], [[claude-code]]; [[index]] and [[overview]] denominators refreshed to 5-possibly-7 of 20.