George Kavuma

The agent recommends, a person signs.
AI dealer sales for an industrial client.

7 months on the account. 3 approvals before any order goes out. 9 days from kickoff to the executive demo.

Role
Product Experience Lead, NextGen AI
Client
Confidential, global industrial technology company
Discipline
Workflow design, approval flows, interaction design
Team
2 developers day to day, in Albania, from the 7 I manage; stakeholders in 5 cities
Status
Executive demos delivered, August 2026
Year
February to September 2026
Internal approval card, the first of three approvals: waiting time, the rejection rule, and three buttons. Rebuilt with made-up data.
The decisionApprove, reject with a reason, or send it back to the agent. No setting turns this step off.

The client wanted agents that could sell on their own. I gave every agent a person to answer to.

The situation

A global industrial technology company sells through independent dealers. The equipment goes out on leases that run for years, and the software rides on top of it. They asked NextGen AI for AI agents inside that sales process: one to quote new solutions, and one to catch leases before they run out. I led the product design, on the same platform team as the NextGen AI case.

The people who would run these agents are dealer reps and the order desk, not engineers. They work from a list of accounts they know by heart. Real money, and no room for a wrong email.

The problem

An agent that prices a deal or emails a customer can lose money and trust in one action. Dealers keep their cost and margin hidden from the manufacturer, and from customers, by contract. Nobody could say yet what an agent was allowed to do on its own, or who would answer for it when it got something wrong.

Two products were also tangled together: ordering new solutions, and renewing leases near their end date. Same dealer, same list of accounts, different pace. A quote is a conversation. A lease renewal is a deadline.

The constraint

Nine days from kickoff to an executive demo, with the client confirming the process on day three. Two developers, both in Albania, in the middle of a release. Stakeholders in five cities across North America, and me in Toronto. The confidentiality rules were in the contract: if cost leaks, that is a breach, not a bug.

The demo also had to run on the real build. Slides would not do it. A rep had to be able to click through.

What I tried first

A new layout for the leasing screens, built around the lease instead of the account. It demoed well and it taught badly: reps now had two ways of thinking about one job. I threw it out and rebuilt leasing on the account list they already knew.

I also sketched levels of trust, where an agent that had earned it could send low-risk email on its own. It died on one question: who eats the wrong email? Nobody in the room would own it, so that level could not exist.

The decision

The agent recommends. The platform writes it down. A person signs.

Every recommendation comes through one door, with the agent's reasoning, how sure it is, and which version of the agent made it. Three people have to sign before an order goes out: internal approval, customer approval, and the dealer submitting it. No setting turns those off. Picking an option only highlights it; a second, labeled click preps the email.

I mapped the order process before any screen was drawn: ten steps from discovery to licensing, and every step written to a log nobody can edit. The customer approves from an emailed link, or by signing in to their own portal. Either way it lands in the same log.

A round light shows where the order is. A square light means something went wrong.

What I refused

Anything past recommending. Agents flag problems; they never resolve them.

Hiding dealer cost in the browser. Who sees what is decided on the server, by role. Opening the cost view is logged. The customer never receives cost or margin, because the server never sends it.

A build that only works as a demo. We logged fifteen decisions as we went, each with what we turned down and why, so the production team gets the reasons and not just the screens.

What I traded away

There is no separate rep role. Cost visibility is tied to the dealer role, so a wrong flag shows too much, and the fix is a process rule, not the product. The order also moves forward when the dealer submits, not when fulfillment confirms, because the demo needed a visible step. Both are logged as risks with a trigger to revisit them. Both are still open.

Seven months, start to finish.

February

The first version: the order process, the approvals, and who sees what, on a real screen.

In between

The client took the prototype in house to build it. Ten weeks later that stalled and they came back.

August

The nine-day push to the executive demo. Selling and leasing on one screen pattern, so a rep learns the job once.

The real process, rebuilt with made-up data.

Lease renewal list with one row opened: the agent's reasoning on the left, three suggested options on the right. Rebuilt with made-up data.
Leases up for renewalThe list reps already use. Open a row and the agent's reasoning is under it.
Quote screen with the dealer view, cost and margin included, beside the customer view, which has neither. Rebuilt with made-up data.
Who sees costCost and margin are decided on the server, by role. The customer never receives them.
Suggested options card: the recommended option highlighted, two alternatives below it, and separate Override and Prep customer email buttons. Rebuilt with made-up data.
Two clicks to sendPicking an option only highlights it. A second click opens the email as a draft a person signs.
The same quote in two views: the dealer table with cost and margin, and the customer table with price only. Rebuilt with made-up data.
One quote, two viewsThe dealer view has cost and margin. The customer view never does.
Order timeline with six status lights and the log of every step. Rebuilt with made-up data.
Order statusA round light shows where the order is. A square light means something went wrong.
Recommendation card: the agent's reasoning, how sure it is, and its version, above one main button. Rebuilt with made-up data.
Why the agent said soIts reasoning, how sure it is, and which version made the call.
Order timeline with a square light on the integration step, a problem flagged to order entry, and Retry and Resolve buttons. Rebuilt with made-up data.
When it goes wrongThe agent flags it. A person fixes it, and the fix is logged.
Order process diagram: ten steps from discovery to licensing, with the three approvals marked. Rebuilt with made-up data.
The order process, ten stepsThree of them need a person to sign. No agent can skip them.
Request to view
Walkthrough of the working buildIt shows the real build, so it is not public. Email me for it.

What was delivered, and where it stands.

Delivered: the whole order process, quote to license, with three approvals and a log of every step.

Delivered with it: the lease renewal list, on the same pattern as the selling list.

The dealer portal was mine end to end. The leasing agent was a teammate's; I designed the list it reports into.

It is a demo build. The client's order and ERP systems are stand-ins, and they say so.

The screens are rebuilt with made-up data. The process and the decisions are real.

Outcome.

Verified 7 months on the account. February to September 2026.
Verified 9 days. Kickoff Monday, process confirmed Wednesday, executive demo the next week.
Client-confirmed 3 approvals. Internal, customer, and the dealer submitting. No setting turns them off.
Delivered 3 products demoed. The dealer portal was mine. Leasing and live sales ran beside it.
Verified 15 decisions logged. With what we turned down, and why.
Delivered 4 views of one quote. Decided on the server, by role.
Delivered 10 steps, discovery to license. Every step is logged, and the log cannot be edited.
Verified 10 weeks. The client tried to build it in house, then came back.
Team 2 developers day to day. Both in Albania, from the seven I manage.