AI strategy and team training

Find the work AI should take off your team’s plate. Then teach them to build it.

We sit with your team, map how the work gets done today, and pick the automations worth building first.

Then we build them together in custom training sessions, in the tools you already pay for, until your people can keep going without us.

30-minute intro call with Kelly Diekvoss or Bryce Arii · On-site or online

Process review

Example

Monthly client renewal report

4 steps · 14 staff hours a month

  1. 01

    Export account data from 3 systems

    Scheduled Power Automate flow

    5 h

    Automate

  2. 02

    Clean and merge it in Excel

    Power Query, built once and refreshed

    4 h

    Automate

  3. 03

    Write a summary for each client

    Copilot drafts from a shared team prompt, staff edit

    3 h

    AI assist

  4. 04

    Review exceptions and sign off

    Judgment call. Stays with your people.

    2 h

    Keep human

9 h automated3 h AI assisted2 h kept human

Every process we review gets a worksheet like this. Your numbers come from your team.

The problem

The class ended.
The work didn’t change.

Most AI training runs on someone else’s examples. People watch a demo, go back to their desks, and do the job the same way on Monday. Leaders stop attending because nothing in the class touches their numbers.

We start from your work. Standard work before AI work: we map how each process runs today, put hours against each step, and pick the ones where AI pays back. Then your staff build those, live, in sessions designed around them.

Every session ends with something running, or a clear next step.

How it works

Three steps, in order

How long each step takes depends on what we scope together: how many processes, how many use cases, and how many people on your team.

01

Assess

Find the work

We interview and shadow your team and collect the tasks that eat their week. Each process gets mapped with time, volume, systems touched, and where errors happen. Every use case is scored on hours saved, risk, and build effort, and your leaders pick the first ones.

02

Train

Teach to build

Custom Flow sessions on your use cases, one per session. Your staff build it with AI, test it on real data, and leave able to run it on their own.

03

Own

Hand off

Your prompt library, a plain-language AI use guide, and a ranked list of what to build next. Champions on your team own each build.

For leaders

Leaders join the first session and get a 30-minute readout at the end: what got built, hours saved per month, and which use cases to fund next. They see results from their own teams, so they stay in the room.

Who leads your engagement

Kelly Diekvoss

Kelly Diekvoss

Chief Innovation Officer, Humagined

Meet your lead
Bryce Arii

Bryce Arii

Founder, Humagined

Meet your lead

Inside a Flow session

One hour. One real problem.
Worked live with AI.

Every session runs on one of your team’s use cases. Your processes, your data, the tools you already license.

0:00

Check in

Review the problems people brought. First-timers go first.

0:05

Frame it

What happens today, what good looks like, and what data exists.

0:15

Build it live

Build with AI, test on a real example, refine. Your staff drive.

0:45

Make it stick

Turn the result into a repeatable process the team runs without us.

0:55

Next steps

Actions for this week and what to bring next time.

Every session ends one of four ways

Solved

It runs before the hour is up.

Unblocked

You know who to ask, and the request is drafted.

Homework

A short list of concrete next steps.

A clear no

A reason to stop chasing it and move to the next item.

Microsoft 365 Copilot, Copilot Studio, Power Automate, Power BI, Claude, or ChatGPT. We work in what you have.

What your team keeps

Working automations and the people who can build the next ones

  • A scored list of your team’s use cases with estimated hours saved
  • A worksheet for each use case: steps, hours, and what changed
  • Working automations from the sessions, built by your own staff
  • A prompt library written for your roles, documents, and data
  • A plain-language AI use guide: what data goes where and what needs human review
  • Internal champions and a ranked list of what to build next

Ways to start

Pick the size that fits

Scope, timing, and pricing are set after a 30-minute call about your team and your processes.

1 session

Try it first

One custom Flow session on a use case your team picks. Your leaders see how it runs before you commit to more.

Most teams start here

Scoped to your use cases

Find and teach

We review your processes, pick the use cases, and run a custom training session on each one. Ends with working automations your staff built and know how to change.

Monthly

Ongoing Flow

Regular sessions afterward for new use cases, build reviews, and bringing new hires up to speed.

Scoped to your department

Go further

A full process assessment. We map and rank processes across a department before building. For teams ready to automate at scale.

Q&A

What teams ask first

We already took a Copilot class. How is this different?

That class taught the tool on generic examples. We start by finding where AI fits your processes, then train your team on those use cases. Every session ends with something built or a clear next step.

Do you build it, or teach us to build it?

Both. We build the first version side by side with your staff. After a few sessions, your people lead the build and we coach.