One of the biggest mistakes an startup can make is spending way too much time picking their tech stack instead of actually building their product.
Admittedly, I almost made this mistake when I started building Senja all the way back in January this year. If I hadn't set aside 30-days to get an MVP out, I'm sure I would've spent much longer 😅
Fast-forward 11 months, and we now have 1K users, and Senja's testimonial embeds are viewed almost a million times each month 🤯
In this post, I'll show you the tools we're using to build a SaaS that serves this many people, and why we chose these tools.
Development speed is extremely important to us. It's the biggest advantage we have over the kingpins of the testimonial collection and sharing industry.

I needed to build with tech that wouldn't slow me down, but help me move fast enough to overwhelm our competition.
I chose Sveltekit for my frontend framework over Nuxt and Next because it allows me to do just that.
When I started building with it though, it was a pain to work with, reason being that there was always one breaking change after the other. At one point, I almost rewrote my entire codebase with VueJS.
Now I'm really damn happy that I didn't.
Now that Sveltekit is approaching its first stable release, I've had zero problems using it in the last few months.
As for CSS, I'm building with the magnificent TailwindCSS.
I wanted to share as much code as possible between my frontend and backend, so I chose to use Node + Express for my backend framework.
Senja's using a mix of many services under the hood.
We host all of our websites on Vercel. That includes our marketing site, our app, user-generated pages and embeds.
Vercel has been nothing short of amazing to use, though I'm really disappointed that you can only have one concurrent plan for free ($50/mo per extra concurrent build ☹️).
As for our backend, and database, we use Railway, and it's been a joy to use. We also have an on-demand image generation server hosted there.

We have a Notion doc with a summary of all the tools we use and a breakdown of their costs. And yes, we keep it updated regularly 😉

Nice list! For analytics, I'd suggest looking at all-in-one tools rather than stacking GA4 + Hotjar + something else. I built Zenovay to solve exactly that, one tool for traffic analytics, heatmaps, session replay, error logs, and uptime monitoring. Reduces context-switching and costs.
The best technology for the application front end and back end, backend storage database, and application server must be chosen if I am to construct a SaaS solution. Most SaaS applications use Javascript frameworks like Vue. js, React, and Angular as well as frontend technologies like HTML and CSS.