Souk's Notes - Unofficial Summaries

Unofficial, machine-generated summaries, as of 2026-11-09.

Scott HanselmanCan you cheat cloud insurance?
  • Commitment insurance is pitched as good for clouds and customers alike. One speaker says customers get "an out" on unused commitments and can reinvest the money rather than getting mad at Amazon or Azure, likening it to Ford wanting Geico to exist so people will buy the F-150.
  • Abuse is held off by underwriting against moral hazard. Asked how they stop a failing startup buying cover just before it collapses, the speaker says the answer is underwriting, which exists partly to avoid moral hazard: buying insurance and then taking more risk because of it. The clip ends before any specific safeguard is described.
Scott HanselmanScott & Mark Learn To...Build from Vibes to Craft
synopsis

Hanselman and Mark, back from Build, end agreeing that AI will drive the cost of simple software towards zero but not the cost of complex software, because specification gaps and evaluation keep people in the loop. Both concede they could be wrong.

No end of engineers. Mark relays a session with Ion Stoica, who said at once that programmers will still be needed, for Mark's own reason: nothing can be fully specified, and AI fills gaps by inventing things. Mark calls engineering sculpting, refined by use. Hanselman says specification taken far enough becomes programming, and recalls his own push towards determinism, including checking a system32 folder into source control.

IKEA and carpentry. Mark places software on a complexity spectrum where simple, well-specified systems need no engineer and medium complexity falls apart. Hanselman's analogy, tried on Japanese CTOs, is IKEA against Japanese carpentry; Mark puts web-plus-database apps and bespoke state retirement systems on the IKEA side.

Evaluation. Mark argues the bottleneck is evaluation: tests and human oversight, with Azure test runs taking hours. Hanselman pushes on whether more evaluation just means more AI; Mark says it does, and that it costs time and money too.

Skills files and taste. Mark raises the claim that a skills file makes a junior senior; Hanselman rejects it. Hanselman says early-career developers declare done too soon, and admits he called a project done at 80% where Mark kept going.

Shipping. Hanselman's OpenClaw Windows companion app is alpha despite weeks of use; Mark says Microsoft's bar is higher than a solo open-source project's, and relays Simon Willison's view that the only software to trust is software many people have used for some time.

  • Mark holds that AI will not eliminate software engineers. He relays asking Ion Stoica of Berkeley at a Build session, who answered no at once, for the reason Mark gives himself: nothing can be fully specified, and where the spec has gaps AI makes things up that may violate implicit assumptions. Mark calls engineering sculpting, needing feedback from use, and concedes it is opinion he cannot win from first principles; Hanselman adds that spec taken far enough is just programming ("Word documents don't break the build").
  • System complexity decides where AI can stand in for engineers. Mark says simple, well-understood systems can be built from a few sentences but medium complexity "falls apart". Hanselman's analogy, from a meeting with Japanese CTOs, is IKEA against Japanese carpentry; Mark maps IKEA to low-complexity web-plus-database apps and bespoke state retirement systems, and Hanselman offers his podcast admin site: "classic late 2025 software" with a god object and a thousand tests, fine for an audience of one.
  • Evaluation is the bottleneck that will not go to zero. Mark says evaluation means the tests plus human oversight of the output, and that a moderately complex Azure service has tests taking hours, so a commit that kicks off 5 hours of tests forces more evaluation up front, costing time and money. "Cost of software is going to zero" comes, he says, from people seeing only the simple end; both hosts say they could be wrong.
  • Hanselman rejects a skills file as a shortcut to seniority. Mark puts the "controversial take", heard from smart people, that a skills file turns a junior into a senior. Hanselman is irritated by "you're an expert" prompting ("I am more than the sum of my context") and unsure whether to be offended by a request to turn his 20-plus years of blog posts into a skill.
  • The bar for shipping depends on who ships it. Hanselman calls his OpenClaw Windows companion app alpha despite weeks of trouble-free use, since odd builds or non-English systems will break it; Mark says a solo open-source project can have rough edges but software from Microsoft to many people cannot. Mark relays Simon Willison trusting only software used by many people for a while, and Hanselman says to treat LLM code like a stranger's pull request.
Professor G MarketsAnthropic's Insane Valuation + The Future of Marketing
  • This post includes paid content that is not available publicly. See the original source.
Y CombinatorPick One Idea and Go Deep
  • Founders should stop hunting for the "perfect" idea and commit to one. John, a YC partner, says overthinking startup ideas — either waiting for the ideal concept or doubting your own founder-market fit — produces paralysis; citing Boom Supersonic's Blake Scholl, who came from ad tech with no aerospace background, he argues deep customer knowledge can be built quickly if you commit and go deep.
  • "Burning the other boats" means fully abandoning alternatives, not just prioritizing. He points to GovDash, which pivoted at least five times, changing its name and even email addresses each time, before its fifth idea in government-contract software worked so well the company raised a Series B — evidence, he argues, that half-committing to multiple ideas at once produces unreliable signal.
  • The bar for "going deep": could you actually run your customer's business? John's test is whether you know their daily crises, whether a specific problem is a top-five pain point, and what they'd pay to solve it — a level of knowledge he says should let you "teach a class" on the problem, built through tight loops of customer conversations and shipped product together.
  • Good AI-era startups should verticalize into owning outcomes, not just software. He argues software costs are heading to zero, so durable value shifts to trust, licenses and outcome ownership — citing Corgi Insurance, which acquired an insurance carrier during its YC batch rather than staying a tech-enabled broker, as a model for "being the insurer" instead of selling tools to insurers.
All Things FinancialGeographic Primacy
  • When the maritime commons stops being a guaranteed public good, geography returns as the binding constraint on power. Political strategy can open doors and accumulate goodwill, but it cannot manufacture reach or compel a guarantee another nation has chosen to stop providing. The Iran conflict is the demonstration: it presented as political — regime, enrichment, civilisational stakes — and was decided as geographic, ending at a twenty-one-mile aperture where the only question was who could keep crude moving and who could survive it stopping. The sanctions architecture had already reached the end of its travel; it could still inflict pain but no longer dictate terms. Ideology was the costume; the factors were the actual terms.
  • The eighty-year era was rent, and most tenants mistook the subsidy for a law of nature. One navy underwriting every sea lane flattened the map, so distance stopped billing anyone and alliances could be drawn anywhere regardless of terrain. Land empires never received that subsidy and never forgot the older arithmetic — a continental power holds what it can physically reach. But the paper is careful not to overclaim: contiguity is a multiplier, not a winning side, since fourteen borders is also fourteen potential fronts, and a hollow core hemorrhages through its frontiers rather than projecting through them.
  • The retrenchment is real, staged deliberately, and Canada is the cleanest refutation of political strategy. June 2026 cuts to European commitments reduced committed fighters by roughly a third and thinned maritime reconnaissance — but the disclosure was withdrawing every aerial-refuelling tanker, because refuelling is reach, the connective tissue letting power travel past the horizon and stay there. Canada has a genuinely strong factor base yet touches exactly one neighbour, earns roughly seven of every ten export dollars selling south, and would have to double combined sales to China, Germany, France, Mexico, Italy and India at once merely to move a tenth of its exports — every one of them across water no longer guaranteed. So it is not diversifying; it is swapping a continental dependency it can drive a truck across for a maritime one requiring the exact commons being withdrawn. The paper coins a typology for it — the Vault Node, high on four factors and hollow on Security — and stages the reversion in three regimes: repricing by ~2031, regionalisation with in-region providers by ~2036, and a multipolar continental order supplanting the treaty map by ~2051.
All Things FinancialPolicy is no longer made in abstraction; now decisions are made by location, logistics & resources 6-17-26
  • His organising claim is a dating: before 2019 decisions were political, after it they are economic. He recorded a video the day before the Iran war began saying it was the wrong war on Five Factor grounds. His account of how it resolved is the argument in miniature — it began political, turned economic the moment Hormuz closed, and then the only live question was whether an undefined political win exceeded a very defined economic loss. It did not, and that is what forced the end.
  • The European drawdown numbers are specific, and he singles out the least-covered one as the real signal. Fighters cut from 150 to 100, P-8A maritime reconnaissance from 26 to 15 — a 42% reduction — all eight KC-46 aerial refuelling tankers withdrawn entirely alongside carrier and warship reassignment, plus 5,000 troops out of Poland. Everyone covered the troops; he argues the tankers matter more because they are attached to a task force that is leaving. His blunt summary of the alliance position: NATO exists in name only.
  • He translates the framework into an instruction for reading decisions. Over five years to 2031 the guarantee frays but persists, so geography becomes a repriced risk factor — every commitment now carries the question of whether the guarantor can actually arrive. By 2036 sea-lane security is partly privatised with in-region providers emerging by necessity, Turkey for the Sunni near abroad being his example. By around 2051 a multipolar continental order organised around geographic clusters supplants the treaty map. The practical takeaway he leaves: any country or company still making decisions on political rather than geographic and economic grounds is making a mistake.
Professor G MarketsOpenAI’s Financials Leaked — The Losses Are Staggering
  • This post includes paid content that is not available publicly. See the original source.
Polis PanditJapan's 1% Confession
  • This post includes paid content that is not available publicly. See the original source.
Professor G MarketsTrump Loses the Iran War, Weakens America — as Newsom and Vance Make 2028 Moves
  • This post includes paid content that is not available publicly. See the original source.
AI Analyst LabHow to choose a north star metric (with a Claude Code audit)
synopsis

