Ad hoc Builds

Some problems need a custom build.

Every ad hoc engagement starts with a free discovery call. Larger builds then go through a paid scoping step, and the build itself is quoted at a fixed price. The price is agreed after scoping, so you know the total before we write a line of code.

Is this right for you?

When ad hoc makes sense

  • The problem spans more than one department and no single catalogue item covers it.
  • Your work has unusual rules, regulations or data formats that standard tools do not handle.
  • The build has to connect to a legacy system, an on-premise database or a proprietary platform.
  • You have run the AI Automation Audit and the top opportunity does not map to a catalogue item.
  • You need an AI assistant that works from your own documents and data, not a generic tool.
  • The build is large enough that a single catalogue price does not fit.

How it runs

From first call to handover

  1. Discovery call

    Twenty minutes. We hear where the hours go and say whether this is a catalogue fit or a custom scope.

  2. Scoping

    We map the process with the people who run it and write a brief you can hold us to.

  3. Fixed quote

    This is a quote, not an estimate. The price on the proposal is what you pay, and it is agreed before any build starts.

  4. Build in sprints

    You see working output early and correct it before go-live. Every platform and AI account is set up in your name and billed to you.

  5. Handover

    Documentation, training for the people who will run it, and a support window. Issues caused by build errors are fixed at no charge.

Book a discovery call

We hear the problem, say whether it is a catalogue fit or a custom scope, and give you a rough cost range before you commit to anything.

Book a discovery call