Process Transformation · A Human Layer Lab programme

Take the processesyou run on.Rebuild them withAI inside.

A practical programme for transforming existing processes with AI tools and agents. We find the processes worth transforming, redesign them around how your teams actually work, help you implement the new way of working, and measure what lands. One process at a time, expanding when the evidence says so.

Book 30 minutes See the shapeStart with the process that matters most
Shape
Five stepsmap, prioritise, design, implement, traction
Price
Fixed feeper step and per process, never hourly
Platform
The Human Layer Graphyour processes mapped as one connected picture
You own
The new way of workingthe map, the scenarios and the playbooks are yours
Map · Prioritise · Design · Implement · Traction

01 The problem

The tools changed. The processes didn’t.

Everyone has been told to bring AI into the business, so your teams are experimenting: a Copilot licence here, a Claude window there, a workflow someone automated on a Friday afternoon. Useful, individually. Invisible, collectively.

Meanwhile the work itself still runs the way it always has: manual, repeated, half-documented, held together by the three people who know where everything lives. The tools changed. The processes didn't.

The missing piece is not another tool. It is knowing which processes are worth transforming, what the new workflow should look like, and which tools, agents, data and knowledge have to sit underneath it.

So we transform processes, not slide decks. Pick the one that matters most. Redesign it with AI inside. Implement it with the team that owns it. Measure what lands. Then take the next one.

The process, todayfive stages, all manual
The process, transformedAI carries the drafts · people keep the decisions

The same process, today and transformed

02 The offer

Map. Prioritise. Design. Implement. Traction.

Five steps from scattered AI experiments to a transformed process with adoption you can read. Three fee shapes, no hourly billing, and you own everything the programme produces.

Step 01 · MapFixed feeTwo weeks of mapping on the platform, ending in a baseline of your processes and the AI opportunities, with the evidence attached. From $8,000 USD.The map is yours
Steps 02 to 04 · Per processFixed fee per processWe prioritise together, then each process is designed for a fixed fee and the implementation is priced from the scenario before it starts.The scenarios are yours
Step 05 · TractionIncludedAdoption and impact measured from live systems, reviewed together at 30, 60 and 90 days after each process goes live.The numbers are yours

We do not publish an implementation price, because an honest one does not exist before the scenario. The map is quoted on the call and fixed before it starts. Each design is quoted from the map and fixed before it starts. Each build is quoted from the scenario and fixed before it starts. All fees are quoted in USD, and nothing renews by default.

Already run the Workforce AI Impact Assessment? That is the map. The programme starts at prioritisation, and the first scenario can be underway inside a week.

Book 30 minutes

A short call to identify the first process worth transforming. If it fits, the map takes two weeks, and you keep it either way.

03 The walk

Five steps, one process at a time.

A fixed shape, not an open-ended engagement. The track below shows a typical first cycle: about a quarter from a standing start to a transformed process with adoption you can read. A gate at each end, and nothing renews by default.

Week 0Gate · your call

The scoping call

30 minutes sets the perimeter: which part of the organisation we map, which processes are already suspects, and who owns the work on your side.

Weeks 1 and 2

Map

The AI impact baseline. We map how the work actually runs today on the Human Layer platform: the processes, who does them, the tools they touch and the hours they take. Opportunities surface with evidence attached, not opinions.

You see which processes are worth transforming.Our engine, your team confirms
Week 3

Prioritise

We sit down with the map and choose. Each candidate process is weighed on value, feasibility and urgency, and the shortlist is agreed with the people who own the work, not imposed on them.

A prioritised shortlist, with the reasons written down.Leadership, at the table
Weeks 4 to 6

Design

The per-process scenario. We gather evidence from the people doing the work, document the current state honestly, and design the AI-enabled workflow: the tools, agents, prompts, integrations, roles and operating model it needs. Specialist partners fold in where the process demands it.

A future state precise enough to price and build.Us, with the people who do the work
Weeks 7 to 10

Implement

The process comes to life. From configuring the tools you already pay for through to agent workflows on a knowledge layer, built alongside your team so the new way of working belongs to them, not to us.

The process, live, in the hands of your team.Us and your team, together
Weeks 10 to 12

Traction

Adoption and impact read from the live systems, not from a survey. Who is using the new process, where it sticks, where it slips, and what that says about the next candidate. Reviewed together at 30, 60 and 90 days.

Proof, and the next process chosen from evidence.Measured from live systems
Week 12Gate · your call

The expansion decision

Take the next process, pause, or stop. Nothing renews by default. The map, the scenarios and the playbooks are yours whatever you decide.

