I built a 7-Figure ARR SaaS as a product guy. https://xitter.cf/t.co/iTBZm4V7Qx - Subscribe to be a part of my next project.
YouTube.com/@SaaS
Joined March 2011
- Tweets2.3K
- Following1.4K
- Followers2.4K
- Likes7.4K
AI will build your SaaS in a weekend but wont protect it from edge cases.
I scaled a SaaS to millions of users before Ai. Every item cost me manhours and money.
Copy this and give it to your agent so you don't have to deal with the headache later when something breaks or someone tries to break it:
1. SQL Injection: a user types code into your form and reads your whole database
2. Cron Jobs: tasks that run on a schedule, and silently stop running
3. P99 Latency: how slow your app is for the unluckiest 1% of users
4. Idempotency: clicking "Pay" twice should not charge twice
5. Secrets Management: your API keys do not belong in your code
6. CDN: serve files from servers near your users, not one box in Virginia
7. Race Conditions: two actions at the same instant corrupt your data
8. CI/CD: code gets tested and shipped automatically, not by hand
9. Webhooks: other apps notify yours when something happens
10. Sharding: splitting one giant database into smaller pieces
11. Backups: if you've never restored one, you don't have one
12. Liveness & Readiness Probes: is the app alive, and is it ready for traffic
13. Timeouts: never wait forever on a slow service
14. CORS: rules for which websites can call your API
15. Autoscaling: servers added automatically when traffic spikes
16. N+1 Queries: one page load quietly fires 500 database calls
17. Infrastructure as Code: your servers defined in files, not memory
18. Alerts: your phone buzzes before your customers email you
19. Saga Pattern: undoing step 1 when step 3 of a process fails
20. Cold Starts: the first request after idle is painfully slow
21. Caching: store answers so you stop recalculating them
22. DNS: the internet's phone book, and the cause of half of all outages
23. Optimistic Locking: assume no conflict, check before saving
24. TLS: the padlock in the browser bar
25. Rolling Deployments: update servers one at a time, not all at once
26. Message Queues: a line of jobs processed in order
27. Dependency Hell: one library update breaks five others
28. Leader Election: deciding which server is in charge
29. Rate Limiting: stop one user from hammering your API
30. SSRF: tricking your server into calling internal systems
31. Logging: a record of what happened, for when it goes wrong
32. WebSockets: a live two-way connection for chat and real-time updates
33. Cost Optimization: your cloud bill grows faster than your revenue
34. Backpressure: telling upstream to slow down when you're overwhelmed
35. Kubernetes: software that manages your containers at scale
36. Error Budgets: how much downtime you're allowed before you stop shipping features
37. Database Indexing: the reason a query takes 2ms instead of 20 seconds
38. On-Call: someone wakes up at 3am. Is it you?
39. Blue-Green Deployment: run two copies, flip traffic to the new one
40. Exponential Backoff: retry after 1s, then 2s, then 4s, not 1,000 times a second
41. Clock Skew: two servers disagree on what time it is
42. Encryption in Transit: data scrambled while it moves
43. Load Balancing: spread traffic across multiple servers
44. Memory Leaks: the app slowly eats RAM until it crashes
45. Semantic Versioning: what version 2.4.1 actually means
46. Read Replicas: copies of your database that handle reads
47. OAuth: "Sign in with Google" done correctly
48. Event-Driven Architecture: systems react to events instead of constantly asking
49. Failover: a backup takes over when the main system dies
50. Health Checks: is this server okay right now
51. Circuit Breakers: stop calling a service that keeps failing
52. HTTP/2 & HTTP/3: faster versions of how browsers talk to servers
53. Distributed Locks: only one server edits a record at a time
54. CSRF: another site tricks your user's browser into acting for them
55. Throughput: how many requests you handle per second
56. Metrics: numbers that tell you how healthy the system is
57. Terraform: the most popular infrastructure-as-code tool
58. Dead Letter Queues: where failed jobs go instead of disappearing
59. Vertical Scaling: a bigger server
60. Query Optimization: rewriting slow database requests
61. Postmortems: writing down why it broke so it never breaks that way again
62. Reverse Proxies: a gatekeeper server in front of your app
63. Disaster Recovery: the plan for when everything is gone
64. Feature Flags: turn features on or off without redeploying
65. CAP Theorem: under a network failure you choose consistency or availability, not both
66. Retries: try again, carefully
67. Build Caching: stop rebuilding what didn't change
68. WAF: a firewall that blocks malicious web requests
69. SLIs: the actual measurement, like % of requests under 300ms
70. Long Polling: the client waits on the server until there's news
71. Connection Pooling: reuse database connections instead of opening new ones
72. Serverless Limits: execution time caps, memory caps, surprise bills
73. Distributed Transactions: one action that has to succeed across multiple systems
74. Edge Caching: cached content stored at the network edge, close to the user
75. IAM: who is allowed to do what
76. Deadlocks: two processes wait on each other forever
77. Tail Latency: the slowest requests, which your users remember
78. Docker: package your app so it runs the same everywhere
79. Database Migrations: changing the database structure without losing data
80. Monitoring: watching the system 24/7 so you don't have to
81. gRPC: a fast way for services to talk to each other
82. Eventual Consistency: the data will match everywhere, just not instantly
83. Garbage Collection: automatic memory cleanup that can freeze your app
84. Pub/Sub: one message broadcast to many listeners
85. Encryption at Rest: data scrambled while it sits on disk
86. Production Incidents: the outage happens. What's the playbook?
87. API Gateways: one front door for all your APIs
88. Chaos Engineering: break things on purpose to find weak spots
89. Partitioning: splitting a big table into chunks
90. Service Discovery: services finding each other automatically
91. JWT Rotation: replacing login tokens before they get stolen
92. Rollbacks: undo a bad deploy in seconds
93. Network Partitions: servers can't reach each other but both keep running
94. Server-Sent Events: a one-way live stream from server to browser
95. Horizontal Scaling: more servers instead of a bigger one
96. API Versioning: change your API without breaking every customer
97. XSS: an attacker's script runs inside your users' browsers
98. Cache Invalidation: knowing when stored data is out of date
99. Replication: copying data across machines
100. SLOs: your promise, like 99.9% uptime
101. TCP vs UDP: reliable delivery vs fast delivery
102. Multi-Region Deployment: running in multiple parts of the world
103. Thread Safety: code that doesn't break when it runs in parallel
104. Observability: understanding why it broke, not just that it broke
105. Helm Charts: prepackaged Kubernetes setups
106. Canary Releases: ship to 5% of users first
107. Pessimistic Locking: lock the record before anyone touches it
108. Distributed Tracing: follow one request across 10 services
109. DDoS Protection: survive a flood of fake traffic
110. Schema Versioning: tracking every version of your database structure
Spence (YT:@SaaS) retweeted
If you want to know every top level domain that's coming to the internet in 2027-2028...
Obviously .saas is the best. 😏
Here's the full list: 👇
.acc
.account
.accounting
.ace
.act
.action
.active
.adk
.add
.admin
.advice
.advisor
.advisors
.advisory
.aeon
.age
.agent
.agentic
.agentid
.agi
.agnt
.agt
.aid
.air
.all
.alliance
.aloha
.alpha
.alum
.alumni
.amor
.anime
.anon
.ans
.any
.api
.apparel
.arc
.archive
.artist
.asap
.asi
.ask
.ass
.asset
.astro
.atelier
.atto
.audit
.aura
.auth
.automation
.backup
.bad
.bag
.bakery
.ball
.bao
.base
.bay
.bbq
.beach
.ber
.beta
.bewell
.big
.biotech
.bit
.bitcoin
.bldg
.block
.blvd
.board
.body
.boom
.brain
.brand
.brew
.bro
.browser
.btc
.btw
.bug
.cams
.cancel
.cap
.cart
.cas
.cast
.cause
.ccc
.cdn
.central
.cert
.chain
.change
.charge
.check
.chef
.chi
.chic
.ciao
.class
.classroom
.claw
.clean
.clear
.cli
.clone
.cmo
.coaching
.coin
.collection
.collective
.come
.comedy
.comics
.commerce
.commercial
.compute
.con
.config
.connect
.consult
.consultants
.control
.core
.corp
.corporation
.cosmetics
.counseling
.craft
.create
.creations
.creative
.creator
.crew
.crm
.crypto
.culture
.cyber
.daily
.dao
.daybreak
.ddd
.decor
.deep
.defense
.demo
.den
.deploy
.depot
.development
.device
.did
.dine
.dna
.dns
.donate
.dpp
.dragon
.dream
.droid
.drone
.drop
.dyna
.earn
.edge
.electric
.elite
.engine
.ent
.equs
.era
.etc
.ether
.evals
.explore
.expo
.ext
.eye
.fab
.factory
.fafo
.fam
.fantasy
.faq
.fart
.feed
.fest
.festival
.file
.files
.find
.fintech
.firm
.fix
.flow
.flux
.folio
.follow
.forge
.form
.forms
.founder
.foundry
.frankfurt
.fresh
.ftw
.furry
.future
.gamer
.gaming
.gas
.gate
.gear
.geek
.gem
.genie
.get
.ghost
.gig
.glasses
.glitch
.globe
.glow
.goat
.god
.good
.goods
.gram
.great
.grid
.grit
.grow
.growth
.gym
.hack
.hall
.han
.hao
.happy
.heart
.hello
.her
.hero
.hey
.hire
.hit
.hive
.hola
.honey
.hop
.hope
.hub
.human
.hvac
.iam
.icon
.icp
.idea
.identity
.ify
.iii
.impact
.index
.indie
.industrial
.infinite
.inn
.intel
.intelligence
.interiors
.internet
.invest
.invite
.ion
.island
.jackpot
.jazz
.jet
.jia
.join
.journal
.journey
.kai
.kek
.key
.king
.kit
.lab
.labs
.lake
.lan
.larus
.league
.learn
.learning
.legacy
.lei
.lend
.lesson
.lfg
.lift
.light
.line
.links
.list
.lit
.llm
.lock
.lodge
.log
.login
.logistics
.look
.loop
.lot
.lounge
.luck
.machine
.mad
.mag
.maga
.mai
.mail
.make
.maker
.mall
.manga
.maps
.mark
.mars
.mart
.matrix
.matt
.max
.mcp
.meditative
.meow
.mem
.member
.merch
.met
.metaverse
.mind
.mine
.mission
.mix
.mmm
.mod
.mode
.model
.moon
.more
.motors
.move
.muenchen
.mvp
.nation
.national
.nav
.neko
.neo
.nerd
.nft
.nice
.nil
.node
.nonprofit
.not
.note
.nova
.npc
.nsfw
.nut
.nutrition
.official
.oil
.omg
.only
.onn
.opc
.ops
.orb
.order
.organization
.oss
.out
.outlet
.own
.pai
.painting
.pal
.panda
.park
.pass
.path
.pec
.person
.pharma
.pinet
.pki
.plan
.planet
.planner
.platform
.plc
.pod
.podcast
.point
.pool
.pop
.port
.portal
.portfolio
.pos
.pot
.pov
.pow
.power
.ppp
.praxis
.predict
.pride
.print
.private
.product
.products
.profile
.program
.project
.prompt
.protocol
.proxy
.public
.puff
.punk
.quantum
.queen
.quince
.quote
.qwe
.race
.ranch
.rating
.real
.realm
.records
.registeredagent
.rem
.research
.resort
.retail
.rewards
.road
.robot
.robotaxi
.robotics
.roofing
.saas
.safari
.sat
.say
.scam
.scan
.sdk
.sea
.sec
.see
.self
.sell
.send
.sense
.server
.set
.share
.shield
.shift
.ship
.shorts
.sign
.sim
.skill
.slot
.smith
.sns
.soc
.socialmedia
.society
.soft
.solana
.solo
.sou
.soul
.sound
.source
.sov
.spice
.spring
.src
.sss
.stack
.start
.stats
.status
.stay
.stiftung
.stock
.stone
.story
.strategy
.street
.stupid
.substrate
.summit
.super
.superintelligence
.sus
.swap
.swi
.sync
.synth
.sys
.tag
.tea
.teach
.ten
.tex
.text
.therapy
.thing
.this
.time
.tiny
.tkns
.tldr
.token
.track
.trademark
.trainer
.transport
.trek
.trip
.tron
.truck
.true
.truth
.trx
.try
.twente
.uid
.ultra
.ultraview
.uni
.universe
.unlimited
.update
.url
.user
.uwu
.van
.vault
.venue
.ver
.verein
.verified
.via
.vibe
.vid
.vids
.view
.vintage
.viral
.virtual
.visit
.viv
.voice
.vpn
.vps
.wallet
.want
.war
.water
.wave
.way
.wealth
.wear
.wearables
.weed
.well
.wellness
.west
.why
.wifi
.wild
.wire
.wit
.wizard
.wood
.xmr
.在线
.株式会社
.地址
.商标
.中文网
.购物
.人工智能
.餐厅
.网络
.品牌
.官网
.xoxo
.xxl
.yam
.yay
.yes
.yyy
.zan
.zec
.zen
.zzz
How far could you throw a server rack? I'm gonna try.
I guess it depends if it's a U1/2/4.
25 - 125lbs / 11kg - 60kg.
People on X and heavy in the SaaS space need to understand LOCAL DISTORTION.
If you are constantly seeing people vibe code their own solution every day and on every feed, you will of course see it as the norm and will become your baseline.
The majority of people wont do this.
Here’s a simple test for whether AI can replace your job:
If you can explain your work as a tidy bullet list, AI can copy it.
If your work takes judgment, context, and handling pushback from people who disagree, AI needs you.
Unpopular opinion:
The more time you spend on X, the less you'll understand what normal people will pay for.
Not everyone is going to vibe code their own [insert game / saas / tool / here]
Normal people couldn't care less about ai taking over everything.
They clock in and clock out and sleep fine. I know plenty of people that sleep with not a care in the world. We are a different kind of people.
🤖 Made with AI
Anyone can buy PVC pipe at Home Depot and plumb their own toilet after two YouTube tutorials.
Yet plumbers make $150/hr because nobody wants to wake up swimming in sewage at 3 AM.
Does anyone believe a lawyer or their paralegal is going to vibe code their client intake?
The bubble each section of society lives in amazes me...
Everyone on twitter is screaming software is dead.
People in everyday life... Don't work on the weekends and have zero worry about ai for the most part (aside from the mainstream media fearmongering.)
If you want to know every top level domain that's coming to the internet in 2027-2028...
Obviously .saas is the best. 😏
Here's the full list: 👇
.acc
.account
.accounting
.ace
.act
.action
.active
.adk
.add
.admin
.advice
.advisor
.advisors
.advisory
.aeon
.age
.agent
.agentic
.agentid
.agi
.agnt
.agt
.aid
.air
.all
.alliance
.aloha
.alpha
.alum
.alumni
.amor
.anime
.anon
.ans
.any
.api
.apparel
.arc
.archive
.artist
.asap
.asi
.ask
.ass
.asset
.astro
.atelier
.atto
.audit
.aura
.auth
.automation
.backup
.bad
.bag
.bakery
.ball
.bao
.base
.bay
.bbq
.beach
.ber
.beta
.bewell
.big
.biotech
.bit
.bitcoin
.bldg
.block
.blvd
.board
.body
.boom
.brain
.brand
.brew
.bro
.browser
.btc
.btw
.bug
.cams
.cancel
.cap
.cart
.cas
.cast
.cause
.ccc
.cdn
.central
.cert
.chain
.change
.charge
.check
.chef
.chi
.chic
.ciao
.class
.classroom
.claw
.clean
.clear
.cli
.clone
.cmo
.coaching
.coin
.collection
.collective
.come
.comedy
.comics
.commerce
.commercial
.compute
.con
.config
.connect
.consult
.consultants
.control
.core
.corp
.corporation
.cosmetics
.counseling
.craft
.create
.creations
.creative
.creator
.crew
.crm
.crypto
.culture
.cyber
.daily
.dao
.daybreak
.ddd
.decor
.deep
.defense
.demo
.den
.deploy
.depot
.development
.device
.did
.dine
.dna
.dns
.donate
.dpp
.dragon
.dream
.droid
.drone
.drop
.dyna
.earn
.edge
.electric
.elite
.engine
.ent
.equs
.era
.etc
.ether
.evals
.explore
.expo
.ext
.eye
.fab
.factory
.fafo
.fam
.fantasy
.faq
.fart
.feed
.fest
.festival
.file
.files
.find
.fintech
.firm
.fix
.flow
.flux
.folio
.follow
.forge
.form
.forms
.founder
.foundry
.frankfurt
.fresh
.ftw
.furry
.future
.gamer
.gaming
.gas
.gate
.gear
.geek
.gem
.genie
.get
.ghost
.gig
.glasses
.glitch
.globe
.glow
.goat
.god
.good
.goods
.gram
.great
.grid
.grit
.grow
.growth
.gym
.hack
.hall
.han
.hao
.happy
.heart
.hello
.her
.hero
.hey
.hire
.hit
.hive
.hola
.honey
.hop
.hope
.hub
.human
.hvac
.iam
.icon
.icp
.idea
.identity
.ify
.iii
.impact
.index
.indie
.industrial
.infinite
.inn
.intel
.intelligence
.interiors
.internet
.invest
.invite
.ion
.island
.jackpot
.jazz
.jet
.jia
.join
.journal
.journey
.kai
.kek
.key
.king
.kit
.lab
.labs
.lake
.lan
.larus
.league
.learn
.learning
.legacy
.lei
.lend
.lesson
.lfg
.lift
.light
.line
.links
.list
.lit
.llm
.lock
.lodge
.log
.login
.logistics
.look
.loop
.lot
.lounge
.luck
.machine
.mad
.mag
.maga
.mai
.mail
.make
.maker
.mall
.manga
.maps
.mark
.mars
.mart
.matrix
.matt
.max
.mcp
.meditative
.meow
.mem
.member
.merch
.met
.metaverse
.mind
.mine
.mission
.mix
.mmm
.mod
.mode
.model
.moon
.more
.motors
.move
.muenchen
.mvp
.nation
.national
.nav
.neko
.neo
.nerd
.nft
.nice
.nil
.node
.nonprofit
.not
.note
.nova
.npc
.nsfw
.nut
.nutrition
.official
.oil
.omg
.only
.onn
.opc
.ops
.orb
.order
.organization
.oss
.out
.outlet
.own
.pai
.painting
.pal
.panda
.park
.pass
.path
.pec
.person
.pharma
.pinet
.pki
.plan
.planet
.planner
.platform
.plc
.pod
.podcast
.point
.pool
.pop
.port
.portal
.portfolio
.pos
.pot
.pov
.pow
.power
.ppp
.praxis
.predict
.pride
.print
.private
.product
.products
.profile
.program
.project
.prompt
.protocol
.proxy
.public
.puff
.punk
.quantum
.queen
.quince
.quote
.qwe
.race
.ranch
.rating
.real
.realm
.records
.registeredagent
.rem
.research
.resort
.retail
.rewards
.road
.robot
.robotaxi
.robotics
.roofing
.saas
.safari
.sat
.say
.scam
.scan
.sdk
.sea
.sec
.see
.self
.sell
.send
.sense
.server
.set
.share
.shield
.shift
.ship
.shorts
.sign
.sim
.skill
.slot
.smith
.sns
.soc
.socialmedia
.society
.soft
.solana
.solo
.sou
.soul
.sound
.source
.sov
.spice
.spring
.src
.sss
.stack
.start
.stats
.status
.stay
.stiftung
.stock
.stone
.story
.strategy
.street
.stupid
.substrate
.summit
.super
.superintelligence
.sus
.swap
.swi
.sync
.synth
.sys
.tag
.tea
.teach
.ten
.tex
.text
.therapy
.thing
.this
.time
.tiny
.tkns
.tldr
.token
.track
.trademark
.trainer
.transport
.trek
.trip
.tron
.truck
.true
.truth
.trx
.try
.twente
.uid
.ultra
.ultraview
.uni
.universe
.unlimited
.update
.url
.user
.uwu
.van
.vault
.venue
.ver
.verein
.verified
.via
.vibe
.vid
.vids
.view
.vintage
.viral
.virtual
.visit
.viv
.voice
.vpn
.vps
.wallet
.want
.war
.water
.wave
.way
.wealth
.wear
.wearables
.weed
.well
.wellness
.west
.why
.wifi
.wild
.wire
.wit
.wizard
.wood
.xmr
.在线
.株式会社
.地址
.商标
.中文网
.购物
.人工智能
.餐厅
.网络
.品牌
.官网
.xoxo
.xxl
.yam
.yay
.yes
.yyy
.zan
.zec
.zen
.zzz
If I hypothetically wanted to fund a few SaaS projects (Or Games) for their paid ads....
Pitch me why it should be your project?
1. Make the billed price the biggest number, not the weekly math
2. Remind users before the trial converts
3. One-tap cancel, no maze
4. Refund day-one “I forgot” requests without a fight
5. Don't force annual unless you want a higher chargeback risk. ASK for it, don't force it.
A refund costs you $50. A chargeback, a platform ban, or a class action costs you the company.
What's next for SaaS if software is no longer the moat?
16%Open Source SaaS
21%Fewer Soloprenuers
42%More Ai Slop SaaS
21%Nothing - It'll be fine.
19 votes • Final resultsI still can't write any code and built a 7figure SaaS before AI could build one for you.
every lesson below cost me real money and real time. now you can skip most of the cost. you can’t skip the lessons
7 short Things 👇
The first version cost me $6K and crashed every 2 hours. Today that version is one prompt and $20. the lesson is the same: ship the broken thing that solves a real problem before the polished thing that doesn’t
1. one forum beat every ad I ever ran. I answered questions in the same community for a year before I asked anyone to pay. AI can write your product. it can’t earn you a year of trust.
2. I interviewed 100 developers to find one. half wouldn’t turn their camera on. you’ll never have to do that again. but you’ll still have to know what to build, and no tool answers that for you.
3. put a real dollar amount on it: $2K a month to run, $140K a month coming in. software margins were the whole game then and they’re better now. your build cost went to zero. your distribution cost didn’t
4. we priced as a percentage of each payment, not a flat fee. customers making $0 paid $0. customers making $100K paid us a lot and never complained once. pricing was never a code problem. it still isn’t. Its solvable.
5. support replies in under an hour. 30 saved templates covered about 90% of tickets. the moat was never the code. when everyone can generate the same app in an afternoon, it’s even less the code.
6. we never built a mobile app. 6M users and no app. now that a feature costs ten minutes, the hard skill isn’t building. it’s refusing to if it could potentially detract from your focus.
7. two numbers every Monday: new paying customers and churn. everything else was noise. a tool can build your dashboard. it can’t make you look at it
on top of that, one core rule: don’t quit the thing that works because it got boring. we ran the same playbook for years
I did this the hard way BEFORE ai. You don't have to. But you need to change the way you think about your workflow.
For all the vibe coders and SaaS founders that are worried about "but someone will just build their own version of my software".
This chart is the US only. The vast majority of people barely pay for ai. Plenty of people will still use your app or saas if it provides enough value.
Calm down. You still have 5 years before you have to panic.
98% of US households aren't paying for AI yet
More charts in State of Markets II: a16z.news/p/state-of-markets…
