The hidden cost of building

The hidden cost of building

April 10, 2026

Gurjeet Singh

Everyone quotes the engineer salary. Nobody quotes the rest. The real cost of shipping a modern software product is the sum of a dozen small bills, most of which you do not see until they have already compounded.


This is the breakdown I wish I had before I shipped three products in twelve months.


The API bill, and how it creeps


You start with $100 a month. A year later you are at $4,000 and nobody can tell you why. Here is the actual shape of how that happens.


Stage
Prototype
Monthly spend
$40–$120
What drove it
You testing
What you assumed
"Should stay under $200"
Stage
First users
Monthly spend
$300–$800
What drove it
50 real users
What you assumed
"This scales linearly"
Stage
Growth
Monthly spend
$1,200–$3,500
What drove it
Retry loops, streaming, agents
What you assumed
"We will optimize later"
Stage
Scale
Monthly spend
$4,000–$15,000
What drove it
Long-context chains, vector costs, background jobs
What you assumed
"We need finops"

The creep is not usage. The creep is **context length**, **agentic retries**, and **forgotten cron jobs** that re-embed your whole database every night because someone wrote "just in case."


The three silent drivers


  • Context bloat. Every feature tacks more system-prompt, more retrieved documents, more conversation history. Your per-request token count doubles every two quarters without anyone noticing.
  • 2. **Agent recursion.** One user action fans out into 5–12 model calls. A 2x cost-per-call savings becomes an 8x total-cost savings.

    3. **Unthrottled retries.** A model API returns a 500, your library retries 3x, your app retries 2x, your client retries 2x. One user click now charges you 12 times.


    The codebase gravity problem


    Three products sounds efficient. Until you are in month seven and every bug fix is a three-codebase migration.


    Three products, one founder — what actually happens


    **Process Steps:**

    Build product A → Build product B (copy-paste A's auth) → Build product C (diverges) → Fix a bug in auth → Port to B → Miss C → C breaks in production


    **Time Investment:**

    fine → fine → ship → 2 hours → 3 hours → forgot → outage Sunday morning


    **Total Duration:** you are now a maintenance engineer with three jobs

    **Key Challenge:** shared code gravity is the thing you pay for the *second* you have more than one codebase.


    The fork in the road


    Approach
    Monorepo
    Upside
    Shared code, one migration
    Cost
    Heavier tooling, every product ships when the slowest ships
    Approach
    Separate repos
    Upside
    Ship independently
    Cost
    Every shared concern forks eventually
    Approach
    Shared npm package
    Upside
    Clean boundaries
    Cost
    You are now a package maintainer on top of a founder

    There is no correct answer. There is a choice, and you pay either way. The mistake is thinking there is a free path.


    The Apple tax (and the Google tax, and the Stripe tax, and...)


    Nobody tells you this upfront. Every consumer app is a stack of taxes.


    Line item
    Apple Developer
    Annual cost
    $99
    What it buys
    Access to the App Store (required)
    Line item
    Apple 15–30% cut
    Annual cost
    15% (Small Business Program) / 30%
    What it buys
    Billing, distribution, review
    Line item
    Google Play
    Annual cost
    $25 one-time + 15–30%
    What it buys
    Same as Apple on Android
    Line item
    Stripe
    Annual cost
    2.9% + $0.30
    What it buys
    Card processing (web)
    Line item
    Domain + SSL + DNS
    Annual cost
    $30–$200
    What it buys
    Basic existence on the internet
    Line item
    Postmark / Resend
    Annual cost
    $15–$100
    What it buys
    Transactional email that actually lands
    Line item
    Push notifications
    Annual cost
    $0–$99
    What it buys
    If you use a service layer
    Line item
    Supabase / Auth0
    Annual cost
    $0–$599
    What it buys
    Auth + database + storage
    Line item
    Object storage
    Annual cost
    $50–$800
    What it buys
    Images, videos, files
    Line item
    Observability (Sentry, etc.)
    Annual cost
    $26–$479
    What it buys
    Knowing your app is broken before users tell you
    Line item
    AI APIs
    Annual cost
    $200–$15,000
    What it buys
    See previous section

    A small, shipping iOS + web product runs **$600–$2,000/month** in pure infrastructure before anyone is paid. Scale brings that to $5,000–$30,000.


    Apple specifically


    The review process is the one founders underestimate the most.


    Submission
    First submission (new app)
    Median time
    24–72 hours
    Median rejection rate
    ~40%
    Submission
    Update (established app)
    Median time
    4–36 hours
    Median rejection rate
    ~10–15%
    Submission
    TestFlight (beta)
    Median time
    24 hours
    Median rejection rate
    ~5%

    Forty percent. Your first submission has a near-coin-flip chance of coming back with a rejection. Reasons from my own ledger: a screenshot did not match the app exactly, a purchase flow used web checkout instead of IAP, a privacy string was too vague, a tracking framework was flagged. Each rejection is a 2–5 day round trip. Plan 2–3 submissions for any first release.


    Verification, not interviews


    The hidden cost nobody writes about: the hour you spend on every partnership, every integration, every enterprise conversation, proving you are a real company.


    Verification
    Apple Developer identity
    Time
    1 hour + 2 days wait
    Frequency
    Annual
    Verification
    Stripe KYC
    Time
    30 min + 1–5 days
    Frequency
    Per account
    Verification
    Google OAuth scopes (restricted)
    Time
    4–12 hours of prep
    Frequency
    Per scope, one-time-ish
    Verification
    Business verification (banks, payroll)
    Time
    2–4 hours
    Frequency
    Per vendor
    Verification
    Partnership due diligence
    Time
    2–6 hours
    Frequency
    Per partner
    Verification
    Enterprise security reviews
    Time
    10–40 hours
    Frequency
    Per deal

    A solo founder loses **10–30 hours a month** to verification work that builds nothing and ships nothing. It is the single most under-discussed expense in early-stage building.


    Infrastructure layers silently


    You start with a dev server. A year later:


    **Process Steps:**

    Dev server → Vercel → Vercel + Supabase → + CDN → + queue → + cron worker → + separate staging → + observability stack → + secrets manager → + CI/CD → + domain management


    **Time Investment:**

    day 1 → week 1 → month 1 → month 3 → month 5 → month 7 → month 8 → month 9 → month 10 → month 11 → month 12


    **Total Duration:** you now administer ~11 pieces of infrastructure

    **Key Challenge:** each one was added for a real reason. None of them are removable. Collectively they are ~$400–$1,500/month and consume a day a week to maintain.


    What this adds up to


    For a solo or two-person consumer AI product in 2026, here is the actual monthly cost of "shipping" before founder salary, before marketing, before a single feature:


    Category
    AI APIs
    Low end
    $200
    Realistic
    $1,200
    High end
    $8,000+
    Category
    Infrastructure
    Low end
    $150
    Realistic
    $500
    High end
    $1,800
    Category
    Platform fees (Apple/Google/Stripe)
    Low end
    $100
    Realistic
    $400
    High end
    $2,500+
    Category
    Tooling (email, auth, storage, observability)
    Low end
    $100
    Realistic
    $350
    High end
    $900
    Category
    Verification / compliance overhead
    Low end
    10 hrs
    Realistic
    20 hrs
    High end
    40 hrs
    Category
    **Monthly total**
    Low end
    **~$550 + 10 hrs**
    Realistic
    **~$2,450 + 20 hrs**
    High end
    **~$13,200 + 40 hrs**

    The punchline: a solo shipper with three products live is running a **~$30,000/year infrastructure-and-platform-tax bill** before their first engineer is paid, plus a part-time job worth of invisible verification and maintenance work.


    The point


    None of this is complaint. All of it is why consumer AI products are harder than the "one GPU and a weekend" narrative suggests. If you are thinking about building — or funding someone who is — these are the line items to ask about. The product quality is usually not the bottleneck. The maintenance cost of having shipped is.

    More Posts

    Learning how to lead

    Learning how to lead

    April 26, 2026

    This started as curiosity. The same instinct that pulled me into building things eventually asked a harder question: what does it take to lead them? Courage, I have come to understand, is not the absence of fear. It is being scared and doing the thing anyway.

    The pace of AI, in perspective

    The pace of AI, in perspective

    March 20, 2026

    We overestimate what AI can do in a month and wildly underestimate what it can do in a year. A look at the actual slope — training cost per capability, inference cost, benchmark jumps — and what that means if you are building on top of it.

    How to build in the digital

    How to build in the digital

    January 15, 2025

    The introduction of digital intelligence has paved the way for learning and rapid implementation of ideas, transforming how we approach creative problem-solving and innovation in the modern world.

    The art of creation

    The art of creation

    December 8, 2024

    Exploring the relationship between creative freedom and the mental constraints such freedom introduces, revealing how boundaries can paradoxically enhance artistic expression.

    What are tools?

    What are tools?

    June 14, 2025

    How the unique ability of humans to craft and use tools has helped change the course of history, from primitive implements to digital technologies.