Your AI group

Build the team that takes the work forward.

Your internal AI group is the centre of the operating model. IT, the process owner and internal champions work together to run the workflow, assess its quality and prioritise improvements.

Your AI group

Build the team that takes the work forward.

Your internal AI group is the centre of the operating model. IT, the process owner and internal champions work together to run the workflow, assess its quality and prioritise improvements.

2–4

people, with roles sized to your team

Business sponsor

Sets priorities and decides which process deserves the next investment.

Access, integrations, budgets and recovery.

Rules, exceptions, acceptance and external commitments.

Daily operation, examples, colleague support and feedback.

IT owner — Access, integrations, budgets and recovery.

Run → inspect → resolve → improve

  • A reviewed operating record
  • A growing evaluation set
  • An owner-approved improvement backlog

One person can hold more than one role. The 2–4-person structure is a proposed operating model, adapted to the company.

Learn on the system you will actually use.

Training combines a guided run, exception handling, evaluation exercises and a handover rehearsal. The output is a runbook and a team that knows who owns the next decision.

↗

The delivery is more than a working demo.

Your team should be able to run the workflow on an ordinary day—and know what to do when it fails.

01

A working path

The scoped integration, configuration and reusable Skills in an agreed company-owned location.

02

A visible decision map

Inputs, outputs, owners and the actions that need approval.

03

A testable standard

Representative examples, known exceptions and agreed acceptance checks.

04

An operating playbook

Daily checks, failure handling, recovery and rollback instructions.

05

A team that has practised

Guided runs, an exception exercise and a handover rehearsal.

06

A next-step backlog

What to improve next, who decides and what evidence would justify it.

01 — 03

A clear route from problem to ownership.

  1. 01

    Understand

    One recurring task, its tools, constraints and a useful result.

  2. 02

    Build & check

    A limited pilot, realistic examples and explicit review gates.

  3. 03

    Transfer & improve

    Working notes, team practice, acceptance checks and next steps.

FAQ

Before we start

Do we need to replace our systems?

Usually the first step is one handoff between tools you already use. We check available APIs, permitted browser paths and data quality before selecting an implementation.

What can we start with?

One recurring task, its main tools and a few permitted examples. A focused assessment defines the boundary, useful output and acceptance checks for a pilot.

Is every action fully automatic?

No. Drafting, retrieval and record preparation can often be automated. Your process owner decides which production writes, customer messages or commercial decisions need approval.

How do CC Switch and Sub2API fit?

They may be evaluated as components where their features, licenses, security and provider terms fit. The foundation is eligible company-owned seats and APIs, clear access and usage ownership—not shared personal subscriptions.

What happens after the handover?

A small internal group practises running, checking and recovering the workflow. You receive operating notes and evaluation examples; any continued support is scoped separately.

Who delivers the work, and in which language?

Chen Xulin works independently and remotely in English. These pages have six language versions; total capacity is 40 hours per week across engagements. Fees, dates and scope are agreed in writing.

One independent practitioner. Working with your team.

I’m Chen Xulin (陈旭林), publicly known as Leon S Kennedy: an independent FDE engineer and AI implementation consultant. I work remotely in English, with 40 hours per week total capacity across engagements. Scope, timing and meeting overlap are agreed together.

These pages are available in six languages. Project communication and delivery are in English.

↗ Discuss a project

Which workflow deserves a closer look?

Discuss your workflow

These pages are available in six languages. Project communication and delivery are in English.