01
We map the path
We scope the Workflow with its owner: what starts it, each step, the tools, where a person checks, and the result.
From your team
Show us how the work moves today, and where it waits.
Workflows
Work that moves on its own,
from tool to tool
The numbers pulled from every ad platform, the script that becomes a voice-over and a video, the shortlist that becomes a booked interview.
We connect the tools you already run so each step starts itself. Your team checks the result, not every hand-off.
Book a Discovery Call30 minutes. Free.
See a Workflow at work
For work that crosses
more than one tool
A Workflow suits work that passes between tools, AI models or people, in the same steps every time.
Channel reports
Pull the week’s numbers from each ad platform, the shop and analytics into one draft report.
Video and audio versions
Turn one approved script into voice-overs and video cuts, using a different AI tool for each.
Campaign requests
Log each request as it arrives, ask for what’s missing and draft the brief for its owner.
New product pages
Draft descriptions and alt text when a product is added, ready for the brand lead to approve.
Review round-ups
Collect reviews from every site you sell on into one weekly digest of themes and quotes.
Hand-offs between teams
Pass the finished draft to the next person with the files they need, so nobody has to chase it.
Same work
Fewer hand-offs
Three jobs, drawn as the workflow that runs them: what starts it, the tools it reaches, the paths it takes and where your team checks.
Every Monday, 7:00Example
- ScheduleEvery Monday, 7:00
- Google AdsSpend and results
- Meta AdsSpend and results
- ShopifyOrders and revenue
- GA4Sessions by channel
- Google SheetsCombine into one table
- ClaudeDraft commentary for each channel
- If a channel is 15% or more off targetSlackFlag it to the channel owner
- SlackPost the draft to the growth channel
- Your teamChecks the draft · 20 min
- ReadyReport ready for Monday’s meeting
- By hand
- 110 min
- With a Workflow
- 20 min
- Time freed up per report
- 90 min
Script approved in the briefExample
- NotionWatch for an approved script
- ClaudeTighten the script for each format
- ElevenLabsRecord the voice-over
- HiggsfieldVertical video, 9:16
- HiggsfieldSquare video, 1:1
- If the brief asks for YouTubeHiggsfieldWide cut, 16:9
- Google DriveSave every version to the campaign folder
- Your teamPicks and edits · 40 min
- ReadyVersions ready to upload
- By hand
- 200 min
- With a Workflow
- 40 min
- Time freed up per script
- 160 min
Candidate moved to interviewExample
- GreenhouseA candidate is shortlisted
- Google CalendarFind slots the whole panel shares
- If no slot this weekSlackAsk the recruiter who to swap in
- If slots are freeClaudeDraft the invite and the panel’s questions from the role and CV
- If the role is seniorSlackAdd the head of HR to the panel
- GmailSave the invite as a draft
- The recruiterChecks and sends the invite · 10 min
- SlackSend the questions to the panel
- ReadyInterview booked, panel briefed
- By hand
- 75 min
- With a Workflow
- 10 min
- Time freed up per candidate
- 65 min
Your path,
running in your tools
You keep five things, yours from the day it goes live.
The Workflow
Built in your automation platform, live in your accounts, with an alert that tells its owner if a step fails.
The instructions for its AI steps
Where a step uses AI, its instruction is a plain page in your account your team can read and change. With a Team Brain, it reads those pages too.
The runbook
One page: what the Workflow does, and what to do when it breaks.
The operating rules
What it may do on its own, what needs a person’s yes, and what it must not touch. You agree them before it goes live.
Trained owners
Training for its owner and your AI Ambassador: running it, reading an alert and keeping its rules current.
Built around
your real work
We do the building. Your side needs one named owner, about two to four hours a week while we build.
02
We build it in your accounts
In the tools you already run, without custom code wherever the tools allow. If a small code step is ever the only way, we say so and write it into the runbook.
From your teamGive us access, or have your own person build while we direct.
03
We test it on your real data
We run it on real work, test its failure alert, and adjust until the owner signs it off.
From your teamGrade the results before it goes live.
04
We put it live and train the owner
It goes live in your accounts with its runbook and rules. With more than one, the first is live before the next one starts.
From your teamName who owns it and who keeps its rules current.
Your team keeps
the judgement
Nothing goes out without a yes. A Workflow asks before it publishes, sends anything outside your company, or changes your CRM, ad account, product catalogue or website. Once it’s live, you can sign off one named action to run without asking.
Run
The Workflow does its steps
Workflow at workApprove
The owner approves or changes it
Your judgementReady
Work goes out
Work moves forwardA named owner
Responsible for the Workflow, its alerts and its results.
One AI Ambassador
The one person who changes its rules and AI instructions. It can be anyone on your team. Until you choose someone, it’s you.
15 days of small adjustments
From each Workflow’s delivery, at no cost.
Ongoing support
Your team owns the Workflow from go-live. After the 15 days, changes, new steps and fixes when a vendor changes its tool come under the Fractional AI Operator.
Explore the Fractional AI Operator
A few questions
you may have
Do we need an audit first?
No. If you know the work you want to connect, you can start with a Workflow. We work out the detail together in Workflow Scoping, at the start of the build.
When is a Skill enough?
When one AI assistant can do every step itself, using its own connectors. A Workflow is for what it can’t do in one go: reach a tool none of its connectors reach, use a second AI company, or hand work to someone else with nobody starting the next step. If someone must approve halfway, two Skills often do it. We tell you which you need.
Explore SkillsDo you write code?
No. We build with what the tools give us: scenarios, connectors and plain instructions. If a small code step inside the tool is ever the only way, we agree it with the owner first and write it into the runbook. We never leave behind software that needs maintaining.
Can we use our existing tools?
Yes, when they do the job well. Make.com, n8n, Zapier or whatever is already on your bill. If you have nothing suitable, or another tool would serve you better, we explain why and show its licence cost. You decide and pay the vendor directly.
What happens when a tool changes?
It will, sooner or later. The Workflow’s alert tells its owner when a step fails, and the runbook says what to do. In the first 15 days, we adjust it at no cost. After that, either your person fixes it or we do, under the Fractional AI Operator.
How do we judge whether it’s worth building?
By the hours it gives back. We check whether those hours, at what your team’s time costs, pay for the Workflow within six months. With no audit, we check this in Workflow Scoping, after signing, and tell you if it falls short. These are estimates, not promises.
Who owns the Workflow?
You do, from the day it goes live. It runs in your accounts, under your licences.
Where does
your team’s work wait?
Bring one piece of work that stalls between tools or people to a free, 30-minute Discovery Call. We’ll look at whether a Workflow fits it. If it does, your proposal follows within one working day.
Book a Discovery Call30 minutes. Free. A conversation about your work.Explore Agents