Property management portal
A community portal for a property owners' association: staff build pages and forms without a developer; residents search records, file requests and pay online.
- React
- Redux
- Tailwind CSS
SaaS modernisation 4–12 weeks
Modernise your SaaS without a rewrite
I modernise SaaS products that have become hard to change, usually in 4–12 weeks, without pausing feature work. I start by learning why the system behaves the way it does, then change the parts that slow you down, one release at a time.
Who it is for
- Teams with a live product and real users whose codebase has become slow and risky to change.
- Products that need a migration (framework, database or hosting) without freezing new features.
What the work covers
- A written review of the architecture: why the system behaves as it does, and what to change first.
- Migrations planned in steps, so the product keeps shipping throughout.
- Performance work, measured before and after.
- Technical debt paid down where it slows the team, not everywhere.
- Product and customer requirements turned into engineering decisions, in writing.
Proof
Telehealth platform
Patients request an online consultation and see a registered doctor by video; four portals run on one platform, live in production in Australia.
- React
- Node.js
- REST APIs
Questions
- Where do you start?
- With a written review of the system: why it behaves the way it does, what slows the team down, and the changes ranked by cost and risk. Nothing is changed before we agree that list.
- Do you rewrite everything?
- No, my preference is to stabilise what exists and replace parts only where they cannot be fixed. A rewrite that stops shipping for months is the outcome to avoid.
- Will you work with our existing team?
- Yes. My preference is to work in your repository and process, so nothing depends on me afterwards.
Tell me what you’re building and where it’s stuck.
I’ll tell you the cleanest path forward, including if it’s “don’t build that.”
Or write tocontact@alihassan.dev