This AI Analyst Lab lightning lesson, run by Shane with the lab's two co-hosts, argues that a team's North Star metric should measure customer value delivered, not activity. It also argues that the metric only becomes useful once it is broken into the input levers that drive it. The lesson builds a seven-question test with four deal breakers and a four-lever breakdown, then runs both through a Claude Code skill. It ends on a synthetic e-commerce case where a sixfold rise in orders turns out to come almost entirely from new buyers who do not return. The lab says it is partnering with Amplitude on the session, and much of the framework and the skill's knowledge base comes from Amplitude's North Star playbook.

The problem. Shane's premise is that dashboards carry 10 to 40 numbers and few teams can name the one that says they are winning. AI makes this worse because anything can now be measured. Activity metrics such as logins, sign-ups and revenue rise without proving users got value. A wrong North Star sits above every decision and passes its error down. A gameable one that reaches the board can become impossible to drop, as with a past employer's email-open "active users".

The tests. A real North Star captures customer value, reflects strategy, leads rather than lags, can be moved by the team, can be understood, can be measured, and is free of vanity. Failing customer value, leading, movable or not-vanity rules it out. Nights booked at Airbnb is the example that passes. Shane polls the room on daily active users and defers the verdict to the AI.

The levers. A North Star cannot be moved directly. The levers underneath it are breadth, depth, efficiency and frequency. An input that merely renames the North Star, such as active buyers under weekly active buyers, breaks nothing down. A countable event like orders decomposes cleanly.

The audit demo. Shane uses a North Star skill from the lab's course-only repo, not yet merged, with audit, triage, explain, draft and drivers modes. A librarian agent cites a knowledge base of cases, anti-patterns, debates and industry notes. Daily active users was refused outright as an anti-pattern, with "happy deliveries" offered as a value-based replacement. Weekly completed orders passed five of seven with no fatal failure but was called weak. It counts orders regardless of returns or late delivery, so the suggested fix was "weekly completed orders with no issues". Its strategy fit was generic. Answering an attendee, Shane says more business context, ideally a wiki of the company, would sharpen that. Results are cached to JSON so a repeat audit is instant.

The drivers demo. Breaking down 2024 on the synthetic dataset, from a cached earlier run, orders grew sixfold. About 99% of that came from more buyers, with frequency flat, average order value down about 9% and the membership program contributing 2–3%. Shane reads it as growth by "renting new customers", which points work at frequency and depth. He says the AI does the grading and breakdown in minutes, but deciding what to measure and which lever to prioritize remains a human judgment.

Q&A. Shane advises auditing a new North Star weekly for its first month to six weeks, then each quarterly planning cycle, and at least annually. In B2B he says to anchor it at the user-workflow level, giving a past team's metric of time to an error-free completed task.

  • Most teams measure activity instead of customer value. Shane says logins, sign-ups and revenue go up and to the right without showing users got value, which shows up as a vanity metric or a dashboard of 30–50 numbers no one rallies around. Because the North Star sits above every decision, a wrong one passes its mistake to everything beneath it; he cites a former employer whose weekly active users counted anyone who opened an email, which iOS auto-opens inflated.
  • Four of seven North Star tests are deal breakers. The seven are customer value, fit with strategy, leading rather than lagging, movable by the team, understandable, measurable, and free of vanity; failing customer value, leading, movable or not-vanity disqualifies a metric regardless of the rest. Airbnb's nights booked is his passing example; the frameworks are drawn largely from Amplitude's North Star playbook, and the lab says it is partnering with Amplitude on this session.
  • Input metrics must decompose the North Star, not rename it. The levers are breadth, depth, efficiency and frequency (how many customers, how much each does, how reliably it goes through, how often they return). Shane warns that "active buyers" under a "weekly active buyers" North Star is the same number in a different hat, so pick a countable event such as orders or nights booked that splits into separate levers.
  • The demo audit refused DAU and graded completed orders weak. A North Star skill in the lab's course-only "AI analyst plus" repo, not yet pushed to main, grounds each verdict in a cited knowledge base via a "librarian" agent. It refused daily active users as a canonical anti-pattern (logins, not value received) and suggested a value-delivering action instead; weekly completed orders passed five of seven checks with no fatal failure but was flagged "issue-blind" to returns, defects and late delivery, with the fix "weekly completed orders with no issues", plus a generic strategy fit that more business context would sharpen.
  • A strong headline number hid growth built on one lever. The drivers mode on the synthetic Novamart data for 2024 (served from an earlier cached run) found orders grew six times, with about 99% from breadth, flat frequency, average order value down about 9% and the membership program at 2–3%. Shane reads this as "renting new customers" and says the AI can grade and decompose a metric but the choice of what to measure and which lever to prioritize stays a human decision.
AI Analyst LabHow to publish Claude Code analysis to Google Docs, Notion and Slides
synopsis

This AI Analyst Lab lightning lesson argues that once an analysis is finished, the slow part is packaging it. Claude Code can remove that cost if the analyst decides each audience's format in advance and names it in the prompt. One of the lab's co-founders presents, with the host adding comments. The lesson ends with one finished analysis published three ways in minutes: a Google Doc for a VP, a detailed Notion page for the team, and a slide deck. The presenter is candid that each would still need iteration.

The packaging tax. The presenter's premise is that charts, titles, layout and coherence often take longer than the 30–60 minutes of actual thinking. The fault is the sequence of manual steps, not slow people. The answer is to analyze once and repackage for each reader. Templates and frameworks are set up beforehand, which takes time to build but makes each later publish fast.

One analysis, three jobs. In the demo's audience-format map, the VP's Google Doc is a decision record: executive summary, findings, recommendation and the decision being asked for. The Notion page is a living team wiki with every chart and the SQL, so colleagues can check the work. The slides serve a 5–10 minute slot, one message per slide with an insight headline and a chart as proof. Each publish prompt names the audience, the format, the length and depth, and what to include. Slack and email are acknowledged but not demonstrated.

Choosing. The hardest decision is which of many insights and charts to show. The presenter describes cutting juniors' 50–60-slide decks to 15. The host recounts a 200-chart deck reduced to seven.

Feedback loops. In response to an attendee, the presenter describes feeding meeting transcripts from Otter into Claude Code through an MCP to plan the next version. Claude Code also answers leadership comments in Notion or Coda. The host analyzes workshop chats the same way and keeps stakeholder profiles drawn from their writing.

The demo. On the lab's synthetic Novamart dataset (13 tables, 6 million records, local DuckDB), Claude Code summarized 2024 as revenue growing 5.4x to 3.15 million, with growth that was leaky and costly. It then laid out the skills and subagents behind the analysis, from question framing to validation and export. The VP Google Doc came back with insight-led titles and an explicit ask. The Notion page, from a run made before the session, used tabs, embedded charts, unrequested emojis and an appendix of SQL and methodology. The presenter would still move the text next to its chart. The first-pass slides needed more explanatory text. The presenter notes that the speed depended on the analysis already being done. The host says he finds Notion easier than terminal markdown for reviewing his own work, and that he keeps two versions of a document rather than letting Claude edit in place.

  • Packaging costs more than analysis because its steps run in sequence. The presenter says formatting a finished analysis into a document — charts, titles, placement, coherence between sections — often takes longer than the 30–60 minutes of thinking, and every analyst on a team pays that tax each time. The proposed fix is to analyze once and repackage per audience, with formats and templates decided in advance so Claude Code can publish in minutes; the presenter concedes that scaffolding takes time to build.
  • Every publish prompt should name four things. They are the audience, the format, the length and depth, and what to include. The demo's map gives each format a different job: a Google Doc for a VP as a decision record (executive summary, findings, recommendation, the decision needed), a Notion page as a detailed team wiki carrying all charts plus SQL and methodology for review, and slides for a 5–10 minute slot with one message per slide, a headline that states the point and a chart as the proof.
  • The hard part is choosing what to cut. The presenter says junior analysts put everything in, leaving 50–60-slide decks to cut to 15; the host adds a new graduate whose 200-chart deck came down to seven. The generated documents titled every chart and section with its insight rather than a description, which the presenter singles out as the point.
  • The demo published one finished analysis three ways. Working from the synthetic Novamart dataset (13 tables, 6 million records, a local DuckDB), Claude Code summarized 2024 as revenue up 5.4x to 3.15 million with growth "leaky and getting more expensive", then wrote the VP Google Doc through the Google CLI, a multi-tab Notion page through an authenticated MCP (shown from a run made before the session), and a first-draft slide deck. The presenter says the analysis was already done, which is why it was fast, would still iterate on the Notion layout and on the slides' thin text, and skipped Slack and email.
  • Audience feedback should flow back into the next version. Answering an attendee, the presenter describes feeding an Otter transcript via MCP to Claude Code after each meeting to plan a V2, and having it read and answer leadership comments in Notion or Coda. The host adds that he analyzes Claude Code workshop chats and transcripts the same way and built profiles of his main stakeholders from their documents and Slack messages to tailor what he presents.
AI Analyst LabHow to design an A/B test with Claude Code (live demo)
synopsis

This AI Analyst Lab lightning lesson, presented by Shane with two co-hosts on the chat, argues that A/B tests fail mainly through the motivated reasoning of whoever reads the result, not through bad math. It also argues that an agentic system can add rigor by splitting the work. Deterministic code makes the call, LLMs draft and explain with deliberately limited context, and humans keep the judgment calls. The lesson demonstrates this with the lab's early open-source Agent XP repo in Claude Code and gets as far as a sealed design brief. The analysis stage is described but not run.

The problem. Shane says that across teams with 40 million and with a few hundred weekly users, badly run tests came from the reader wanting a particular outcome. He names four habits. People move the decision threshold to where the result landed, as when a 2% target becomes acceptable at 1.6%. They peek and stop while winning. They explain away broken guardrails ("we'll fix latency next sprint"). They swap in a secondary metric when the primary is flat. Each, he says, is a story told after the data arrives that rewrites the original question.

