going fast

engineer_mindset:
  savings = hours_spent * hourly_rate
  if savings > 0: celebrate()

founder_mindset:
  cost = burn_rate * days_delayed
  if shipping_late: panic()

engineers think they’re saving money. they’re often burning it.

a talented engineer spends a week optimizing cloud costs. saves 500 euros per month. everyone celebrates. dashboards go green.

let’s do the actual math.

the hidden cost of “cost killing”

one week of engineering time: easily $4000-5000 with taxes, benefits, equipment.

the invisible costs:

• hiring took 3 months and cost 15k+ in recruiter fees, interview time, onboarding
• that engineer could leave tomorrow and you’d spend another 3 months replacing them
• while they optimized bills, a competitor shipped a feature
• while they optimized bills, a customer churned waiting for that feature

so you “saved” 500 euros per month. you’ll break even in… 8 months? assuming nothing else matters?

spoiler: everything else matters.

time has three price tags

engineers see their time through one lens: salary. “i work 40 hours, i get paid X.”

but time costs money in three ways:

1. the salary math

obvious. engineer costs Y per hour. they spent Z hours on cost killing. total cost = Y × Z.

2. the burn rate math

your company has a burn rate. salaries, servers, saas, rent, lawyers, taxes. every month, money leaves. divide by 30, you get a daily burn. divide by 24, you get an hourly burn.

that burn doesn’t stop on weekends. doesn’t stop at night. doesn’t stop when engineers are “just researching the best cloud provider.”

every day you’re not shipping is a day you’re spending money without earning it back.

daily_burn = monthly_expenses / 30
cost_of_delay = days_late * daily_burn

// hint: this number is always bigger than you think

3. the opportunity math

this one hurts the most.

every day you’re not in market, someone else is. every week you delay, a competitor gets feedback you don’t have. every month late is a month of revenue you’ll never recover.

speed isn’t about saving money. it’s about making money. learning faster. surviving.

the cost killer paradox

the engineers obsessed with killing costs are often the most expensive people in the company.

not because they’re bad. because they’re good. good at the wrong thing.

they see a 500 euro monthly bill and think “waste.” they don’t see the 50000 euro opportunity cost of not shipping.

they’re playing defense on a field that requires offense.

what actually reduces cost

1. go faster

ship faster. learn faster. iterate faster.

every day saved is worth your entire daily burn rate in real money, plus whatever opportunity you’d otherwise miss.

2. reasonable defaults, not optimization theater

don’t spend money on stupid things. use sensible instance sizes. turn off what you don’t use. set budgets and alerts.

this takes an hour, not a week.

3. delegate the boring stuff

cost optimization is real work. but it’s not work for your best engineers.

use:

• cost management services (they exist, they’re good at it)
• junior engineers who need to learn the infrastructure anyway
• ai tools that monitor and suggest
• finance people who actually care about this stuff

your senior engineers should be building. period.

the rule

func Prioritize(task Task) Action {
    if task.Affects(Product) || task.Affects(Shipping) {
        return DoItNow
    }
    if task.Type == CostKilling {
        return Delegate
    }
    return Skip
}

your best people should build. build. build.

everything else is noise.

the fastest company wins. not the cheapest one.

related: exploring vs finalizing on shipping ugly v1s. unplanned planning on why fluid strategy beats rigid plans.