Skip to main content

Pricing All Guests

KR

Kimberly Rhodes

Kimberly Rhodes is the host of The Rework Podcast, where she guides conversations with 37signals co-founders Jason Fried and David Heinemeier Hansson about sustainable business practices. Her interviewing style draws out practical insights on company culture, product development, and the philosophy of building profitable, calm companies that reject hustle culture and venture-backed growth pressures.

45episodes

1podcast

Featured On 1 Podcast

The Rework Podcast

45 episodes

All Appearances

45 episodes

Product walkthroughs, the next open source product & other listener questions

The Rework Podcast

Feb 4, 202627 minHost

AI Summary

→ WHAT IT COVERS 37signals cofounders Jason Fried and David Heinemeier Hansson answer listener questions about creating product demo videos without scripts, their approach to open sourcing products like Writebook after Fizzy, how they use both Basecamp and Fizzy internally for different workflows, and why adding delightful UI touches matters even in enterprise software. → KEY INSIGHTS - **Unscripted product demos:** Record product walkthroughs in single takes without scripts by doing four to five dry runs first, then letting the interface naturally guide the narrative. Start over only if the first minute contains errors, but continue through any later mistakes to maintain authentic flow and enthusiasm rather than robotic precision. - **Video production philosophy:** Avoid over-rehearsing product demonstrations because trying to remember scripted lines kills enthusiasm and makes presenters think from behind instead of performing live on the edge. One Hotwire video took eight to nine hours to produce with perfect precision but performed worse than naturally flowing versions with minor imperfections and human stumbles. - **Dual tool workflow:** Use Fizzy exclusively for bug tracking and issues while keeping Basecamp for broader project work, creating separation where Fizzy notifications only pertain to problems needing immediate attention. This single-purpose approach provides clearer mental context than mixing issue notifications with thirty active Basecamp projects, though both tools connect through Basecamp doors for easy navigation. - **Open source strategy:** Writebook will follow Fizzy into open source after establishing proper bandwidth to process community contributions, as merging contributor code requires significant time investment. The payoff from open sourcing Fizzy has been substantial, with developers creating AI style guides based on 37signals code quality and building their own applications using production-grade examples without negative consequences. - **Enterprise software delight:** Add playful UI touches and Easter eggs to business software without seeking management approval, following the proud tradition of developers shipping delightful details that leadership never notices anyway. The satisfaction comes partly from the small rebellious act of improving user experience despite organizational resistance, and customers may eventually speak up about enjoying these human touches. → NOTABLE MOMENT David Heinemeier Hansson advocates treating software tools like mechanical keyboards or clothing choices, where switching between options provides valuable variety without needing to identify one perfect solution. He personally rotates between different keyboards and computers throughout the week simply because the tactile variation and design differences make work more enjoyable, applying the same philosophy to using multiple productivity tools. 💼 SPONSORS None detected 🏷️ Product Demos, Open Source Software, Workflow Design, Enterprise UX, Software Development

Read Full Summary Listen

Give it a name

The Rework Podcast

Jan 28, 202622 minHost, 37signals team

AI Summary

→ WHAT IT COVERS Jason Fried and David Heinemeier Hansson explain their product naming philosophy at 37signals, detailing how names like Fizzy, Basecamp, and Kamal emerged. They emphasize that naming comes first, drives momentum, and matters more than securing perfect domains. The episode covers twenty-five years of naming decisions across products and open source projects. → KEY INSIGHTS - **Name-first development:** Jason requires a product name before building begins, treating it as fuel for the project. Without an early name, he considers it a signal that something fundamental is missing from the concept. The name serves as an anchor to grab onto and pull through the development process, making it essential rather than optional. - **Sound over concept:** When choosing between Boxcar and Fizzy, the team prioritized phonetic appeal over conceptual tightness. Fizzy sounds more pleasant and fluid to say, even though Boxcar had stronger conceptual ties to Chicago train yards and the product's card-based interface. Pleasant pronunciation beats perfect conceptual alignment when names need daily repetition. - **Domain flexibility strategy:** 37signals launched four major products without exact domain matches: basecamphq.com, backpackit.com, campfirenow.com, and highrisehq.com. They waited ten years before acquiring basecamp.com. The lesson: avoid over-indexing on domain availability unless giving out email addresses like hey.com, where short domains matter. Pick the right name first. - **Legal naming boundaries:** David's open source tool Maersk triggered a trademark dispute with the Danish shipping company, resulting in police serving papers at Copenhagen Airport. The maximum penalty was seven thousand dollars under Danish law, revealing how different legal systems handle trademark conflicts. He renamed it Kamal, which became his preferred choice anyway. - **Momentum makes names permanent:** Instagram, Yahoo, Slack, and WhatsApp succeeded with names that would never pass a rebranding committee ten years later. Names become inseparable from products through momentum and familiarity. The takeaway: choose something you enjoy saying for your early-stage project, then let success make it legitimate rather than overthinking initial perfection. → NOTABLE MOMENT David shares his pronunciation philosophy for Umachi, deliberately dropping the r sound despite how people naturally read it. He compares himself to the GIF creator who insists on JIF pronunciation, arguing that English and Danish contain many words where spelling and sound disconnect. He claims the right to define pronunciation for his own creations. 💼 SPONSORS None detected 🏷️ Product Naming, Brand Strategy, Domain Acquisition, Trademark Law, Startup Branding

Read Full Summary Listen

Launch day — a little logistics, a lot of luck

The Rework Podcast

Jan 7, 202631 minHost

AI Summary

→ WHAT IT COVERS 37signals cofounders Jason Fried and David Heinemeier Hansson discuss launching their new product Fizzy, covering launch timing strategy, variable scope negotiation, open source positioning, and how algorithmic social feeds have fundamentally changed product marketing dynamics. → KEY INSIGHTS - **Launch timing flexibility:** Pick internal deadlines but avoid public date announcements unless required by trade shows or media buys. This prevents unnecessary pressure and anticlimactic delays since customers aren't actively waiting for your launch anyway, unlike limited-supply physical products. - **Variable scope with fixed dates:** Set launch dates months in advance to drive development focus. As the deadline approaches within six weeks, tunnel vision naturally clarifies what's essential versus nice-to-have, making it easier to cut features and ship the product's core essence without becoming precious about ideas. - **Algorithmic feed impact:** Large follower counts no longer guarantee reach on platforms like X, LinkedIn, and Instagram. Even dedicated followers miss posts unless content goes viral, breaking the traditional jab-jab-right-hook model where 99 giving posts earn one promotional ask. Email lists now provide more reliable direct audience access. - **Open source as marketing:** Releasing code open source creates permission to share technical insights and contributions repeatedly without appearing to constantly shill products. This dual-purpose content strategy works better in algorithmic feeds that penalize pure promotional posts while rewarding educational or entertaining content that can go viral. → NOTABLE MOMENT During the live launch call, the team discovered they were accidentally DDoS-ing themselves with a bug causing continuous page refreshes. They watched request rates skyrocket in real-time and scrambled to fix it while hundreds of users signed up simultaneously. 💼 SPONSORS None detected 🏷️ Product Launches, SaaS Marketing, Social Media Algorithms, Open Source Strategy

Read Full Summary Listen

Software as art

The Rework Podcast

Aug 6, 202524 minHost

AI Summary

→ WHAT IT COVERS 37signals cofounders Jason Fried and David Heinemeier Hansson explain how they build opinionated software with strong perspectives, refuse popular feature requests like Gantt charts, and develop product vision through execution rather than upfront planning. → KEY INSIGHTS - **Refusing Customer Requests:** Basecamp rejected Gantt chart requests for 20 years despite thousands of customer demands because their core premise defines project management as primarily communication, not charts and graphs, demonstrating commitment to product vision over feature accumulation. - **Taste Development Process:** Product principles emerge from execution, not planning. Build first based on gut instinct and accumulated taste, then extract and articulate the underlying principles afterward. The implicit feeling precedes explicit documentation, making retrospective analysis more honest than forward planning. - **Fisher Price Easy Standard:** 37signals uses this specific mental model to test whether features meet their clarity goals. Having concrete phrasings like this provides a measurable benchmark to evaluate whether current work aligns with intended product perspective and user experience aspirations. - **Blue Ocean Strategy Framework:** Companies succeed by making deliberate trade-offs, not excelling at everything. Google demonstrates massive profitability while scoring zero on customer service, proving organizations must choose which parameters to optimize and which to sacrifice when defining their competitive position. → NOTABLE MOMENT David reveals Gmail has displayed a fuzzy, incorrect icon for three months because users assume Google will not respond to bug reports, illustrating how a company worth billions deliberately sacrifices customer service to optimize other priorities. 💼 SPONSORS None detected 🏷️ Product Development, Software Design Philosophy, Customer Service Strategy, Opinionated Software

