Skip to content
Artwork for Just Now Possible
Just Now Possible · Thursday · 1 hr 6 min

Creating Aha! Builder: Concept to Code, No Engineers Required

Guests Brian De Haaff, CEO and Co-Founder, Aha! Chris Waters, CTO and Co-Founder, Aha! Sarah Moisan-Thomas, Senior Product Manager for Aha! Builder, Aha! Key Takeaways Aha! is fully bootstrapped, remote-first, and profitable—built by product people, for product people Containerized infrastructure proved too wasteful for AI app building at scale, pushing Aha! to rebuild on a single-instance, multi-tenant architecture Deterministic, pre-built components (authentication, SSO, database, email) cut token cost and guarantee reliability that AI-generated code can't A multi-phase, multi-agent pipeline—design system, then prototype, then backend—produces better outcomes than a single open-ended chat prompt As building gets easier, knowing what to build becomes the product manager's real differentiator In this episode Aha!'s 13-year bootstrapped, remote, no-salespeople business model The five-step discovery framework Aha! uses for every new product, including Builder Why their first containerized version was too slow and expensive to scale Rebuilding for a single-instance, multi-tenant architecture Reusing the agent framework and tool set originally built for "Elle"—Aha!'s roadmapping AI assistant Deterministic components for authentication, SSO, database access, and email The multi-agent, multi-phase build pipeline: design system, then prototype, then full application Enterprise governance: authentication policies, deployment guardrails, and PII/PHI considerations Why Aha! is optimizing for prototypes, proofs of concept, and internal "meta applications"—not primary line-of-business apps What's next: expanded design systems and tighter feedback loops across Aha!'s product suite Resources & Links Aha! Chapters 00:00 Meet the Aha! Team 00:19 Aha! Bootstrapped Remote Story 01:29 What Is Aha Builder 02:27 Leaders Stay Hands On 04:49 Origin and AI Shift 07:44 Why Build in Aha! 14:12 Discovery Framework 17:50 From Slides to Early Access 21:40 Proof of Concept Approach 23:36 Under the Hood Architecture 27:01 Agent Tools and UX 30:59 Deterministic Components 33:42 Skills Docs and Iteration 35:48 Higher Level Building Blocks 36:33 Knowing What To Build 38:57 Builder UX For PMs 44:10 Enterprise Governance Guardrails 47:29 What Builder Is For 50:39 PII Security And Compliance 53:15 Quality Evals And Pricing 55:29 V8 Isolates Architecture 58:22 Multi Agent Build Pipeline 01:01:14 Roadmap Design And Feedback 01:03:01 PMs Engineers And PR Flow 01:05:52 Wrap Up And Thanks

0:00-1:06:34

transcript

No transcript — this publisher did not publish one.

show notes

Guests

  • Brian De Haaff, CEO and Co-Founder, Aha!
  • Chris Waters, CTO and Co-Founder, Aha!
  • Sarah Moisan-Thomas, Senior Product Manager for Aha! Builder, Aha!

Key Takeaways

  • Aha! is fully bootstrapped, remote-first, and profitable—built by product people, for product people
  • Containerized infrastructure proved too wasteful for AI app building at scale, pushing Aha! to rebuild on a single-instance, multi-tenant architecture
  • Deterministic, pre-built components (authentication, SSO, database, email) cut token cost and guarantee reliability that AI-generated code can't
  • A multi-phase, multi-agent pipeline—design system, then prototype, then backend—produces better outcomes than a single open-ended chat prompt
  • As building gets easier, knowing what to build becomes the product manager's real differentiator

In this episode

  • Aha!'s 13-year bootstrapped, remote, no-salespeople business model
  • The five-step discovery framework Aha! uses for every new product, including Builder
  • Why their first containerized version was too slow and expensive to scale
  • Rebuilding for a single-instance, multi-tenant architecture
  • Reusing the agent framework and tool set originally built for "Elle"—Aha!'s roadmapping AI assistant
  • Deterministic components for authentication, SSO, database access, and email
  • The multi-agent, multi-phase build pipeline: design system, then prototype, then full application
  • Enterprise governance: authentication policies, deployment guardrails, and PII/PHI considerations
  • Why Aha! is optimizing for prototypes, proofs of concept, and internal "meta applications"—not primary line-of-business apps
  • What's next: expanded design systems and tighter feedback loops across Aha!'s product suite

Resources & Links

Chapters

00:00 Meet the Aha! Team 00:19 Aha! Bootstrapped Remote Story 01:29 What Is Aha Builder 02:27 Leaders Stay Hands On 04:49 Origin and AI Shift 07:44 Why Build in Aha! 14:12 Discovery Framework 17:50 From Slides to Early Access 21:40 Proof of Concept Approach 23:36 Under the Hood Architecture 27:01 Agent Tools and UX 30:59 Deterministic Components 33:42 Skills Docs and Iteration 35:48 Higher Level Building Blocks 36:33 Knowing What To Build 38:57 Builder UX For PMs 44:10 Enterprise Governance Guardrails 47:29 What Builder Is For 50:39 PII Security And Compliance 53:15 Quality Evals And Pricing 55:29 V8 Isolates Architecture 58:22 Multi Agent Build Pipeline 01:01:14 Roadmap Design And Feedback 01:03:01 PMs Engineers And PR Flow 01:05:52 Wrap Up And Thanks

links1