Skip to main content

Loading…

Skip to main content
HomeProjectsPostsApproachesStackResourcesContact
Justin Tsugranes LogoJustin Tsugranes Logo

Justin Tsugranes

HomeProjectsPostsApproachesStackResourcesContact

Stay in the loop

Occasional notes on what I'm building, lessons earned, and the studio behind it.

By subscribing, you agree to receive No spam. Unsubscribe in one click anytime. from Justin Tsugranes. No spam. Unsubscribe anytime. Privacy Policy

© 2026 Total Ventures LLC. All rights reserved.

Privacy PolicyTerms of ServiceCookie Policy

Builder's Playbook

Approaches

How I actually build things. The patterns, decisions, and trade-offs behind running a solo-operator portfolio of digital products.

  • agentsAgent-First DevelopmentBuild assuming agents will write most of the code. Optimize the codebase for them, not just for humans.
  • agentsClaude Code as the EngineerTreat Claude Code as the implementation engineer; treat yourself as the staff engineer reviewing the work.
  • agentsAgent Autonomy TiersDifferent work needs different leashes. Internal refactors get carte blanche. External actions ask first.
  • agentsHuman-in-the-Loop Where It MattersApprove copy, pricing, and anything customer-facing. Skip approval on internal lint, refactors, doc updates.
  • agentsMulti-Agent ParallelismSpawn parallel agents for independent work. Serial reviews when work depends on each other.
  • agentsSystemize CorrectionsWhen you correct an agent, codify the correction in CLAUDE.md or a feedback memory. Don't re-correct twice.
  • workflowMonorepo as Operating SystemOne repo, one CI, one deployment surface. Every brand inherits the studio's infrastructure for free.
  • workflowCommit Often, Push DeliberatelyLocal commits are free. Pushes trigger CI, change visibility, and need a green light.
  • workflowQueue-Driven Attention5 active items max. Everything else lives in the roadmap or inbox. The queue is the next-action surface.
  • workflowCI Local Before CI RemoteRun the full validation locally before pushing. Catch failures in seconds, not minutes.
  • workflowDocs as SourceAGENTS.md / CLAUDE.md / brand-specific maps are agent context. Keep them current or watch agents drift.
  • workflowAudits as CronsAnything you'd manually check belongs as a cron. Drift detection runs nightly; you only see real anomalies.
  • monetizationProfit-First AllocationPay the profit account first. Build the studio inside whatever margin remains, not around hopes.
  • monetizationMultiple Revenue Streams, One Back OfficeEach brand monetizes independently — ads, products, services, subs — but shares the same Stripe + Mercury ops layer.
  • monetizationCredit Packs over SubscriptionsSubscriptions create renewal anxiety and churn drama. Credit packs match perceived value to actual use.
  • monetizationPaid Generation Fan-OutEvery paid AI call must produce content for ≥5 surfaces. Single-use generation is a design failure.
  • monetizationLead Magnet → Paid LadderFree PDF captures email; $5 entry-price PDF tests willingness to pay; $20+ bundles test depth.
  • craftVoice as Source of TruthEach brand has one voice.md. Every AI consumer loads it via the same loader. No re-stated voice in prompts.
  • craftThesis-First ContentEvery piece opens with a concrete claim about THIS specific subject. Generic intros die at the critic gate.
  • craftCritic Gates for Mass ContentWhen you generate thousands of pages, run a second LLM as critic. Specificity, differentiation, helpfulness — score before save.
  • craftImagen over Stock PhotosGenerate brand-specific images at the moment of need. Stock photos make every site look the same.
  • craftPDFs as React ComponentsCustomer-facing PDFs are real React, not Word docs exported. Quality is the product, regardless of price tier.
  • businessSolo-Founder PortfolioRun multiple brands instead of one bet. Diversifies revenue without diluting attention if AI is your team.
  • businessDeep Domains, Not Wide NetworkDepth beats breadth. Compound the ones that ship.
  • businessBuilding in PublicShip in the open. Treat the audience as part of the team. Lessons compound when you write them down.
  • businessCash Before VanityProfit, runway, conversion — not page views, follower counts, or PR. Track money first, attention second.
  • businessRunway as Decision FrameEvery spend, every hire, every pivot evaluated against runway. The number that makes other numbers matter.
  • shippingKISS, YAGNI, Rule of ThreeSimplest thing that works. No premature abstraction. Extract on the third occurrence, not the second.
  • shippingFail Fast, Fix FasterSurface failures loudly. Type errors, build errors, validator errors — all should scream, not whisper.
  • shippingTests as DesignWrite the test in the same pass as the code. The test forces the interface to be usable, not just typeable.
  • shippingStop Short of PerfectionPolish the path users will walk; leave the rest as known-incomplete. Perfectionism is a tax on shipping.
  • shippingDocument While ShippingUpdate the doc in the same commit as the code. Stale docs are worse than missing docs.