Where to intervene. Of the three stages, design, instrumentation and analysis, the system guards the first and third. Instrumentation is procedural engineering whose errors no framework can rescue, so Shane deliberately leaves it out. Platforms already compute correct lifts and intervals but leave judgment to people at their most biased moment. LLMs share the bias. So Python issues the verdict, LLMs translate and draft without making the call, and humans judge what to test and whether it is the right bet.

The architecture. Five agents (understander, designer, critic, SQL, narrator) work alongside design and analyze skills plus audit, data-connection and readout skills, with deterministic stats and decision-tree code underneath. Project-level YAML semantic models and metrics define users, sessions and conversion. Experiment-level folders hold each test's hypothesis and decision rule. Agents choose metrics from the catalog rather than inventing them. The critic does not know the hoped-for result, and design is sealed before any outcome data is touched. Analysis runs ordered gates: the split must match the brief, guardrails must hold and the sample must be large enough before lift is computed, then come direction, magnitude, effect durability and the verdict. Outputs are design, sample-ratio and analysis briefs, written at several depths from executive to engineer.

The demo. The repo's 14 metrics are YAML files. Revenue per user is a mean, with numerator and denominator in plain text and a default −1% guardrail. For moving the buy-now button above the fold, the designer chose conversion rate as primary and buy-now click rate as secondary. It then expanded the intent into a hypothesis with rationale and ran power analysis on the primary and the guardrails, settling on a 5% relative MDE. The critic reviewed the brief before it was sealed. The run took 13 minutes, and the readout first came back only as markdown.

Q&A. Shane says metric YAMLs should come from the team's existing definitions, shaped into the template with Claude. Unlike the general AI analyst repo, Agent XP handles only A/B design and analysis, aimed at letting non-data staff produce a sound simple design, with review by a data scientist. Randomization is checked afterwards but not performed. Data connects through semantic models pointing at a warehouse or a local DuckDB with an exposure table.

  • A/B tests go wrong because the reader wants a result. Shane says bad tests come less from weak tooling or rigor than from the person reading the result being the one who hoped for it. He names four habits: moving the threshold to where the result landed (a 2% minimum detectable effect quietly becoming 1.5% after a 1.6% lift), peeking and stopping while winning, explaining away broken guardrails, and promoting a secondary metric when the primary is flat. He calls this how brains work, not dishonesty.
  • Let code decide, LLMs translate, and humans judge. Experimentation platforms compute the statistics correctly but, in Shane's account, act as calculators that leave the call to people at the moment their judgment is most compromised, and LLMs pattern-match toward hoped-for results the same way. His system targets design and analysis and deliberately leaves instrumentation alone as too high-risk. Deterministic Python issues the verdict, LLMs draft and explain, and judging agents get less context on purpose — "blind judges" — because the failure being defended against is motivated reasoning, not ignorance.
  • Metric definitions live in files the agents cannot invent around. The open-source Agent XP repo has five agents (understander, designer, critic, SQL, narrator), design and analyze skills, and a whitelist of stats functions the critic checks were used. Project-level YAML files define semantic models and the demo's 14 metrics, each carrying its type and defaults; revenue per user, for example, brings a −1% guardrail to every experiment that uses it. Shane says deciding those definitions remains a human conversation with the team.
  • Analysis runs as ordered gates before any lift is shown. The steps check that the split matches the brief (a 57/43 split on a planned 50/50 halts before lift is computed), that no pre-set guardrail broke, and that the sample is large enough. Only then does it read the primary lift's direction and magnitude, then whether the effect held over the window (for example a 25–30% drop in the last third flags novelty), before a ship, don't-ship or learn verdict.
  • The live demo produced a sealed design but never reached analysis. The run took 13 minutes. For "move the buy now button above the fold", the designer picked conversion rate as primary from the catalog because it matched the word used, proposed buy-now click rate as secondary, and ran power analysis on the primary and on the guardrails, finding a 5% relative MDE feasible. A critic agent then reviewed it and the brief was sealed. The analyze stage was not run, and Shane says the tool does not do randomization or assignment and is early, actively changing work.
AI Analyst LabHow to push back on a vague data request, at work and in interviews
synopsis

This AI Analyst Lab lightning lesson argues that most wasted analysis time is lost before any data is touched, by starting on a question that names no decision, rests on no available data, or has no end point. The fix is a three-check gate (decision tied, data grounded, specific enough), a hypothesis with a pre-written rejection condition, and an impact-feasibility triage that makes declining a request legitimate. One of the lab's co-founders presents, and the host adds commentary and Q&A. It ends with the gate built into a Claude web prompt and into the lab's Claude Code repo, turning a vague churn request into a bounded question with a stop rule.

Why framing first. The host says analysts outside an embedded team often lack context, so a seemingly concrete request can consume weeks while analyst and stakeholder talk past each other. Agentic systems can be built to check human bias, not only model bias. The presenter reports that the first cohort of the lab's five-week course named question reframing its most valuable lesson. The same skill applies to interviews, which open vague on purpose, and to AI, which fills a vague prompt's gaps with assumptions.

The three checks. The first check asks what decision the answer informs. If none can be named, stop; the presenter calls this the hardest and most important. The second asks whether existing data can answer it, or whether to wait for tracking rather than give a half-baked answer. The third asks whether there is a metric, comparison and time frame that bounds the scope. "Why are signups down?" becomes "did the pricing page redesign cause the 12% signup drop in the two weeks after launch?", with rollback as the decision. In interviews, strong candidates ask "success for whom?" and "measured against what?" before listing metrics.

Hypotheses and triage. A sharp question carries a hunch. The analyst should say up front what would confirm it and what would reject it, as in the example of onboarding versus pricing as the cause of mid-market churn. Requests are placed on impact and feasibility. High-impact, feasible work goes first. High-impact work missing data gets planned. Quick wins serve as buffer. Low-low asks are declined with stated reasons, and the stakeholder can reopen them by supplying the decision and data.

The demos. In the Claude web app, a "question quality coach" prompt with work, interview and rank modes found a VP's "look into our churn numbers" had no decision, partly grounded data and no metric, segment or time frame. It then coached it into a question about where to point the retention team. In Claude Code, the repo's question-framing gate scored the same request 0/3. Metric spec, data audit and prioritization steps then produced a sharpened question: monthly voluntary logo churn against a 3% target over two quarters, by plan tier and tenure, to decide on funding a retention intervention, with a rejection condition. The presenter notes the gaps were filled with assumptions for the demo.

Q&A. The host says data teams building agentic systems is now the expectation. He calls company-wide self-serve tools much harder because their users cannot validate the answers. He often sets the model back to Opus 4.6 for analytics, saying 4.7 and 4.8 add little and 4.6 is faster and cheaper.

  • Pushing back on the question is the highest-value analyst skill. The presenter says students in the lab's first five-week cohort named reframing the question as the single most valuable thing they learned, ahead of the repo of 60 skills and agents. A vague ask like "analyze user engagement" yields generic observations no one can act on; "which segment drove the engagement drop last month so we can decide where to focus" names a segment, a quantified driver and the decision.
  • Every question must pass three checks before analysis starts. The presenter's 30-second gut check asks whether the question is tied to a decision (if none can be named, stop), grounded in data that actually exists, and specific enough to know when you are done. The worked ladder runs from "why are signups down?" to "did the pricing page redesign cause the 12% signup drop in the 2 weeks post launch?", with the decision being whether to roll it back.
  • Interview prompts are vague on purpose and reward clarifying first. Asked how to measure a new search feature, candidates who list DAU, retention and engagement fall into "the trap", the presenter says, while those who get offers ask success for whom (power users or everyone) and against what baseline. Only then do they set a primary metric, a guardrail and a 30-day bar for continued investment, confirming the decision with the interviewer as they go.
  • State in advance what result would prove you wrong. For a hypothesis that mid-market churn comes from failed onboarding rather than pricing, the presenter lists confirming evidence (churn clustered in accounts that never finished setup) and rejecting evidence (churn spread evenly, pricing dominating exit interviews). Requests are then scored on impact and feasibility: do high-impact, data-ready ones first, plan ones that lack instrumentation, use quick wins as buffer, and decline the low-low "graveyard of side quests" with written reasons.
  • The demos turned a churn Slack into a bounded question. A "question quality coach" prompt in the Claude web app (work, interview and rank modes) failed "can you look into our churn numbers?" on two of three checks and coached it toward a segment-ranking decision. A question-framing gate in the lab's Claude Code repo scored it 0/3 and, filling gaps with assumptions for the demo, produced: has monthly voluntary logo churn risen above a 3% target over two quarters, in which plan-tier and tenure segment, so leadership can decide on funding a retention intervention — with "below 3% and no single segment" as the stop condition. The host adds that vagueness often hides in windows, filters and thresholds.
Loss DogIs Moonshot Investing the NEW Norm; Warren Buffett MOAT Dead. #shorts #wearelossdog #investing
  • Shrinking attention spans are pushing retail toward moonshot bets. The question posed is whether hypergrowth "moonshot" investing, aimed at quick exponential wealth, has replaced Warren Buffett's moat style of capital preservation and steady growth. One host blames social media for cutting attention from 5–15 minutes to 20–30 seconds, and calls Gen Z more of a gambling, quick-fix crowd. That host credits the GameStop, Koss and AMC meme-stock episode with showing that retail can move markets.
  • SpaceX is trading on price, not value, and will break. The same host says retail piles into a stock or two each day, and SpaceX buyers keep calling it cheap at 135, 150, 200 and 220 regardless of company quality. The forecast: moonshot investing is the norm "for the foreseeable future", until the market breaks and something like moat-style investing returns.
  • The hosts split on whether moonshot investing is permanent. A second host calls the question silly, says moonshot investing "will always be the norm", and reminds the first of past advice to young traders: risk all of a $5,000 or $10,000 account instead of setting money aside in bonds. The clip ends with someone insisting moat style "is not going away". The captions do not show who said it.
