← All four ways I can help

Consulting services

Make an AI idea work

You've identified something worth improving. Now the job is to work through the details so the idea fits the way your team needs to operate.

Your starting point

We know what we want to improve and need help making it work.

Choose this when there is a clear task, a person responsible for it and a reason to make a change. You may have a preferred tool or a design already. We can start there, but we still check whether it fits the work before building around it.

Questions we work through

  • What should AI do, and what should remain with a person?
  • Which information and tools does the workflow need?
  • How will someone check and correct the output?
  • What should happen when information is missing or the tool fails?
  • Who will maintain the workflow after handover?

How we work together

1. Agree the result and responsibilities

We define one workflow, its users and the result you need. The scope states which parts I will design, configure or review, and which parts your team or another specialist will build. You know what is included before committing.

2. Work through the design

We map the path from the incoming information to a usable result. We compare suitable approaches, discuss access and review requirements, and decide how exceptions reach a person. This is also where we check whether an existing tool can do enough without custom development.

3. Try a working version

For agreed, technically suitable work, I can help configure or build a focused version, or work alongside your delivery team. We try normal tasks and awkward cases with approved information. We measure the whole task, including checking and corrections, rather than just how quickly AI produces a draft.

4. Review and hand over

We compare the results with the agreed expectations and document what needs changing. Handover covers how to use the workflow, who maintains it and what to do when it fails. Moving into production or extending to more teams is a separate decision unless explicitly included.

What this could look like

A situation you might recognise

If a team receives recurring forms by email, we could explore extracting a few agreed fields and sending uncertain entries for review. The design would keep the original document available, give staff a way to correct a result and avoid automatically acting on missing information. We'd test different document formats and incomplete submissions before deciding whether the workflow is ready for its intended use. A useful outcome might be a working test version and a clear list of changes needed before wider use, rather than an immediate rollout.

What you bring

  • A named process owner and representative users
  • Examples of ordinary work and the exceptions that matter
  • Approved access to the tools and information needed for the agreed scope
  • Someone responsible for internal approvals and any specialist implementation

We'll agree how information is shared before you provide anything sensitive.

What you receive

  • An agreed workflow design and division of responsibilities
  • The configuration, prototype or delivery support specified in the scope
  • Test findings, known limits and a recommendation for the next step
  • Working guidance, handover notes and agreed support boundaries

Keeping the work clear

A working test version is not automatically a production-ready system. Custom integrations, security reviews, software licences and ongoing support are included only when stated in the proposal. I won't promise to cover every technical discipline; specialist work is identified and agreed separately.

How pricing works

This work is quoted by scope and agreed stages. Design, a working test and production support can require different amounts of effort, so the proposal separates them. Tool charges and third-party costs are made clear. Changes to the agreed workflow are discussed and priced before work expands.

You'll receive a written scope, fee, payment terms and any applicable tax before the engagement is confirmed. Ongoing support is optional and agreed separately.

Let's talk about your work

Describe the task you want to improve, what you've already tried and who will use the result.

Discuss this service

Not the right starting point? See the other three choices.