Fizzy Q's and A's

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 Questions Answered

• •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.