The pilot nobody uses
A team built something clever in a demo. Daily work never changed, and the licence still renews every year.
From possibility to practice
Consulting for teams
I help teams connect AI, business processes and the systems they use every day. We start with the people and the work, agree on what better looks like, then make it happen through practical advice, a clearer workflow or a software build.
Where projects usually stall
I have seen these four patterns in well-run organisations. A clearer process and an owner come first. Then we can judge where training, an integration or custom software will make the improvement stick.
The tool nobody opens
Software was given to 300 people. Nine use it. The training was one webinar.
The policy came first
A ban was written before anyone understood the tools. Staff now use AI quietly on personal accounts, where nobody can see it.
The plan with no owner
A strategy deck with a timeline and no names. Everyone agrees with it. Nothing happens.
How we work
We do not start with a tool or a whole department. We pick one process that is slow, repetitive and annoying, and we make that one better.
1
Pick one process
For about two weeks I sit in, ask questions and watch how work really flows. We choose one process with a clear owner and a cost we can measure.
2
Test it small
We build a working version on your real data within weeks. If it does not save time, we stop and I will tell you why.
3
Hand it over
Your team gets the documentation, any prompts and source code, and a clear view of exceptions and ownership.
4
Then the next one
Only when the first process is running well do we choose a second one.
What good looks like
Success is quiet. The monthly report that took four hours now takes forty minutes, and nobody finds that exciting anymore. It is just how work gets done.
That is the aim. Your team owns the improvement, and you stop needing me.
Ways to work together
Most teams start with the sprint. Some stop there, and that is fine.
The sprint
Two to four weeks to test one process. You get a working prototype and a written recommendation. Sometimes the honest answer is do not proceed, and I will say so.
Monthly advice
A regular session with the team doing the work. You get a second opinion before you spend the budget, not after.
The build
A website, application, custom system or integration shaped around the process. I scope the work, build it and hand over the source code and setup notes.
Schools, public institutions and non-profits pay less. Ask me and I will quote for your situation.
Explore software servicesTell me about your project
Describe the process you want to fix, in plain words. If I am not the right person, I will tell you on the first call and suggest someone better.
Prefer email? Write to saiffilfariz@gmail.com.