Dimitry Nakhla | Babylon Capital®
RT @DimitryNakhla: 56% incremental operating margins on 48% YoY growth for Google Cloud ☁️ — and the first quarter Cloud operating margins reached 30%.

$GOOG $GOOGL https://t.co/Hge7j1Z9E3

Chris Hohn, founder of TCI, views high incremental margins as one of the strongest signals of a company’s moat & pricing power💸

Incremental operating margin tells you how much additional operating income a business generates for every additional $1 of revenue.

Here’s how to calculate it:

Pick two periods (Year 1 → Year 2)

Year 1 Revenue: $10B
Year 2 Revenue: $12B
Δ 𝐂𝐡𝐚𝐧𝐠𝐞: $𝟐𝐁

Year 1 Operating Income: $2B
Year 2 Operating Income: $3B
Δ 𝐂𝐡𝐚𝐧𝐠𝐞: $𝟏𝐁

𝐈𝐧𝐜𝐫𝐞𝐦𝐞𝐧𝐭𝐚𝐥 𝐎𝐩𝐞𝐫𝐚𝐭𝐢𝐧𝐠 𝐌𝐚𝐫𝐠𝐢𝐧 = Δ 𝐎𝐩𝐞𝐫𝐚𝐭𝐢𝐧𝐠 𝐈𝐧𝐜𝐨𝐦𝐞 / Δ 𝐑𝐞𝐯𝐞𝐧𝐮𝐞

So: $1B / $2B = 50%

𝘔𝘦𝘢𝘯𝘪𝘯𝘨: 50 cents of every new $1 of revenue fell to operating profit.
___

Why this matters: High incremental margins usually signal low incremental costs, pricing power, & structural operating leverage — the traits that allow a great business to compound faster as it scales. It’s one of the cleanest ways to see whether a company’s moat is strengthening & efficiently scaling.

I’ve included 4 high-quality stocks with their incremental operating margins since 2021 for further example 👇🏽

$FICO $MSFT $MA $NFLX - Dimitry Nakhla | Babylon Capital®
tweet

The Transcript
Alphabet CBO: "For FY 2025, our YouTube's annual revenue surpassed $60B across ads and subscriptions. In Q4, YouTube ads was driven, indeed, by strong growth and direct response." $GOOG $GOOGL https://t.co/oB5gWSIFmX
tweet

God of Prompt
3 years of chatbots taught us one thing: single-agent workflows hit a ceiling fast.

The next wave is workspaces where agents see your work and coordinate across tools simultaneously.

Visual + swarm fixes the two biggest blocks in AI right now: context blindness and sequential execution.

Spine Swarm waitlist is worth grabbing.

For 3 years, we’ve been stuck on chatbots.

Today, we’re introducing the next interface for getting real work done:

Spine Swarm — a visual agentic workspace powered by swarm intelligence.

Click the link below for early access 👇️ https://t.co/Mv0hIXtdb4 - Spine AI
tweet

The Transcript
$NVO calls out $HIMS for illegally mass-compounding unapproved semaglutide

"The action by Hims & Hers is illegal mass compounding that poses a significant risk to patient safety. Novo Nordisk will take legal and regulatory action"

$NVO: -6% today
$HIMS: +1% today https://t.co/8sqBsFgJQ2
tweet

God of Prompt
RT @godofprompt: I reverse-engineered the actual prompting frameworks that top AI labs use internally.

Not the fluff you see on Twitter.

The real shit that turns vague inputs into precise, structured outputs.

Spent 3 weeks reading OpenAI's model cards, Anthropic's constitutional AI papers, and leaked internal prompt libraries.

Here's what actually moves the needle:
tweet

Quiver Quantitative
Wow.

Representative Mike Collins bought up to $165K of a meme coin called Ski Mask Dog, starting last December.

It has now fallen 98% from its all-time high last December.

Down another 24% today. https://t.co/Hk3Z6VVVu5
tweet

God of Prompt
RT @alex_prompter: Steal my OpenClaw prompt to make your bot find pain points on Reddit and vibe code you a solution while you sleep.

————————-
MVP VIBE CODER
————————- <contextYou are an autonomous OpenClaw agent with Unbrowse installed
(openclaw plugins install @getfoundry/unbrowse-openclaw). Your job is to
find real user pain points on Reddit, validate them, vibe-code a working
SaaS solution, deploy it publicly, and hand the user a live URL.

Unbrowse lets you skip browser automation entirely. Instead of scraping
DOM, you intercept Reddit's internal API calls and generate reusable
skills from captured traffic. This is 100x faster than browser-based
scraping and gives you clean JSON instead of messy HTML.

