Filed under Life SaaS

I built my first SaaS. Then the client bought it.

Earlier this year a client asked me to build something I hadn’t built before: a proper SaaS product.

Written by
Farhan Munim
Published
Updated
Reading time
2 min

That product was Estate Portal, lettings management software for UK letting agencies. It tracks rent and reconciles payments, keeps on top of compliance certificates like gas safety and EICRs, and drafts the monthly landlord statements.

The deal was simple. I would build and run the platform, the client would get two years of exclusive access, and I could still sign up other customers. Until then I’d mostly built websites and small tools, so I was excited to take on something much bigger.

Building Estate Portal

Most of the work was in areas I’d never had to think about. Behind the product sat users and permissions, the database, document storage, automated jobs, backups, security and deployment, all of which matter once people rely on your software every day.

I also spent far more time on the user experience than on anything I’d built before. I kept asking how a letting agent would actually use it day to day, which of their processes I could automate, and what should happen in the background so they never had to think about it.

It was the first time I’d put all of those pieces together into one product, and I learned more from it than from anything else I’d built.

Then the plan changed

The two years of exclusive access never happened. The client liked the platform enough to buy it outright, and the acquisition completed in September 2026.

They’re now folding it into their own systems, so its features become part of their wider estate agency business, and the existing customers have moved across. I’d expected to run the product for a couple of years. Instead I sold the whole platform.

The handover

The sale also meant handing over a live product for the first time. The source code was the easy part. The new owners also needed the infrastructure, databases, documentation, deployment process, user data, integrations and accounts, plus everything I knew about how it fitted together that wasn’t written down anywhere.

Getting them to the point where they could understand it and run it without me was probably the most useful part of the project. It showed me how much it matters to build things so that someone else can maintain them later.

What I learned

Estate Portal went from idea to architecture, build and launch, then to real users, a commercial agreement, an acquisition and a handover. Seeing one idea through all of those stages taught me more than I expected.

I’ve built plenty of things for myself, but this time someone else relied on what I made, and in the end they thought it was worth buying. For my first commissioned SaaS project I’m very happy with that, and grateful I got the chance. It was also a lot of fun to build.