SaaS platforms
This is what I have gone deepest on: at Entreredes I ran a SaaS that generated landing pages on my own, from scratch to production.
What makes a SaaS hard
A SaaS isn't just the part the user sees. There are accounts and permissions, an admin panel, slow tasks that can't block anyone, and a deployment that has to hold up. If that isn't thought through from the start, every improvement costs twice as much.
What I did at Entreredes
During my internship I ended up running one of the company's projects on my own: a SaaS to generate landing pages, built with Laravel and Filament, with Gemini integrated through job queues and deployed to production with Docker.
- -Admin panel with FilamentI built the admin panel with Filament on top of Laravel, so the team could manage it without touching code.
- -AI through job queuesGeneration with Gemini ran in asynchronous Jobs, so the rest of the application kept responding.
- -Tests with PHPUnitThe important parts had tests, so things could be changed without fear of breaking others.
- -In production with DockerIt didn't stay a demo: I left it deployed and running.
How I'd approach it again
Scope the first version
What is essential for someone to use it and what can wait.
- ›Users and permissions
- ›Minimum features
Lay the foundations
Data, accounts, admin panel and queues for heavy work.
- ›Data model
- ›Authentication
- ›Admin panel
- ›Queues
Production
Deploy with Docker, with tests where it matters and some monitoring.
- ›Docker
- ›Tests
- ›Monitoring
What it should include
- ✓User accounts and permissions
- ✓Admin panel
- ✓Heavy work in queues
- ✓Tests where it matters
- ✓Docker deployment
- ✓Documented code