Evoriqa
My own SaaS: a multi-tenant AI customer-support platform, live in production, built by the person who also pays its inference bill.
- Next.js
- TypeScript
- PostgreSQL
Funded AI startup
A founding engineer for your AI product, without the three-month hire.
I own the architecture, ship every week, and hand over a codebase your first hires can run.
Email me
Available for new projects
Sound familiar?
- “We have funding but no senior AI engineer yet.”
- “Hiring one will take months.”
- “The prototype won't survive real users.”
- “Model costs are climbing faster than revenue.”
- “Investors want it live, not in a demo.”
That’s the work I take on.
Proof
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
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
Ali is easy to work with very knowledgable and is able to provide clear feedback. He also is able to suggest better alternatives which I appreciated very much. Sometimes we can overlook things but when working with Ali it feels like a real team environment. I appreciate all the work he has done and will work with him again!
Rayan Rader Ali, is a great asset to our company projects. He delivers on time and has a deep understanding of the work and is able to give input which enhances the project. We enjoy having him on our team and hope to work with him again.
Neha Parikh
How we'd work
- 01
Fractional CTO or senior AI engineer
Retainer
Typical budget $4k–$8k a month
- 02
Build an AI product from scratch
8–14 weeks
Typical budget $15k–$40k
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
- Will you work with our in-house 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.
- What happens when we hire our own engineers?
- How I like to finish a project: a documented repository, a walkthrough recording, and your own team on the accounts and infrastructure, so you are not dependent on me afterwards. What is actually delivered is whatever the scope we agree lists, so say if any of that matters to you and we will write it in. Staying on for support or further work is a separate arrangement rather than something bundled in.
- 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
