Every developer has that one project that starts as a small idea and slowly turns into something much bigger.
For me, that project became PostDrop.
I'm currently a Computer Science student, and over the past year I've built numerous web projects. One problem kept appearing again and again: contact forms.
Creating the frontend was always easy.
Making the form actually send emails wasn't.
For a simple portfolio or landing page, setting up a complete backend just to receive a few contact form submissions felt unnecessary. Many developers either learned PHP, created a small Express server, or relied on services that required SDKs, complicated configuration, or pricing that didn't fit small projects.
That made me wonder:
Why should receiving a form submission require so much setup?
That question eventually led me to build PostDrop.
The Idea
The goal was simple.
I wanted developers to be able to build a contact form using plain HTML, React, Next.js, or any frontend framework and start receiving submissions in their inbox without writing backend code.
The experience should be straightforward:
Create a project
Copy a Public ID
Add it to the form
Start receiving emails
No backend.
No SMTP configuration.
No server deployment.
Building the Backend
As the project grew, I realized there were many challenges hidden behind what looked like a simple product.
Some of them included:
Authentication
Secure project management
Email delivery
Spam protection
Rate limiting
Background job processing
Database design
Dashboard analytics
Every new feature introduced another engineering problem to solve.
Things I Learned
Building a SaaS taught me far more than building tutorial projects.
I learned about:
Designing REST APIs
Authentication with JWT
MongoDB schema design
Background workers and queues
Redis caching
Email delivery systems
Deployment
Logging and debugging
User experience
SEO
Technical writing
Product marketing
One of the biggest surprises wasn't writing code.
It was realizing that building a product is only half the job.
Getting people to discover it is just as important.
That pushed me into creating documentation, recording YouTube tutorials, writing blogs, improving SEO, and learning how developers actually search for solutions.
The Biggest Challenge
The hardest part wasn't implementing a feature.
It was polishing the product.
Handling edge cases.
Improving performance.
Making error messages understandable.
Building something that other developers could actually trust.
Those details often took more time than the initial implementation.
Why I'm Writing This
I'm documenting this journey because I believe building in public helps everyone.
If you're a student thinking about building your own SaaS, my advice is simple:
Start with a problem you've personally experienced.
Solve it well.
Ship it.
Improve it based on feedback.
Repeat.
You don't need to build the next billion-dollar company to learn an incredible amount.
What's Next?
I'm continuing to improve PostDrop with better developer experience, more integrations, and additional features while learning more about building software products.
If you're interested in backend development, SaaS, APIs, or modern web development, I'll be sharing more tutorials and lessons from this journey.
Thanks for reading!
Resources
🌐 Website: https://postdrop.online
📖 Documentation: https://postdrop.online/docs
🎥 HTML Tutorial: https://youtu.be/6P1NMM1Oalc?si=PDwi_6yvIb5QYa1R
💼 Connect with me on LinkedIn: https://www.linkedin.com/in/mayank-joshi-7b0634317/
Top comments (0)