Digital workflow optimization, in the right order.
Growth broke your workflow. Most fixes install software before anyone understands the process it replaces. We map how your team actually works, cut what is redundant, and only then automate. Enterprise discipline, sized for a team that never had it.
My own track record, across enterprise agency and studio environments. Detail below.
The scaling paradox
Informal ways of working scale, right up until they suddenly do not. Without operational discipline, revenue growth leads directly to operational chaos.
- Every approval routed through you is an hour you are not selling.
- Every deadline that slips is a client relationship you spend the next quarter repairing.
- Every project whose margin you cannot see is one you may be losing money on right now.
Where teams get stuck
Approval Bottlenecks & No Visibility
You end up approving every small detail because the tools do not talk to each other. Without a dashboard showing real margins and capacity at a glance, there is no way to actually step back.
Tool Chaos & Misaligned Teams
Software gets deployed without clear governance. Redundant steps, missing handoffs, and siloed communication turn into missed deadlines and team frustration.
You Are Running On Averages
You know roughly how long a job takes and roughly what it costs. When someone asks for the actual number, nobody can produce it, because the data was never captured in a form anyone can query.
Output And Headcount Stopped Matching
You have added people and the throughput has not moved with them. The team is absorbing the difference in hours and stress, and that is a cost that shows up later as turnover.
Why most operational fixes fail
The PREPARE Framework
Structure and clarity come before technology. Fix the operating model first, automate second.
For most of 25 years I watched people take sides. One camp says people over process. The other says process over people. I have always believed in process for people.
Designing a workflow someone will actually use means understanding the psychology of the people already doing the work, not just the steps on paper. Selling a redesign to leadership is the easy half. If the team does not accept it, it fails quietly and everyone goes back to the old way. So I listen first, and I roll changes out in pieces, even when I can already see the whole picture, because handing someone the whole picture at once is how you overwhelm them.
PREPARE is that sequence, written down.
Probe
Interview the team before prescribing anything. Understand how the work actually moves.
Record
Map the current state as it happens, not as the process document claims.
Eliminate
Cut redundant steps and assign a single owner to each remaining one.
People
Redesign around the people who will run it daily, then test it with them before rollout.
Arrange
Sequence the common path first. Route edge cases separately instead of building for them by default.
Rules
Encode the decisions that are deterministic. Save AI for the ones that need judgment.
Evolve
Ship in small increments that build trust, not one overhaul that invites resistance.
Probe
Interview the team before prescribing anything. Understand how the work actually moves.
Record
Map the current state as it happens, not as the process document claims.
Eliminate
Cut redundant steps and assign a single owner to each remaining one.
People
Redesign around the people who will run it daily, then test it with them before rollout.
Arrange
Sequence the common path first. Route edge cases separately instead of building for them by default.
Rules
Encode the decisions that are deterministic. Save AI for the ones that need judgment.
Evolve
Ship in small increments that build trust, not one overhaul that invites resistance.
You cannot simplify a process you have not mapped.
Twenty-five years in delivery.
25 years across software development, animated production, and visual effects, spanning India, Germany, and North America. Seven of those years leading enterprise digital delivery on large-account programs. I lead every engagement personally, backed by a vetted network of 25+ technology partners who work as an extension of the team.
Selected experience
Selected work from 25 years across enterprise agency and studio environments. Client names withheld under confidentiality.
Largest US telecom provider
There was no intake form and no briefing process. Work arrived informally and we went into client meetings blind, without knowing what the brief was, when it was due, or what was expected of us. Projects at that volume look alike, the team sat in three locations, and there was no shared reference for any single piece of work.
Across roughly 11,000 deliverables a year, on the same headcount. Fewer QA misses, fewer revision rounds, and faster project closure, without adding people to the account.
Intake, and one project ID
I built an intake form split by digital and print that asked the questions the client needed to answer upfront. On submission it generated a unique project ID and notified the team automatically. I then enforced that ID everywhere downstream: email, documentation, estimates, invoicing. At that volume, across three locations, one shared identifier is the difference between a conversation and a guess.
One estimate template
I built a single Google Sheets estimate template with embedded identifiers and required every team to use it, stored in one Drive structure. Estimating stopped being a per-person habit and became a format the whole account shared.
Reporting that ran itself
I wrote an Apps Script that walked the Drive folder every night at 2am, pulled every estimate into one sheet, and fed it into Snowflake alongside the intake data. Project counts, delivery volume by asset type, and monthly and quarterly earnings became live rather than reconstructed after the fact. Duplicates were flagged to the project owner the same night.
Alignment through production
I built a deliverable matrix that the client and the production team both worked from, so scope stopped being interpreted twice. With the brand guardian I built design templates the team assembled from, and with the QA lead I documented a QA checklist. The templates cut design time and QA misses at the same time, which is where the revision rounds went.
Leading Canadian telecom
Licensed animal photography arrived from several partners with no central home to track usage or license expiry. I built a centralized library, which the team nicknamed the Critter Library, tracking location, fees, and expiry dates in one place.
Singapore television
An animated series running to a two-month-per-episode industry standard, with a crew that could not be expanded. I restructured the production sequence rather than adding people to it.
How we work together
A fixed-scope audit to diagnose and build the foundation, then implementation and ongoing oversight that protect delivery speed and give you your time back.
A current-state map
Exactly where work enters, how it moves, and where it stalls. Drawn from how your team actually works, not from how the process document says it works.
A ranked cut list
What can be eliminated, in priority order, with the time each redundant step is costing you now. You will be able to see what your averages have been hiding.
A 90-day sequence
What to fix first, what to automate, and what to leave alone. Written so you can run it yourself, with or without us.
Ops & Workflow Audit
If you decide within 7 days of delivery that the audit did not surface changes worth more than its fee, you do not pay. Your call, no discussion.
Already have a documented problem and a scope in hand? We skip the audit and move straight to delivery. Everything else, including my personal ownership of the work, stays the same.
Fractional Operations Lead
I scope and brief every engagement precisely. Our network of 25+ vetted technology partners handles execution as an extension of your team, from workflow tooling to custom development and design builds, so you never hire headcount you do not need.
Implementation engagements, where the network builds what the audit calls for, typically run $40,000 to $80,000 CAD depending on scope and team size. If that range is not realistic for you right now, the audit still stands on its own: you keep the map, the cut list, and the 90-day sequence, and you can run them yourself.
One point of contact. A delivery network behind it.
Most small and mid-size businesses have needs that outside delivery could solve, but lack the resources to find, vet, and manage a team themselves. That is the gap we close. You contract with one Canadian company, and our vetted network of 25+ technology partners executes across the US, Canada, the UK, and India.
- Diagnosis and current-state mapping
- Workflow architecture and the operating model
- Requirements and the technical brief
- Partner selection and sequencing
- Governance and executive communication
- Review and sign-off on everything before it reaches you
- Workflow tooling and automation
- Dashboards and reporting
- Custom web and app development
- Design and production overflow
- Data and AI integration
- ERP, cybersecurity, and infrastructure, on request
When a specialist is the right person to answer your question, I put them in front of you directly rather than relaying it back and forth. What does not change is that nothing ships to you until I have reviewed it. I do not hand over work I have not scrutinised and do not understand myself.
The three engagements below were delivered by partners in this network. They are shown as evidence of what the network can execute, not as my own case studies. My own work is in the section above.
Global executive search firm, Switzerland
Same firm
Intersnack, Germany
Who this is for, and who it is not.
- You are roughly 12 to 40 people and you have grown faster than your process.
- You are managing on averages, and when someone asks for the actual number, nobody can produce it.
- You cannot explain your own process to me in plain language without calling it complicated.
- Your output and your headcount stopped matching, and the team is carrying the difference.
- You are being pushed toward automation or AI and you do not know what has to come first.
- Leadership does not have a clear direction for the company. I cannot redesign an operating model in service of a destination nobody has chosen.
- The team is not growing. This work pays back through scale, and without growth the return is not there.
- You want someone to install software. That is the mistake this practice exists to prevent.
The onboarding sequence
Discovery
A call to identify your core bottlenecks and financial tracking gaps. No prep required on your side.
The Audit
2 to 3 weeks inside your workflows, tool configurations, and team handoffs.
Build & Roadmap
The network deploys the tracking, reporting, or workflow tooling the audit actually calls for. I brief it, review it, and sign it off.
Ongoing Oversight
Fractional operations leadership that keeps delivery fast and accurate as you grow.
Tell me where the work is getting stuck.
A 30-minute call. I will ask how your projects actually move through the shop and where they stall. If I can help, I will tell you how. If I cannot, I will tell you that too.
Engagements are contracted through Motion by Videopost Inc., a Canadian company holding the insurance and infrastructure behind delivery.