Know which AI ideas work before you pay to build them.

For teams buried in documents, inboxes or data entry, or holding a list of AI ideas with no clear way to choose. We test AI on your real work, then build what passes into the systems you already run. You can stop after any stage.

You get the scope and the fee in writing before any paid work starts.

The dots are the AI work. They begin by shadowing yours.

Four stages. You can stop after any of them.

Each stage answers one question and ends with something you keep.

  1. Assessment

    What is worth testing, and what should wait?

    Fixed fee, agreed before work starts2 to 3 weeks

    We sit with the people who run the workflow and look at the tools and data you already have. If a plain script beats AI, we'll say so.

    You get a ranked idea list, a value estimate with its assumptions, a risk list and a 90-day plan.

    You can stop here. Your own team or another partner can run with the plan.

  2. Pilot

    Does it work on your own cases?

    Fixed fee, agreed before work starts3 to 5 weeks

    We pick real cases with you and agree the pass mark before we write any code. Then we build a small version and test it on them.

    You get a technical design, a working prototype and the results on your real cases, failures included.

    You can stop here if the results don't justify a build. You'll have paid for a pilot and nothing else.

  3. Implementation and handover

    How do we put it into daily use?

    Fixed fee, agreed before work starts1 to 3 months

    We build it into your systems with the tests, human checks and limits we agreed. The code lives in your repository and runs in your own cloud account.

    You get working software, tests, a runbook and a handover session.

    You can stop here. Your team runs it from now on.

  4. Ongoing development

    Who looks after it once it's live?

    A monthly scope, or hours as you use themMonth to month

    Suppliers change layouts and models get replaced. We fix what breaks, retest, and add what you ask for, or work alongside your developers.

    You get a short monthly note, plus a fixed monthly scope or authorised hours invoiced as worked.

    You can stop any time with 30 days' notice. Everything built stays with your team.

One example, followed through.

A wholesale distributor. Three people spend part of every week typing supplier invoices into the ordering system. The owner has a list of AI ideas and no time to test any of them.

An illustration, not a client. The same method fits support inboxes, contracts, reports and sales data.

Assessment

Supplier ordering, 4 ideas

  1. Read supplier invoices into the ordering systemAbout 400 a week, and every one can be checked against its PDF.
    Pilot this
  2. Draft replies to routine customer emailsUseful, if a person approves each reply before it goes out.
    Later
  3. A chatbot on the websiteNobody owns it yet, and nobody has said what success looks like.
    Wait
  4. Predict which quotes will closeThe sales history has too many gaps to learn from.
    Not now

Top idea, rough value. Three people each spend about 6 hours a week on invoices. If a pilot reads 9 in 10 correctly, that frees roughly 15 hours a week. Assumes volume stays near 400 a week.

Made up for illustration. Yours will look different.

Pilot results

30 real invoices, 12 suppliers

Pass mark, agreed before the build. At least 27 of 30 read correctly, and anything it can't read is flagged for a person, never guessed.

28
read correctly
2
flagged for a person
0
wrong and unflagged

The two flagged were a faded scan and a delivery note with handwritten changes.

Passed. 28 correct against a pass mark of 27, and nothing wrong went through unflagged.

Made up for illustration. Yours will look different.

Then it went live

The pilot passed, so the owner chose to build it. Now every invoice gets read as it arrives. When the reader is sure of every field, the invoice goes straight into the ordering system. When it is unsure of anything, a person checks it first.

Three months in

A supplier changed its invoice layout, so we retested on 20 of its invoices and fixed the reader. The team asked for credit notes, and we added them. The owner reads one short note a month and approves the next month's work.

What you can hold us to.

These apply to every engagement, large or small.

  • The fee is agreed before any work starts.

    You get a written scope and fee before paid work begins. Anything outside the scope is quoted separately before we do it.

  • Every estimate shows its assumptions.

    Cost and value estimates list their assumptions and how uncertain they are. They help you decide. They are not a promise of savings.

  • We tell you when we'd profit from our advice.

    If we recommend work we could sell you, we say so. We disclose any referral fee or resale arrangement.

  • You own what you paid for.

    The custom work you paid for is yours. If it uses tools we already own, you get a licence to run and maintain it, and to pass it on to your own customers where we agree that.

  • Your data stays under a written agreement.

    Before we work with real data, we sign an NDA and a data processing agreement that names every provider involved. We use provider terms that exclude training on your data.

  • Support only when you buy it.

    Hosting, monitoring and support are separate. If you buy them, the response times are written down. If you don't, we're not on call.

A smaller way in. A written second opinion on an AI feature or automation your team already built. It says what will break and how to fix it, and takes about a week.

Before you email.

Do we need to know what to build?

No. A list of ideas is enough, and so is one process everybody complains about. The assessment sorts out what's worth doing.

Does an assessment commit us to more work?

No. It is a complete piece of work. Use the plan with your own team, another partner or us.

Who will we work with?

One engineer, from the first email to the handover. The person who scopes the work is the person who does it.

What happens to our data?

Before any real data moves, we sign an NDA and a data processing agreement that names every AI provider involved. We use provider terms that exclude training on your data, prefer processing in the EU, and can work entirely inside your own cloud account. When the work ends, we delete our copies and confirm it in writing.

Can you work with the tools we already have?

Usually. We start from the systems you already run and add to them. What they let us access decides what's possible.

What if the pilot doesn't work?

Then you know before paying for a full build. We agree the pass mark before the pilot starts, so there's no arguing about the result afterwards.

Can you work inside our team?

Yes. We can work with your developers on hours agreed each month, invoiced as worked or reserved in advance.

Tell us about one workflow.

A few sentences is enough. We'll tell you whether an assessment is worth doing, or whether you need something else.

  1. You email. The letter here is a starting point.
  2. We reply within 2 working days and suggest a 30-minute call.
  3. Within 3 working days of the call, you get a written scope and a fixed fee. If you accept, work usually starts within 2 weeks.
To
hello@enhanceconsult.net
Subject
A workflow we want to improve

Hello,

Today, .

It's done by , about .

We've already tried .

Open this as an email

Fill in the blanks, or ignore them and just write.