The questions we are asked most.

Start with the routine work people most often call slow, or the one most often redone. The Routine Work Map walks you through mapping it yourself: who does what, where the time goes, and which steps repeat. If it is still unclear after that, the diagnostic session will pick it for you.

No, and it is better if you have not. A tool bought before the process is mapped is usually chosen for a problem nobody has examined. If you already have one, that is fine too, because we start from what is already there.

A pilot needs access to the data the work uses. If that access is limited, the pilot’s scope narrows with it. If the data does not allow it at all yet, we say so in the diagnostic session, not after the pilot has started.

What matters most is who owns the process, not the technology. Without someone who decides and has the authority to change how the work is done, the result stops at a demonstration.

ChatGPT used by each person on their own helps one person finish their task faster, and the benefit stops with that person. AI inside a team’s way of working has agreed steps, clear limits, someone who checks, and a result measured against how things were before. The first never shows up in a report, while the second can be proven.

No. The result depends on the quality of the data, who owns the process, and how far the team actually uses it, and all of that is outside our control.

What we commit to is a starting point measured before the work begins, a way of measuring agreed together, and an honest report of what was achieved and what was not.

No. If the evidence does not support running a pilot, we say so rather than push on.

How far the team uses it is part of the result, not something to deal with later. AI the team does not use produces nothing, so guiding the team is in scope from the start.

Your own people. From week four of the pilot onward, your team runs that work, not us. Maintenance only keeps the way of working fitting the work as the work changes.

The tool and our methods remain Handeliv’s, while your data and work output remain yours. While maintenance is active, your team uses the tool and it runs on Handeliv’s accounts. If you want full ownership, a buyout option is available at a price agreed in writing.

You can stop with 30 days’ notice after the three-month minimum. During those 30 days we prepare a handover, so your work keeps running without us.

All your data and work output, as Excel or CSV.

The routine work map, your team’s working rules, and the latest numbers report.

Access to the tool closes at the end of the notice period, unless you choose to buy the tool.

We delete the copy of your data in Handeliv’s account within 30 days of handover and confirm it in writing.

Third-party costs, such as AI models and the WhatsApp Business API, are paid by your company. The amount follows actual usage or an agreed quota, and we set it out in the agreement before the pilot starts.

We sign a confidentiality agreement before the diagnostic session begins, and use only the data the agreed work needs. Where possible, the data is anonymised or masked first.

Where data is stored, how long it is kept and how it is deleted are agreed in writing before a pilot starts. How we handle data is designed to align with Indonesia’s Personal Data Protection Law (UU No. 27 of 2022).

The minimum term is three months after the pilot ends, so the tools have time to settle into daily work. After that you can stop at any time with 30 days’ notice.

That is not the work we do. What is handed over are repeated steps with clear rules. Setting goals, deciding unusual cases, checking risky output, and being accountable for decisions stay with people. Where a piece of work should stay with a person, that is also what we write in the report.

Our focus is Indonesia: local context, language and data handling. We consider work with organisations outside Indonesia where a team or operation in Indonesia is part of it. Raise it in the diagnostic session, and we will tell you whether it fits.