Professor G MarketsReplay: How Trump Changed the Rules — with Heather Cox Richardson
  • This post includes paid content that is not available publicly. See the original source.
Crosstalk SolutionsCrosstalk Mobile: Top 5 Questions About Our 5G Unlimited SIM Cards (ANSWERED)
  • Crosstalk Mobile runs on T-Mobile as an authorized MVNO. The company, launched about two months before the video, has a direct agreement with T-Mobile, its only carrier for now, with multi-carrier SIMs planned "in the near future". The host contrasts this with gray-market resellers buying wholesale SIMs without a carrier agreement, which he says get shut down when caught.
  • The unlimited SIMs really have no caps or overages. Plans start at $119 a month, and the host says no amount of data changes that. Cheaper limited tiers are planned as a priority, for backup links, IoT and RedCap devices such as Netgear's $99 5G backup device and the GL.iNet Comet 5G, with no date given.
  • The SIMs suit 5G routers, not phones or tablets. The host says they work well in Netgear 5G and Peplink gear and he has not yet found a router they fail in, but phones and tablets are hit and miss and discouraged. He cites a reseller who got a Peplink router chosen, preconfigured on InControl 2 and drop-shipped with the SIM installed, all by text in a few hours.
  • The SIMs get real public IPv4, not CGNAT. The host argues CGNAT makes 5G failover incomplete, since inbound services such as a VPN server for remote staff stop working when the office fails over. Crosstalk SIMs get real IPv4 addresses, and a static IP is $5 a month extra; he personally tested port forwarding through the UniFi 5G Max and the Dream Router 5G Max.
  • There is no contract lock-in. Plans are month-to-month, or year-to-year if bought annually, and can be cancelled at any time. The host presents engineers answering customer calls and texts directly as the service's most underrated feature, contrasting it with Verizon Business or AT&T support.
Professor G MarketsThe Iran “Deal” Isn’t What It Seems
  • This post includes paid content that is not available publicly. See the original source.
Dr. Jon KrohnThe AI Model That Finally Beat Me (with Jon Krohn)
synopsis

For episode 1001, founder Kirill Eremenko hosts and Jon Krohn, the usual host, is the guest. Krohn's position by the end is a techno-optimist one: AI has erased the technical moat he spent 20 years building, but that makes skilled engineers more valuable; even an AI bubble would leave lasting infrastructure; the real business opportunity is wiring AI into actual workflows and data; and whether AI makes people's lives calmer or more frantic is, for now, up to each individual.

From neuroscience to finance and back. Krohn studied neuroscience at Oxford on a full scholarship, drawn by how the mind emerges from physics and chemistry, and moved into massively parallel computational statistics and machine learning there, with a NeurIPS paper in 2010. He says he did this work professionally until a few months before recording, when Claude began doing it better than him. After the PhD in 2012 he spent 2 years at a New York hedge fund, taken for the money, and now regrets leaving academia and its community. He is edging back: supervising a University of Auckland PhD on AI in clinical settings, lecturing at NYU and Columbia, and co-writing a book on agentic AI with Ed Donner.

What AGI requires. Asked whether AGI is judged by outcomes or needs something brain-like, Krohn starts from Google DeepMind's five levels of AGI, covered in his episode 748, which rank depth by the share of humans a system outperforms, and adds breadth. On depth, AI already rivals many people at computer-based work like coding and writing; on breadth, physical-world competence is years off, which he says explains the very large world-model seed rounds such as Yann LeCun's AMI and Fei-Fei Li's company. He sees no obvious mechanism for machine consciousness and no reason AGI would need it. Artificial neurons are a drastically simplified model of biological ones, and brain structures can inspire designs, but he argues silicon scales and moves at speeds brains cannot. Asked whether humans are just predicting the next token, he says fast, automatic speech and skills like experienced driving resemble it, and reasoning models' hidden thinking resembles deliberate slow thought, but the mechanisms differ entirely; prediction is simply central to any agent navigating the world.

Bubble or not. Pointing to his episode 974, Krohn argues that whether or not AI is a bubble, society wins: railway and dot-com busts ruined investors but left rails and fibre that powered later growth. He says he avoids individual stocks and stays diversified, and that market prices aggregate crowd judgement, so he would bet this is probably not a bubble, unlike ICOs and NFTs. To Eremenko's point, which Eremenko attributes to Andrej Karpathy, that scaling is yielding diminishing returns, Krohn answers that chips like Nvidia's GPUs or Amazon's Trainium and Inferentia, though tuned for Transformers, still serve any parallel matrix multiplication, so post-Transformer candidates such as Mamba or Pathway's Baby Dragon Hatchling (episode 929) will be designed to run on them. Jevons paradox, he says, means cheaper intelligence raises total compute demand, and more inference-time computation needs data centers too; he hopes AI-aided plasma control speeds commercial fusion.

Consulting and automation. He describes Y Carrot, his consulting firm founded a little over a year earlier: about eight people, US-based consultants with graduate technical degrees, a weekly half-hour cadence and a working prototype usually by week two, with a $50,000 minimum engagement copied from a former guest. He says the most valuable projects fully automate a repeated workflow, and that several clients now get in minutes what took weeks, with AI also doing the cross-checking more cheaply than people. In his telling no deployment has cost jobs so far, because freed time moves people to higher-value work.

Choosing projects and why they fail. For clients unsure where to start, he lists projects in a spreadsheet and scores reach, impact, confidence and effort (RICE), with effort as the denominator, crediting product managers and noting Dell's John Roese described cutting about 800 ideas to a dozen or so. The scores must estimate production, not prototype, and should come from workflow users plus technical staff rather than executives. Citing MIT NANDA's 95% figure while noting it has been debunked as an exact number, he says the top failure is missing enterprise data behind a capability a CEO saw in ChatGPT; Eremenko adds missing pipelines, his "Ferrari needs a highway". Krohn notes data engineering is itself being automated, citing a recent guest's company.

After pure SaaS. He argues pure SaaS's 80% margins break down when Claude Code can replicate the software, so durable value lies in forward-deployed or consultative models: Palantir engineers embedded full-time at a client like a police department, now copied by Anthropic and OpenAI, and firms like Unframe that tailor a limited set of products to each enterprise. Always-on lives. Eremenko asks whether AI will make people happier, citing Christopher Nolan's flip phone and printed emails. Krohn says he envies that and misses distraction-free study with a paper calculus textbook; a phone-free Memorial Day weekend meant missing a Kyunghyun Cho lecture a short walk away. He argues the technology already exists to build an agent that acts as a Nolan-style assistant, phoning only about what matters, though it takes time and tolerance for mistakes. He hopes access to such agents might one day be guaranteed like health care, but says for now it is up to each person.

  • AI erased his technical moat but raised engineers' value. In this role-reversal episode, hosted by founder Kirill Eremenko, Krohn says the machine-learning skill set he built from his Oxford neuroscience PhD onward stopped being a moat a few months before recording, when Claude started doing that work better than him. His argument is that engineers who stop typing code by hand and use tools like Claude Code can deliver far more, so hiring them is worth more, not less.
  • AGI needs breadth into the physical world, not consciousness. Krohn points to Google DeepMind's five-levels paper (his episode 748), which grades AGI by the share of humans a system outperforms, and argues that AI now matches or beats many people on computer-based work like coding and writing but is years from acting in the real world, hence world-model startups' huge seed rounds. He sees no reason consciousness is required, and says biological brains are useful inspiration but silicon has different limits and advantages of scale and speed.
  • An AI bubble bursting would still leave useful infrastructure. Citing his episode 974, he argues that, as with 19th-century railways and dot-com-era fibre, investors might lose their shirts but data centers, model advances and talent would benefit everyone; he personally holds diversified investments rather than individual AI stocks and would bet this is probably not a bubble. He invokes Jevons paradox to argue more efficient architectures will raise total compute demand, and says the hardware won't become obsolete because any successor to the Transformer will still need parallel matrix multiplication.
  • Most AI projects fail because the enterprise data isn't there. Krohn says the number-one failure he sees is a CEO proving a capability in ChatGPT or Copilot when the company lacks the underlying data at scale (Eremenko adds: or the pipelines to use it). He prioritises projects with RICE scoring (reach, impact and confidence over effort), estimated for production rather than prototype, and argues the people doing the workflow plus the technical team score it better than executives; he cites MIT NANDA's 95% failure figure while noting the exact number has been debunked.
  • The money is in bridging AI to real workflows, not pure SaaS. He says his consulting firm Y Carrot, about eight people and founded a little over a year earlier, typically shows a prototype in week two and has cut multi-week processes to minutes without job losses so far, because freed time goes to higher-value work. He argues the 80%-margin pure-SaaS model breaks down when Claude Code can replicate it, leaving durable opportunity in forward-deployed or consultative models like Palantir's, now used by Anthropic and OpenAI.
Professor G MarketsChina Gets Locked Out of SpaceX and America’s Biggest IPOs — with Ed Elson
  • This post includes paid content that is not available publicly. See the original source.
