[ketzu]

The descriptions seem a little bit scarce for me. Like others I also wonder who's the intended audience. For 1k/year/repository I need to be quite serious with a project, but that project needs to be basically non existent (otherwise I would probably have the basis already) while also being somewhat serious.

Formulating it a bit provocative: In what way is it more than an expensive cookiecutter repository? (Especially with a one-time-use policy per subscription)

[davegaeddert]

> Like others I also wonder who's the intended audience.

Me too — trying to figure that out!

> but that project needs to be basically non existent while also being somewhat serious

Super interesting point. I've helped integrate it into some existing projects and it is not fun.

> In what way is it more than an expensive cookiecutter repository?

I don't disagree with this. A couple differences in my mind are support (that you're paying for, and has an incentive to be as helpful as possible) and on-going updates (a cookiecutter won't help you integrate improvements over time, as far as I know).

Pricing is totally an experiment right now, and I shot high on purpose. Suggestions?

[vincentmarle]

The project seems really well put together but until you figure out your ideal target customer (and their needs) I would hold off on pricing it too high. Maybe offer it for free, get some learnings and as you add more value and get more clarity on your target group, you can then ramp up the price?

[davegaeddert]

Yeah I've been considering that. Probably more likely that I'll lower the price, learn some things, then ramp it up. Free feels hard to reverse and the difference between "I wouldn't pay at all" vs "I'd pay less than that, but something" is pretty big (and important to me unless I figure out another way for the project to get paid for).

[yunohn]

> Free feels hard to reverse

Absolutely true. I remember the amount of hate HN spewed at Docker for making their desktop app /paid/ for Corp users.

[ketzu]

Thanks for the reply!

> support (that you're paying for, and has an incentive to be as helpful as possible) and on-going updates (a cookiecutter won't help you integrate improvements over time, as far as I know).

That's true, good point.

> Suggestions?

I think it highly depends on your target audience.

[davegaeddert]

Also this

> Things like django-coookiecutter are great, but they only really cover the project structure.

https://news.ycombinator.com/item?id=30781528

[tthun]

tailwind ui had a Goldilocks pricing imho .. you could always offer discounts case by case if prospect can fill out a form.

[davegaeddert]

Good point. Still trying to figure out who is interested, but I'll probably add a student/educational discount too. (If anybody sees this and wants that, let me know.)