Show HN: Wrote book that builds a SaaS boilerplate. Save weeks on side projects
builderbook.org
builderbook.org
Your site does not inspire that confidence so far. Here are some things that leave me disinclined to purchase your book even though I consider the price reasonable and am interested in the topic:
1. I don’t know who you or your co-author are, and I don’t know of any SaaS you’ve built that I’ve used or contemplated using. Have I used something you’ve made? If so, tell me!
2. Show me an example of the SaaS that the book teaches me to build. If I could experience what result I might produce, it’s easier to spend the money to learn how.
3. In light of points (1) and (2) not being satisfied, your terms of purchase are really scary. I can’t download a copy of the book to keep? You can revoke my access at any time? No refunds? I know I can reliably get my credit card company to issue a chargeback within a month or two if something’s not as promised, but I tend to read this kind of content more slowly than that. I want to make sure that I can continue to have it as I make my way through it at my own pace.
I hope none of that sounds like hostile feedback. It’s not... I’m someone who’s actively looking for this kind of resource. The price itself isn’t a problem, except that I can’t see what I’m getting, I don’t know your work well enough to know I’ll find this work useful, and you say you won’t offer a refund if I don’t find it useful. Plus you say you might revoke my online access and refuse to offer offline access.
Each chapter has ample of free excerpt (10-20% of total content), all code is public under MIT license: https://github.com/async-labs/saas
This worked well for us so far. We received less than 10 refund requests out of 850 purchases. Not sure what else to add here.
Code speaks for itself, I am just no-name guy in the cabin in the middle of the forest, with hotspot and generator. I have early-stage SaaS business with few paying customers but nothing to brag about it: https://async-await.com
If I were you I would not buy this book. At least one author is not a celebrity =)
(I’m glad to hear you’re not receiving many refund requests. Are you refunding those requests you receive? The terms page makes it look as though you are not. That would be the relevant thing to add there, relative to my questions.)
The code might speak for itself if I were already an expert. I’m not. I’m a good programmer who wants to learn more about the details of building a service offering, and I’m trying to figure out how effectively your book will teach me what I want.
The link to your SaaS business is part of what I was asking about. Is there a way for me to explore that without paying to see what it’s all about? Is that a typical example of what the book is helping me build?
> If I were you I would not buy this book. At least one author is not a celebrity =)
I’m smiling at that, but it’s not at all what I meant when I said I don’t know who you are. I didn’t mean I literally need to know who you are; I meant I was hoping to see an example of the end state your book is purporting to guide me towards. SaaS is kind of a big space.
I’m really glad it’s working well for you so far. I hope that continues, and a cabin in the middle of the forest with a hotspot and generator sounds like a great place!
---
I see many are unhappy about price. How much time would you need to build subscription API with Stripe in your SaaS project? Few hours at least if you are good and know where to look. How much is your time worth, $50 an hour? So here you go $100-$200 saved. The book paid itself. And that's just one feature out of few dozen.
For example, one of the things the application I'm imagining needs to do is send people text messages to remind them about appointments. That feels like a very "boilerplate SaaS" thing. But I can't tell if that's part of what you're selling here or not.
For another example, my app would need to send mobile push notifications. That also feels like boilerplate SaaS and I can't tell if your book covers it or not. It could break either way based on the outlines you list.
Your terms page just says "(5) We use Stripe to securely process payments. We do not offer refunds."
If I spent $200 on your book and learned what I wanted, it'd feel like a wonderful purchase. If I spent $200 and it didn't teach me the things I was seeking to learn, it'd feel like a terrible purchase. Since I don't want a refund to enter the picture anywhere, I'm trying to figure that out in advance :)
I apologize if this discussion is unwelcome. I'm mostly engaging it because I am actively seeking to purchase reading material on this specific topic, so talking about it in detail seems relevant and helpful here, as you are, at least superficially, seeking to sell what I am seeking to purchase.
This is a useful discussion - we should update terms to allow refunds within 48 hours and no refund after that. To be updated later today.
For me, books are really useful as pdfs as I can load them into eink readers. Easier on the eyes.
"If you are unhappy with a book purchase, you can request a refund by contacting team@builderbook.org. We will grant refunds within 48 hours of book purchase, no questions asked. After that point, we cannot guarantee a refund."
SaaS implies multi-tenancy and your project does not seem to offer support for that.
Irrespective to that, your book's regular price IMO is too high - similar books/tutorials/courses (targeting various stacks) can be found for as low as $59.
When you talk about consumer apps or low cost business apps your point is well taken.
edit: Sometimes SSO ties it together so single tenants appear to be a multi tenant environment.
2. Reliability is not a pure function of whether you use SOL or NoSQL
3. ORMs hide but do not remove the need for schema management in SQL dbs. They often create more problems than they solve.
4. SQL databases support JSON because it my accurately reflects the programming model that programmers want to use. This is making an argument for NoSQL.
5. Which NoSQL you use is a matter of personal choice in many cases. I prefer MongoDB (I would say that though, I work there). Cassandra has some challenges as it is eventually consistent by design (and default). MongoDB is strongly consistent by design (and default) which makes reasoning about your programs easier.
2. I was only referring to mongo and not to NoSQL as a whole. Cassandra worked just as a advertised.
3. You don't have to use an ORM with a relational database just as you don't have to for mongo. There are other alternatives
4. JSON is no longer an advantage for NoSQL since it's supported by relational databases. It also means that relational databases as a whole can adapt to the market.
5. Which NoSQL you use and for what purpose matters, and it's not just "personal choice". NoSQL in general aren't the generic swiss army knives that relational DBs are. Each NoSQL project has different use cases, which in turn also have different levels of reliability and performance.
They look very similar? But they're different? According to the docs this one is more focused on advanced patterns? Does a person need to buy the first to get value from the second?
Very confusing UX IMO
Later this month I plan to somewhat re-write first book, many packages push changes often (Next.js and Material-UI) plus many explanations can be improved and I need to do better job with diagrams. First book, Builder Book, is either for junior developer or someone who wants to save time to learn this particular stack.
I hope this helps.
- Quantitative evidence, we have over 150+ pre-orders in the last 3 month which is more than good for us. No advertising, no social media. We sold first book 700 times. So that's 100-120 people out of 700 who pre-ordered second book.
- Qualitative evidence. We have way more polite customers after raising price in the past ($49 -> $99) for our first book. More polite emails, more feedback and less emails asking for support.
EDIT: My co-author says that we have evidence that higher percentage of people who bought the book at higher price point actually read it.
PS: Price will go to $199 on Sunday midnight PST, that's when pre-order period ends.
Steam and other platforms employ prices based on purchasing power of the buyer which I think is good but also require more work which might not be worth it for smaller teams.
We do get emails asking for discounts but I personally feel that it is unfair to the previous buyers.
But I am keeping an open mind about it. Is there reliable way to charge people in other countries different price?
Sometime I choose to give a deal to a person for my own reasons, so my one-off pay portal is used there as well.
Or one-off a client for additional money.
It took less than an hour to build, years ago, the functionally it's a one off invoice just tightly integrated with my business and optimised to two inputs. #bpaftw
He's got an episode on his podcast on how he implemented it [2].
It does sound like some work and I'm not saying you should discount or give away your work though.
[1]https://wesbos.com/ [2] https://syntax.fm/show/233/hasty-treat-purchasing-power-pari...
Obviously. If I were to run a restaurant I would rather choose/open as expensive as I could so I wouldn't have to deal with people without proper manners and education sufficient to appreciate my fine culinary skills /semi-sarcastic
By the way. Here had already been some posts by free software authors devastated by rude and ignorant people demanding support and/or bullying them by e-mail. I find it very important for all the authors (regardless of whether they code/write for free or for serious money) to learn to just ignore (without any emotional response) the correspondence from this kind of people. You don't alienate them this way, they already got what they are eligible for for free or for their money, personal support should be a premium, for nice people only :-) Yet, there actually are many nice people for whom $100 (let alone $200) per book is a way too much. Some of them even living in the US, not necessarily in an utterly poor country.
Many blue collar users have no idea it exists, and it cripples your app for that percentage of users.
As a counter-point, I work for a large national telco and our mass-market site and mobile app (usage in the tens of millions of unique users across all demographics) both use hamburger menus and our internal stats show that almost everyone understands that it's the menu.
My evidence is anecdotal - though repeated - in US fleet/manufacturing/facilities maintenance, and other labor industries.
P.S. I was trying to get in touch with you a few months back, and was unable to find an avenue. Any place I can send an email/PM? Thanks for your time.
I’m on 11 Pro Max iOS 14 beta
I've been looking for something exactly like your book, but I need to use a SQL database.
Is `sequelize` a good library to use for PostgresSQL?
If the first, I guess my side-projects were too small if they need 25k LOC just for the boilerplate.
Your own code.
Yes, the name "boilerplate" is deceiving here. Not sure where to draw the line. This boilerplate does have some features - websocket with rooms, working with Markdown, S3 file uplod, API Gateway with AWS Lambda, webhook from Stripe and many more.
Is there name for boilerplate with "popular" features?
The book's code is actually free and hosted here:
https://github.com/async-labs/saas/tree/master/book
We charge for book's content which is bunch of explanations and diagrams.
"batteries-included framework"?
After clicking button, you should be asked to log in and then redirected to checkout page hosted by Stripe. Would you try later again? You can also email us if you prefer email, at team@builderbook.org