Reporting that takes hours every week
Manual exports, copy-paste, reformatted into a deck. The data is all there. Somebody just has to touch it every time.
Operations
Automate the work your team keeps doing manually.
I map your manual processes, build the automations, and hand them over with documentation your team can follow, modify, and extend.
The situations I see most often
Every team has a version of these.
Processes that live in one person's head
When that person is on leave, the process stops. Everyone knows it. Nobody has had time to fix it.
Tools that were bought and connected to nothing
The stack has grown. Each platform holds its own data. Moving information between them is still a manual task.
What you walk away with
Most automation engagements end at "it works." These go further. Every outcome below is something your team operates independently after handover.
Automated workflows with time savings you can measure
Specific manual tasks replaced by automated processes. The time recovered is measurable.
Tools that exchange data without human intervention
Integrations built for your actual data flows, without middleware that creates new problems.
Your team modifies and extends automations without calling me back
Every workflow automation is documented in plain language. When requirements change six months later, your team has what they need to adapt the system themselves. No ongoing dependency on an external consultant.
How it works
Four phases. Audit first, then build, then deploy, then hand it over so your team can run it.
Workflow audit
Map the manual processes. Identify which are worth automating and which need redesigning first. Not everything should be automated.
Build and test
Build iteratively with your team watching. Test against real data before switching off the manual process. Edge cases belong in testing.
Deploy and monitor
Live rollout followed by a monitoring period. Automations break when data changes unexpectedly. That is what the monitoring period is for.
Documentation and handover
Every automation documented. Trigger logic, error handling, what to do when it breaks, how to modify it. Your team owns it from this point.
What clients say about the work
From clients across strategy, execution, and advisory engagements. Different sectors, different problems.
“Working with him was straightforward and collaborative. He is very detailed, reliable, and quick to translate discussions into clear, actionable steps. He also takes the time to guide and teach the team, which really helped build our internal capability. I can see why people describe him as a “walking Google” — he brings a wide range of knowledge and connects things quickly.”
Melissa Jailani
Digital Experience & Marketing Lead
“…every decision for the web site is always based on our side and Yassir best experience on the do’s and donts. The price you pay is what you get. Before production, during production and after production it is worth every ringgit spend. Hands down, the best experience and he knows what he is doing. My advice, don’t just get a web site, but get the web site. Great job Yassir, appreciate your work. The best.”
Elisa
Real Estate Negotiator
Why me
The build is one part of it.
I use automation in my own practice, which means I know what reliable looks like in production. I know which tools fail quietly, when a simple script beats a platform integration, when adding another tool creates more maintenance than it removes, and where AI genuinely reduces work versus where it adds noise.
The technical build is the easier part. The harder part is knowing when automation is the right answer. Some processes are broken in ways that automation would just accelerate. I come with enough business context to tell the difference. No platform affiliations, no preferred vendors. The tool follows the problem, and wherever possible, the work starts with what you already have.
Common questions
Answers to the questions I get asked most often.
What tools and platforms do you use?
n8n, Make, Zapier, Python scripts, and others. The tool follows the problem. If you already have a platform in your stack that can handle the automation, that is where we start. Adding another platform to maintain is only justified when the existing options genuinely cannot do the job.
What happens after the engagement?
Full documentation and handover. Your team can maintain and modify everything that was built. Optional ongoing check-ins are available if you want a point of contact as your processes evolve, but they are not required. The handover is designed so you do not need them.
Is this only for AI automations?
No. Traditional workflow automation and AI-assisted automation are both covered. AI is used where it genuinely reduces work and adds reliable output. A lot of valuable automation has nothing to do with AI.
What is a realistic timeline for ROI?
Simple automations recover time immediately. A reporting workflow that runs overnight instead of taking two hours every Monday pays back on week one. Complex multi-system builds may take several weeks to stabilise and optimise. The workflow audit phase produces a rough estimate before any build starts.
Find out where your team is losing hours.
A workflow audit usually surfaces two or three high-value targets quickly. Book a conversation to get started.