[alexdanilowicz]

1. We're using Sonnet 3.7 for the first prompt. I've noticed with some prompts that require lots of files it can be PAINFULLY slow. Our servers also might be getting slammed from the HN traffic. We have a "fast" mode that uses 3.5 that you can toggle and that's the default for editing, however, it won't be as visually rich. We need to improve the loading experience for sure. One big UX/UI difference between our product and others is that our preview is always shown versus on other tools the code is always shown. Other tools will stream in the code to mask the load time. We used to do that, and will likely bring it back.

2. Re pricing - that's the most important feedback we'll hear all day! We used to have a "contact us for pricing" tier, but have found self-serve a lot more effective and easier to scale.

We actually still only 2 people, just my co-founder and me. When you say "custom value-based" are you referring to a "contact us for pricing" tier?

[nrmitchi]

> When you say "custom value-based" are you referring to a "contact us for pricing" tier?

Ya. Not saying that it's applicable to everyone (or even most people), but really once a team gets above maybe 20+ people actively using this, they're not going to blink at $1200/month (good for you now, but you'll be leaving a ton of money on the table, and it's hard to adjust expectations later).

Maybe capping the size of a team on the "pro" plan would be an inbetween, but it's something to talk to your customers about.

Happy to chat more directly; my email's in my bio.

[alexdanilowicz]

> Maybe capping the size of a team on the "pro" plan would be an inbetween

That's interesting. We already have teams with 20+ folks on it today at very large companies, but haven't thought about that type of stuff too much - have been laser-focused on core product building. I think in the early days we spent a little too much time tweaking minor pricing plan details. You're right though we are now at a point where we are very likely leaving money on the table.

For example, "centralized billing" on our platform only exists because it was the result of a feature request from a larger customer.

P.S. I emailed you, but it bounced!

[nrmitchi]

Email you too; thanks for the heads on the bounce. Should be fixed now.

[sizzle]

Don’t change your pricing model based off n=1 go do some market research first.

Don’t kill your adoption rates in the critical early days of growth.

[alexdanilowicz]

We have been around for 2 years and at one point had "contact us for pricing", so don't worry not changing anything on n=1!