Read Full Summary Listen

BONUS EPISODE: 37signals is moving to Omarchy

The Rework Podcast

Aug 8, 202535 min30x7 Signals Team

AI Summary

→ WHAT IT COVERS 37signals CTO David Heinemeier Hansson announces the company's three-year transition from Mac to Linux using Omarchy, their new open-source distribution built on Arch Linux and Hyperland for developers. → KEY INSIGHTS - **Tiling Window Managers:** Hyperland automatically organizes windows without mouse dragging—opening new applications splits screen space automatically into grids, eliminating manual window management and creating a keyboard-centric workflow that increases productivity for developers. - **Three-Year Hardware Transition:** 37signals mandates technical teams switch to Linux over three years aligned with natural hardware replacement cycles, allowing gradual adaptation while maintaining productivity. New hires start on Linux immediately, existing staff transition as equipment refreshes. - **Dogfooding Company Tools:** Companies should use their own distributions like they use their own products. 37signals built Omarchy with internal development scripts from Shipyard, so technical teams must run it to improve it faster, similar to how they mandate Rails for web applications. - **Breaking Computing Habits:** Expect three days of frustration and two weeks of reduced productivity when switching operating systems after twenty years of muscle memory. Initial motivation from frustration must transform into attraction to new capabilities to sustain the transition successfully. → NOTABLE MOMENT Hansson describes his initial resistance to Linux as something for a different kind of nerd, only to discover eighteen months later that his twenty-year Mac addiction required a painful detox period before revealing superior development capabilities. 💼 SPONSORS None detected 🏷️ Linux Development, Open Source Software, Developer Tools, Operating Systems

Read Full Summary Listen

Titles, tenure, and paths don't matter

The Rework Podcast

Aug 13, 202526 minHost

AI Summary

→ WHAT IT COVERS 37signals cofounders Jason Fried and David Heinemeier Hansson explain their hiring process for designers and programmers, emphasizing how actual work samples outweigh credentials, tenure, and prestigious company backgrounds when evaluating candidates. → KEY INSIGHTS - **Portfolio creation without clients:** Candidates can redesign existing company websites like FedEx or banks without permission to demonstrate skills and build portfolios with recognizable brand names, bypassing the need for prestigious work history or formal client relationships. - **Take-home project structure:** Designers receive five-day projects with broad prompts and zero research or requirements, allowing assessment of creative range and thinking process. Programmers complete four-to-six hour tests, enabling evaluation of 75 candidates from 2,200 applicants for four positions. - **CV unreliability at scale:** Resumes frequently contain half-truths about individual impact versus team contributions, especially from large tech companies. Work samples reveal whether candidates can operate at 37signals' pace and scale, which differs fundamentally from billion-user platforms requiring different skill applications. - **Open source as proof:** Programmers can contribute to existing open source projects relevant to target companies, creating undeniable work records in three months. Companies may already use these contributions before candidates apply, providing immediate credibility without requiring years of professional experience. → NOTABLE MOMENT David reveals that despite 22 years evaluating candidate code, he still cannot predict who will succeed based on cover letters and resumes alone. One-third of hires do not make it past one year, demonstrating no foolproof hiring method exists. 💼 SPONSORS None detected 🏷️ Hiring Process, Work Portfolios, Open Source Contribution, Junior Developers

Read Full Summary Listen

Total transparency

The Rework Podcast

Sep 3, 202518 minHost/Moderator

AI Summary

→ WHAT IT COVERS 37signals cofounders Jason Fried and David Heinemeier Hansson explain their approach to radical business transparency, sharing work-in-progress designs, code, and company decisions publicly without legal approval. → KEY INSIGHTS - **Chef philosophy for sharing:** Companies should emulate chefs who publish complete recipes without fearing competition, recognizing that sharing blueprints attracts attention and customers rather than enabling competitors to replicate success. - **Work-in-progress documentation:** Recording and sharing unfinished designs, code reviews, and problem-solving processes in real-time provides more authentic learning value than polished retrospectives where details get misremembered or sanitized. - **Timing over content restrictions:** The main regret from years of transparency was announcing their no-politics policy too quickly after internal communication in 2021, not the decision itself—suggesting brief delays matter more than censoring information. → NOTABLE MOMENT The cat JPEG incident from 2011 taught them a permanent lesson when operations staff revealed a customer's uploaded filename publicly, crossing the line from sharing company data to exposing customer information. 💼 SPONSORS None detected 🏷️ Business Transparency, Product Development, Company Culture

Read Full Summary Listen

Balancing it all

The Rework Podcast

Jul 30, 202530 minHost

AI Summary

→ WHAT IT COVERS Jason Fried and David Heinemeier Hansson explain how they maintain work-life balance over 25 years in business by rejecting meeting culture, protecting calendar availability, and refusing to compress success into unhealthy sprints. → KEY INSIGHTS - **Calendar protection:** Executives should maintain the most open schedules in their organization to preserve availability for reacting to fires, customer needs, and serendipitous opportunities rather than packing calendars with efficiency-focused meetings that eliminate flexibility and responsiveness. - **Meeting elimination:** Strip away unnecessary work like strategy meetings, decks, and excessive processes that prevent actual productive work. Most executives need only a handful of essential tasks per month or quarter, not eighty-hour weeks filled with obligations that don't move the business forward. - **Time ownership:** Basecamp prevents employees from viewing others' calendars or scheduling on their behalf, requiring explicit permission requests for time. This friction protects against the corporate pattern where most calendar items are initiated by others, leaving employees with leftover scraps of their own time. - **Sustainable success:** Running a business as a multi-decade marathon rather than a five-to-seven-year sprint prevents the burnout and damaged relationships that come from ignoring health, family, and hobbies. Enjoy success incrementally throughout your twenties, thirties, and forties instead of postponing rewards indefinitely. → NOTABLE MOMENT David challenges the common excuse of lacking time for hobbies by pointing out most people spend four-plus hours daily on screens doom-scrolling, revealing how time scarcity is often about choices rather than actual availability for meaningful pursuits. 💼 SPONSORS None detected 🏷️ Work-Life Balance, Calendar Management, Meeting Culture, Sustainable Business

Read Full Summary Listen

Finding focus

The Rework Podcast

Sep 17, 202524 minHost

AI Summary

→ WHAT IT COVERS Jason Fried and David Heinemeier Hansson explain their approach to maintaining focus, handling procrastination as a decision-making tool, practicing negative visualization, and protecting uninterrupted work time by avoiding scheduled commitments. → KEY INSIGHTS - **Procrastination as clarity:** Procrastination reveals true priorities rather than being inherently negative. Tasks you genuinely want to complete get done immediately, while delayed tasks signal misalignment with interests or need for reframing to become engaging work. - **Negative visualization practice:** Weekly practice of imagining worst-case scenarios, from project failures to personal catastrophes, builds resilience without creating anxiety. Walking through specific consequences reveals most outcomes are manageable, reducing fear of taking calculated risks. - **Calendar protection strategy:** Avoid scheduling commitments more than one week in advance. Future obligations create false enthusiasm that transforms into resentment when the date arrives, disrupting flow states and preventing deep work on current priorities. - **Attention versus time:** Single one-hour meetings destroy entire workdays not through duration but by fragmenting attention. Starting the day knowing an interruption comes at 1pm prevents diving into complex problems, triggering procrastination on meaningful work. → NOTABLE MOMENT David Heinemeier Hansson procrastinated on his Rails World keynote preparation by building Umachi, then incorporated the new project into his presentation. He scheduled only one week for slides after spending weeks on development, finding compressed timelines produce better results. 💼 SPONSORS None detected 🏷️ Focus Management, Stoic Philosophy, Calendar Strategy, Deep Work

Read Full Summary Listen

Built on Trust

The Rework Podcast

Oct 8, 202528 minThirty Seven Signals Team Member

AI Summary

→ WHAT IT COVERS 37signals cofounders explain how they built a high-trust organization over 20 years, allowing employees unrestricted access to delete tasks, approve their own expenses, and work remotely without micromanagement or permission-based workflows. → KEY INSIGHTS - **Expense autonomy:** Employees receive company credit cards with one policy—spend wisely on job necessities—without approval processes or spending limits below several thousand dollars, reviewed only after the fact if concerns arise. - **Data access protocols:** While most operations run on trust, customer email access in HEY requires multi-layer encryption, documented reasons for unlocking data, and secondary team review to protect sensitive information despite trusting employees. - **Remote work oversight:** Managers gauge work quality and pace through weekly planning questions, daily work summaries, and six-week heartbeat reports rather than monitoring time spent at desks or using surveillance tools. - **Cloud cost reallocation:** Exiting cloud services saved two million dollars annually, which flows through profit-sharing to employees, creating financial incentive to spend cautiously on unnecessary expenses while investing in quality tools. → NOTABLE MOMENT During final hiring stages, routine verification revealed a candidate had fabricated their entire work history and positions—the only instance of deliberate fraud in 25 years, caught because their exceptional skills seemed inconsistent with deception. 💼 SPONSORS None detected 🏷️ Remote Work Management, Organizational Trust, Employee Autonomy, Expense Policy