Silver AllianceThe US-Iran peace deal is not what you think it is.
  • Gold and silver rose on the peace announcement instead of falling. That's the opposite of the usual safe-haven reaction to easing tensions, which the video treats as a reason to question whether the deal is substantive or timed for effect.
  • The timing lines up with Kevin Warsh's first day as Fed chair. Caught between pressure to cut rates to refinance $39 trillion in debt and pressure to hold given 4.2% inflation, the peace news dropped oil more than $4 a barrel, easing inflation optics right before his first meeting.
  • The deal's substance is contested by a key party. Israel says it was excluded from the negotiations and won't withdraw from Lebanon, a stated condition of the deal, and the Strait of Hormuz reportedly remains blocked pending mine-sweeping.
Professor G MarketsTrump’s Big Iran Announcement Raises More Questions Than Answers — with Ian Bremmer
  • This post includes paid content that is not available publicly. See the original source.
Loss DogGold vs Silver: The Widow Maker Trade & IPO Secrets! #shorts #wearelossdog #goldtrading #silver
  • One host calls a short-gold leg the trade's real "widow maker." He pairs it with a long silver position (two gold micro futures short to one silver micro long); the combined trade had moved $4,000 since Friday, with the long side sitting near the top of a three-to-four-month range around $65.
  • A liquid, hyped IPO like SpaceX will price with wildly inconsistent volatility. One host expects different market makers to quote implied volatility anywhere from 40 to 90 on day one, and predicts most of the street will wait for Citadel to post the first markets before committing.
  • New IPOs should not be traded until options exist and settle. The advice is to wait a few days for options (hedging with short stock if needed), then give volatility time to find its level — the speaker recalls once profiting and once losing badly by pricing volatility too early.
Professor G MarketsThe Business of Media: 60 Minutes, Billionaire Owners, and the Podcast Economy (with Sara Fischer)
  • This post includes paid content that is not available publicly. See the original source.
Polis PanditIran "Peace" and Kevin Warsh's First Test
  • The author ties the rushed Iran peace framework directly to Fed Chair Kevin Warsh's first FOMC meeting. Rising energy prices from the Iran war have pressured inflation and borrowing costs ahead of the midterms, and the piece argues Trump is willing to make concessions in Iran specifically to help Warsh start with lower rates.
  • The deal favors Iran, whose regime remains intact and emboldened. The Strait of Hormuz operated without incident before the war began, so ending the war doesn't recover lost ground, it just removes a self-created risk — while Israel, the author argues, now has less leverage than before fighting started, given the economic toll on the West.
  • The author predicts Iran will stall negotiations to maximize leverage into the midterms, forcing Warsh into a defensive, quiet posture. Disrupting Hormuz costs Iran far less than it costs the U.S. and Israel to defend against, and continued disruption risk keeps Treasury yields elevated — pressure the author expects Warsh to manage by minimizing public communication rather than through policy moves.
All Things FinancialThe algorithm doesn't delete you, it disappears you. TikTok suppresses without suppression 6-15-26
  • He opens on his own distribution risk, which is the title's point: suppression now works by disappearance, not deletion. Views have fallen from 6,000–8,000 per video six months ago to 300–500, with follower counts frozen near 17,000 on TikTok and 11,200 on X for two years. Nothing is removed; it simply stops being shown. His response is to push the audience toward Substack for a semblance of control he does not have on a platform someone else owns.
  • The addressable-market arithmetic is his actual investment point about US AI. The administration froze two Anthropic models to foreign nationals — 90 minutes to comply, no detailed rationale given — which means labs have been told they may serve 330 million people out of 8 billion. Set against DeepSeek at roughly 19.66 cents per million tokens versus Anthropic at $15, and OpenAI cutting prices 40–50% while unable to service existing debt, he concludes there is no revenue model that makes sense. He also relays the widely-agreed technical caveat: jailbreaks cannot be fully fixed in these models, and other US labs are presumably equally exposed.
  • His post-war macro read hinges on one pair, with an explicit tail risk attached. Warsh's arrival reopens two parked Fed cuts; Europe benefits most from energy normalising; the BOJ is at 1% and expected near 2% by end-2027, narrowing the differential the carry trade depends on. He gives USDCNY at 6.8088 as the level to watch, with above 7 signalling trouble. His highest-conviction expression is dollar-yen, because both legs push the same way — but he names the paradox: a gentle yen appreciation delivers the clean yen-up, dollar-down, risk-off picture, while a violent disorderly unwind lets the dollar catch a safe-haven bid against everything except the yen, producing both rising together and breaking the dollar-down thesis temporarily. Gold he flags as the outlier, supported by lower real rates even in a risk-on tape.
Professor G MarketsThe Real Bottleneck in the AI Boom — with Jigar Shah
  • This post includes paid content that is not available publicly. See the original source.
Stock TokStocks to Buy...And NOT Buy ❌
  • This post includes paid content that is not available publicly. See the original source.
Y CombinatorGroww: If Your Customers Don't Love It or Hate It, You've Already Lost
synopsis

Lalit Keshre, co-founder and CEO of the now-public Indian investing platform Groww, traces the company's arc from a failed robo-advisor to India's largest brokerage, arguing throughout that unglamorous customer obsession, not clever strategy, explains its survival through multiple business-model changes.

Keshre and his co-founders started in 2016 believing India's low investor penetration meant a Wealthfront-style robo-advisor would take off; it didn't. Talking constantly to early users, via WhatsApp groups and sometimes literally approaching people in movie theaters, revealed customers wanted the opposite of an algorithm's recommendation: full visibility into every product and transparent pricing, closer to how Flipkart sells retail goods. Relaunched on that premise in May 2017, the product got 600 signups against an internal goal of 100, with word-of-mouth growth following and no paid acquisition.

Keshre frames two decisions as strategically deliberate rather than accidental: choosing to operate only inside regulated financial territory even though gray-zone alternatives existed, because it removed ambiguity from decision-making; and tolerating four straight years of zero revenue, betting that near-zero acquisition cost and high retention would eventually justify a business model. Vocal power users demanding zero-commission mutual funds later forced Groww to abandon its original commission revenue, and stock trading became the actual monetization lever.

Four co-founders have stayed aligned for a decade, Keshre says, not through daily consensus but through one values document — "customer first" — written at founding and treated as fixed even as strategy repeatedly changes, paired with clearly assigned ownership. He closes by describing wanting every launch to provoke either love or hate, never indifference, as the real measure of whether a product matters.

  • Groww's first idea, a robo-advisor, failed before pivoting to full transparency. Lalit Keshre, Groww's co-founder and CEO, says the 2016 robo-advisor model stalled despite India's low investor penetration; customers kept asking "why this product, why not that," which led the team to open the full catalog with transparent pricing instead, Flipkart-style.
  • He chose to operate only in regulated territory as a risk strategy. Rather than exploit unregulated or gray-zone areas — which he estimates cover roughly 40% of the space — Groww obtained licenses upfront, which he says removed decision variables and made execution simpler even though it was slower.
  • Groww ran four years at zero revenue before customer demand unlocked monetization. Early commission-based mutual-fund revenue was abandoned after vocal power users demanded zero-commission "direct" funds; the company bet that near-zero acquisition cost, high retention and heavy money flow would eventually produce a business model, and stock trading later became the monetization lever.
  • Four co-founders stayed aligned for a decade via one values document. Keshre says strategy can change "like pencil," but core values like "customer first," written down at founding, should not; he also stresses genuinely enjoying each other's company as a practical requirement, not a nicety.
Professor G MarketsSpaceX IPO Takes Off — And Elon Is Now A Trillionaire
  • This post includes paid content that is not available publicly. See the original source.
Technology and FriendsFabio Padua on Using AI to Increase Productivity [EPISODE 907]
  • One prompt built and deployed a conference sessions site. Padua, who has been at Microsoft for four years, gave the new GitHub Copilot app a JSON file of Build session data, and it created a repo, built the app and set up deployment to Azure. He puts the time at about five minutes at one point and "10 minutes tops" at another. The app ran a team of about 15 agents under a "director". His only manual step was copying the Azure static web app token into the repo's GitHub Actions secrets.
  • An internal agent tool matched conference sessions to a partner. Padua says Scout, an internal Microsoft tool built on the open-source OpenClaw, ran parallel agents that read his site and researched the partner Solo Network. When Playwright failed, they fell back to simulated mouse and keyboard input. They picked 16 best-fit sessions, built a table with links and levels, and drafted an email offering a 30-minute call. He has done this for three partners, in Portuguese where he remembered to ask.
  • Agents act as you, so limit what they may do. Padua advises running OpenClaw in a virtual machine you can destroy and letting it only draft, never send or auto-reply to email, citing stories of agents deleting emails or a whole operating system. He had Copilot write a PowerShell deploy script for him to review rather than letting it deploy through the Azure MCP server tied to his credentials, to avoid unwanted resources and costs.
  • Copilot digs answers out of dense internal documentation. Padua uses Microsoft 365 Copilot to summarize meetings he missed and to draft LinkedIn posts. Searching the documentation this way, he found why a partner lacked the Anthropic model quota it expected in Foundry: he says those models work only under an EA contract, and the customer was on CSP. He also tries competitors' tools, such as OpenAI's DALL-E, Anthropic and Perplexity, because customers ask his opinion of them.
  • AI amplifies technical knowledge rather than replacing it. Padua argues that results depend on the user knowing what they want to do, and that AI then delivers "the best of the people can do with a prompt". Giard adds that the agents narrate their failures and change approach, as when Playwright failed, which he says is what a person would do, only faster.
Silver AllianceSilver's Weekly Snapshot for June 13, 2026
  • No spoken content. The 50-second short has no captions, and the whisper transcript of its audio is empty; its subject is in its title alone: "Silver's Weekly Snapshot for June 13, 2026".