Processes after the first move faster: the map is already live, the operating model is proven, and design and implementation run for the new process alone. Most organisations run the second cycle in half the time.

04 The scenario

One document that makes the change buildable.

Every priority process gets its own scenario: the evidence, the current state, the future workflow and everything that has to sit underneath it, pinned down precisely enough to price the build and hold it to the number.

Evidence from the people doing the work

Not a workshop of opinions: structured sessions with the people who run the process, capturing what actually happens, including the workarounds nobody wrote down.

The truth, on the record
The current state, documented

The process as it really runs: every stage, handoff, wait, tool and side spreadsheet, mapped on the platform so the baseline is checkable rather than anecdotal.

Hours, handoffs, failure points
The future workflow, designed

The new process, drawn end to end: what AI drafts, what people decide, where the handoffs go, and what stops existing altogether.

AI drafts · people decide
The stack underneath it

The tools, agents, prompts, integrations and knowledge the new workflow needs, chosen from what you already pay for first and bought new only when it earns its place.

Tools · agents · prompts · connections
Roles and the operating model

Who runs the new process, who approves what AI produces, and how exceptions get handled. The part most AI projects skip, and the reason most AI projects stall.

Ownership · approval · exceptions
The implementation plan, priced

The build sequenced into steps, each with a fixed price. You can take the scenario and build it with anyone, including nobody. It is yours.

Fixed price · yours either way

Where a process needs deep domain knowledge, specialist consulting partners fold into the scenario work on our platform, under the same fixed shape. You get the expertise without a second engagement to manage.

05 The ladder

Three levels of implementation. Start where you are.

Not every process needs agents, and no process needs a platform project before it can improve. The scenario names the level each process actually warrants, and every level ships value on its own. Nothing requires the next.

Level 1 · EnableDays to live

Tools, configured properly

The AI you already pay for, actually set up for the process: Copilot and Claude configured for the work, prompt workflows the team shares instead of reinventing, and the busywork stages handed over.

  • Copilot and Claude, set up for the process
  • Shared prompt workflows, not private hacks
  • Templates and playbooks the team owns
Fastest payback · no new systems
Level 2 · ConnectWeeks to live

AI wired to your systems

AI connected to the systems the process actually runs through: Claude connectors and MCP, retrieval over the documents that matter, drafts landing where the work happens instead of in a chat window.

  • Connectors and MCP into your systems
  • Answers grounded in your own documents
  • Drafts delivered into the flow of work
AI that sees the work, not a chat window
Level 3 · AgentsThe compounding end state

Agents on a knowledge layer

Agent workflows carrying the process step to step, with a company knowledge layer, the brain, giving them the organisational context to work properly. Everything the agents produce is drafted for a person to approve.

  • Agents carrying the process end to end
  • A knowledge layer agents can rely on
  • People approving, not compiling
Each process makes the next one easier

The knowledge layer is optional here and a whole programme in its own right. When the processes justify it, that work runs as Build Your Company Brain: one connected system of the organisation that every agent, and every future process, works from.

06 Who runs it

Your team, our experts, or both.

Every path runs on the same foundation: the graph holding how your organisation works, and Anima doing the analysis. How much delivery help you take is a dial, not a package, and you can turn it per process.

Run it yourselvesSelf-serve · on the platform

Your team, on the graph

Your team drives the transformation directly on the platform: the graph holds the evidence of how you run, Anima does the analytical heavy lifting, and the scenarios and playbooks guide the build.

  • The graph and Anima under your team
  • Scenarios and playbooks to build from
  • Our team a message away
Fold in expertsThe usual shape

Specialists, at key points

Solutions experts and specialist partners fold in exactly where a process needs them: scenario design, agent builds, training, rollout. Scoped to the moment, working on your graph, gone when the moment passes.

  • Design, implementation, training, rollout
  • Domain specialists for regulated work
  • One engagement, one fixed shape
We run itFull delivery

End to end, run for you

A Human Layer Lab team runs the whole cycle, folding in the specialists each process demands, with your people confirming rather than compiling and your team trained as the new way of working lands.

  • The full five steps, delivered
  • Your team trained along the way
  • Capability that stays when we leave
Where the bench folds inScenario designTool and agent implementationPrompt and workflow trainingRollout and adoptionChange communicationDomain specialists

The bench is our network of solutions experts and consulting partners, all working on the platform, on your graph, under the same fixed shape. Whoever does the work, the evidence, the scenarios and the capability land with you.

07 The expansion

Prove one process. Then compound.

The first cycle does the expensive work once: the map exists, the operating model is proven, and your team has shipped a transformed process they own. Every cycle after that starts from evidence, and the traction data names the next candidate for you.