Read Full Summary Listen

Refining before release

The Rework Podcast

Oct 1, 202525 minHost from Thirty Seven Signals team

AI Summary

→ WHAT IT COVERS Jason Fried explains 37signals' approach to finalizing Fizzy, their new product, covering authentication decisions, onboarding design, team structure changes, and why they reject roadmaps in favor of real-time customer learning. → KEY INSIGHTS - **Authentication simplification:** 37signals switched from their traditional Launchpad system with passwords and two-factor authentication to magic link authentication via email, reflecting changed user expectations and reducing complexity for both company and customers at launch. - **Onboarding timing strategy:** Product interface videos and walkthroughs must wait until final design decisions are made, even if this creates last-minute scrambles, because material changes like button repositions invalidate early documentation and waste production effort. - **Feature withholding based on data:** The FizzyAsk AI search feature exists internally but won't launch publicly because new users lack sufficient data to make it useful. Features should only ship when customers can actually benefit from them, not to showcase capabilities. - **Roadmap rejection philosophy:** Companies should sell products based on current capabilities, not future promises. Roadmaps create false obligations to outdated ideas and prevent teams from responding to real usage patterns and emerging customer needs discovered post-launch. → NOTABLE MOMENT Jason reveals he personally onboarded every customer for Know Your Company with half-hour individual tours, an unsustainable approach that worked for an expensive product targeting business owners but contradicts their typical self-service philosophy for all other products. 💼 SPONSORS None detected 🏷️ Product Development, User Onboarding, Product Launch Strategy, Feature Prioritization

Read Full Summary Listen

Soft openings aren't just for restaurants

The Rework Podcast

Nov 12, 202515 minHost

AI Summary

→ WHAT IT COVERS 37signals prepares to launch Fizzy by inviting handpicked beta testers in staged batches, starting with five to twenty people before expanding to thousands. → KEY INSIGHTS - **Staged rollout strategy:** Start with 5-20 handpicked users familiar with your products to catch blind spots in onboarding and login flows, then expand to 2,000+ email signups before public launch to minimize risk. - **Beta as forcing function:** External testers create urgency that clarifies priorities by forcing teams to focus only on what must be fixed before strangers use the product, eliminating debates over long feature lists. - **Community feedback structure:** Use shared chat spaces like Campfire or Discord for early testers instead of individual emails to build community, encourage participation, and surface issues multiple people experience but wouldn't report alone. → NOTABLE MOMENT The team delayed their planned beta launch by a week because inviting outsiders revealed they weren't actually ready, demonstrating how external pressure surfaces issues internal testing misses completely. 💼 SPONSORS None detected 🏷️ Product Launch, Beta Testing, Software Development

Read Full Summary Listen

Revisiting the good old days

The Rework Podcast

Oct 22, 202516 minHost/Team Member at Thirty Seven Signals

AI Summary

→ WHAT IT COVERS Jason Fried explains why 37signals shifted from single-product focus in 2018 to building multiple products simultaneously, including Basecamp, HEY, Fizzy, Campfire, and Writebook today. → KEY INSIGHTS - **Team structure for multiple products:** Small two-person teams (one programmer, one designer) enable 60-person company to run five to six simultaneous product teams without requiring massive headcount growth. - **Expansion versus contraction cycles:** Companies should alternate between focused contraction periods and creative expansion phases based on team energy and capacity, not rigid long-term plans or external pressure to maintain consistency. - **Idea management philosophy:** Write down ideas only for immediate consideration, not future backlogs. New ideas deserve equal consideration regardless of documentation timing, preventing stale roadmaps from blocking better opportunities that emerge later. → NOTABLE MOMENT Fried admits feeling stretched thin while simultaneously preferring that sensation, acknowledging some team members likely think the company tackles too much but maintains it remains energizing without requiring overtime. 💼 SPONSORS None detected 🏷️ Product Strategy, Team Structure, Business Philosophy

Read Full Summary Listen

Fizzy Q's and A's

The Rework Podcast

Oct 29, 202527 minHost

AI Summary

→ WHAT IT COVERS Jason Fried and David Heinemeier Hansson answer questions about Fizzy, their upcoming issue tracking product, addressing concerns about competing with Basecamp, discussing software aesthetics and saturated colors, and explaining their cautious approach to AI features. → KEY INSIGHTS - **Product differentiation through feel:** Software selection works like test-driving cars or holding knives—users know within 10 minutes if a product feels right through tactile elements, flows, and interface grip, not feature comparison charts that reduce products to meaningless checkboxes. - **Aesthetic design as competitive advantage:** Most business software looks identical, following leaders like Slack or Gmail. Fizzy uses saturated colors, gradients, and texture instead of muted pastels or monochrome designs, creating distinct visual identity that influences user mood and daily enjoyment of the tool. - **AI feature threshold requirements:** AI features need 99% accuracy in end-user applications to avoid frustration, unlike developer tools where 80% accuracy remains useful. Fizzy removed early AI experiments because features working only 80-87% of the time create annoyance that overshadows the successful interactions. - **Scope-based product coexistence:** Basecamp runs entire businesses with comprehensive tools while Fizzy focuses specifically on issue and bug tracking with smaller scope. Both products serve different needs within organizations, similar to how email and project management tools coexist despite overlapping capabilities. → NOTABLE MOMENT David describes visiting car dealerships with just 7% purchase intent to test-drive vehicles, often discovering he hated cars he thought he wanted or loved unexpected options—illustrating how hands-on experience reveals preferences that specifications and research cannot predict. 💼 SPONSORS None detected 🏷️ Product Design, Software Aesthetics, AI Implementation, Product Strategy

Read Full Summary Listen

Traditional marketing doesn't work for us

The Rework Podcast

Oct 15, 202530 minHost

AI Summary

→ WHAT IT COVERS 37signals cofounders explain why three attempts at traditional paid advertising failed despite spending millions, with customer acquisition costs reaching tens of thousands per customer for their project management software Basecamp. → KEY INSIGHTS - **Branded keyword trap:** Buying your own brand name on Google appears profitable but cannibalizes organic clicks—users who click paid ads would have clicked free organic results instead, making the spend wasteful without incremental customers. - **Product-market fit for ads:** Impulse-buy products like sneakers and games convert well through social media ads, but complex B2B software requiring organizational adoption has astronomical acquisition costs that rarely justify the spend at small-to-medium business price points. - **Earned versus bought audiences:** Building an authentic audience through consistent teaching, writing, and sharing over years generates sustained customer interest, while content calendars and instrumental marketing produce disengaged ghost audiences that ignore corporate posts despite large follower counts. - **Testing baseline incrementality:** Run dark periods by turning off all paid advertising for one month to measure true impact—eBay discovered tens of millions in annual ad spend produced zero incremental results when accidentally disabled. → NOTABLE MOMENT The team discovered their most successful marketing came from unpaid placements like a New York Times feature and podcast appearance that generated measurable spikes and baseline growth, outperforming millions spent on Meta and Google ads combined. 💼 SPONSORS None detected 🏷️ B2B Marketing, Customer Acquisition Cost, Organic Marketing, Founder-Led Marketing

Read Full Summary Listen

Out of Office, Together

The Rework Podcast

Nov 19, 202530 minHost

AI Summary

→ WHAT IT COVERS 37signals holds twice-yearly company meetups for their remote team, alternating between North America and Europe. They require minimal scheduled sessions, focusing instead on trust-building and high-intensity collaborative work periods together. → KEY INSIGHTS - **Minimal required sessions:** Only two mandatory daytime sessions across the week—Monday all-hands and Thursday peer appreciation—plus one dinner. Everything else remains optional, allowing spontaneous collaboration and preventing schedule fatigue that undermines relationship-building goals. - **Trust battery charging:** In-person meetups every six months recharge workplace relationships that drain over time in remote settings. Without regular face-to-face contact, written communication reads harsher and colleagues become avatars rather than humans, degrading collaboration quality and workplace satisfaction. - **Strategic release timing:** Schedule major product launches and account closures during meetups to transform mundane digital tasks into shared ceremonies. 37signals launched products and executed their cloud exit on-stage during meetups, creating collective memorable moments that strengthen team bonds. - **Location strategy matters:** Rural retreat settings keep teams together more than city meetups where people scatter to explore. Whistler's remote location increased spontaneous interactions and personal connections despite longer travel times, particularly for European employees requiring eighteen-hour journeys. → NOTABLE MOMENT David argues that complaining about connecting flights once yearly represents extreme privilege compared to workers with daily commutes or weekly travel schedules. He emphasizes that minimal sacrifice strengthens appreciation for otherwise pampered remote work arrangements. 💼 SPONSORS None detected 🏷️ Remote Work, Team Retreats, Trust Building, Distributed Teams

