Someone has to own AI. Right now, that's you.
Leadership wants a plan, a handful of people are power users while everyone else hesitates, and every vendor has something to sell. I help you work out what's worth doing, which tools to focus on, and how to get everyone onboard.
I've spent two decades helping companies adopt new technology: picking the platform, getting teams to agree, and making sure people use it once it lands. You work directly with me, every time.
Where most companies are right now
Some version of these comes up on nearly every intro call.
- 1
A few power users, the rest hesitate
A few people use it well. Some tried it once and stopped. Most of the rest use it as a chatbot and never touch the parts that do real work.
- 2
Too many tools, no decision
Copilot, ChatGPT, Claude, Gemini, and a vendor for every workflow. Nobody has said which ones the company is standardizing on.
- 3
Leadership wants a plan
You've been asked what the company's AI plan is: which tools, what to automate, who gets trained, and in what order.
- 4
Nobody has written the rules
People are pasting things into tools nobody approved, and security is nervous. There is no policy, so everyone guesses.
- 5
We could be doing more
Reports built by hand every cycle. Data copied between systems. Tools used as chatbots. Everyone can feel the gap between what they're doing and what AI can do.
- 6
Nobody owns it
IT is at capacity and it isn't in anyone's job description. So it landed on whoever runs operations, on top of everything else, and with nobody to do it with.
What I help with
The work that sits between "we should be doing something with AI" and a company that does:
Employee enablement
Company-wide fundamentals plus training by department, so adoption reaches past the handful of people already experimenting.
Tool selection and integration
Which platforms to standardize on, which seats to consolidate, and how to connect the tools your teams already use.
AI strategy and roadmap
Where AI pays off in your business, and in what order, so you have a plan instead of a pile of pilots.
Governance, policy, and data
Usage rules and data handling your security and legal people will sign off on. Written for your stack, not copied from a template.
Workflow automation and agents
Find the workflows worth automating, prove them out, and build them or guide the build, with your systems and your constraints in the room.
Data analysis and reporting
Surveys, transcripts, and messy spreadsheets turned into clean analysis and answers, in a session rather than a week.
Three ways to work together
Two fixed-scope programs and one ongoing arrangement.
AI Enablement Program
Fixed scope, a few weeks
Get your teams using these tools, one department at a time. What helps your accounting team has little to do with what helps the people in the field, so nobody gets the same generic prompts.
- Week one: an AI fundamentals session for the whole company
- Then one department at a time, sitting with the people doing the work
- Prompts and small automations built around each team's real tasks
- Each team ends with a handful of things they use every week
- Individual coaching and scheduled follow-ups as needed
AI Readiness Assessment
Fixed scope, a few weeks
Find out where AI and automation would help your business before anyone buys a tool. Most of what I find isn't AI work at all, and I'll say so.
- A short call with each department lead to hear where the roadblocks are
- Research into how each team works and what already fits
- A longer working session with each full department
- A prioritized roadmap: what to automate, which tools to use, and what not to touch
- A draft usage policy, so the roadmap comes with rules
Fractional AI Support
Month to month
An AI person for your company, without hiring one. Leadership uses me to work out what to do next. Your team books time with me to get it done. Same person, month to month.
- Flat monthly fee, pause or cancel whenever
- Anyone on your team books time with me whenever they're stuck
- Screen-share sessions: we build it, fix it, or find the tool that already does it
- Training, building, and integrating the tools your team already uses
- Straight answers on what isn't worth doing
Every engagement gets scoped to your company over a few conversations, so these are starting points rather than a menu. Large builds are scoped separately.
Standard MSA and NDA, your paper or mine. Invoiced on your terms.
What this looks like in practice
A few recent engagements, grouped by how we worked together.
It all starts with a 30-minute intro call.
Book an intro callWhy not hire someone?
| Figure it out in-house | Hire a full-time AI lead | Bring in a consultancy | Movemnt.AI | |
|---|---|---|---|---|
| Cost | Your team's time, plus unused licenses | $220-300k+ fully loaded | $150k-500k per engagement | A fixed-scope project, or a flat monthly fee |
| Time to value | When someone has the time | 4-6 months to recruit and ramp | 6-10 weeks of scoping and SOWs | Discovery sessions, a statement of work, then we start |
| Who does the work | Whoever can fit it in alongside their real job | Whoever you can land | A rotating pod, often junior | Me, every engagement |
| Commitment | Nothing formal | A permanent headcount | Six-figure SOW up front | Fixed scope, or month to month |
| Adoption | A few power users, the rest hesitate | Depends on who you hire | A deck and a handoff | I sit with the people doing the work |
If you have full-time AI work every week, hire someone. Most companies don't, yet. They have leadership asking for a plan and a few people experimenting. That is a few weeks of focused work, or a few hours a month, and by the time it needs a headcount you will know what the role should be.
From "we should do something about AI" to something your teams use
How it works
- 1
Intro Call
A quick 30-minute call to understand where your company is at with AI, what leadership is asking for, and whether I'm the right person to help.
Book a Call - 2
Discover
A few working sessions with you and your leadership team to dig into your issues, priorities, and concerns. This is where we work out which approach fits: training, readiness assessments, or fractional support.
See Engagements - 3
Decide
Based on what came out of discovery, I send a short proposal: what we'd do, in what order, and what it costs. Once everyone's comfortable with it, it becomes a signed statement of work.
Learn More - 4
Start
Sessions get scheduled around your priorities and your team's availability. Everything I produce lives in your systems, and you own it whether or not we work together again.
See Recent Work
Not sure which one? That's what the intro call is for. If your teams need training, start with enablement. If you don't yet know where to focus, start with the assessment. If you'd rather have an expert you can call on when you get stuck, start with fractional support. Whichever you choose, it starts with the same thirty-minute call.
Fixed scope, or month to month.
I work with the tools your teams already use.
Whatever your company runs, that's where the work happens. If it has an API, I can connect to it. If it doesn't, there's usually an export. Nobody has to switch systems to get started.
Microsoft Copilot
M365, Azure OpenAI
Google Gemini
Google Workspace
Claude
Enterprise, Cowork, Code
ChatGPT
Enterprise, Codex
Common business systems
Microsoft 365
Google WorkspaceSalesforce
HubSpot
SlackSharePoint
Zoom
AsanaMonday.com
Notion
AirtableNetSuite
QuickBooksMicrosoft Dynamics GPAppFolioWorkdayDocuSign
StripeWhat I build and integrate with
Zapier
Make
n8nPower Automate
Cursor
GitHub
Vercel
Cloudflare
SupabaseApifyRetell AI
VapiPipedream
ResendAll product names and logos are property of their respective owners and are used for identification only. No endorsement implied.
Who you're working with
I'm Tom Bouwman. I spent nearly two decades as a solutions architect and sales engineer, running discovery, designing systems, and getting IT, security, finance, and operations to agree on one answer. For the last three years I've worked with AI full time, as a builder first and an advisor today. I started Movemnt.AI because the hard part of adopting AI is deciding what to do, in what order, and getting your people to use it.
More about meLet's find out if it's a fit.
Thirty minutes, no pitch deck. Tell me where your company is with AI and what leadership is asking you for, and I'll tell you honestly whether I'm the right person to help, and what I'd do first if I were.
Prefer email? tom@movemnt.ai