
Sign up to save your podcasts
Or


Pete and Andy dig into "unruggable productivity" and what it means to build software that respects the customer instead of trapping them inside a vendor's AI stack.
They connect recent 37signals ideas to their own work on Wingman and Flight Deck, arguing for agent-friendly software, clearer work surfaces, and business systems designed around control, portability, and real workflows.
## Chapters and Themes
- `00:00-05:06` Opening on 37signals, Rework, and whether software should embed its own agent or let users bring their own.
- `05:06-08:54` Why chat is a bad place for structured follow-up, and why forms may be a better primitive for agents gathering information.
- `08:54-14:17` Chats, tasks, and documents as different work surfaces with different jobs inside Flight Deck.
- `14:17-21:06` "Unruggable productivity" as positioning: software that respects you and does not hold your business hostage.
- `21:06-31:16` Venture-backed software incentives, authentic marketing, and finding a values-aligned audience instead of chasing everyone.
- `31:16-37:11` Product design tradeoffs around control, self-hosting, onboarding, and releasing sooner with a narrower target market.
- `37:11-45:03` Whether the highest leverage move is selling the tool or using it to launch workflow-native challenger businesses.
- `45:03-55:03` Examples, reflection loops, and pipeline-based automation as the real path to better AI output.
- `55:03-01:07:20` Why chat cannot be the whole interface, and why future businesses will need many constrained agents instead of one all-knowing assistant.
## Key Takeaways
- The best AI software may be agent-friendly, not agent-controlled.
- Chat is useful for exploration, but not for all forms of work.
- Software should preserve customer control instead of increasing dependency.
- Narrow markets and strong principles may beat broad generic positioning.
- Examples, reflection, and structured pipelines matter more than prompt tricks.
- Businesses will likely need multiple agents with limited context and clear boundaries.
## Notable Lines
- "Software that respects you."
- "I should not have an off switch for your business."
- "You should have the agent work where the work is."
By Other StuffPete and Andy dig into "unruggable productivity" and what it means to build software that respects the customer instead of trapping them inside a vendor's AI stack.
They connect recent 37signals ideas to their own work on Wingman and Flight Deck, arguing for agent-friendly software, clearer work surfaces, and business systems designed around control, portability, and real workflows.
## Chapters and Themes
- `00:00-05:06` Opening on 37signals, Rework, and whether software should embed its own agent or let users bring their own.
- `05:06-08:54` Why chat is a bad place for structured follow-up, and why forms may be a better primitive for agents gathering information.
- `08:54-14:17` Chats, tasks, and documents as different work surfaces with different jobs inside Flight Deck.
- `14:17-21:06` "Unruggable productivity" as positioning: software that respects you and does not hold your business hostage.
- `21:06-31:16` Venture-backed software incentives, authentic marketing, and finding a values-aligned audience instead of chasing everyone.
- `31:16-37:11` Product design tradeoffs around control, self-hosting, onboarding, and releasing sooner with a narrower target market.
- `37:11-45:03` Whether the highest leverage move is selling the tool or using it to launch workflow-native challenger businesses.
- `45:03-55:03` Examples, reflection loops, and pipeline-based automation as the real path to better AI output.
- `55:03-01:07:20` Why chat cannot be the whole interface, and why future businesses will need many constrained agents instead of one all-knowing assistant.
## Key Takeaways
- The best AI software may be agent-friendly, not agent-controlled.
- Chat is useful for exploration, but not for all forms of work.
- Software should preserve customer control instead of increasing dependency.
- Narrow markets and strong principles may beat broad generic positioning.
- Examples, reflection, and structured pipelines matter more than prompt tricks.
- Businesses will likely need multiple agents with limited context and clear boundaries.
## Notable Lines
- "Software that respects you."
- "I should not have an off switch for your business."
- "You should have the agent work where the work is."