A remote AI automation developer that ships without a seat in your office.
Most of my engagements never need a plane. The build is driven by a shared staging URL, a weekly demo, a written decision log and a single Slack channel. When a day in your office is genuinely worth it, it is a line item on the scope, not a monthly overhead.
Bishal Paul
AI automation developer · Remote across the UK
Hi, my name is Bishal Paul. I run Erudience (see erudience.com), a UK entity, and work with distributed teams across the UK and further afield, alongside my role as Head of AI at Absolute Intelligence UK. This page is for teams that want a UK based supplier who does not need a permanent seat in their building to deliver.
Async first delivery is not a slogan. It is a set of specific tools, rhythms and habits that the sections below describe. Real time calls happen when they are genuinely faster than writing it down. They are not the default.
Remote tooling
Four surfaces every engagement runs on.
Slack or Teams
Single shared channel per engagement. Async first, real time when it earns its keep.
Google Meet or Zoom
Weekly demo, ad hoc scoping calls, recorded when the client wants a record for the wider team.
Notion or Google Docs
Living scope, runbooks, decision log. Written trail so nothing depends on a meeting attendance.
GitHub or GitLab
Code, workflows, migrations, prompt versions. Everything reviewable, everything reversible.
Delivery rhythm
Four surfaces the build lives on, week to week.
Nothing depends on a single meeting. Everything is reversible.
- Weekly demo
- One recorded video call showing the build inside a shared staging URL. Same time each week, cancellable when there is nothing new to show.
- Written weekly note
- Two paragraph note: what shipped, what is next, any decisions the client needs to make. Sits in Slack and the shared doc.
- Ad hoc scoping
- Short calls when a decision would take longer async than on a call. Booked through the same Cal.com link used for discovery.
- Incident channel
- For live systems, a dedicated on call channel with a target response window agreed at handover. Not 24/7 unless the retainer is scoped that way.
Coverage
Remote engagements already on the books.
United Kingdom
Distributed teams in London, Manchester, Edinburgh, Cardiff, Bristol and elsewhere across GMT.
European Union
Ireland, Netherlands, Germany and France. Overlap windows agreed at scoping.
United States and Canada
US East and West Coast teams, with morning UK overlap for demos and afternoon overlap for East Coast.
Common builds for distributed teams
Six workflows remote first UK teams ask for.
All shipped without a permanent seat in any one office. Async first, weekly demos, written trail on every decision.
n8n workflow suite for a distributed team
B01A pack of five to ten interlinked n8n workflows covering the most repetitive parts of ops: intake, routing, drafts, chase loops and reporting. Runs on your cloud or self hosted, monitored end to end.
First AI feature inside a SaaS product
B02Structured LLM calls behind product UI with quotas, per tenant logging and cost caps. Shipped remotely with a shared staging URL and weekly demos, so nobody has to be in the same room to sign off.
Voice AI for a fully remote support function
B03ElevenLabs and Twilio voice agent that covers inbound calls when no human is at a desk. Transcripts and structured summaries filed into your CRM before the caller has hung up.
Document extraction and routing
B04PDF, email and portal document intake, parsed into structured records, routed into your existing systems of record. Confidence scores on every field, human review on anything below threshold.
Internal knowledge retrieval for a distributed workforce
B05Retrieval augmented answers over SharePoint, Confluence, Notion or Google Drive with citations. Access respects your existing SSO groups so nobody sees a document they should not.
Retained AI operator on a monthly retainer
B06A named engineer on your Slack for evolution, incidents and small builds. Cancellable monthly, capped hours, priced flat so nobody has to negotiate every change.
Engagement models
Four ways remote first teams start.
Pick the one that fits the decision you are trying to make. Most engagements start with Discovery or Advisory before a scoped build.
Recently shipped, remote first
Three builds distributed teams keep asking about.
Client names withheld. All shipped without anyone flying anywhere.
AI call assistant for overflow and weekend cover
Recently shipped for a distributed support team: a voice agent that answers overflow and out of hours calls, files transcripts and structured summaries into the CRM, and pages a human only when it genuinely needs to.
Email marketing and conversation automation
Recently shipped for a remote first agency: an n8n pipeline that drafts, sequences and replies to email campaigns with human approval gates on anything sensitive. Ran across timezones without a single missed handoff.
AI powered client support system
Recently shipped for a distributed professional services firm: LLM triage on inbound tickets with drafts pulled from an approved knowledge base and a human on the record for anything material.
Answered before the call
Eight questions from distributed teams.
What does remote UK actually mean?+
Erudience is a UK entity. I work with distributed teams across the UK and beyond, but the contract, invoicing and legal home sit in the UK. Remote means the build runs without a permanent seat in any one office, not that the supplier is offshore.
How do you avoid the classic remote failure modes?+
Written scope, weekly demos, shared staging URL from day one, and a single Slack or Teams channel that both sides live in. Every decision that would normally happen in a corridor is written down. Async first, but real time when a call is genuinely faster.
How do you handle time zones outside UK working hours?+
Core hours align with UK business hours. Overlap windows for teams outside the UK are agreed at scoping. Anything that is not time critical runs async with a target response window measured in hours, not days.
Can you work inside our SSO and access controls?+
Yes. Least privilege by default, MFA required, per environment credentials in secrets management, and access removed on the day the engagement ends. Standard for regulated shops and best practice for everyone else.
What if we need occasional in person time?+
Trips to London, Manchester, Edinburgh, Dublin and elsewhere are planned in at scoping when the build genuinely benefits from being in the room. Priced as a line item, not a monthly overhead.
Do you sign NDAs and DPAs?+
Yes, always. Mutual NDA if the topic needs it on the first call, DPA before any production data changes hands. Sub processor list on request. No client data on a laptop without paperwork.
Can you take over an existing n8n or automation stack?+
Yes. First step is a paid week of discovery to map what is running, what is fragile and what is duplicated. You get a written report and a prioritised plan even if we do not continue past that.
How fast can a remote engagement start?+
Paid discovery usually within a week of the first call because there is no travel to schedule. Scoped build starts one to three weeks after that depending on access and holidays.
Available for new work
Fully remote across the UK and Ireland
Reply within 24 hours
Start a conversation
Let's talk. Wherever you are.
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.
- Direct line to me, not an account manager or a sales team.
- No slide deck. We look at your current workflow and where it hurts.
- Written summary in your inbox within 24 hours of the call.