4 ms·
I was thinking of building this for Next.js in a very similar way. I love the fact that this exists for a different stack! I think your implementation of the pr
by Ethan_Mick 3y ago
I was thinking of building this for Next.js in a very similar way. I love the fact that this exists for a different stack! I think your implementation of the project template is definitely the way to go. As a customer, when I buy something to jump-start me, I want it to be as clean and simple as possible. Generating the project from a configuration handles that nicely.
Outside of the generator itself, what have you found most beneficial for converting customers and convincing people to buy? Documentation? Videos? The community access?
- czue 3y agoYeah, as I mention in the post, I started without the template option and just couldn't stomach how much extra cruft would be lying around... Re: converting, it's a mixed bag and often hard to know. But some factors that customers have mentioned: 1. Positive comments (there have been a few threads about Pegasus/boilerplates on HN and Reddit where people have had good things to say). 2. Some trust in me. I have a blog, write Django guides, publish YouTube videos, am active on Twitter, have been on podcasts, etc. I think people realizing that the creator is a serious person who has at least some credibility goes a long way. 3. I think the high-quality docs and regular release history help a lot to convince people it's a solid product. Those are the first ones that come to mind. But honestly, I'm lucky if I find out why a customer picked me! And I'm sure some just google "django saas boilerplate" and buy the first thing that comes up, which, thankfully, at the moment is Pegasus.
- Ethan_Mick 3y agoThanks for the response! It sounds like (in a good way) there's no shortcut. You build something, make it better, make it great, and talk about it for a long time to establish credibility. Probably a good lesson in there for everyone.