I've shipped a bunch of half-finished projects over the years. Most never saw the light of day.
But I've also built two SaaS products that people ...
For further actions, you may consider blocking this person and/or reporting abuse
But what if my app suddenly scales to hundreds of endpoints and 500 developers?!??!?!
ah shit, you're right.
This is extremely impressive, honestly. I feel like you summed up every pain point I hit when I started out
Thank you! I'm glad to hear.
This ia a great post man, keep going! I finally can give the unicorn emote to someone
Haha thank you :)
Oof, this hit home 😅
This is so real - setting up feedback loops early changed everything for me, too. Curious, what was the hardest piece of negative feedback you had to act on?
This is sow insightful 🙌
There's some good advice here. Thanks.
This hit way too close to home...in the best way
A very insightful post thanks, really thanks you
Sure thing
Solid list. The "charge from day one" point is the one I'd underline, and it has a catch that bites right after you start charging: your pricing will change several times in the first year.
The trap is hardcoding plan logic, things like
if (plan === "pro")scattered across the app. Then every pricing tweak (a new tier, a higher limit, a grandfathered customer) means digging through code. What's worked better is storing plans and limits as data. A small entitlements table maps each plan to its limits and features, and the app asks one function, "can this account do X?", instead of checking plan names directly. Stripe stays the source of truth for billing, and your app only reads what the customer is entitled to.It's about a day of work at the start, and it saves a lot of pain later. It also makes things like custom deals, trials, and "upgrade to unlock" prompts much easier to add.
It's the kind of boring, off-the-shelf-style decision you describe in #7. On the SaaS builds our team at Technource works on for clients, entitlements are one of the first things we set up now, because plan changes always come sooner than founders expect.
Good write-up, especially the dashboard vs CSV export story.
Yeah it is right, nowadays most of the India based top metaverse real estate development company has introduced various new techniques also in their development project while delivering real estate software to various clients.
Really interesting — I noticed that userJot offers a generous free tier, which is great for onboarding.
That said, your point #4 emphasizes the importance of focusing on paying users early.
I'm curious how you balance both?
As someone who overcomplicates stuff. I feel attacked on point 7! Great stuff man. Enjoyed the content of this article.