ClearAi

Work through it.
Then hand it back.

This pilot is for property-maintenance office teams. Gary starts with one recurring reporting task. A suitable pilot includes a configured process, practical training, a short guide and a follow-up after 14 days. Your team keeps responsibility for using it and checking the work.

Find the actual hold-up.

Describe one recent example, its volume and the time spent capturing, checking, correcting and chasing. Agree who will use the process and who will check the result.

What you receive: a clear problem and a baseline, not a list of fashionable tools.

Check the simpler answer.

Look at built-in features, existing templates, free vendor help and suitable specialist onboarding. If they already solve the problem, use them.

What you receive: a recommendation on whether paid help is needed, and what it would change.

Agree one clearly scoped setup.

Agree what information comes in, what the finished document needs, who uses it and what they check. Gary confirms the tools, permissions, delivery time and work he can demonstrate before an agreement.

What you receive: a scope that can be tested, with no surprise dependencies.

Practise with your team.

Practise with three agreed real examples across at least two days. Include a missing detail and a request the setup should not handle. Check that your team can use the process without Gary.

What you receive: a record of what worked and what still needs fixing. Nothing is sent without a person checking it.

Check what stuck.

After 14 days, Gary checks whether your team is using the process and whether anything within the agreed setup needs fixing. Compare the whole task with how it worked before, including checking and correction time.

What you receive: a follow-up on use and any remaining problems, not a guaranteed saving.

Pilot scope and included time.

£750 total, proposed

Optional £250 standalone diagnosis, credited against setup. Diagnosis should produce a useful process map, check of built-in features and recommendation even if you do not proceed.

One recurring process, one template and one person on your team trained to use it. Diagnosis, configuration, the short guide, training, testing and the 14-day follow-up share six total delivery hours. If the work cannot fit that allowance, the scope is agreed again before proceeding.

What it does not include

Integrations, migrations, custom software, technical diagnosis, safety certification, quote pricing, autonomous sending, daily operation or unlimited support.

Any additional tool cost is separate and must be agreed. Extra work needs a separate agreement. Enquire to check whether the pilot is a fit; no payment is taken on this website.

Check whether the change is useful.

A faster draft is only useful if the whole task improves. Include collecting information, checking it and correcting mistakes in any comparison.

Start with the bit someone keeps having to redo.

Describe one recurring task