Workflow and process design
Mapping how work actually enters the team, who owns each step, and where it stalls. Then rebuilding the path from request to delivery with clear stages and definitions of done.
Marketing Operations
Marketing operations and process design.
Most marketing teams do not have a talent problem. They have an operations problem. I design the workflows, documentation, and automations that let a team ship consistently without chasing every handoff.
What the engagement includes
SOPs and documentation
Standard operating procedures written to be followed, not filed. Short, task level, and paired with templates so new team members can produce on week one.
Automation and AI assisted handoffs
Task routing, status updates, recurring reporting, and drafting support built into the tools the team already uses, so admin work stops eating billable hours.
Capacity and load balancing
Planning around how long work truly takes rather than counting tasks, so assignments are fair and deadlines are realistic.
How I work
01
Observe
I sit with the current system, review the tool setup, and interview the people doing the work before changing anything.
02
Design and pilot
One team or one workflow gets rebuilt first. Once it holds up under real volume, it becomes the pattern for the rest.
03
Train and hand off
Documentation plus recorded training so the system survives after the engagement ends and does not depend on me.
Based in Utah County
Springville, Utah. Working with teams across the state and remote.
I work with agencies, contractors, and in house marketing teams across Utah County and the Wasatch Front, along with remote teams. Recent operations work includes a two month migration from Monday.com into a fully customized ClickUp build with automated SOPs and a ten module training library.
Selected work
Case studies from real engagements
Green House Sales and Marketing
Agency systems architecture: Monday.com to ClickUp migration
The problem. The agency was executing client deliverables and campaigns across Monday.com with inconsistent project structures, which created communication gaps, administrative friction, and slower handoffs between departments.
What I did. Engineered a full agency wide migration to ClickUp. Designed custom space architectures, standardized task templates, and automated status workflows that map directly to marketing operations, then created and implemented a complete staff training protocol.
The outcome. Unified client execution under a single system, standardized project lifecycles across accounts, and removed operational friction with minimal supervision.
- Agency wide migration
- Standardized templates
- Staff training protocol
Green House Sales and Marketing
Full spectrum agency operations and client portfolio leadership
The problem. Managing a high volume portfolio of distinct clients, each requiring tailored strategy, technical execution, and strict quality control without administrative bottlenecks.
What I did. Led comprehensive digital marketing and systems operations across the board. Spearheaded end to end project management encompassing custom website design and web development, local SEO, paid media campaigns, social media strategy, reputation management, brand architecture, content creation, and professional videography, with rigorous operational frameworks keeping every deliverable on time.
The outcome. Delivered a diverse suite of digital marketing assets and infrastructure that modernized client brands, established local search presence, and scaled lead generation across multiple industries.
- Multi client portfolio
- End to end delivery
- Quality control frameworks
Common questions
Which tools do you build in?
ClickUp most often, along with Monday.com, Asana, Notion, and Google Workspace. I fit the system to the tool the team will actually keep using.
How long does an operations engagement take?
A focused workflow rebuild takes a few weeks. A full platform migration with training usually runs two to three months.
Will the team adopt it?
Adoption comes from training and simplicity, not from the build itself. Every engagement includes documentation and walkthrough sessions for that reason.
What does the first two weeks look like?
I map how work actually moves today, where it stalls, and who owns each handoff. That map is what the build is based on, so we are not automating a broken process.
Do you write the SOPs or do we?
I write them, then have the people doing the work review them. A procedure written without the operator never survives contact with a busy week.
Where does automation help and where does it hurt?
Automation is good for status changes, handoffs, reminders, and reporting. It hurts when it hides decisions people should be making, so I keep approvals human.
How do you handle reporting for leadership?
One recurring view with the few numbers leadership actually acts on, pulled from the same system the team works in so nobody maintains a separate spreadsheet.
What happens after the engagement ends?
You keep the documentation, templates, and training material, and an internal owner is trained before I step out.
Related services