I scope it, build it, and ship it myself.

The person who scopes your project is the person who writes the code, deploys it, and answers when something breaks.

I am Rayyan Abzal, an AI consultant and engineer in Auckland, New Zealand, running a solo practice. I have shipped production systems across creator-economy CRMs, payout automation, and on-chain platforms, for clients in New Zealand, Malta, and the US. Different domains, same engine: find the manual bottleneck, replace it with the lightest system that solves it.

Solo by design, so there is no accounts team and no junior developer getting handed the actual build. You talk to me, I write the system, you get the outcome.

Alongside the practice I work as a Full Stack Developer and AI Engineer at Growlab, an AI transformation consultancy in Parnell, Auckland, building custom AI systems for infrastructure and engineering firms. Same discipline there as here: production systems that a real team runs every day.

AI is a tool, not a deliverable

Four principles shape every engagement.

Replace work, don't add it

If implementing AI means more tools to learn, more dashboards to check, or more processes to follow, it is the wrong implementation. Good AI is invisible to the people whose work it replaces.

Start with the bottleneck, not the technology

“We should use LLMs” is not a project. “This manual process eats 20 hours a week” is. Find the real bottleneck, then choose the lightest tool that solves it. Sometimes an LLM, often just well-built automation.

Build for the team, not the demo

AI tools are only valuable if non-technical people use them every day. I ship simple interfaces a team adopts in an afternoon, not impressive demos that gather dust in a Notion doc.

Measure in hours saved, not features shipped

The only metric that matters is whether the business runs faster after the build. Every proposal names the manual hours we expect to remove, and we measure against that at handover.