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
SaaS team with a live product
Add AI to the product you already run, without breaking it.
I learn why your system behaves the way it does before changing it, then add AI or modernise the parts that slow you down.
Email me
Available for new projects
Sound familiar?
- “Our product has become hard to change.”
- “We want AI features, not an AI rewrite.”
- “Every release breaks something else.”
- “Model costs are a guess, not a budget.”
- “The codebase outgrew the people who wrote it.”
That’s the work I take on.
Proof
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
AI audit reviewer
A draft financial-statement package goes in; a categorised exception report comes back in about 90 seconds, at a measured $0.24–0.28 per review.
- Python
- FastAPI
- Anthropic Claude
Ali, is very responsive and smart. He knows his stuff and is easy to work with.
Mike I feel extremely comfortable working with Ali, we were talking about problems or improvements to the website and how to improve it, Ali was able to analyze and propose concrete actions to improve performance. Reliable and professional. thanks
Maria Torres
How we'd work
- 01
Modernise a SaaS product that's hard to change
4–12 weeks
Typical budget $5k–$20k
- 02
Fractional CTO or senior AI engineer
Retainer
Typical budget $4k–$8k a month
- 03
AI accuracy and cost audit
5–10 days
Typical budget $1.5k–$3k
From email to launch
- 01
You email
Say what you're building, how far along it is, your budget and your timeline. The draft already asks.
- 02
I reply within 24 hours
With questions, or a time for a call.
- 03
A short call
We find the smallest version worth building, or agree not to build it.
- 04
A written plan and quote
Model choice, retrieval design, how output gets checked, and a cost and speed budget, in writing.
- 05
A demo every week
Something you can click every week, not a reveal at the end.
- 06
Launch and handover
A codebase the next engineer can read, on your accounts. The code and the rights to it are yours.
Questions
- 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.
- How much overlap will we get with our team?
- I work remotely with clients worldwide, and I would rather agree the overlap window with you on the first call than publish one here. How many hours actually need to overlap depends on how you want to run the work — a daily standup and a written weekly update need very different amounts — so it is worth settling early rather than assuming.
- Who owns the code?
- You do. The code, the schema, the design files and the deployment setup belong to you, and the agreement we sign says so. If your company has its own contract or IP assignment, I'll work to yours.
Tell me what you’re building and where it’s stuck.
The draft asks four short questions. I reply within 24 hours.
Or write tocontact@alihassan.dev