Read Full Summary Listen

Picking Pricing

The Rework Podcast

Dec 3, 202535 minHost

AI Summary

→ WHAT IT COVERS 37signals cofounders Jason Fried and David Heinemeier Hansson explain their pricing philosophy across products, from per-project consulting fees to SaaS subscriptions, revealing why they cap Basecamp at $299 monthly and avoid enterprise sales. → KEY INSIGHTS - **Capping whale customers:** Basecamp limits pricing at $299 monthly for unlimited users, deliberately avoiding enterprise sales that would require salespeople, key account managers, and product features built for individual large deals rather than broad customer needs. - **Testing time horizons matter:** AB pricing tests can mislead when evaluated short-term. Basecamp's switch to $99 flat pricing showed immediate revenue gains but took four years to reveal negative viral effects from fewer signups reducing downstream customer acquisition. - **Bucket pricing reduces friction:** Highrise charged based on user ranges (0-15 people, 15-30 people) rather than per-seat, eliminating the constant internal debate about whether adding each individual user justifies the incremental cost that per-seat models create. - **Scarcity drives premium pricing:** HEY charges $99 yearly for four-plus letter addresses, $300 for three-letter addresses, and $1000 for two-letter addresses. The limited namespace creates real estate value that justifies higher prices compared to crowded email providers. → NOTABLE MOMENT When Twitter used Campfire as a whale customer, 37signals raised prices to $5000 monthly hoping to scare them off. Twitter stayed, creating an unwanted enterprise relationship that reinforced their philosophy of structurally preventing large account temptation. 💼 SPONSORS None detected 🏷️ SaaS Pricing, Enterprise Sales, Pricing Psychology, Product Strategy

Read Full Summary Listen

When is enough, enough?

The Rework Podcast

Dec 10, 202518 minHost

AI Summary

→ WHAT IT COVERS 37signals cofounders Jason Fried and David Heinemeier Hansson explain their philosophy for deciding when product version one is complete before launching Fizzy. → KEY INSIGHTS - **Aerodynamic Design Principle:** Version one should be the smoothest, tightest shape possible where every extra feature creates drag. Remove features that stick out even if nice to have, focusing on essential functionality only. - **Half Not Half-Assed:** Ship fewer features executed excellently rather than many rough features. The Concept2 rower exemplifies this with LCD screens and rubber buttons instead of touchpads, dominating its market for twenty years unchanged. - **Late-Stage Feature Removal:** 37signals pulled an audacious database architecture from Fizzy just before launch despite months of development work, choosing proven technology over risky innovation to ensure stable launch and maintain confidence. → NOTABLE MOMENT David finds greater satisfaction in deleting code than writing it, spending months perfecting a five-line reduction that smooths the codebase, comparing it to aging and appreciating trees. 💼 SPONSORS None detected 🏷️ Product Development, Software Launch Strategy, Feature Prioritization

Read Full Summary Listen

Rapid Fire Questions with Jason and David

The Rework Podcast

May 14, 202521 minHost

AI Summary

→ WHAT IT COVERS Jason Fried and David Heinemeier Hansson answer rapid-fire questions about essential software tools, underrated founder skills, mind changes about company growth, ignored customer requests, and upcoming products including Fizzy and major Basecamp updates. → KEY INSIGHTS - **Writing as leverage:** Founders underestimate writing as the most scalable influence tool compared to in-person rallying or video. Written ideas and vision travel farther than any other medium, making it more valuable than becoming a media personality. - **Gut-driven decisions:** Founders waste time seeking certainty through endless feedback loops. Trust educated guesses over consensus-building. Business rarely offers obvious right answers, so develop comfort making decisions without complete information and testing outcomes in real time. - **Growth pressure origins:** Attempts to scale bigger often stem from ego, insecurity, or proving capability to others rather than genuine business needs. Boredom after twenty years can drive experimentation, but work required for growth may not align with work founders actually want to do. - **Testing convictions:** Periodically try the opposite of long-held beliefs to validate whether they remain valid. 37signals tested engineering managers and growth targets after decades of opposition, ultimately confirming original approach but gaining valuable perspective through experimentation. → NOTABLE MOMENT David explains how switching from Mac to Linux forced him to discover Obsidian, revealing he was completely oblivious to superior note-taking options because Apple Notes kept him out of the market for alternatives for years. 💼 SPONSORS None detected 🏷️ Founder Skills, Product Development, Company Growth, Decision Making

Read Full Summary Listen

Picking Priorities

The Rework Podcast

Apr 16, 202512 minHost

AI Summary

→ WHAT IT COVERS 37signals cofounders explain their six-week priority cycles for product development, rejecting long-term roadmaps in favor of making decisions close to execution time. → KEY INSIGHTS - **Six-week cycles:** Teams commit to priorities for only six weeks at a time, then reassess based on current knowledge rather than guesses made months earlier, preventing outdated commitments. - **Decision timing advantage:** Making priority decisions immediately before work begins provides significantly more accurate information about product needs, team capacity, and customer requirements than advance planning allows. - **Flexible reallocation:** When a team member departed, 37signals immediately paused one of two concurrent products rather than stretching resources thin, demonstrating priorities can shift when circumstances change. → NOTABLE MOMENT Both founders admit they generate exciting new ideas every Monday but restrain themselves from disrupting mid-cycle work, only introducing changes at six-week intervals. 💼 SPONSORS None detected 🏷️ Product Management, Agile Development, Priority Setting

Read Full Summary Listen

Say No by Default

The Rework Podcast

Oct 16, 202433 minHost

AI Summary

→ WHAT IT COVERS Jason Fried and David Heinemeier Hansson explain why defaulting to no on product features, pricing complexity, and business commitments prevents regret, reduces technical debt, and maintains product simplicity over 25 years at 37signals. → KEY INSIGHTS - **Commitment costs compound:** Saying yes feels cheap now but creates expensive future work through unwinding failed experiments, maintaining legacy code, supporting deprecated features, and working around accumulated complexity that limits future product decisions and development velocity. - **Translation baggage example:** Adding eight language translations in 2008 created ongoing drag where every feature required multiple translation steps before launch, slowing development velocity significantly despite only marginal customer acquisition gains, illustrating how yes decisions create permanent operational overhead. - **The tomorrow test framework:** Before accepting any commitment, ask whether you would say yes if execution was required tomorrow instead of months away. This mental model reveals true costs and prevents calendar regret from commitments that feel easy when distant but burdensome when immediate. - **Dependency debt accumulates:** Reusing infrastructure between products like their Signal ID login system created interdependencies that prevented individual products from having optimal user experiences. Self-contained products with minimal cross-dependencies enable better design decisions and easier maintenance over time. → NOTABLE MOMENT David admits both founders still regularly fall into saying yes despite knowing better, committing to features or engagements months out that they regret when the work arrives, demonstrating how difficult maintaining no discipline remains even for experienced practitioners. 💼 SPONSORS None detected 🏷️ Product Management, Technical Debt, Business Strategy, Decision Making

Read Full Summary Listen

Principles of Communication

The Rework Podcast

Oct 23, 202427 minHost

AI Summary

→ WHAT IT COVERS Jason Fried and David Heinemeier Hansson explain their 30-point guide to internal communication at 37signals, covering principles like avoiding immediate response expectations, using long-form writing over chat, and shipping content quickly without approval processes. → KEY INSIGHTS - **Publishing velocity:** Write and ship content in one day rather than spending three days perfecting it, because inspiration is perishable and additional editing time often adds minimal value while killing momentum and completion likelihood. - **Response time expectations:** Never require immediate responses unless it's a true emergency. The expectation of instant replies is toxic to productivity. Use phone calls specifically for urgent matters, making the medium itself signal importance rather than assuming all messages demand speed. - **Clarity in high-stakes communication:** When discussing important topics, use simple, direct language with minimal surface area for misinterpretation. Avoid flowery writing that can be perceived multiple ways, as ambiguous words will typically be understood in the most harmful interpretation possible. - **Time as decision tool:** Let heated discussions cool over days rather than forcing immediate resolution. Arguments that feel critical in the moment often become inconsequential within 24 hours, and waiting allows people to reconsider positions and acknowledge when others are right. → NOTABLE MOMENT The founders describe having no approval process between them after 20 years of trust. They publish directly without legal review or editorial back-and-forth, believing the alternative to shipping imperfectly is never shipping at all. 💼 SPONSORS None detected 🏷️ Internal Communication, Remote Work, Asynchronous Communication, Writing Culture

