Aakash GuptaHe Built a $2M/Yr One-Person Business - Steal His Playbook
CHAPTERS
- 0:00 – 2:47
Aakash and Brett’s $1M+ one-person business milestone + why Brett waited to quit
Aakash introduces the theme: two creators who crossed $1M+ revenue as solo operators. Brett shares the unusual detail that he kept a corporate job until DesignJoy was generating ~$80K/month, framing the episode around risk tolerance, simplicity, and conviction.
- •Aakash reveals his own $1M+ last-12-months milestone
- •Brett is nearing ~$2M ARR run-rate from monthly revenue
- •Both built their businesses alongside full-time jobs
- •Brett emphasizes he has no team, no pipeline, no traditional marketing
- 2:47 – 5:51
Building DesignJoy in a weekend, then juggling it for 4–5 years
Brett explains how DesignJoy was created extremely fast—essentially a weekend build with immediate customers—yet he continued to juggle it with corporate work for years. Once he finally went all-in, growth accelerated rapidly, largely due to increased focus rather than major operational changes.
- •DesignJoy started as a “Friday night to Saturday launch” project
- •He managed corporate work plus DesignJoy for ~4–5 years
- •A layoff didn’t immediately push him full-time; he still sought another job
- •After going full-time, revenue roughly doubled within a few months
- 5:51 – 7:59
Fear, founder insecurity, and the ‘this could die tomorrow’ mindset
Brett unpacks what held him back: the business felt like it appeared too quickly to be durable, and he worried it might be a trend or luck. He also discusses ongoing anxiety due to being a solo operator without traditional demand-gen systems.
- •Fast early traction felt fragile and potentially trend-driven
- •Imposter syndrome: feeling undeserving of success
- •Ongoing risk perception: no lead gen, no pipeline, no team
- •Long-term repetition built confidence and trust in sustainability
- 7:59 – 9:54
DesignJoy explained: productized design subscription (Netflix-for-design)
Brett details the core offer: a fixed monthly subscription with flexible pause/cancel, one request at a time, and fast turnaround. The model positions itself as a simpler alternative to hiring full-time or managing freelancers/agencies.
- •Fixed monthly subscription (often confused with retainer, but different)
- •Pause/cancel anytime; budget-friendly and flexible
- •One active request at a time; broad request types allowed
- •Typical delivery target ~48 business hours
- •Runs ~20 concurrent clients as a solo designer
- 9:54 – 14:02
How the packaging emerged: adapt a model, keep tools simple, raise prices with demand
Brett describes borrowing an early inspiration from a lower-end design subscription service and applying it to higher-value work (web/product/branding). He emphasizes that the business stayed operationally simple (Trello, landing page) while pricing evolved dramatically based on demand.
- •Model inspiration existed, but he adapted it upmarket
- •Operational stack stayed simple: landing page + Trello
- •Started at ~$450/month; now ~$5K/month base rate
- •Demand-based pricing: raise rates as demand rises
- •Key differentiator: cutting bloated agency process and timelines
- 14:02 – 17:05
How to replicate: prerequisites, scope discipline, and a clear productized promise
Aakash pushes for a replicable framework; Brett stresses that solo success at scale requires being both ‘good and fast’ and staying tightly scoped. He explains that productized services are essentially modern freelancing with better packaging and expectations.
- •Prerequisite: be both high-quality and fast
- •Strictly limit scope to what you can deliver efficiently
- •Start low to get adoption; increase pricing with proof + demand
- •Set a clear package + turnaround + intake system
- •Think of it as a freelance model, not necessarily an ‘agency’
- 17:05 – 20:47
Offer boundaries + delivery mechanics: what clients request and how 48-hour delivery works
Brett clarifies what’s included (branding, landing pages, product design, web dev, decks, social) and how he handles both small and huge requests without formal upfront ETAs. He explains interval delivery, breaking down large projects, and why the 48-hour window works as a buffer.
- •Core categories: branding, landing pages/websites, product design, web dev, slide decks, social assets
- •Most requests fit a 48-hour delivery window
- •Large requests are delivered in slices/intervals over time
- •No rigid upfront timeline; consistent progress keeps teams unblocked
- •Work often takes far less time than the delivery window—enabling concurrency
- 20:47 – 22:46
Work-life structure: weekends off, no vacations, and managing expectations around weekends
The conversation turns to sustainability: Brett doesn’t take vacations but does protect weekends. He explains how he navigates requests around weekends to avoid clients feeling like they’re waiting 3–4 days.
- •No vacations (by preference), but weekends are protected
- •48-hour promise is business days, with practical flexibility
- •Thursday requests often delivered Friday; weekend requests by Monday
- •He now works less than a typical full-time schedule
- •Early days (while employed) were more intense; later stabilized
- 22:46 – 24:43
Distribution in the early days: Product Hunt + Indie Hackers + communities
Brett breaks down how he got initial customers by building in public and leveraging founder-heavy communities when those channels were more effective. He credits Product Hunt and Indie Hackers as major accelerants for early traction.
- •Early channel focus: Indie Hackers + Product Hunt
- •Building in public: sharing milestones and progress to drive demand
- •Supplemented with Facebook/Slack founder groups
- •Notes Product Hunt is less effective today than back then
- •Early distribution was a ‘goldmine’ that may not exist in the same way now
- 24:43 – 28:29
One channel at a time: all-in on X (Twitter) and the platform-risk tradeoff
Brett explains his one-track approach: focus deeply on a single distribution channel at a time. Aakash reinforces how platform mastery creates outsized returns, but both acknowledge the danger of algorithm changes and reliance on one platform.
- •Brett: obsessive focus on one platform at a time
- •Today: X is the only platform he actively uses
- •Aakash: platform mastery creates huge ‘top-decimal’ advantage
- •Platform risk is real—reach can drop without changes in creator behavior
- •Brett’s background includes seeing businesses harmed by algorithm shifts
- 28:29 – 32:34
X content strategy: playing the algorithm with AI design tutorials that ‘serve’ the audience
Brett describes an evolving content playbook driven by what performs in the algorithm. He’s shifted from sharing revenue numbers to highly practical AI/design tutorials, aiming to create useful, shareable content rather than self-serving AI gimmicks.
- •Iterate content formats as algorithms change
- •Self-described ‘plays the algorithm’ rather than posting raw thoughts
- •Tutorials currently outperform everything else for consistent reach
- •Focus on AI that produces practical outcomes (textures, 3D spins, dithering, avatars)
- •Free curated packs and step-by-step breakdowns as growth engines
- 32:34 – 55:12
Live teardown + redesign: Brett’s one-shot, high-fidelity Figma workflow
Aakash challenges Brett to redesign Aakash’s high-traffic site live in Figma. Brett demonstrates his ‘one-shot’ philosophy—jumping straight into high fidelity, avoiding mood boards/wireframes, and using patterns from experience to move quickly.
- •Starts with critique: busy layout, hidden ‘No Thanks’ path, thumbnail clutter
- •Design philosophy: pick a direction fast, ship a V1, iterate only if needed
- •Works directly in high fidelity—no wireframes/sketching
- •Builds clean sections: featured post, popular posts, category organization, footer
- •Uses gradients/textures and simple components to quickly add polish
- 55:12 – 1:01:41
Thumbnails, templates, and scaling the design system without templating everything
They discuss how to handle article visuals: Brett would standardize aspect ratios and create a repeatable design language, often via a set of templates—even though he doesn’t rely on templates for core work. He contrasts tooling choices (Canva/Photoshop) and explains how he’d create a framework others can execute.
- •Recommend fixed aspect ratios and simplified, consistent blog graphics
- •Create a ‘framework’ of 10–15 layout templates for repeatability
- •Templates are for client teams to execute; Brett’s core work isn’t templated
- •Tooling discussion: Canva vs Photoshop vs Figma for asset production
- •Design ‘snaps’ into place as patterns + textures + layout systems converge
- 1:01:41 – 1:05:48
Figma hot take: too developer-focused; emerging alternatives like Paper
Brett critiques Figma’s recent direction: prioritizing developers and non-designer users over visual design innovation. He points to new tools (like Paper) that are adding more creative-native capabilities and suggests designers could switch quickly if the value is compelling.
- •Claim: ~2/3 of Figma users aren’t designers (dev/marketing growth)
- •Figma updates perceived as dev-mode/tokens-heavy rather than visual-design advances
- •Designers want bigger leaps in creative tooling
- •Mentions Paper as a Figma-like tool with more creative features (e.g., shaders)
- •Historical precedent: designers moved from Photoshop → Sketch → Figma quickly
- 1:05:48 – 1:08:59
Closing lesson: conviction + experience beats endless iterations
Aakash synthesizes the live demo into a broader takeaway: speed comes from taste, pattern memory, and commitment to a direction. Brett reinforces that heavy exposure to great design builds an internal library that enables fast, confident execution—and quick pivots when needed.
- •One-shotting reduces meetings, mood boards, and wasteful exploration
- •Deep design consumption builds an internal pattern library
- •Fast drafts can be production-ready, then refined if needed
- •If a direction is wrong, re-spin quickly instead of debating endlessly
- •Conviction + reps create the compounding advantage in solo businesses
