Working With Me
What to expect when I embed with your team.
Your leadership brought me in for outcome assurance. This page explains how the engagement actually works — what I need from you, what you'll get from me, and how we'll communicate.
Engagement Structure
I offer three engagement types depending on where you are in your migration:
Assessment
Best for teams evaluating whether to migrate, or wanting a second opinion before signing an agency contract.
Deliverables: Platform decision framework, gap analysis, build vs. buy assessment, requirements foundation, vendor evaluation criteria
Clear migration decision with stakeholder buy-in
Migration Support
Best for teams mid-build who need someone to own cross-functional readiness. Can be scoped to specific workstreams.
Deliverables: UAT library (100–200 scenarios), department sign-offs, migration dry runs, phased release plan, rollback procedures, go/no-go criteria
Successful launch with minimal business disruption
Can be scoped to UAT only, data migration oversight, CX readiness, or launch coordination
Post-Launch Optimization
Best for teams who launched but aren't getting full value from their new stack.
Deliverables: Integration audit with prioritized fixes, automation gap analysis, flow implementations, team training, internal documentation
Full stack value realization with team independence
What I Need From You
For the engagement to work, I need access and participation:
A primary point of contact
Someone who can unblock access requests, schedule stakeholder time, and make day-to-day decisions. Usually a PM, project lead, or ops director.
Stakeholder access
I'll need 30–60 minutes with leads from each affected department (CX, ops, marketing, data, engineering) during discovery. Ongoing access for UAT sign-off.
Tool access
Admin or analyst access to relevant platforms — Shopify, Klaviyo, Ordergroove, Gorgias, etc. Read access to project management tools (Jira, Asana, Linear).
Agency/vendor introductions
If you have an implementation agency, I'll need to coordinate with their PM. I'm not here to replace them — I'm here to catch what falls between scopes.
Decision-making clarity
I'll surface tradeoffs and make recommendations. I need to know who has authority to make calls when we hit blockers.
What You'll Get From Me
Weekly status updates
Written summary every Friday: what got done, what's blocked, what's next. No surprises.
Risk register
Living document of open risks, owners, and mitigation status. Updated continuously.
UAT library
Spreadsheet or Notion database of every use case, acceptance criteria, test status, and sign-off. Your team keeps this after I leave.
Decision log
Record of key decisions, who made them, and why. Useful when someone asks 'why did we do it this way?' six months later.
Async availability
Slack or email access during business hours. I respond same-day to blockers.
Handoff documentation
At engagement end, everything is documented and transferred. No dependency on me to maintain what we built.
How We'll Work Together
Week 1: Discovery
Stakeholder interviews, tool access, current-state documentation. I learn how your business actually runs.
Weeks 2–3: Framework
Build the UAT library, risk register, and project plan. Align with agency on scope boundaries.
Ongoing: Execution
Run the UAT program, coordinate dry runs, surface issues, track sign-offs. Weekly syncs with you; ad-hoc with stakeholders.
Pre-launch: Go/No-Go
Compile readiness assessment. Present recommendation to leadership. Support the decision, whatever it is.
Post-launch: Stabilization
Monitor for issues, coordinate rapid response, document what we learn. Typically 1–2 weeks.
Handoff
Transfer all documentation, walk through with your team, close out.
Communication Cadence
| Audience | Format | Frequency |
|---|---|---|
| You (project lead) | Slack + weekly sync | Daily async, weekly 30-min call |
| Department stakeholders | UAT reviews | As needed during testing phases |
| Leadership | Status summary | Bi-weekly or on-demand |
| Agency/vendors | Coordination calls | Weekly during active build |
Common Questions
No. Your agency builds. I make sure what they build actually works for your business. I'm the verification layer, not the implementation layer.
I can slot in at any point. We'll do a rapid assessment of where things stand and scope to the workstreams that need the most help.
I'll tell you if I think you should. The decision is yours — I provide the information and recommendation, you make the call.
Yes. Common examples: UAT only, CX readiness only, data migration oversight only. We'll define deliverables and timeline for the specific scope.
Everything is documented and handed off. Your team owns the UAT library, the decision log, and any processes we built. No ongoing dependency.
Remote by default. I can travel for key moments — kickoff, go/no-go, launch week — if it's valuable. We'll discuss during scoping.
Ready to scope an engagement?
If your team is evaluating, mid-build, or just launched, let's talk about what you actually need.