Expand across a function, then across the organisation, at the pace the results earn. Or stop at one working process. Both are wins, and both are your call at the gate.

The process backlog, filling in

monthly invoicingclient onboardingproposal draftingsupport triagesupplier renewalsboard reporting

Two live, four queued: the traction data from each cycle scores the rest of the map, so the order is argued from numbers rather than volume.

08 Fit

This is not for everyone.

The programme is built for organisations that want AI in the work, not in a slide deck: real processes, real owners, and the patience to prove one before scaling to ten.

Worth a conversation

  • There are processes everyone complains about, and nobody has rebuilt.
  • Your teams are already experimenting with Copilot or Claude, and you want it to add up to something.
  • A process owner will sit with us and tell the truth about how the work actually happens.
  • You want a working process, not a strategy document.
  • You would rather prove one process than launch a transformation office.

Probably not yet

  • ×You want the enterprise AI strategy deck first and the working process later.
  • ×The process changes every month, because the business is still finding its shape.
  • ×A product on the market already runs this process end to end. Buy it.
  • ×Nobody who actually does the work can give us time.
  • ×The systems the process runs through have no way in.

Built for organisations that check.

SOC 2 Type II. Singapore region infrastructure. The same platform behind every Human Layer Lab engagement.

  • Engagement-scoped accessStaff access is scoped to the engagement, never broader.
  • Least-privilege connectionsWe connect with the minimum permissions the build needs, and you can revoke them.
  • No training on your dataEver. Your map stays yours. Full detail in our Trust Center.

09 Questions

Asked, answered.

Licences are the easy part. The scattered experiments your teams are running prove the appetite, but a licence does not tell you which processes are worth transforming, what the new workflow should be, or whether anything actually changed. The programme turns the licences you already pay for into processes that run differently, and it measures the difference.

No, and deliberately so. You do get a roadmap, but it is a by-product of the map and the traction data, not the deliverable. The deliverable is a process that runs differently, with adoption you can read from live systems. Strategy documents follow working processes far better than the other way round.

The ones with high volume, clear rules and painful handoffs: invoicing and billing, client or employee onboarding, proposal and report drafting, support triage, compliance checks, recurring reporting. But that is a pattern, not a prescription. The map scores your processes on value, feasibility and urgency, and the shortlist comes from your evidence, not our habit.

That is a dial you control, per process. Some clients run the programme themselves on the platform, with the graph holding the evidence and Anima doing the analysis. Most fold in solutions experts at key points: scenario design, agent builds, training, rollout, and domain specialists where a process demands them. And if you want it run end to end, a Human Layer Lab team delivers the whole cycle with your people confirming rather than compiling.

Access to the tools the process runs through, a process owner who will make time, and your people's honesty. The map only works if we hear how the work actually happens, including the workarounds. The people who do the work always know where the process really lives.

From the live systems, not surveys. Who is using the new workflow, how often, where it sticks and where it slips back to the old way. We review the numbers together at 30, 60 and 90 days after go-live, and the same data scores the remaining candidates for the next cycle.

The map is a fixed fee, from $8,000 USD, quoted on the call. Each process scenario is a fixed fee. Implementation is priced from the scenario before it starts, so the number you agree is the number you pay. Nothing is hourly, and nothing renews by default. All fees are quoted in USD.

Only when the processes justify it. Plenty of transformations stop at level one or two of the ladder: tools configured properly, AI connected to your systems. When agent workflows need real organisational context, the knowledge layer becomes worth building, and that work runs as its own programme, Build Your Company Brain, with its own map and its own fixed fees.

No. It replaces the re-typing, the chasing, the copy-paste between systems and the Friday spreadsheet. The operating model in every scenario is explicit about it: AI drafts, people decide. Everything an agent produces is prepared for a person to approve, not fired off on its own.

Then the scenario says so. Sometimes the honest answer is a simpler fix: a form, a rule, one deleted approval step. You would rather learn that in a two-week design than after an implementation, and it is exactly why the design is priced separately from the build.

Your data stays yours and is used only to run your engagement. Access is scoped and logged, we connect with the minimum permissions the work needs, and we never train on your data. Fuller security detail is available in our Trust Center and on request.

The map runs on the same platform and discipline as the Workforce AI Impact Assessment, so if you have already run the assessment, the map is largely done and the programme starts at prioritisation. When a transformation grows into building the full knowledge layer, that is Build Your Company Brain. If you want a senior operator embedded throughout, that is Forward Deployed.

One process, transformed. Then the next.

30 minutes to identify the first process worth transforming and whether the fit is there. If it is, the map takes two weeks, and you keep it either way.

We use cookies to improve your experience and analyze traffic.