A narrow scope, metrics defined before starting, and a business user who signs off on every iteration. The method in detail, week by week.
Kais KhenineDigital marketing consultant, i2Business
Most enterprise AI projects stop after the demo. The tool works, leadership is convinced, and six months later nothing has changed in operations. The problem is rarely technical.
We never open a pilot on an entire process. We take one task, one team, one metric. The constraint forces the decisions a broad project lets you postpone indefinitely: what data goes in, who validates the output, what happens to the cases that aren't handled.
On a recent retail engagement, the initial scope fit in one sentence: answer product availability questions on WhatsApp, during opening hours, for a single store. Everything else came later.
A pilot that can't fail cleanly isn't a pilot, it's a demo.
We measure the starting point before changing anything: average first response time, number of requests handled per day, error rate on inventory information. Without this baseline, the end-of-pilot discussion comes down to impressions.
Four weeks is enough to put one use case into production, not to transform an organization. What follows is governance work: who owns the agent, who adjusts it, how you decide to open a second one. That is where most companies need help, and it is rarely what they ask for at the start.