Sarah Butler

Hey PH We're Baptiste & Samuel, and next week we're launching Capacity Desktop a free Mac app that turns plain English into real apps, built and stored on your machine.

The bet everyone tells us is wrong: move away from credits system. You plug in your own Claude / GPT / Open Router key and pay your provider at cost. Our take is that you feel the credits system is unfair, you never know what a failed fix loop just cost you, and you feel the tool profits from your retries.

For me, I feel like the hardest part isn't choosing between tools like React, Firebase, Railway, etc, it's really deciding which parts of the stack I should commit most of my time and tokens early and which ones may become painful to replace later.

Do you stick with a familiar stack and avoid overthinking it, design around expected scale from day one, let your coding agent influence the architecture, or start with the cheapest setup and migrate later? Also, curious which early technical choice has saved you the most time, and which one you wish you probably shouldn't have overthinked on.

Genuine question. I keep meeting operators with a warm list, a good offer, and no abandoned-cart flow. Or a welcome series that's one email long and just stops.

If that's you which one is it, and what's actually stopping you? The time, the build, or not knowing what email 3 is supposed to say?

Asking because I've been building for exactly this.