GeoHussarThe Overton Window #LearnOnTikTok #DidYouKnow #policy #politics #Overton
  • The Overton window frames how radical ideas become mainstream policy. He credits the concept to Joseph Overton, a VP at a Michigan free-market think tank whose ideas were only published after his death by a colleague; it describes the sliding range of what's politically acceptable, from "unthinkable" to enacted law.
  • He cites abolition and public education as past shifts, and today's immigration and identity debates as ongoing ones. Slavery's abolition and universal public schooling were once branded radical before becoming policy; he points to democratic socialists winning office and the push for mass deportations and ending birthright citizenship as evidence the window keeps moving on both the left and right.
  • He argues most Overton shifts are reversible unless locked into the Constitution. He notes women's suffrage and the freeing of slaves stuck because they were constitutionally codified, while other shifts, including growing distrust of the FBI, CIA and NSA, could still swing back toward the fringe.
Mohamed El-erianThe Weekly Look at the Global Economy and Markets
  • SpaceX's record $75 billion IPO at a $1.8 trillion valuation overshadowed the week's macro news, instantly making it the seventh most valuable US company. The offering, nearly three times the previous largest IPO, made Elon Musk a trillionaire and minted roughly 4,400 millionaires among current and former employees, despite the company generating no profits and carrying significant key-person risk.
  • Hot headline inflation prints contrasted with cooler core readings, yet the ECB hiked rates anyway — its first increase since 2023. US headline PPI came in hot at 6.5% for May while core cooled to 4.9%, and CPI posted its first 4% handle (4.2%) in three years even as core eased to 2.8%; he notes the pass-through to core has consistently undershot forecasts.
  • The week ahead brings a wave of central bank decisions, led by an unusual Fed meeting where new Chair Warsh runs his first session with predecessor Powell still on the committee. Markets have abandoned hopes for 2026 rate cuts and are now pricing a possible hike by year-end, with the Bank of England, Swiss National Bank, Bank of Japan and Reserve Bank of Australia also deciding this week.
Professor G MarketsREPLAY: SpaceX IPO Live Reactions
  • This post includes paid content that is not available publicly. See the original source.
All Things FinancialTungsten Hexafluoride (WF6)
  • WF6 is a tiny line item that gates output worth orders of magnitude more, and it has no drop-in alternative. It is the gas that deposits metallic tungsten to form a chip's contacts, vias, and the word lines stacked through 3D NAND — nicknamed "chip blood." It requires 5N–6N purity, qualifying a new source takes 12–18 months, and there is no substitute chemistry at scale. It is consumed on essentially every advanced wafer and is heaviest in 3D NAND and HBM, with each added memory layer meaning more tungsten per wafer — precisely as roughly 70% of 2026 memory output routes to data centres.
  • The chokepoint sits upstream of the gas makers, so switching supplier does not escape it. China holds about 80% of global tungsten and supplied close to 100% of Japan's powder, and powder is 60–70% of WF6's production cost. China added tungsten to export controls in February 2025 and extended them to high-purity powder under the January 2026 dual-use catalogue; shipments to Japan fell to roughly zero from February 2026, with tungsten powder up ~325% year-on-year and the APT benchmark up 557% since February 2025. Every listed producer — Kanto Denka, Central Glass, Korea's SK Specialty and Foosung, even China's own PERIC — depends on the same upstream powder.
  • What makes this different from an ordinary shortage is that it destroys the midstream rather than rationing it. Because most of WF6's cost is the now-unobtainable powder, the Japanese gas makers exit rather than ration — converting a shock into a permanent supply-base migration. Kanto Denka and Central Glass burned roughly five months of inventory and halt production around 1 July. Exposure downstream is uneven: Samsung is most exposed on heaviest reliance, SK Hynix is cushioned by sister company SK Specialty, DB HiTek and Magnachip have been notified of 70–90% price hikes, and TSMC is racing the 12–18 month qualification of non-Japanese alternatives.
All Things FinancialIndium Phosphide & Tungsten Hexafluoride
  • The familiar AI supply chain describes only the compute, and the two missing pieces are both Chinese-gated. ASML to TSMC to Nvidia to the data centre delivers silicon, but an AI supercomputer is thousands of GPUs acting as one — which requires an interconnect to wire them together and memory to feed them. Neither comes from that chain. Indium phosphide supplies the interconnect and tungsten hexafluoride the memory, and both trace back to materials China controls.
  • Neither can be substituted for reasons of physics rather than commerce. Silicon is an indirect-bandgap semiconductor and physically cannot emit laser light efficiently; InP is direct-bandgap and is the only material making high-speed optical lasers at scale — even silicon photonics still needs an InP laser bonded onto it. WF6 requires 5N–6N purity on a 12–18 month requalification cycle. And demand per GPU is rising structurally: as bandwidth climbs through NVLink generations from 800G to 1.6T, copper fails at ever shorter distances, pushing optics closer to the chip, while cluster topologies add optical links faster than they add GPUs.
  • The decisive finding is convergence — two unrelated chokepoints terminating at the same endpoint. Different minerals, different midstream firms, different licensing gates, but China can squeeze the buildout from two independent directions at once. The severity grid scores indium/InP at ~70% dependency, +250% price shock and a substitution lag running to ~2029, against tungsten/WF6 at ~100% dependency, +325–557% and 12–18 months — with no soft cell anywhere in the matrix and tungsten critical on both dependency and price. On concentration, AXT (US-listed but with fabs in China) and Sumitomo hold roughly 80% of InP substrate with JX Advanced Metals near 10%, but AXT is gated at China's border and Sumitomo consumes much of its output internally, so the merchant market is tighter than the shares imply — Lumentum is already sold out through 2028 with wafers up 250%.
All Things FinancialIndium Phosphide and the AI Data-Center Supply Chain
  • The constraint binds at the interconnect layer, not the compute layer — which is where the famous chip chain stops describing the problem. ASML prints, TSMC fabricates, Nvidia designs, data centres cluster. But a large training run is thousands to tens of thousands of GPUs acting as one machine, and you can have every GPU the silicon chain can produce: if you cannot optically wire them together, you cannot form the machine. The physics is unavoidable — silicon is indirect-bandgap so light emission is wildly inefficient, InP is direct-bandgap, and the one partial alternative (GaAs VCSELs over multimode fibre) covers only short-reach links. Even silicon photonics needs an InP laser bonded onto it.
  • Concentration stacks three deep, and the export permit is what converts latent leverage into disruption. Refining is ~70% China — latent leverage. Substrate is the physical bottleneck, with roughly three firms holding ~90%: AXT is US-listed but fabs inside China and gated at its border, Sumitomo holds ~30% but consumes much of it internally, JX Advanced Metals ~10% — so the merchant market is far tighter than headline shares suggest. The active instrument is China's per-order export-permit regime, added 4 February 2025, requiring a government permit for every overseas shipment. Permits have run 60+ business days and AXT only began receiving them again in March 2026. It is metering rather than embargo — but metering is enough.
  • The cascade runs in order, and the gap is structural for the rest of the decade. Permits slow, AXT shipments are gated and backlog builds past $100M in Q1 2026 — so revenue recognition becomes a function of Beijing's regulatory clock rather than customer demand. Transceiver and laser makers then hit substrate scarcity, with Lumentum sold out through 2028 and average six-inch InP wafers up ~250% to about $5,000 since February 2025. The interconnect layer caps GPU clustering, throttling the AI-specific part of the buildout with a non-compute input. Then forward-buying and stockpiling ratchet prices that persist even if permit volume later loosens — and the first large Western refined-indium addition, Korea Zinc's Tennessee complex, is not expected before ~2029. The asymmetry is the point: a single-digit-kiloton market sits beneath a multi-hundred-billion-dollar buildout.
All Things FinancialInP & Tungsten: effective supply chain leadership starts with mastering the fundamentals 6-12-2026
  • He opens with an unusually direct admission about the state of American supply-chain knowledge. Having imposed tariffs on the premise that the US held all the cards and the world would rearrange around domestic manufacturing, his verdict is that "we were basically deaf, dumb and blind men when it came to the supply chain." The evidence he points to is that US officials have visited China repeatedly to try to resolve the InP export controls — and that Japan asked Washington to intercede on its behalf, which he reads as a statement about who actually holds leverage.
  • He explains the physics plainly and lands on the same conclusion the paper reaches. Direct versus indirect bandgap: in a direct-bandgap material an excited electron drops across the gap and releases the energy cleanly as light, while in silicon that same drop needs a lattice vibration to conserve momentum, making emission wildly inefficient. As bandwidth per GPU climbs from 800G toward 1.6T, the distance at which copper works keeps shrinking, pushing optics from the building edge into the rack and onto the package itself. Every one of those links needs an InP laser, so InP gates the wiring-together.
  • His comparison of the two chokepoints names the trade-off precisely. Tungsten and WF6 are worse on price — up somewhere between 325% and 557% — but the substitution path runs 12 to 18 months. Indium and InP are up around 250% but are not meaningfully addressed until roughly 2029. "One's worse on price, the other one's worse on delivery." His conclusion is a policy one: the country needs an actual industrial policy that decides what it wants to build and then traces where every input comes from, and investors need to get far better at mapping chokepoints — who makes what, and how they make it.
Professor G MarketsThe Week: Iran, IPO Mania, and the New American Dream
  • This post includes paid content that is not available publicly. See the original source.