Read Full Summary Listen

What are You Replacing?

The Rework Podcast

Nov 13, 202429 minHost

AI Summary

→ WHAT IT COVERS Jason Fried and David Heinemeier Hansson explain why successful product development requires understanding what customers must abandon, not just what features you offer, using Basecamp's competition against email as their primary example. → KEY INSIGHTS - **Habit of the Present:** Products rarely compete against obvious competitors but against existing behaviors like email, meetings, and phone calls. Customers must break established habits before adopting new solutions, making the replacement cost higher than the adoption benefit in most cases. - **Email as Baseline Competitor:** Basecamp identifies email as their primary competitor because it has zero onboarding friction and works instantly for project kickoffs. The challenge becomes competing against email's flat entry ramp while solving its backloaded problems like finding information and adding people mid-project. - **Customer Language Research:** Jobs-to-be-done research reveals how customers describe problems using phrases like things falling through the cracks rather than technical terms like project management. This language guides both product positioning and marketing messaging that resonates with actual pain points customers experience daily. - **Return Customer Validation:** Survey data shows 40 percent of Basecamp customers left for competitors like Notion, Asana, or Monday, then returned after experiencing those alternatives. This pattern validates that customers need to understand their actual problems before appreciating solutions that address root causes versus surface-level feature comparisons. → NOTABLE MOMENT David compares product evaluation to TV shopping, where manufacturers maximize brightness to win in-store comparisons despite ruining image quality at home. Reviewers universally recommend disabling these settings, illustrating how checkbox features often mislead buyers who lack context to evaluate true quality. 💼 SPONSORS None detected 🏷️ Product Development, Jobs-to-be-done, Customer Behavior, Product Marketing

Read Full Summary Listen

V1 is for Us

The Rework Podcast

Oct 30, 202433 minHost

AI Summary

→ WHAT IT COVERS 37signals cofounders Jason Fried and David Heinemeier Hansson explain their principle of building version one products exclusively for internal company needs, using real problems rather than imagined customer use cases to guide development. → KEY INSIGHTS - **Internal Use Cases Only:** Version one must solve actual problems the company experiences daily, not hypothetical external scenarios. 37signals scrapped six months of work on Highrise CRM when they realized they were building for imagined customers instead of their own needs. - **Quality Validation Through Dogfooding:** Teams can only gauge solution quality when solving problems they personally experience. When 37signals forced technical staff to use Writebook despite missing search functionality, the internal rebellion revealed exactly what features needed development for reference materials. - **Post-Launch Patience:** Wait weeks or months after launching before acting on customer feedback. Users bring expectations from previous tools and need time to adapt. Hey email still receives archive button requests years later from users conditioned by Gmail habits. - **Problem vs Solution Requests:** Listen to underlying user problems, not their proposed solutions. When Hey users demanded delete buttons, 37signals identified the real problem as not wanting to see dealt-with emails, then created cover art feature allowing users to replace email lists with family photos. → NOTABLE MOMENT David admits sending an angry email five seconds after using a Tesla with swipe-based gear shifting, demanding the traditional stock back, only to realize weeks later the new system actually worked faster than physical levers he expected. 💼 SPONSORS None detected 🏷️ Product Development, SaaS Strategy, Customer Feedback, Dogfooding

Read Full Summary Listen

AI, Employee Equity, and Other Listener Questions

The Rework Podcast

Nov 20, 202426 minHost

AI Summary

→ WHAT IT COVERS 37signals cofounders Jason Fried and David Heinemeier Hansson answer listener questions about managing AI tools without cloud infrastructure, prioritizing multiple products with small teams, and their equity-free profit sharing compensation model. → KEY INSIGHTS - **AI Infrastructure Strategy:** Companies can separate steady-state operations from experimental AI workloads. Run consistent infrastructure on owned hardware while renting cloud GPUs only for spiky training jobs or unproven features, avoiding long-term rental costs for resources needed constantly. - **Multi-Product Development:** Small teams should work sequentially on products rather than splitting resources across simultaneous development. 37signals built four products with eight people by dedicating full team attention to one product for months, then rotating, allowing products to rest six to twelve months between cycles. - **Motivation Over Resources:** The motivational factor to solve a problem you personally experience provides 2x to 10x effectiveness compared to working more hours. This intensity explains how four-person teams can compete against companies with 2,000 developers by maintaining tunnel vision and rocket fuel energy. - **Profit Sharing Model:** 37signals distributes 10% of annual profits based solely on tenure, capping at ten years. Starting at two years employment, everyone at the same tenure level receives equal profit share regardless of salary, rewarding longevity over individual performance metrics or equity lottery tickets. → NOTABLE MOMENT Hansson recalls how 37signals positioned Microsoft Project as their public enemy in Basecamp's early days, causing concern inside Microsoft that four people were creating competitive pressure against their teams of thousands, demonstrating asymmetric warfare through pure motivation and focus. 💼 SPONSORS None detected 🏷️ Product Management, Profit Sharing, Cloud Strategy, Team Structure

Read Full Summary Listen

A Product Pivot

The Rework Podcast

Dec 4, 202422 minHost

AI Summary

→ WHAT IT COVERS 37signals pivoted their HEY email feature mid-development from keyboard navigation to Power Through New, a stacked view that lets users process multiple emails sequentially within the original appetite timeline. → KEY INSIGHTS - **Problem over solution:** When technical limitations revealed inconsistent keyboard navigation behavior across different email contexts, stepping back to ask "what are we actually trying to do" opened the solution space to better alternatives beyond the initial implementation. - **Implementation difficulty as signal:** Encountering hard technical problems during development indicates the design needs deeper examination. When a feature works inconsistently across contexts, that complexity smell suggests the conceptual model itself requires rethinking rather than explaining away edge cases. - **Executive engagement timing:** Product owners reviewing work at week four of a cycle can authorize pivots with remaining time buffer. Too early misses implementation insights; too late eliminates pivot opportunity. The two-week inter-cycle buffer provides additional flexibility for last-minute refinements. - **Building on existing patterns:** The team completed the pivot within appetite by adapting HEY's existing read-together feature rather than inventing from scratch. Leveraging prior art with modified buttons and layout enabled rapid prototyping and shipping within approximately ten days post-decision. → NOTABLE MOMENT Jason compared inconsistent feature behavior to confusing parking signs with multiple conditional rules. When software requires explanations for why functionality works in some contexts but not others, that indicates poor design regardless of technical justification. 💼 SPONSORS None detected 🏷️ Product Development, Feature Pivoting, Software Design, Agile Methodology

Read Full Summary Listen

Question Your Customers

The Rework Podcast

Nov 6, 202418 minHost

AI Summary

→ WHAT IT COVERS Jason Fried and David Heinemeier Hansson explain why 37signals asks customers one open-ended survey question instead of lengthy multiple-choice questionnaires to gather actionable feedback. → KEY INSIGHTS - **Single question surveys:** Ask one open-ended question with a large text field rather than 30 multiple-choice questions to achieve higher response rates and richer, more actionable customer insights. - **Customer language mining:** Open-ended responses reveal how customers naturally describe problems, providing exact terminology for feature naming and marketing copy that resonates authentically with target audiences. - **Survey frequency:** Limit customer surveys to one or two times per year with single questions, while maintaining daily customer service interactions to avoid survey fatigue and preserve response quality. → NOTABLE MOMENT Forty-one percent of Basecamp users had tried the product twice, leaving for competitors like Monday, Asana, or ClickUp before returning after finding alternatives too complicated or unused. 💼 SPONSORS None detected 🏷️ Customer Research, Product Development, Survey Design

Read Full Summary Listen

The End of Year Junk Drawer

The Rework Podcast

Dec 11, 202419 minHost

AI Summary

→ WHAT IT COVERS 37signals explains their December work structure: unstructured time for bug fixes, cleanup, and exploration between six-week cycles, preparing for January's productive quarter. → KEY INSIGHTS - **Year-end buffer time:** Build in unplanned weeks between structured cycles to clear technical debt, fix accumulated bugs, and let teams self-direct cleanup work before starting fresh. - **Seasonal rhythm variation:** Alternate between tight six-week cycles with formal planning and loose December wandering time. Contrast in work pace prevents burnout and enables creative exploration. - **Email marination technique:** Let non-urgent emails sit for three weeks in a reply-later folder. Initial guilt about brief responses fades, enabling two-line replies instead of exhausting novels. → NOTABLE MOMENT One founder admits his past addiction to inbox zero caused constant interruptions and overly long responses, which Hey's design philosophy specifically helps him avoid today. 💼 SPONSORS None detected 🏷️ Work Cycles, Project Management, Email Management

