How much should your SaaS development cost?
Same answer as a piece of string 🧵
There is no fixed price.
Price based on value, not guesswork.
| GitHub | https://github.com/pH-7 |
| YouTube | https://youtube.com/@ph7programming |
| pH7 | https://ph7.me |
How much should your SaaS development cost?
Same answer as a piece of string 🧵
There is no fixed price.
Price based on value, not guesswork.
Docs should be simple and easy to maintain.
Open source options:
• Docusaurus
• Slate
• FumaDocs
Pick the simplest setup. Keep it up to date.
Docs are a product feature.
Bad docs slow users down. Good docs help users ship.
Tools I recommend:
• Readme
• https://Bump.sh
• Mintlify
• GitBook
• Fern

The Healthy Engineer 😋 Start building AI systems without burning out while maintaining healthy habits and a balanced lifestyle 🏝 I share everything as a software engineer and data scientist on AI, ML, positive mindset, and healthy proactive habits🥑🤖🏆. Click to read The Healthy Scientist: Build Using AI With Healthy Habits 🔥, by 🎡 Pierre-Henry™ 🌴, a Substack publication. Launched a year ago.
Search is a product feature.
If users can’t find it, it does not exist.
Focus on relevance, speed, privacy.
Tools I rely on:
• Meilisearch
• Typesense
• OpenSearch
Pick the simplest tool that works.
Don’t over-engineer.
Help users find what they need!
Env files are fragile. Easy to leak. Hard to share.
Use a proper secrets manager.
Examples:
• Doppler → centralised, team-friendly. No more broken .env setups.
• dotenv-vault → encrypt and sync env vars.
🔐 Stop passing .env files around.
Logs tell the truth. Essential for any product engineer! They show in real time what breaks
Tools to rely on:
• Sentry
• LogRocket
• New Relic
• Datadog
• Rollbar
• Papertrail
• GoAccess (open source)
Watch errors, fix better and deliver faster → https://PierreHenry.dev
As a Product Engineer, watch real users.
Session recordings show exactly where people struggle or drop off.
Tools worth using:
- Mouseflow
- Lucky Orange
- Crazy Egg
- Microsoft Clarity
- Hotjar
Stop guessing. Build what users actually need.
→ https://PierreHenry.dev
Don't optimise for how hard you work, optimise for how fast you learn from your errors 🧠
No errors == No learning
The more high-quality mistakes you make (and fix), the faster you grow. Top performers just try to be a little less wrong every day💪