Polis PanditJapan Stops Lending to the World
  • Japan's weakening demand for its own government bonds signals the end of its role as the world's price-insensitive buyer of foreign debt. A June 10th 30-year JGB auction drew the weakest demand since June 2025, with the bid-to-cover ratio falling to 2.94 from a 12-month average of 3.4, as domestic yields near 2.5-2.7% finally compete with returns abroad.
  • As Japanese yields rise, Japan needs to buy less foreign debt, feeding what the author calls the "great repricing" of global bond yields. Japan holds about $1.2 trillion in U.S. Treasuries, and the life insurers and pension funds that have consistently bought foreign debt are starting to recalibrate toward higher yields available at home.
  • A Bank of Japan rate hike, needed to fight inflation, threatens to unwind the global carry trade that lets Western investors borrow cheap yen to buy assets like U.S. equities. With Japan's debt-to-GDP near 230% and BOJ JGB holdings already down from 91% of GDP in mid-2024 to about 80% in January 2026, the piece frames the taper decision, not the rate move, as the key thing to watch.
Stock TokBull Market Resumes & Space X Thoughts
  • This post includes paid content that is not available publicly. See the original source.
Y CombinatorSelf-Play for LLMs, AI for Biology, Formal Verification, and More | YC Paper Club
synopsis

At YC's Paper Club, five researchers and builders each apply the field's core recent pattern — improving through self-generated data and raw scale rather than imitating existing human solutions — to a new domain: protein biology, math proofs, voice AI, formal software verification, and the practice of running an AI-native engineering team. The host frames his own interest as whether "intelligence per sample" can ever exceed what human-imitation training allows.

AI for biology. A Stanford PhD student presents ESM Cambrian, a Biohub protein language model trained only to predict masked amino acids, with no structural data. Unlike its predecessor, which plateaued with scale, this model shows the same clean log-linear improvement with compute that language models show — attributed mainly to scaling training sequences from 50 million to 2.8 billion, pulled from environmental DNA. Tested against AlphaFold 3, which relies on hand-built sequence alignments, the sequence-only model lands within a few points on general structure prediction and edges ahead on antibody design, where alignment data is scarce. Interpretability analysis finds the model organized its internal representations into an unsupervised hierarchy — amino acids, structural motifs, whole protein domains — which the presenter reads as evidence the "bitter lesson" of scale beating hand-engineered features is starting to hold in biology, not just language.

Self-play for language models. A second presenter describes an AlphaZero-style setup where a "conjecturer" model generates problems and a "solver" attempts them, with the conjecturer rewarded for problems that are hard but solvable. Naive versions collapse: the easiest way to look "hard" is to write artificially convoluted, messy problems rather than genuinely difficult ones. His fix grounds new problems in ones the solver already failed on and adds a third "guide" role scoring whether a generated problem is actually related and reasonable. On 3,000 formal math problems in Lean, this lets a 7-billion-parameter model, given eight times more self-play compute, match the solve rate of a roughly 100-times-larger baseline model, though he stresses the method is far from solving everything.

Streaming retrieval for voice AI. A Giga researcher presents work on cutting latency in voice agents that use retrieval-augmented generation: waiting for a spoken question to finish before retrieving adds unacceptable delay in natural conversation. The paper explores retrieving mid-question, either at fixed intervals or by training a model to judge when enough of the question has arrived to act safely. He frames the real challenge less as this specific method and more as deciding, from a live stream of speech, the earliest safe moment to retrieve.

Formal verification. A Caltech PhD student argues Lean, an interactive theorem-proving language, is entering a breakthrough period: DeepMind and OpenAI have both used related methods to solve International Mathematical Olympiad gold-medal problems and decades-old open conjectures, aided by growing formalized-math libraries and LLMs that can search proof steps. He extends this to software, describing an emerging shift from "vibe coding" to "verifiable coding," and cites his own project reimplementing neural-network operations natively in Lean — including a formal proof that flash attention is mathematically equivalent to standard attention — as an early example of AI-written code carrying real guarantees rather than just passing tests.

Running an AI-native engineering team. The final speaker, a startup CEO known for aggressive token spending, argues coding with agents behaves less like chess — a single linear process — and more like a real-time strategy game, where the goal is maximizing parallel throughput across many imperfect simultaneous actions rather than perfecting any one. His team runs many autonomous coding agents at once under a human "orchestrator," instructs each to push forward as far as possible before asking for help even at the cost of wasted effort, and feeds outcomes back into a shared knowledge base rather than treating code itself as the source of truth. He tracks productivity the way an RTS player tracks actions-per-minute — tool calls per agent per hour — and reports the approach grew pull requests shipped per engineer per month 3.5x, then another 60% once the rest of the team adopted it.

  • Protein language models are starting to show the same LLM-style scaling laws. A presenter says a new protein-model family from Biohub, ESM Cambrian, keeps improving log-linearly with more training compute and sequence data — unlike its predecessor, which plateaued — largely because the team scaled training data from 50 million to 2.8 billion sequences pulled from environmental DNA sequencing.
  • Naive AI self-play collapses into generating deliberately convoluted, useless problems. A Stanford PhD student found that rewarding a "conjecturer" model for stumping a "solver" model just produces artificially messy math problems; his fix grounds new problems in ones the solver already failed on and adds a third model to judge relevance, letting a 7-billion-parameter model match a 670-billion-parameter baseline's solve rate after eight times more self-play compute.
  • Lean formal verification marks a shift from "vibe coding" to "verifiable coding." A Caltech researcher says frontier labs have used the Lean proof language to solve IMO gold-medal problems and decades-old Erdős conjectures, and describes his own project formalizing neural-network operations — including proving flash attention mathematically equivalent to standard attention — as evidence AI-written code can eventually carry mathematical guarantees, not just pass tests.
  • Treating agentic coding like a real-time strategy game tripled shipped pull requests. A startup CEO known for aggressive token spending says running many parallel Claude Code "worker" agents under one orchestrator, instructing them to push forward without stopping for feedback, and feeding a shared knowledge base after every task grew pull requests per engineer per month 3.5x, then another 60% once the whole team adopted the workflow.
Dr. Jon KrohnTen Years of the Super Data Science Podcast (Ep. 1000 with Jon, Kirill and Special Guests)
synopsis

Episode 1000 was recorded live, with listeners able to join, by host Jon Krohn and the show's founder Kirill Eremenko. Its most lasting argument is Eremenko's: AI research moves fast but adoption moves slowly, so people worried about keeping up need only stay ahead of adoption. Around that, the hosts and callers trade views on what AI should fix, how companies should choose between building and buying, and how newcomers can get hired.

Origins. Eremenko says he started the show in September 2016 after seeing interview podcasts like Tim Ferriss's and finding nothing similar for data science. He hosted through episode 431; the host took over from episode 432 on January 1st, 2021. Eremenko says he invited the host on as a guest for Deep Learning Illustrated in April 2020 and later offered him the job on intuition; they met in person only last year.

What $10 billion should fix. Jepson Taylor, the show's most frequent guest, asks what each would fix in two months for the bottom 90%. The host wants an agent standing between people, especially the most easily exploited, and the feeds, scams and attention-seeking products that leave them overwhelmed, steering them to activities that make them happy; Taylor notes the Black Mirror risk of an AI scripting your marriage. Eremenko wants AI-run, scalable charities with admin costs cut from what he thinks is about 40% to 5%. Taylor's own goal is to close what an engineer told him is the gap between the top 10% and bottom 90% of AI developers.

Lessons from hosting. Eremenko's hindsight is to have launched on YouTube from day one; the show only went video-first 10 months before recording, and the host says YouTube subscribers rose from 20,000 to over 250,000 since. Eremenko says he started shy and learned to start before feeling ready. The host says Eremenko's advice to be conversational, and to stop visibly taking notes, changed his hosting.

Build versus buy. For a corporate listener weighing vendors' bolted-on agents against in-house builds, the host relays a 2x2 from episode 932's Unframe co-founder: skip what is costly and non-differentiating, build what is differentiating but slow, buy what is fast and undifferentiated, and partner where it is fast and differentiating; he names his own consulting firm among such partners.

Education and the speed of adoption. A former Dutch professor of human-AI collaboration asks how schools can teach safe AI use. The host cites episode 983's Boston principal (children under about 10 should not use AI directly), Kyunghyun Cho's Gemini-based NYU course, and episode 994's view that weak new-grad hiring reflects post-pandemic overhiring as well as AI. Eremenko says time will fix hallucinations, which he estimates are down about 10-fold in two years, so startups fighting that tide fail. The professor replies that universities banned AI within weeks and are still recovering; Eremenko frames this as research moving like a bullet train and adoption like a traffic jam.

Breaking in. For newcomers the host recommends a GitHub of self-built projects and in-person networking over online applications, which AI-tailored résumés have flooded. He suggests readers wanting a simpler version of his book ask an LLM to rewrite it for their background.

  • Beat the speed of adoption, not the speed of research. Responding to a former Dutch professor of human-AI collaboration about teaching safe AI use, Kirill Eremenko, the show's founder, argues research moves like a bullet train while adoption in universities, enterprises and government moves like a highway traffic jam, slowed by legacy systems and change management. He says people anxious about AI only need to stay ahead of adoption, and that startups should avoid problems models will soon solve, citing hallucinations he estimates are down about 10-fold in two years and AI-text detectors as fighting the tide.
  • The host would fund agents that shield people from manipulative feeds. Asked by Jepson Taylor what they would fix with $10 billion in two months, the host proposes an agent between vulnerable people and the feeds, scams and attention-seeking products they consume, steering them toward what makes them happy; Eremenko proposes AI-run charities that cut admin overhead from what he thinks is about 40% to about 5%. Taylor's own answer is closing what an engineer told him is the gap between the top 10% and bottom 90% of AI developers.
  • Build what differentiates you and is slow to build; buy the rest. Answering a corporate listener on the "SaaS apocalypse", the host relays a 2x2 from episode 932's guest from Unframe: avoid projects that are costly and non-differentiating, build in-house what is differentiating but slow, buy what is quick and non-differentiating, and partner (he names Unframe and his own firm) where it is both quick and differentiating.
  • The show's big growth lever was video, adopted far too late. Eremenko, who hosted from September 2016 to episode 431, says his one piece of hindsight is that he should have put episodes on YouTube from the start; the host says the show went video-first only 10 months before recording and grew from 20,000 to over 250,000 YouTube subscribers since. The host's own lesson, from Eremenko's feedback, was to be conversational and stop taking notes on air.
  • In-person networking beats clicking "apply". The host argues weak new-grad hiring reflects degrees losing their "golden ticket" status and post-pandemic overhiring as much as AI, citing episode 994. His tips for entrants are a GitHub of projects actually done yourself and meeting people in person, because AI-tailored résumés let applicants send thousands of applications and flood the traditional pipeline; he also cites episode 977's NYU machine-learning course, taught by Kyunghyun Cho, that required students to use Gemini.