Read Full Summary Listen

Your Competition is Your Costs

The Rework Podcast

Nov 27, 202430 minHost

AI Summary

→ WHAT IT COVERS Jason Fried and David Heinemeier Hansson explain why controlling internal costs matters more than obsessing over competitors, using Basecamp and Hey as examples of profitable businesses built through disciplined spending and healthy margins. → KEY INSIGHTS - **Cost structure flexibility:** Basecamp operates profitably with tens of thousands of paying customers while Gmail needs billions because their cost structures differ. Match your expenses to your market segment, not your competitor's scale or business model requirements. - **Support cost ratio:** Hey reduced customer support costs from six percent to three percent of revenue after realizing an eight-dollar monthly product cannot sustain seven dollars in support expenses. Calculate support costs as percentage of price to maintain healthy margins per product. - **Cloud computing expenses:** Thirty Seven Signals identified AWS as their second-largest expense after salaries, with Hey initially spending thirty dollars of every hundred in revenue on cloud costs. They reduced this to ten dollars through infrastructure changes, demonstrating computing costs warrant regular scrutiny. - **Portfolio approach:** Use cash cow products like Basecamp to fund shooting stars like Hey and tolerate dogs like heritage applications. This Michael Porter framework allows patient investment in new ideas without quarterly pressure, enabled only by controlling overall company margins and expenses. → NOTABLE MOMENT David reveals his ratio test for spending decisions: calculating exactly how many personal dollars each business expense represents from his ownership stake, creating immediate gut-level assessment of whether any purchase genuinely delivers proportional value to the company. 💼 SPONSORS None detected 🏷️ Cost Management, Business Profitability, SaaS Economics, Cloud Infrastructure

Read Full Summary Listen

Hire When It Hurts

The Rework Podcast

Jan 15, 202520 minHost

AI Summary

→ WHAT IT COVERS 37signals cofounders explain their hiring philosophy of waiting until pain is felt before adding staff, avoiding premature hiring and underemployed workers creating unnecessary work. → KEY INSIGHTS - **Hire on pain not anticipation:** Wait until quality slips or critical work cannot be completed before hiring. Assess hurt over months not weeks to distinguish terminal frustration from temporary spikes. - **Underemployed specialists create harmful work:** Hiring roles like general counsel without forty-two weeks of necessary work leads to unnecessary complexity, longer contracts, and wasted resources like 125k on needless international trademark registrations. - **Run with slack not to bone:** Evolution from extreme leanness where losing one person creates crisis to maintaining modest margin. Sustainable hurt threshold is five out of ten over extended period, not eight or nine. → NOTABLE MOMENT The company hired an in-house counsel who had only five hours of necessary weekly work, leading to thirty-five hours spent creating unnecessary legal complexity and policies nobody needed. 💼 SPONSORS None detected 🏷️ Hiring Strategy, Organizational Efficiency, Startup Operations

Read Full Summary Listen

Seven Shipping Principles

The Rework Podcast

Jan 8, 202523 minHost

AI Summary

→ WHAT IT COVERS 37signals cofounders Jason Fried and David Heinemeier Hansson explain their seven shipping principles for building software at a sustainable pace, focusing on quality standards, confidence calibration, and ownership accountability. → KEY INSIGHTS - **Quality threshold:** Ship only good work, not minimally viable products. This standard gives teams permission to stop projects that aren't ready, even after weeks of development. Aim for 80-95% shipping rate, not 100%, to maintain proper standards. - **Confidence calibration:** Apply testing rigor proportionate to criticality. Billing systems require extensive testing and reviews, while minor features need less ceremony. Avoid shooting sparrows with cannons by using one-size-fits-all protocols that waste time on trivial features or underprotect critical ones. - **Post-launch ownership:** Developers and designers must monitor error trackers and handle support issues after shipping their work. This feedback loop prevents isolation from reality and calibrates future confidence levels. The two-week cooldown period provides time for cleanup without jumping to new projects. - **Premise over implementation:** When development becomes hard, question the underlying problem rather than perfecting a flawed solution. Step back from specific solutions like keyboard shortcuts to identify the core need, which may reveal simpler approaches using existing capabilities that better serve user goals. → NOTABLE MOMENT David argues shipping rates approaching 100% indicate standards are too low, not excellence in execution. Teams should expect some projects to fail the quality bar, creating healthy tension between ambition and realistic assessment of readiness. 💼 SPONSORS None detected 🏷️ Software Development, Product Management, Quality Standards, Shipping Principles

Read Full Summary Listen

The Biggest Customer Conundrum

The Rework Podcast

Dec 18, 202423 minHost

AI Summary

→ WHAT IT COVERS Jason Fried and David Heinemeier Hansson explain why landing large enterprise customers creates dependencies that force software companies to build for specific clients rather than their entire customer base, compromising product quality and business independence. → KEY INSIGHTS - **Customer concentration risk:** When one or two large clients represent disproportionate revenue, companies cannot afford to lose them and become consulting firms building custom features rather than products for their entire market, eliminating strategic independence and product vision control. - **Enterprise sales transformation:** Selling to enterprises requires hiring sales teams, navigating three-month sales cycles with legal and security reviews, and managing 42-page questionnaires. This fundamentally changes company culture from product-focused builders to sales-driven organizations with renewal negotiations and discount expectations. - **Pricing power dynamics:** After charging Twitter only one hundred dollars monthly for 5,000 users on Campfire, raising the price to five thousand dollars created an obligation to provide personal concierge service. This demonstrates how underpriced whale customers create unsustainable service expectations. - **Buyer-user misalignment:** Enterprise purchasing managers, lawyers, and security teams make software decisions without using the product themselves. This drives vendors to optimize for checkbox features that satisfy procurement requirements rather than usability, explaining why enterprise software often performs poorly. → NOTABLE MOMENT Thirty Seven Signals discovered Twitter was consuming half their Campfire system resources for just one hundred dollars monthly. When they raised the price fifty-fold to five thousand dollars, Twitter immediately agreed, revealing how enterprise customers operate under completely different pricing expectations. 💼 SPONSORS None detected 🏷️ Enterprise Sales, SaaS Business Models, Customer Concentration Risk, Product Development Strategy

Read Full Summary Listen

Increasing Capacity

The Rework Podcast

Mar 19, 202527 minHost

AI Summary

→ WHAT IT COVERS 37signals maintains 60-person team while simultaneously developing two new products plus Basecamp and Hey, using 2-3 person product teams and strategic hiring to increase capacity without scaling headcount proportionally. → KEY INSIGHTS - **Team size optimization:** Companies between 60-80 people hit an awkward phase requiring management layers that don't pay for themselves yet. 37signals found 60 people more productive than 80, as larger size created coordination overhead that slowed velocity despite 33 percent more headcount available. - **Small product teams:** New products launch with just 2-3 person core teams plus backend support. This approach enabled 37signals to release four products with only seven total employees early on, proving small focused teams outperform larger groups for product development and iteration speed. - **Strategic hiring timing:** Hire before feeling desperate pain, not after. 37signals adds one product designer now to prevent future bottlenecks when four active SaaS products launch, giving new hires time to onboard during a merge lane rather than during crisis when products stall waiting for coverage. - **Senior talent leverage:** Junior hires create net negative productivity initially as multiple senior people redirect time from shipping to mentoring. High-performing teams need experienced managers of one who require minimal oversight. Companies accelerate by letting go of people holding the group back, not just adding more bodies. → NOTABLE MOMENT 37signals released a new product annually for four years while maintaining existing products, then consolidated everything when they realized abandoned products looked bad. Now they balance active development across multiple products without the earlier feast-or-famine approach to product attention. 💼 SPONSORS None detected 🏷️ Team Scaling, Product Development, Hiring Strategy, Organizational Design

Read Full Summary Listen

Bringing Back Free

The Rework Podcast

Mar 5, 202521 minHost

AI Summary

