AI automation for UK companies, run from an EU studio on UK hours

Lukas Ceponis 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 fixed scope at a published price, 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 can move from your systems to ours without standard contractual clauses. The UK treats the EEA as adequate under its own transfer rules, so a controller in Britain sending customer records to a processor in Lithuania is making an ordinary transfer with no additional instrument required. In the other direction, the European Commission adopted adequacy decisions for the UK in June 2021, extended them during 2025 while the review ran, and adopted renewed decisions on 19 December 2025, so data flowing back to you is covered too.

This is a genuine advantage over an American supplier, and it is worth ten minutes of your legal team's time to confirm. A US processor handling UK personal data needs a transfer mechanism in place before anything moves: the UK addendum to the standard contractual clauses or the international data transfer agreement, a transfer risk assessment behind it, and whatever your data protection officer wants to see documented about government access requests on the other side of the Atlantic. None of that appears in our contract because none of it applies.

Adequacy gets reviewed and can change. If it ever does, the fallback is the same set of clauses everyone else already signs, and we would sign them.

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 an EU supplier 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. The company is Lithuanian, the engineer is resident in Lithuania, and every hour of the work is performed there on our own equipment. No UK presence, no UK payroll, no UK duties. You engage a company against a fixed-scope statement of work with a named deliverable and a fixed price.

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.

Lithuania sits two hours ahead of the UK all year, since both clocks move on the same weekends. That gives a full working day of overlap rather than a narrow window at the edges.

A message sent at nine in London lands here at eleven. Calls happen in your afternoon without anyone doing arithmetic, releases go out inside your working day so both sides are awake if a deploy misbehaves, and every email gets an answer within one business day as a standing commitment. 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 US dollars and the dollar figure is the one written into the contract. The sterling column below is converted at roughly 0.78 pounds to the dollar, the rate as we write this in August 2026, and it is here so you can size a budget without opening a currency converter. Treat it as guidance, because it moves with the market and we do not re-cut this table every week.

Invoices can be issued in GBP, converted at the rate on the invoice date, 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-8BEN-E form, 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.