The questions that come up on the call.

Any size. What matters is not headcount, it is whether the same work happens every week and a person is doing it by hand. A solo founder with one process that eats a day a week has the same problem as a fifty person firm with six of them, and the same fix. If Discovery finds no use case with a clear payback inside six months, we say so and the fee is refunded, so the risk of being too small to benefit sits with us and not with you.

No. Discovery is scoped and priced in writing before it starts, and it is self contained. If Discovery leads to a Rollout and you proceed within 60 days, we credit the Discovery fee towards the implementation. If you don't proceed, everything produced through Discovery is still yours: the opportunity map, the baseline, the training your team has had and the proposal, and there is nothing else to pay.

Then that is the answer you get, in writing, at the end of Discovery. It is a real outcome and we say it out loud. If we don't find at least one use case with a clear payback inside six months, we refund the Discovery fee.

We don't resell software licences and we don't take commission from vendors, so a tool recommendation is only ever a tool recommendation. The method is on this page rather than behind a booking form. And the point of the work is that your people can do it without us.

Reasonable. So: the method is published above, the outcome is measured against a baseline we take before anything changes rather than asserted afterwards, the guarantees are published in writing, and the scope and the price are both fixed in writing before any work starts. Judge Discovery on what it produces.

That worry is the reason change management is the actual work here. The policy is written before anything is switched on, your people are in the room while the workflows are mapped, and the training is on their own jobs. Staff who helped build it are the ones who keep using it.

Data handling rules get written before anything is switched on. The policy sets out what may and may not go into a tool, which tools are approved, and who checks an output before it leaves the building. We are not lawyers and we don't audit or certify anything.

Usually not. Most of what a business needs is already inside tools it pays for and has never been set up against the actual work. Custom software happens where nothing off the shelf will do the job, and that is less often than you would think.

Discovery is the first phase. At the end of it you have the map, the baseline, a training session with your team and a proposal. What follows is scoped and dated in that proposal, from what is actually there. We don't quote the Rollout length before anyone has looked at the work.

The people who run your Discovery run your Rollout. You are not handed to someone else after the sale, and you are not training a new face every phase. Every message through this page is read by the person who would do the work.

Scoped from what Discovery finds and fixed in writing before any work starts. It depends on the teams, the people and the number of use cases in scope. We don't publish a number for it, and for the same reason we don't publish one for Discovery either: the honest price depends on your business, and you see it in writing before you commit to anything.

Anum is Melbourne based. Observation and training work best on site, standing next to the people doing the job, so for work further out travel is agreed up front and written into the scope. The call itself is a call, wherever you are.

Assistants your staff already have a licence for, answers drawn from your own documents, software that does a task rather than talks about it, and automation between systems you already run. Which of those is right depends on what Discovery finds. The five patterns are written up in full here.