→ WHAT IT COVERS 37signals reintroduces a free Basecamp plan after removing it in 2015, explaining how freemium models drive organic growth through product exposure rather than immediate conversion, and why they reversed their pricing strategy. → KEY INSIGHTS - **Freemium conversion timeline:** Weekly signups more than doubled after launching free plan, with 3% higher paid conversion early on, but success measured over 2-5 year horizons rather than immediate results to account for long-term exposure effects. - **AB testing duration requirements:** Price and design tests need minimum 21 days to reach statistical significance, as daily fluctuations create false patterns. Early results frequently reverse, making premature decisions based on short-term data actively harmful to outcomes. - **Free plan structure for viral growth:** One project limit with unlimited users creates network effects where non-paying customers expose dozens of potential buyers to the product organically, generating more value than direct conversion from those free accounts. - **Margin-dependent decision making:** Companies with healthy margins should prioritize unmeasurable factors like customer experience over bean counting individual support costs, while low-margin businesses like Walmart must track every expense to survive at 4% margins. → NOTABLE MOMENT The team admits their 2015 decision to remove free plans stemmed from hubris after ten years of success, failing to recognize an entire generation of potential customers aged 10-20 would enter the market never having heard of Basecamp. 💼 SPONSORS None detected 🏷️ Freemium Strategy, Pricing Experiments, Product Growth, AB Testing

Read Full Summary Listen

Build a business that runs without you

The Rework Podcast

Mar 26, 202529 minHost

AI Summary

→ WHAT IT COVERS Jason Fried and David Heinemeier Hansson explain how they built 37signals to operate independently of their constant presence, contrasting sustainable business design with entrepreneurial burnout and the transition from hands-on founders to strategic leaders. → KEY INSIGHTS - **Hiring for autonomy:** Build a team of competent people with good character who can execute without micromanagement, creating space for them to step up by stepping back from daily operations and giving them forty hours weekly to practice their craft instead of attending meetings. - **Founder value timing:** Recognize your differential value appears when changing company direction—launching new products, making major technical decisions—not maintaining current trajectory. The organization can handle icebergs while traveling toward established destinations; founders set new GPS coordinates for novel directions. - **Sustainable work habits:** Maintain forty-hour work weeks from the beginning rather than hundred-hour sprints, allowing gradual reduction to thirty-seven hours over twenty years. Early all-in habits become identity traps that make stepping back impossible after a decade of neglecting relationships, health, and hobbies. - **Process over outcomes:** Design work around enjoying daily tasks for eight hours, not just celebrating results. Entrepreneurs who dislike their day-to-day operations rarely sustain businesses beyond three to five years, regardless of trajectory or success metrics, because forcing unenjoyable work daily proves unsustainable long-term. → NOTABLE MOMENT David describes early years when missing calls meant servers stayed down until he could fix them remotely from vacation, contrasting with current operations where he reads incident reports afterwards while the team handles outages independently—a shift from indispensable to strategically valuable. 💼 SPONSORS None detected 🏷️ Business Operations, Founder Transition, Sustainable Growth, Delegation Strategy

Read Full Summary Listen

Blogging Isn't Dead

The Rework Podcast

Feb 5, 202515 minPodcast Host

AI Summary

→ WHAT IT COVERS Principal programmer Jorge Manrubia explains how 37signals runs their developer blog with no editorial process, focusing on authentic technical content that shares real production code publicly. → KEY INSIGHTS - **No Editorial Process:** Anyone at 37signals can publish without approval or assigned topics. Authors write only when they have something meaningful to share, with no required cadence or SEO-driven content strategy. - **Share Production Code:** 37signals publishes actual code snippets from their commercial products in technical articles. This transparency differentiates them and builds audience trust without revealing competitive advantages through limited code samples. - **Writing Clarifies Thinking:** Technical writing helps authors structure complex problems and learn while documenting. The process transforms unclear thoughts into clear understanding, making writing valuable for the author before considering audience benefits. → NOTABLE MOMENT Jorge describes how sharing details of a Friday email server crisis in HEY resonated strongly with readers, demonstrating that audiences value authentic problem documentation over polished success stories. 💼 SPONSORS None detected 🏷️ Technical Blogging, Developer Marketing, Content Strategy

Read Full Summary Listen

Roles at the company, staying involved as a founder & other listener questions

The Rework Podcast

Mar 12, 202533 minPodcast Host

AI Summary

→ WHAT IT COVERS 37signals cofounders Jason Fried and David Heinemeier Hansson explain their unconventional company structure, including which roles they eliminated, why designers code their own work, and how they structure equity without traditional venture capital. → KEY INSIGHTS - **Eliminated roles:** 37signals operates without project managers, middle management, salespeople, in-house legal, or business development. These roles create work that pulls productive employees into unnecessary projects rather than adding value, reducing overall company capability and speed. - **Designer implementation:** Designers at 37signals write all their own HTML, CSS, and JavaScript. Two-person teams (one designer, one programmer) can take features from concept to production independently, creating faster feedback loops and higher job satisfaction than specialized handoff processes. - **Hire when it hurts:** New roles require ten concrete tasks the person will complete in month one, not fuzzy anticipatory needs. Speculative hiring for future growth creates overhead and invented work, while pain-based hiring ensures immediate value and prevents premature complexity. - **LLC profit sharing:** 37signals uses an LLC structure with profit sharing and a 10% liquidity pool for employees based on tenure, avoiding complicated equity cap tables. This works when not raising venture capital or underpaying employees with equity promises. → NOTABLE MOMENT Jason Zimdars and David spent six hours designing and implementing new product features together in real-time, making progress that would take other teams several days due to handoff delays between separate design and implementation roles. 💼 SPONSORS None detected 🏷️ Company Structure, Organizational Design, Equity Compensation, Product Development

Read Full Summary Listen

Why we choose profit

The Rework Podcast

Apr 2, 202521 minHost

AI Summary

→ WHAT IT COVERS 37signals cofounders Jason Fried and David Heinemeier Hansson explain their 25-year strategy of maintaining profitability over growth, taking money off the table regularly, and how profit margins create business freedom and customer stability. → KEY INSIGHTS - **Profit as freedom:** Profitable companies operate without investor approval, allowing founders to follow hunches and experiment freely. Losses stay contained within the profit pool, enabling quick pivots without external justification or board consensus on strategic direction. - **Take money off the table early:** Entrepreneurs should extract profits regularly rather than reinvesting everything back into the business. Small companies face near-zero long-term survival odds, so shifting money into diversified investments like index funds reduces risk while the business operates. - **10% profit share model:** 37signals introduced a profit-sharing pool five years ago that distributes gains to all employees, creating company-wide discipline around spending decisions. This approach makes everyone conscious of cloud costs and equipment investments, reinforcing sustainable financial habits throughout the organization. - **Reliability as product feature:** Sustained profitability enables 37signals to promise customers their products will remain available indefinitely, even if development stops. This end-of-internet guarantee differentiates them in markets where venture-backed competitors may disappear when funding dries up or priorities shift. → NOTABLE MOMENT David contrasts his risk approach with Elon Musk's biography, noting he would never mortgage everything or invest his last dollars into a venture. SpaceX would have failed five times under his leadership, demonstrating that successful entrepreneurs exist across different risk tolerance spectrums. 💼 SPONSORS None detected 🏷️ Bootstrapping, Profit Margins, Business Sustainability, Founder Compensation

Read Full Summary Listen

Eat your own dog food

The Rework Podcast

Apr 23, 202521 minHost

AI Summary

→ WHAT IT COVERS 37signals cofounders Jason Fried and David Heinemeier Hansson explain their dogfooding practice of using products internally with real data before public release, driving feature decisions and product quality through direct team experience. → KEY INSIGHTS - **Real data requirement:** Teams must use products with actual work data, not test scenarios or lorem ipsum placeholders, to expose edge cases like image cropping issues and flow problems that only surface under genuine usage conditions. - **Early uncomfortable adoption:** Start internal usage before features feel ready, layering in more users gradually while everyone tolerates incomplete functionality. This discomfort drives learning about what's missing and what works better than existing solutions being replaced. - **Designer autonomy through code:** Designers work directly in running software rather than Figma mockups, making micro-decisions about flows and features they encounter daily. This proximity to problems produces better solutions than top-down specifications covering every screen in advance. - **Neglected flows expose gaps:** Sign-up processes and other infrequently used features degrade because teams don't encounter them regularly. Force quarterly reviews of these critical first-impression touchpoints to maintain quality standards across the entire product experience. → NOTABLE MOMENT The team abandoned Highrise 2 development despite strong market demand because neither founders nor staff actively manage customer relationships anymore. Two decades without client work left them unable to dogfood CRM software effectively or authentically. 💼 SPONSORS None detected 🏷️ Product Development, Dogfooding, Software Design, Internal Testing

Read Full Summary Listen

By the Numbers

The Rework Podcast

May 21, 202523 minHost

AI Summary

