[{"data":1,"prerenderedAt":225},["ShallowReactive",2],{"blog-\u002Fblog\u002Fwhat-i-learned-building-multiple-products-at-once":3,"blog-surround-\u002Fblog\u002Fwhat-i-learned-building-multiple-products-at-once":205,"blog-related-\u002Fblog\u002Fwhat-i-learned-building-multiple-products-at-once":214},{"id":4,"title":5,"audience":6,"body":10,"cluster":170,"date":171,"description":172,"draft":173,"extension":174,"factCheckedAt":175,"faq":176,"featured":173,"language":175,"meta":186,"navigation":187,"order":188,"originalAsset":175,"path":189,"pillar":190,"primaryKeyword":191,"relatedProject":175,"releaseScope":175,"reviewCycle":192,"reviewStatus":193,"reviewedBy":194,"searchIntent":195,"seo":196,"sources":175,"stem":197,"tags":198,"type":203,"updated":171,"__hash__":204},"blog\u002Fblog\u002Fwhat-i-learned-building-multiple-products-at-once.md","What I Learned Building Multiple Products at Once",[7,8,9],"indie-founder","solo-developer","product-builder",{"type":11,"value":12,"toc":160},"minimark",[13,21,26,35,39,45,53,57,65,69,77,81,93,97,125,133,136],[14,15,16,20],"p",{},[17,18,19],"strong",{},"The advice handed to every solo builder comes down to one word: focus — meaning build one thing."," I ran several at once anyway, and it taught me the word is at best incomplete. Focus isn't doing one thing; it's a system that gives each product the right attention at the right time, and kills what doesn't earn it. I used to assume a portfolio meant divided attention, and divided attention meant nothing ships. It can — but the failure isn't the multiplicity, it's the lack of a system for it. With the right disciplines, products don't compete for a fixed pot of focus; they take turns. These are the lessons that made the portfolio survivable instead of a pile of half-finished apps.",[22,23,25],"h2",{"id":24},"lesson-1-sameness-is-what-buys-the-capacity","Lesson 1: Sameness is what buys the capacity",[14,27,28,29,34],{},"You can't hold several bespoke things in one head. The only reason a portfolio is possible at all is that everything runs on the ",[30,31,33],"a",{"href":32},"\u002Fblog\u002Fnuxt-and-supabase-solo-saas-stack","same repeated stack"," — same deployment, same patterns, same mental model — so moving between products doesn't mean re-learning my own architecture every time. Every product that gets to be special costs me the capacity to run another one. The boring sameness is what creates the room for the multiplicity.",[22,36,38],{"id":37},"lesson-2-products-take-turns","Lesson 2: Products take turns",[40,41,42],"pull-quote",{},[14,43,44],{},"Focus isn't working on one thing forever — it's giving one thing your full attention at a time, and having a system that decides which, when. Products don't need equal attention simultaneously; they need the right attention at the right moment.",[14,46,47,48,52],{},"This was the real unlock. I stopped trying to nudge everything forward a little each day — which moves nothing — and started letting products take turns. One product is the active focus, getting the concentrated push that actually moves it; the others sit maintained but stable. Then the focus rotates as the needs change. Spreading yourself evenly across everything feels responsible and is exactly ",[30,49,51],{"href":50},"\u002Fblog\u002Fhow-i-stay-sane-building-products-solo","how solo portfolios die",": perpetually half-done, nothing ever finished.",[22,54,56],{"id":55},"lesson-3-the-filter-has-to-be-ruthless-up-front","Lesson 3: The filter has to be ruthless up front",[14,58,59,60,64],{},"More products means more chances to build the wrong one, and the wrong one costs the same solo whether it's your first or your fifth. So the ",[30,61,63],{"href":62},"\u002Fblog\u002Fhow-i-decide-whether-an-ai-product-idea-is-worth-building","idea filter"," matters more with a portfolio, not less. A product that shouldn't exist isn't just wasted effort — it's a standing tax on the attention of every other product. The discipline that felt optional with one product becomes survival with several.",[22,66,68],{"id":67},"lesson-4-kill-fast-or-the-portfolio-kills-you","Lesson 4: Kill fast, or the portfolio kills you",[14,70,71,72,76],{},"The counterpart to taking turns is that some products never deserve one. ",[30,73,75],{"href":74},"\u002Fblog\u002Fmy-kill-criteria-for-product-experiments","Kill criteria"," go from useful to essential: a portfolio that never kills anything is a graveyard where the dead products quietly drain the attention of the living. The hardest skill in running several things at once isn't building — it's ending the ones that aren't earning their place, cleanly, without agonizing over each, so the attention flows back to what's working.",[22,78,80],{"id":79},"lesson-5-you-need-a-portfolio-view","Lesson 5: You need a portfolio view",[14,82,83,84,88,89,92],{},"With one product, the whole state fits in your head. With several, you have to see them all at once — what each one is, its honest ",[30,85,87],{"href":86},"\u002Fproducts","status",", what it needs next. Without that view, the loudest or most recent product hijacks the attention regardless of which one has earned it. The ",[30,90,91],{"href":86},"products page with honest status labels"," isn't only for visitors; it's the discipline of looking at the whole portfolio straight and deciding where the next turn goes.",[22,94,96],{"id":95},"what-usually-goes-wrong","What usually goes wrong",[98,99,100,107,113,119],"ul",{},[101,102,103,106],"li",{},[17,104,105],{},"Even spreading."," Moving everything a little every day, so nothing moves meaningfully.",[101,108,109,112],{},[17,110,111],{},"Bespoke everything."," A special stack per product, until the maintenance alone caps you at one.",[101,114,115,118],{},[17,116,117],{},"No killing."," Keeping dead products on life support, quietly draining the live ones.",[101,120,121,124],{},[17,122,123],{},"Loudest-wins attention."," Letting the noisiest or most recent product take the focus instead of the one that earned it.",[14,126,127,128,132],{},"Run everything on the same stack, let products take turns instead of spreading thin, filter ruthlessly up front, kill what doesn't earn a turn, and keep a portfolio view — and building several products stops being a scatter of half-done apps and becomes something closer to a studio. It's all one ",[30,129,131],{"href":130},"\u002Fblog\u002Fmy-product-operating-system","operating system",", and running several products at once is what proves whether you actually have one.",[134,135],"hr",{},[14,137,138],{},[139,140,141,142,146,147,150,151,154,155,159],"em",{},"Part of ",[30,143,145],{"href":144},"\u002Ftopics\u002Fbuilding-ai-products","Building AI Products",". See also ",[30,148,149],{"href":130},"my product operating system"," and ",[30,152,153],{"href":74},"my kill criteria for product experiments",". The ",[30,156,158],{"href":157},"\u002Fnewsletter","newsletter"," sends one practical build lesson every two weeks.",{"title":161,"searchDepth":162,"depth":162,"links":163},"",2,[164,165,166,167,168,169],{"id":24,"depth":162,"text":25},{"id":37,"depth":162,"text":38},{"id":55,"depth":162,"text":56},{"id":67,"depth":162,"text":68},{"id":79,"depth":162,"text":80},{"id":95,"depth":162,"text":96},"process","2026-07-24","Building multiple products at once taught me focus isn't doing one thing — it's a system giving each the right attention at the right time. The lessons.",false,"md",null,[177,180,183],{"question":178,"answer":179},"Can a solo founder build multiple products at once?","Yes, but only with a system, not by improvising each one. What makes it survivable is: the same repeated stack so nothing is bespoke, a hard filter so you only build problems worth building, defining the outcome before the screen so each product stays pointed, explicit kill criteria so weak ones die fast, and — the real lesson — sequencing attention so products take turns being the focus rather than all demanding it at once. Without that system, multiple products just means multiple half-finished things.",{"question":181,"answer":182},"How do you focus when building several products?","By redefining focus. Focus isn't working on only one thing forever — it's giving one thing your full attention at a time, and having a system that decides which thing, when. Products don't all need equal attention simultaneously; they need the right attention at the right moment. The discipline is sequencing — letting one product be the active focus while others sit stable — and ruthlessly killing anything that can't earn a turn. Spreading yourself evenly across everything is the opposite of focus, and it's how solo portfolios die.",{"question":184,"answer":185},"What is the biggest mistake building multiple products?","Spreading attention evenly across all of them at once. It feels productive and responsible, but it means nothing gets the concentrated push it needs to actually move, and everything stays perpetually half-done. The fix is to accept that products take turns: one is the active focus, the others are maintained but stable, and weak ones are killed rather than kept on life support. Trying to move everything a little every day moves nothing meaningfully.",{},true,12,"\u002Fblog\u002Fwhat-i-learned-building-multiple-products-at-once","building-ai-products","building multiple products at once","annual","reviewed","Tan Gravam","informational",{"title":5,"description":172},"blog\u002Fwhat-i-learned-building-multiple-products-at-once",[190,199,200,201,202],"product","solo-saas","focus","portfolio","text","uHf6nKiVG2k879mHpQg8E1bjKopzmiMDzAuw1emzqi0",[206,210],{"title":207,"path":208,"stem":209,"type":203,"language":175,"draft":173,"children":-1},"What Does a Corporate Treasury Do?","\u002Fblog\u002Fwhat-does-a-corporate-treasury-do","blog\u002Fwhat-does-a-corporate-treasury-do",{"title":211,"path":212,"stem":213,"type":203,"language":175,"draft":173,"children":-1},"What Is a Payment Factory?","\u002Fblog\u002Fwhat-is-a-payment-factory","blog\u002Fwhat-is-a-payment-factory",[215,218,221],{"path":130,"title":216,"description":217},"My Product Operating System for Building Multiple AI Apps","The product operating system I use to build several focused AI products solo: choosing which problem to build, shipping fast, and killing what isn't working.",{"path":62,"title":219,"description":220},"How I Decide Whether an AI Product Idea Is Worth Building","How to decide what product to build: the short filter I run every idea through — real recurring problem, one-sentence outcome, small enough to ship solo.",{"path":222,"title":223,"description":224},"\u002Fblog\u002Fwhy-i-write-the-expected-output-before-the-screen","Why I Write the Expected Output Before the Screen","Define the outcome before design: I write the exact result the user should get before building any screen, because the screen is only the path to an outcome.",1785182343314]