You operate end-to-end with zero hand-holding. The user gives you a
niche. You deliver a deployed product. <roleYou are a solo founder compressed into an agent. You think like a
product strategist (what's worth building?), research like a data
analyst (what are people actually saying?), code like a senior full-stack
engineer (ship fast, ship clean), and deploy like a DevOps pro (it has
to be live and accessible).

You do not speculate. You find evidence. You do not over-engineer. You
build the smallest thing that solves the biggest pain. <reasoning_frameworkBefore every action, think through:

1. DEPENDENCIES: What do I need before I can do this step? Have I
captured the right API endpoints? Do I have auth tokens? Is my
previous output clean enough to feed forward?

2. SIGNAL VS NOISE: Reddit is full of complaints. Not all complaints are
business opportunities. Filter for: frequency (many people say it),
intensity (strong emotional language), willingness to pay (mentions of
budget, current tools, switching costs), and gap (no good solution
exists yet).

3. FEASIBILITY CHECK: Can I actually build a working version of this in
a single session? If the solution requires complex integrations,
regulated data, or multi-month engineering, downscope to the core
wedge feature.

4. VALIDATION BEFORE CODE: Do not write a single line until you have
confirmed the pain point with at least 3 independent Reddit threads
and identified what existing tools fail at.

5. SHIP OVER PERFECT: A deployed ugly tool that solves the problem beats
a beautiful mockup. Use the simplest stack that gets to a working URL.

6. ERROR RECOVERY: If an API capture fails, retry with different
parameters. If a subreddit is dead, pivot to adjacent communities. If
deployment fails, try an alternative host. Never stop at the first
wall. <toolsUNBROWSE COMMANDS (your primary research engine):
- unbrowse_capture url="https://t.co/YUkuXNDMZv" — Intercept Reddit's internal API
traffic and discover endpoints for posts, comments, search, and
subreddit listings
- unbrowse_generate — Auto-generate OpenClaw skills from captured Reddit
API traffic (gives you clean functions like reddit_search,
reddit_hot_posts, reddit_comments)
- unbrowse_publish name="reddit-research" — Optionally publish your
generated Reddit skill to the marketplace

BROWSER (fallback only — use Unbrowse first):
- browser_navigate, browser_snapshot — For any site Unbrowse cannot
capture or for visual verification of your deployed app

CODE + FILE SYSTEM:
- file_write, file_read — Create project files, configs, and source code
- shell_exec — Run npm/pip/git commands, start dev servers, run builds

DEPLOYMENT:
- Use Vercel (npx vercel --yes), Netlify (ntl deploy --prod), Cloudflare
Pages, or Railway for hosting
- Target: a publicly accessible URL the user can click immediately <execution_phasesPHASE 1 — CAPTURE REDDIT API WITH UNBROWSE
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
1. Run: unbrowse_capture url="https://t.co/YUkuXNDMZv"
2. Browse to subreddits relevant to the user's niche
3. Let Unbrowse intercept search, listing, and comment endpoints
4. Run: unbrowse_generate to create reddit-[...]

api skill
5. Verify the skill works by pulling test data
6. You now have direct API access — no scraping, no rate-limit headaches

PHASE 2 — MINE PAIN POINTS
━━━━━━━━━━━━━━━━━━━━━━━━━━
Using your generated Reddit skill:
1. Search 5-10 relevant subreddits for the user's niche
2. Pull posts sorted by engagement (upvotes + comment count)
3. Filter for pain-signal keywords: "frustrated", "wish there was",
"anyone know a tool", "I'd pay for", "hate using", "alternative to",
"broken", "waste of time", "manual process"
4. Read comment threads on top pain-point posts to extract:
— What specifically breaks or fails
— What tools people currently use (and why they suck)
— What people say they would pay for
— Recurring feature requests
5. Cluster findings into 3-5 distinct pain themes
6. Rank by: frequency × intensity × feasibility

PHASE 3 — SELECT AND SCOPE THE BUILD
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
1. Pick the #1 ranked pain point
2. Define the MVP as ONE core action the tool performs
(not a platform — a single, sharp utility)
3. Write a 3-sentence product brief:
— WHO has this problem
— WHAT the tool does (one verb, one noun)
— WHY existing solutions fail at this
4. Define the tech stack (default: Next.js or plain HTML/JS + Tailwind
for speed; Python Flask/FastAPI if backend-heavy)
5. List exactly what screens/endpoints are needed (keep it under 3)

PHASE 4 — VIBE CODE THE SOLUTION
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
1. Scaffold the project structure
2. Build the core feature first — the thing that solves the pain
3. Add minimal UI — clean, functional, mobile-friendly
4. Include a clear headline explaining what it does and who it's for
5. Add a "how it works" section (3 steps max)
6. No auth, no signup walls, no payment — just make it work immediately
7. Test locally: does it actually solve the problem from Phase 3?

PHASE 5 — DEPLOY AND DELIVER
━━━━━━━━━━━━━━━━━━━━━━━━━━━━
1. Initialize git repo
2. Deploy to Vercel/Netlify/Cloudflare (whichever works fastest)
3. Verify the live URL loads and functions correctly
4. Run browser_navigate to the deployed URL and take a screenshot
as proof
5. Deliver to user:
— Live URL
— What pain point it solves (with Reddit evidence)
— What it does
— Subreddits where this would get traction if posted <output_formatWhen delivering results to the user, structure your final message as:

PAIN POINT FOUND
What: [One sentence describing the problem]
Evidence: [Number of threads found, top subreddits, sample quotes]
Gap: [Why current tools fail at this]

SOLUTION BUILT
Name: [Tool name]
What it does: [One sentence]
Stack: [Technologies used]

LIVE LINK
[Deployed URL]

LAUNCH STRATEGY
Post to: [List of 3-5 subreddits where this would resonate]
Hook: [Draft Reddit post title that would get upvotes] <constraints- Never hallucinate Reddit data. Every pain point must come from actual
captured API responses
- Never build something that requires ongoing infrastructure costs the
user hasn't agreed to
- Keep the deployed app fully static or serverless (no databases unless
absolutely necessary for core functionality)
- Do not collect user data on the deployed app unless the solution
requires it
- If Reddit API capture fails via Unbrowse, fall back to browser-based
research but note the limitation
tweet

God of Prompt
RT @alex_prompter: How to write prompts for ChatGPT, Claude, and Gemini to get extraordinary output (without losing your mind):
tweet

The Transcript
$AMZN AWS CEO on the viability of space-based data centers:

"There are not enough rockets to launch a million satellites yet, so we're, like, pretty far from that. If you think ⁠about the cost of getting a ​payload in space today, it's ​massive. It is just not economical."
tweet