→ WHAT IT COVERS 37signals co-founders Jason Fried and David Heinemeier Hansson explain why they eliminated their full-time data analyst role, how they approach product development without quantitative projections, and which business metrics actually matter. → KEY INSIGHTS - **Data analyst elimination:** After two analysts over multiple years, 37signals discovered heavy data analysis rarely changed their decisions. They now handle occasional analytics through their finance lead using AB testing software, avoiding full-time analysis that produces interesting but unusable insights. - **Product launch philosophy:** 37signals builds new products like Fizzy without revenue projections or success metrics. They view experiments as worthwhile even if they fail because new projects cure boredom, enable fresh thinking, and generate learnings that transfer to existing products. - **Cost reduction aesthetics:** Treating expense management like editing prose creates margin and freedom. Reducing line items from twenty-five to fourteen provides psychological lightness and operational flexibility, though cutting too lean eliminates the value of activities entirely, requiring balance around B-plus efficiency. - **Conversion rate reality:** Rigorous analysis of Basecamp usage patterns revealed only obvious conclusions like people who use Basecamp with others stay longer. The search for a holy grail metric similar to Facebook's three-photo upload trigger produced no actionable single conversion driver. → NOTABLE MOMENT The team calculated that changing their Highrise marketing page without running tests or checking conversion rates for six months resulted in a 10 percent drop in signups, costing the company approximately 2.5 million dollars in lost revenue. 💼 SPONSORS None detected 🏷️ Data Analytics, Product Development, Business Metrics, Profitability Management

Read Full Summary Listen

Ignoring the competition, the next wave of CEOs & other listener questions

The Rework Podcast

May 28, 202524 minHost

AI Summary

→ WHAT IT COVERS Jason Fried and David Heinemeier Hansson answer listener questions about ignoring competitors in the AI era, whether young CEOs will dominate tech, and how to identify when team members need help. → KEY INSIGHTS - **Competition strategy:** Focus resources on customer needs rather than chasing competitors, since competitors pay nothing while customers fund the business. Copying competitor outputs without understanding their thinking guarantees second place and misses opportunities to differentiate through unique strengths and perspective. - **Technology pace reality:** Major technology shifts occur roughly once per decade—Internet in 1995, iPhone in 2007, AI in 2020s. HTML from 1995 still functions today. Most perceived rapid change is actually incremental fads or irrelevant noise, not fundamental paradigm shifts requiring constant adaptation. - **Age advantage paradox:** Younger founders possess a superpower through ignorance and arrogance—believing they can build anything quickly propels them to start. This lack of baggage lets them approach solved problems from new angles, often discovering overlooked solutions that create market opportunities despite existing competitors. - **Mentor accessibility principle:** Successful people already share their best insights publicly through podcasts, articles, and social media. One-on-one mentorship rarely reveals secret knowledge unavailable elsewhere. Sample wisdom from multiple sources remotely rather than seeking direct access, then apply learnings independently to your specific context. → NOTABLE MOMENT David refuses to give advice to his younger self, arguing that robbing yourself of first-time experiences and youthful arrogance would eliminate the ignorance-fueled confidence that drives entrepreneurs to attempt ambitious projects they might otherwise consider impossible. 💼 SPONSORS None detected 🏷️ Competition Strategy, Generational Leadership, Mentorship Myths, Team Management

Read Full Summary Listen

Building in Public

The Rework Podcast

Jun 11, 202520 minHost from Thirty Seven Signals team

AI Summary

→ WHAT IT COVERS Jason Fried explains 37signals' approach to building products in public through unedited videos and design reviews, sharing work-in-progress features, design iterations, and internal decision-making processes for their new product Fizzy. → KEY INSIGHTS - **Pre-launch momentum building:** Share product development 6 weeks before launch through blog posts or videos to build anticipation, similar to movie trailers releasing multiple previews. This creates eager customers asking for early access rather than cold launching to an unprepared audience. - **Avoid future promises:** Never commit to specific delivery dates or product announcements publicly. 37signals announced two products but canceled Know It All mid-development, teaching them to say they're working on something without guaranteeing timelines. Use vague terms like "a few months" instead of concrete dates. - **Real feedback requires real usage:** Ignore feedback from people watching demo videos since they only see fragments without full context. Wait until version one launches and users actually interact with the product daily to collect meaningful, actionable feedback worth implementing in future iterations. - **Show incremental design changes:** Document small adjustments like notification card height, color additions, or 15-pixel spacing tweaks that accumulate into great products. Most companies only show polished final results, hiding the 8+ iterations that evolved into the shipped version, missing educational opportunities. → NOTABLE MOMENT Jason records all product walkthrough videos in single takes without editing, including moments when features break or he clicks wrong buttons, deliberately showing the messy reality of building unfinished software rather than creating polished marketing content. 💼 SPONSORS None detected 🏷️ Product Development, Building In Public, Software Design, Transparency

Read Full Summary Listen

The case for cover lettters

The Rework Podcast

Jun 4, 202522 minHost

AI Summary

→ WHAT IT COVERS Jason Fried explains why 37signals requires cover letters for all job applications, how they screen 1000+ candidates by evaluating writing quality first, and detecting AI-generated submissions through pattern recognition. → KEY INSIGHTS - **Cover letter priority:** 37signals reviews cover letters before resumes, requiring applicants to demonstrate writing ability and genuine interest in the specific role rather than generic job hunting, immediately filtering out candidates who cannot communicate clearly in writing. - **AI detection method:** When reviewing 1000+ applications, patterns emerge in phrasing, structure, and punctuation that reveal AI-generated content. Using AI as an editing assistant after writing is acceptable, but having AI write the entire letter is grounds for rejection. - **Standing out strategy:** Only 10% of applicants put in extra effort beyond basic requirements, and 5% go significantly further. Small additional work like designing a custom presentation or writing a thoughtful personalized letter dramatically increases chances in competitive hiring markets. - **Application timing:** Most applications arrive in a curve pattern with high volume at opening, low middle period, and massive spike before deadline. Submitting at the last second signals poor planning and risks technical failures that result in automatic rejection regardless of circumstances. → NOTABLE MOMENT Fried dismisses resume claims like redesigning Amazon.com or increasing sales 30% as likely false, assuming applicants were among thousands involved or present during changes rather than directly responsible, making personalized cover letters the only reliable first impression. 💼 SPONSORS None detected 🏷️ Hiring Process, Cover Letters, AI Detection, Written Communication

Read Full Summary Listen

Open Source Outside the Box

The Rework Podcast

Dec 17, 202525 minHost

AI Summary

→ WHAT IT COVERS 37signals cofounders explain their open source philosophy and debut of Fizzy as both SaaS and open source product simultaneously. → KEY INSIGHTS - **Open Source Foundation:** 37signals builds everything on open source infrastructure (Linux, Ruby, databases), creating moral obligation to contribute back to community that enabled their success. - **Code Quality Hygiene:** Releasing code publicly forces better practices - developers take more pride in work when others can inspect it, leading to cleaner, more maintainable codebases. - **Dual Distribution Model:** Fizzy launches as both SaaS service and open source software with OSASI license, reserving only commercial SaaS rights while allowing unlimited self-hosting. - **Community Collaboration:** Open sourcing complete products enables external contributions on design and features, with GitHub discussions revealing unexpected user priorities like password authentication over magic links. → NOTABLE MOMENT Critics attacked Fizzy's licensing as fake open source, with one comparing it to North Korea's democracy claims, sparking heated debates. 💼 SPONSORS None detected 🏷️ Open Source, Software Development, Product Strategy, Community Building

Read Full Summary Listen

Building On the Side

The Rework Podcast

Apr 9, 202520 minHost

AI Summary

→ WHAT IT COVERS Jason Fried and David Heinemeier Hansson advise on building consulting income while developing side products, addressing market saturation and realistic expectations for entrepreneurial success. → KEY INSIGHTS - **Consulting as primary product:** Treat consulting services as your main product to sell first since acquiring clients for your expertise is significantly easier than building, launching, and sustaining a new software product with paying subscribers. - **Market timing paradox:** Building and hosting software costs almost nothing today with AI assistance and services like Stripe, but breaking through constant market noise to gain customer attention has never been more difficult or competitive. - **Success measurement framework:** Invest months not days in each product, maintain conviction it will succeed while accepting statistical likelihood of failure, and ensure every attempt makes you more skilled regardless of commercial outcome. → NOTABLE MOMENT David compares software entrepreneurship to music streaming platforms where anyone can publish globally now, but breaking out from millions of releases remains mysteriously unpredictable despite quality execution. 💼 SPONSORS None detected 🏷️ Side Projects, Consulting Business, Product Development

Read Full Summary Listen

Explore More

AI & Machine Learning Episodes Startups Episodes Marketing Episodes Best AI Podcasts (2026)Best Startup Podcasts (2026)

Never miss Kimberly Rhodes's insights

Subscribe to get AI-powered summaries of Kimberly Rhodes's podcast appearances delivered to your inbox weekly.

Start Free Today

No credit card required • Free tier available