Half day audit
Half a dayFitSmall UK team, one specific automation or AI feature you want a second opinion on before spending real money.
OutputWritten review, recommended stack, honest go or no go with reasoning.

AI Automation Engineer, UK
I am Bishal Paul, an independent AI automation engineer based in the UK. I take a small number of scoped engagements per quarter and ship each one into real production. You speak to me from discovery through to the runbook.
Hi, my name is Bishal Paul. I am an AI automation engineer working with UK teams that need real production systems, not slide deck demos. I run Erudience (see erudience.com), the AI automation agency I founded, and I am Head of AI at Absolute Intelligence UK. Under my own name I also ship four live products: push8, Extinde, Automation Workflows and ExcelErrorFinder. Every one of them runs in production, which is where I do my strongest work.
The UK AI automation market is loud. Agencies resell tools, junior implementers hand off demos, and nobody stays around long enough to see what breaks on a Tuesday morning. My work is the opposite: I sit inside the failure modes a real production system has to survive. Late FTP feeds. Retry loops. LLM calls that time out under load. Phone calls that hit voicemail at exactly the wrong moment.
Sectors already in production
Outbound voice collections with in call card capture.
Voice ordering into Shopify, seven department inbound routing.
Multilingual subsidy qualification on a single call.
Weekend and overflow coverage priced per minute, not per seat.
Deal sourcing and LOI drafting with Slack approval on every outbound.
Multi brand social pipelines across LinkedIn, Facebook, Instagram.
UK market context
estimated UK AI sector revenue with 3,700+ companies employing over 60,000 people.
of organisations globally report using AI in at least one function, up from 55% the prior year.
of generative AI projects expected to be abandoned after proof of concept by end of 2025.
Independent engineer vs agency
How I engage
No open ended time and materials. Scope, timeline and price are agreed before the build starts. The plan below is the same for every engagement.
30 minutes on the actual problem, current state, and what a good outcome looks like. Free.
1 to 2 weeks. Produces a clear architecture, a fixed build price, and a timeline you can commit to.
End to end, with weekly demos into a shared environment. You see the workflow taking shape, not a reveal at the end.
Into your infrastructure. Runbook, monitoring, and a session with your operator.
Optional. A defined block of hours per month for evolution, incidents and second opinions. Cancellable monthly.
Tools in use
Engagement models
The first 30 minute discovery call is free. Beyond that, every engagement is scoped, priced, and dated before the build starts. Numbers below are indicative floor prices in GBP, exclusive of VAT and third party costs (LLM tokens, telephony minutes, infrastructure). No hourly time and materials.
FitSmall UK team, one specific automation or AI feature you want a second opinion on before spending real money.
OutputWritten review, recommended stack, honest go or no go with reasoning.
FitYou have a problem and need an honest architecture, a fixed build price, and a timeline before committing.
OutputArchitecture doc, integration map, risk register, fixed build quote.
FitYou have a defined workflow to ship. Usually one voice or automation system, in production, on your infrastructure.
OutputLive system, runbook, monitoring dashboards, operator handover session.
FitThe system is live and you want a defined block of engineering hours for evolution, incidents, and second opinions.
OutputWeekly working session, on call for defined severity, quarterly review of cost and reliability.
FitYou already have an in house team, you want a senior AI engineer as a sounding board, not a builder.
OutputAsync architecture reviews, procurement help on tools, hiring rubric for AI roles.
Signals it is time to hire
If two or more of these are already true, the ROI on a scoped engagement is usually clear inside the discovery call.
Support inbox, outbound calls, or manual data work is scaling headcount linearly with revenue.
You already tried Zapier or Make and hit the ceiling on branching, retries, or state.
An LLM feature works in a notebook but nobody on the team is comfortable putting it in front of paying users.
A contractor built a proof of concept months ago and it still is not in production.
You need after hours or weekend coverage on phone or chat without adding shift staff.
Finance is asking why the AI bill is unpredictable and nobody can answer.
Integrations already in production
Not a marketing checklist. Every tool below is one I have already wired into a live client workflow, usually more than once.
When I am not the right hire
Saying no early is part of the job. If any two of these describe your situation, we should talk anyway, but the honest recommendation will not be an engagement.
Recent production work
Telecom outbound with DTMF payment handoff and structured call outcomes.
Energy client, cross lingual eligibility flow validated on live calls.
Sourcing, qualification, LOI draft, Slack approval on every outbound.
Answered before the call
Design, build and operate systems that use AI models plus workflow tooling to remove repetitive work. In my case: self hosted n8n on DigitalOcean, Supabase for state, Claude and OpenAI for reasoning, ElevenLabs and Twilio when the workflow involves phone calls. Most of the value sits in the integration and operational layer, not the model.
Yes to both. Erudience is a UK entity. Most client work is with UK teams, a meaningful share is US and EU. Remote is default, on site is available for UK clients when it actually helps the build.
Agencies resell tools through junior implementers. Every engagement I take is delivered by me end to end, or by a small trusted network I bring in for specific specialisms. You always speak to the person building the system.
Fixed scope discovery, a defined build project measured in weeks not months, or a retained operator role on a system already in production. No open ended time and materials.
Discovery starts with the process, not the tools. Repetitive, rule based, high volume, clear success signal, that is a strong candidate. Judgement calls, ambiguous inputs or a hidden broken process, the answer is often to fix the process first. Saying no is part of the job.
If the underlying process is broken or undocumented, automation makes it faster to fail. Fix the process first. If the volume is genuinely tiny, a spreadsheet or a well written SOP beats any system. And if the real problem is org design, not tooling, an engineer will not solve it. I will say so at scoping.
Yes. Mutual NDA at first call if requested, DPA before any client data moves. I ship into financial services, energy and professional services, all with structured audit trails, data residency respected, and recordings stored under the client's policy.
Free discovery in the same week. Paid scoping in one to two weeks after that. Build in three to eight weeks depending on scope. So four to twelve weeks end to end for a single scoped system, and the first weekly demo lands seven to ten days into the build.
Yes, and it is one of my most common opening engagements. Health check first: what runs, what does not, what is undocumented, where the risk sits. Then a written recovery plan, then a fixed scope stabilisation, then optional retained operator. I will not silently rewrite things without agreement.

Available for new work
UK based, working across timezones
Reply within 24 hours
Start a conversation
A free 30 minute discovery call. You leave with a concrete direction on scope, sequencing and cost, even if we do not end up working together.