Video summary

How to Get So Rich as a Dev It Feels Illegal

Main summary

Key takeaways

Business

Core Thesis

“Get so rich as a developer it feels illegal.”

The speaker frames “illegal” outcomes as the result of:

  • Leverage
  • Communication
  • Fast execution

—not superior engineering.

A billing/pay gap story is used to explain how developers can move from being “paid hourly” to earning based on value and outcomes.

1) Leverage: Own (or monetize) what others monetize

Billing / Pay Gap Case Study

  • The speaker discovered his firm billed him out at $1,850/hour per client to three clients.
  • Total revenue attributed to his work:
    • $1,850 × 3 ≈ $5,550/hour
  • His personal pay:
    • < $150/hour
    • (He notes no overtime.)
  • Key conclusion:
    • The code produced the same output, but leverage came from code ownership, solving other people’s problems, and distribution/brand.

Leverage Sources (Explicitly Listed)

(1) The code itself

  • “Write once, run many times” → near-infinite leverage
  • The employer’s model captures the upside because the business owns the code.

(2) Other people’s problems → pricing on value

  • Example: a two-person business spends 15 hours/week manually copying data.
  • Implied payroll cost: ~$60,000/year
  • Automation via scripting/workflow:
    • Suggested timeline: ~3 weeks (potentially faster)
  • Example charge: $15,000 for the automation solution
  • Lesson:
    • Your billing should be tied to value captured, not your hours.
    • If the client saves $60k/year forever, charging $15k is framed as value-based pricing.

(3) Distribution (brand)

  • Same skill, different buyer trust:
    • The firm’s brand charged $1,850/hour because the client trusted the name more than the individual engineer.
  • Personal content acts as distribution:
    • posts, videos, case studies, testimonials → “24/7 salespeople”

Actionable Recommendation

“Get to the other side of that receipt” by ensuring control over:

  • the asset (code/automation)
  • the buyer outcome/value narrative
  • your distribution/credibility channel

2) Communication: Translate technical work into business money

Case Study: The partner who wasn’t the top engineer

The speaker argues the highest paid person wasn’t the best engineer—rather, a partner who translated engineering into the “language CEOs understand: money.”

The difference is framed as:

  • $150/hour (technical description)
  • $1,850/hour (business value + outcome framing)

Framework: “Lead with number, sell where they land, eliminate unanswered questions”

Move 1: Lead with the number instead of your stack

Talk first about:

  • cost of inaction
  • hours burned
  • money leakage
  • customers walking away

If you don’t know the numbers yet, the speaker implies you’re “not ready to pitch.”

Move 2: Sell where they land (outcome over implementation)

Analogy: passengers don’t care about the plane engine—they care about safe landing.

Similarly, clients don’t care about architecture; they care about results.

Move 3: Kill questions before they ask

Unanswered concerns become discount pressure later:

  • “Will this work?”
  • timeline (“How long will it take?”)
  • friction (“Will it disrupt workflow?”)
  • personal time impact

Responses should include:

  • proof
  • specific timelines (ideally a date range)
  • risk-reduction offers, such as:
    • “You give me one login / or CTO / or the tech owner, I’ll handle everything else.”

Business Tactic

De-risk the buyer until “price stops being the conversation.”

Positioning Note

The speaker addresses objections like:

  • “I’m not a sales guy”
    • Communication is treated as a system, not a personality trait.
  • The “CEO language” can be learned with practice (suggesting ~6 months).

3) Bias for Action: Speed as a money multiplier

Execution Playbook (Principles and Examples)

The speaker references Amazon’s “Bias for Action” leadership principle.

They argue the real risk in disruption isn’t moving too fast—it’s standing still while others learn the new game.

Concrete Example: ChatGPT Launch

  • On launch day, developers panicked (“we’re cooked”).
  • The speaker:
    • submitted two weeks’ notice
    • started a consultancy
    • began with $258 in the bank
  • Later result (as reported by the speaker):
    • over $100k+/month within a year
    • within “a few weeks, even a few months,” enough to cover rent

Key claim:

  • He wasn’t necessarily smarter than peers—he executed sooner.

Key Metric / Benchmark

Inside the speaker’s “Code to CEO” context:

  • Average founder lands their first client in ~47 days
  • Compared with “47 weeks” of prep (portfolio/research)

The speaker’s causal claim:

  • It’s mostly speed and outreach effort, not competence.

Example contrast:

  • One person spends a year building
  • Another sends 10 ugly messages / 10 bad DMs in week one, receives “no” 40 times, lands clients, raises price, and builds case studies while the first is still tweaking a portfolio (fonts/dark mode).

Actionable Process

Treat business like software shipping:

  • ship an MVP
  • get feedback
  • iterate

There’s “no course”—the market teaches you; every “no” is actionable feedback.

Stated Offer / Timeline (Business Execution)

  • Free live training
  • July 26th at 11:00 a.m. PT
  • Goal: help developers land their first $10,000+ client
  • Claim: without writing production code

Key KPIs & Numeric Targets Mentioned

Billing / Value Pricing Examples

  • Billing gap:
    • Firm billing: $1,850/hour per client
    • Number of clients: 3
    • Total billed: ~$5,550–$6,000/hour (rounded)
    • Developer pay: < $150/hour
  • Value pricing:
    • Manual time: 15 hours/week
    • Payroll cost: ~$60,000/year
    • Automation timeline: ~3 weeks
    • Charge: $15,000

Execution Benchmarks / Outreach

  • Average time to first client (“Code to CEO”): ~47 days
  • Suggested outreach behavior: 10 DMs/messages in week one
  • Example “no” count: ~40 nos

Income & Training Targets

  • Initial bank: $258
  • Later income: over six figures per month (no exact figure)
  • Training target:
    • land first $10,000+ client
    • date/time: July 26, 11:00 a.m. PT

Presenters / Sources Mentioned

  • Primary presenter (speaker): “Bugo”
  • Framework / source cited: Amazon (its 16 Leadership Principles, especially “Bias for Action”)

Named Individuals (from “Code to CEO” context)

  • Dom (CEO, “Scalar Code”)
  • Pedro (Brazil)
  • Toufic (Bangalore, India)
  • Marco (Serbia)
  • Carl (Switzerland)

Program / Context

  • Code to CEO

Original video