AI automation for UK companies, priced in pounds and run on UK hours

The engineer who scopes your system writes the workflows, wires the integrations, runs the deploys and answers the email. Nobody sits between you and the person doing the work, so replies come back with specifics rather than a promise to check with the team.

Every engagement is a written scope with a price agreed before any work, running on accounts registered in your company name, which means you own the credentials, the workflows and the code from the first day to whenever we stop working together. Past builds and rescues are written up on the work page.

Personal data leaving the UK for a processor in the United States needs a transfer mechanism, and we bring one to the table rather than leaving it for your counsel to chase. Every engagement that touches personal data runs under a data processing agreement with the UK addendum to the standard contractual clauses attached, signed before anything moves.

Where your data protection officer wants a transfer risk assessment on file, we provide the completed supplier half: what is processed, where it is stored, which sub-processors are involved and what each one holds. Sub-processors are named in the DPA, which for a typical build means the model vendor, the telephony provider and the hosting platform, and you hear about it before that list changes.

Where a system can keep personal data inside the UK or the EEA, we configure it that way: the transfer question gets smaller when fewer things actually transfer.

We act as a processor. You decide what personal data is collected and why, we handle it on your written instructions, and a data processing agreement covering the Article 28 duties is part of every engagement. Sub-processors are named, which for a typical build means the model vendor, the telephony provider and the hosting platform, and you hear about it before that list changes.

The Data (Use and Access) Act 2025 received Royal Assent in June 2025 and amends the existing UK regime rather than replacing it, with provisions commencing in stages. Broadly it touches the grounds available for certain processing, the treatment of automated decision-making, how complaints reach a controller before they reach the regulator, and the structure of the information rights regulator itself. The effect on a build like ours is modest: the controller duties still land on you, the processor duties still land on us, and the paperwork looks much as it did. Where a specific provision matters to a specific system, your privacy counsel is a better source than a supplier page, and we build to whatever their reading turns out to be.

For business-to-business services supplied by a business outside the UK to a UK VAT registered customer, the place of supply is where the customer belongs, and the customer accounts for the VAT under the reverse charge. Our invoice therefore carries no VAT line. You declare the output tax and recover the input tax on the same return, and in most cases the two cancel out.

Send us your VAT registration number when the contract is set up, since the invoice has to carry it. If your company is not VAT registered, tell us early and we will look at how the supply should be treated before the first invoice rather than after it. Your accountant should confirm the treatment for your own circumstances, because we build software and give no tax advice.

IR35 exists for a UK-resident individual providing services through their own intermediary to a UK client, where that individual would look like an employee if you engaged them directly. The machinery works by deeming a payment of employment income and applying PAYE to it.

Here it has nothing to attach to. You engage Meridal Group LLC, a US company, against a fixed-scope statement of work with a named deliverable and a price agreed in writing. The work is performed outside the United Kingdom by engineers who are not UK residents, on our own equipment. Beyond a UK correspondence address there is no UK establishment, no UK payroll and no UK duties.

For your procurement team that removes a status determination statement, the dispute process behind it, and a line of risk that usually needs sign-off from two departments. Your own advisers should confirm it, and they will.

A number presented by a voice agent has to be one your business is entitled to use, it has to be valid and dialable, and a person who rings it back has to reach you. Those are the conditions Ofcom places on presentation numbers, and enforcement has tightened, including the blocking of calls arriving from outside the UK that carry a UK caller ID nobody can verify.

For a build that means numbers provisioned properly under your own account with a provider that knows who you are, a presentation number on any outbound leg that rings back to your business, and a test of the return path before launch. Spoofing a CLI to look local is something we will not set up, and it has largely stopped working anyway.

Unsolicited marketing calls made by an automated calling system need the prior consent of the person receiving them, live marketing calls cannot go to a number registered with the Telephone Preference Service, and marketing texts to individuals need consent as well. Those are the Privacy and Electronic Communications Regulations, and the ICO enforces them with fines that land long after the campaign has finished running.

We decline that work.

Inbound answering, callbacks to people who asked for one, appointment reminders to existing customers and internal automations are all fine, and they are most of what we build. If the brief is a dialer aimed at a bought list, we will say no in the first reply and point you elsewhere.

Engineering coverage runs through UK business hours, so calls happen inside your working day and a message sent from London in the morning gets its answer the same day, not overnight. Every email gets a reply within one business day as a standing commitment.

Releases go out inside your working day, so both sides are awake if a deploy misbehaves. Build sprints run a weekly call with a shared channel in between, and care clients get fixes inside 24 to 48 hours depending on tier, which is set out in the post on what a care retainer should include.

Every price on this site is published in both currencies, and the switch in the header changes the whole site at once, not just this table. Landing on this page sets it to pounds for you; if you would rather read the site in dollars, the control below does that and remembers it.

The sterling figures are a list price rather than a live conversion. They are set at a fixed 0.78 to the dollar and reviewed quarterly, last checked in August 2026, and that rate sits a little above the market on purpose. The reason is the same one behind every other number here: a quote that moved every time sterling did would not be a quote you could plan around. If you would rather carry the currency risk yourself and track the market, say so and we will contract and invoice in dollars instead, at the dollar figures in the left-hand column.

Invoices are issued in whichever currency the contract names and paid by bank transfer. Builds run 50 percent on signature and 50 percent on delivery. Retainers bill monthly and roll, with 30 days notice to stop. Model usage, phone numbers and hosting are billed to you directly by those vendors at cost with nothing added, and the ones people forget to budget for are itemised in the post on running costs nobody mentions. What each tier includes is on the pricing page.

American buyers arrive with a different list of questions, mostly about the W-9, 10DLC registration and the TCPA, and those are answered on the US page. The rest of the site reads the same from either country: the rescue service when a build is failing right now, the fix library for specific symptoms with a workflow file attached to each one, and the questions worth asking any AI supplier before you sign with us or with anyone else.