3 engagement modelsCost per stageWritten scope

Packages and engagement models

Each package below explains what we do, what you receive, how long it typically takes and who it suits best. There are no fixed prices on this page because effort depends heavily on scope.

Overview

Package 1 — Short consultation

This package is for organisations unsure whether their need really requires AI, or wanting a second opinion before committing a large budget. We examine the existing process, assess the opportunity and deliver a written recommendation — including when the conclusion is AI is not needed.

What we do

Short interviews with the relevant team, workflow walkthrough, sample data review and assessment of technical and economic feasibility.

What you receive

Findings notes, a prioritised opportunity list, estimated model usage cost, risks to manage and a recommended next step.

Duration

Typically 1–2 weeks once data and access are available.

Best suited to

Management needing a written basis before approving budget, or teams just beginning to explore AI.

Package 2

Staged project

This is the engagement shape we run most often. Work is split into short stages, each with a testable deliverable. You can stop or change direction at the end of any stage without losing what has already been produced.

What we do

Solution design, development, testing and launch preparation — including integration with your existing systems and agreed data handling.

What you receive

A working application or automation, complete source code, technical documentation and usage guides, team training, and an agreed support period.

Duration

Typically 4–16 weeks, split into 2–4 stages depending on complexity.

Best suited to

Organisations with a clear problem or process that want a real outcome rather than another pilot.

Package 3

Support retainer

Software needs care after launch. This package keeps systems running, secure and improving — without you having to staff routine technical work internally.

What we do

Availability monitoring, backups with recovery testing, security updates, priority-based incident handling and small continuous improvements.

What you receive

Periodic system health reports, incident and resolution logs, improvement recommendations, and a pool of hours for small adjustments.

Duration

Monthly with a minimum three-month commitment, so maintenance delivers visible value.

Best suited to

Organisations already running our systems, or other systems that need to stay stable.

Comparison

Comparing the three packages

Summary of differences
AspectShort consultationStaged projectSupport retainer
Primary goalDeciding directionBuilding the solutionKeeping it healthy
Your involvementModerateHigh at the start, then periodicLow
PaymentOnce, up frontPer stageMonthly
Source code handed overNot applicableYesYes (already yours)
Can lead into other packagesYes, into a projectYes, into a retainerYes, new development
Cost

How costs are calculated

We issue a written proposal rather than fixed rates on this page, because cost depends on scope, the number of integrations and data complexity. Cost components are itemised separately:

  • Delivery effort — based on the agreed stages, not open-ended hourly billing.
  • AI model cost — an estimated monthly figure, billed separately at actual usage.
  • Infrastructure — servers, storage or third-party services where required.
  • Post-handover support — if you choose a continued support period.

You know every component before work begins, so there are no surprise costs mid-project. With a limited budget we usually suggest one small first stage as proof.

The initial discussion stays free

Assessing whether our packages fit your needs costs nothing, and carries no obligation to continue.

Questions

Questions about packages

Can we start with a small scope?

We strongly recommend it. One workflow or one automated report is enough to assess how we work before expanding.

Can packages be combined?

Yes. The most common sequence is a short consultation, then a staged project, then a support retainer. Each transition still goes through a separate proposal.

Can you work on a system built by someone else?

Yes, after we review the code and documentation first. If the remediation risk is high, we will say so before you decide.

What if requirements change mid-project?

Changes are raised as a written request; we estimate the impact on schedule and cost, and you decide. No extra work proceeds without approval.

Ready to discuss your needs

Send a short brief or your question. We will explain which package fits and what the next step is — with no charge for the initial discussion.

Email us WhatsApp