Professor G MarketsThe IPO Frenzy Has Begun — with Howard Marks
  • This post includes paid content that is not available publicly. See the original source.
Scott HanselmanCloud Commitments Without the Lock-In with Archera's Aran Khanna
synopsis

Aran Khanna, co-founder and CEO of Archera, ends arguing that pay-as-you-go is a promotional price for prototyping, and that serious cloud users should commit, crawling into larger and longer commitments as projects mature, with Archera's insurance taking the downside if usage falls away.

Why commitments exist. Hanselman, a pay-as-you-go user for 17 or 18 years, says he leaves money on the table but fears lock-in. Khanna, who spent almost a decade at Azure and AWS, says data centres take heavy capital, lenders underwrite guaranteed revenue, and providers therefore discount by more than 80% for 3-year commitments. With GPU shortages, he says, commitments in 2026 are often the price of access at all.

The product. Insured commitments pay back unused months, the right to break a lease. Archera sells mostly through the AWS, Azure and Google marketplaces, and Khanna says provider sales teams like it because it gets customers to commit larger amounts for longer.

How it avoids being gamed. Asked about moral hazard, Khanna cites a year of usage history, priors from a petabyte-plus of data across thousands of customers, a diversified book built by quants, and machine-learning models over billing metadata. About 40% of customers buy insurance.

What broke. Commitments grew from reserved instances into a tool for rationing GPUs, deterring multi-cloud and pushing modernisation, and very large bills can no longer be trusted. Capacity is uneven: new Nvidia Grace Blackwell machines are scarce, while over half of new AWS CPUs for two years were Arm-based Graviton.

Who it is for. Waste is partly engineering, usage optimisation, and partly finance, rate optimisation, which is Archera's ground. Savings become meaningful at $100,000–200,000 a year.

  • Archera sells insurance that lets customers break cloud commitments. Khanna, co-founder and CEO, describes "insured cloud commitments": commit for 3 years and, if the last 24 months go unused, Archera pays back the difference; he says no one else offers it, and customers can cancel the insurance once confident. His analogy is buying the right to break a 3-year apartment lease after the first year.
  • Commitments exist because clouds finance capex against guaranteed revenue. Like a builder whose lender underwrites leases rather than Airbnb income, providers borrow to build data centres (CoreWeave is his extreme example), so discounts can exceed 80% for moving from per-second use to a 3-year commitment. He says that in 2026 a commitment is often required just to get GPUs; Hanselman calls on-demand "the convenience store price of compute", and Khanna calls it the promotional price, where you prototype.
  • Commitments became a hammer applied to every cloud problem. Reserved instances made sense in the early 2010s, he says, but from the 2017 SageMaker launch, which he worked on at AWS, they were used to ration scarce Nvidia capacity, then to deter multi-cloud and push modernisation, leaving "a spaghetti mess". At $80–90 million a year with one provider, he says, bills contain errors and cannot be treated as a source of truth.
  • Underwriting relies on spend history, peer priors and diversification. Archera wants at least a year of real usage data, draws priors from over a petabyte of history across thousands of customers (offering less on Azure VMware Service, which tends to migrate to AKS within a year), and spreads its book across instance types, GPUs and customers. Only about 40% of its customers buy insurance; the rest use free billing and commitment tools.
  • Small teams qualify, but savings matter most at larger spend. Khanna puts the meaningful threshold at $100,000–200,000 a year of cloud spend, with savings that could fund a headcount from $500,000-plus, though two-person startups on credits use it and a quote takes 5 minutes. He separates his rate optimisation, a finance question, from usage optimisation, an engineering one.
Professor G MarketsTrump Flip-Flops on Iran as Markets Brace for Impact
  • This post includes paid content that is not available publicly. See the original source.
GeoHussarThe Persian Gulf countries and dark oil transfers #oil #geopolitics #iranwar #straitofhormuz
  • Saudi Arabia, the UAE, Qatar and Kuwait are now using the same dark-fleet tricks as Russia, Iran and Venezuela to move oil. He describes tankers switching off transponders to slip through the Strait of Hormuz undetected by Iran, or turning them off just outside the Strait to do ship-to-ship transfers before the receiving vessel sells the cargo.
  • He credits this evasion, alongside shifting trade flows, with helping keep oil under $200 a barrel. He pairs it with China and India cutting oil imports while the US, Canada, Venezuela, Mexico and Norway raise exports, though he calls the dark transfers slower and costlier than normal shipping.
  • He predicts an "economic rollercoaster" within four to five months if the Strait of Hormuz stays disrupted. He argues the longer these workarounds continue, the less leverage Iran retains over global oil markets through control of the Strait.
Professor G MarketsThe New Rules of Power — with Anne Applebaum and Fiona Hill
  • This post includes paid content that is not available publicly. See the original source.
Loss DogAI Token Tax: Offset Labor Loss or Not #wearelossdog #shorts #ai #finance
  • AI firms are floating token or energy taxes to preempt labor-displacement backlash. The hosts characterize this as AI companies signaling they'll need far fewer workers while offering to accept a token-usage or energy-usage tax as a concession.
  • One host doubts AI will displace as much labor as feared, calling the tax question moot. The other pushes to table it anyway, arguing taxpayers are already subsidizing AI companies' heavy resource use since those firms pay little tax while building trillion-dollar market caps.
  • They propose taxing firms that cut jobs via AI to offset lost payroll-tax revenue. The argument: if a company replaces a 100-person support desk with AI, a modest tax on that displacement would offset states' biggest revenue source, correcting a system where AI firms get all the upside and consumers/taxpayers get none.
Y CombinatorHow Meesho Became India’s Biggest Shopping App
synopsis

Vidit Aatrey, co-founder and CEO of Meesho, traces the company through three distinct businesses before it became India's most-downloaded shopping app, and ends by arguing that voice interfaces will let Meesho reach the share of India's population still excluded from e-commerce.

Aatrey and his co-founder started in 2015 struck by a stark gap: e-commerce felt "done" in Bangalore, yet neither of their small-town families bought anything online. Their first product, a hyperlocal fashion-listing app, shut down after three months once they finally spoke to consumers, who called it "the worst of both worlds" versus a mall or full e-commerce. Their second attempt, Meesho, initially aimed to help small shops sell via WhatsApp, an idea discovered after the founders simply sat and watched inside shops rather than interviewing owners. That version reached YC but couldn't monetize, since small Indian businesses wouldn't pay for software. Digging into which users were actually addicted to the product revealed a different profile entirely: online-native drop-shippers, largely homemakers, running zero-inventory resale businesses through WhatsApp groups, whose real bottleneck was supplier access. Pivoting to serve them as a supplier, under a relaunched Meesho Supply, produced sustained month-over-month doubling with zero marketing spend, which Aatrey says is what actually taught him what product-market fit means.

The company's hardest decision came in 2020: falling data costs and pandemic-driven online adoption erased WhatsApp's advantage, so Meesho chose to cannibalize its own network of ten million reseller-run WhatsApp groups by launching a direct consumer app, a bet competitors running similar WhatsApp models did not make and have since shut down. The app hit #1 on India's Play Store the day after its July 2021 launch and has held that spot every day since, reaching 100 million monthly users within five months.

Aatrey closes on Meesho's next bet: a voice-only shopping agent, Wani, designed to eliminate reading, typing and clicking for rural users who don't understand what "add to cart" means and fear accidental charges — a bid to move Indian online shopping from roughly 250 million users toward the country's full billion.

  • Meesho's first product failed within three months because they never interviewed consumers. Vidit Aatrey, Meesho's co-founder and CEO, says their 2015 hyperlocal fashion-listing app collapsed once customers said it was "the worst of both worlds" — the limited selection of a local shop without the touch-and-feel of a mall — a mistake he calls "the most notorious mistake you can make."
  • The real business emerged from noticing shops secretly ran WhatsApp storefronts. Sitting silently inside small shops rather than interviewing owners, the founders found sellers already used WhatsApp to message customers about new inventory, which led to a WhatsApp-commerce tool, and later to the discovery that the platform's true power users were online-only drop-shippers, mostly homemakers, needing supplier access rather than tooling.
  • Meesho abandoned its profitable WhatsApp network in 2021 to launch an app. Aatrey says the shift from expensive mobile data to near-zero-cost data during COVID erased WhatsApp's core advantage, so the company knowingly risked alienating ten million reseller-run WhatsApp groups; the new app hit #1 on India's Android Play Store the day after its July 2021 launch and has stayed there every day since, growing to 100 million monthly users within five months.
  • Meesho is building a voice-only agent for users overwhelmed by apps. Called Wani, it aims to remove reading, typing and clicking entirely — consumers speak preferences, hear responses, and give an address and OTP by voice — because Aatrey says rural users often don't understand what "add to cart" or a star rating means and fear that any button might deduct money.