Show how services
works today.
You sent your framework and examples, then suggested walking through the ticket system together. We had a real process and the people doing it to work from.
Start with the team's actual workJoe, we started with your services framework. Then you brought Nick and Gianni’s workflows into the conversation. That is the direction I want to keep building on.
My idea is to put a small team around that work: I lead it, we work with you and Charlie, and we turn the team’s priorities into connected workflows with ongoing support.
“There is likely a phase 5&6 that will be added to this.”
ANC Labs: a small external team I lead, working with your people to carry this forward.
You brought the framework and the people. Here is how that conversation developed.
You sent your framework and examples, then suggested walking through the ticket system together. We had a real process and the people doing it to work from.
Start with the team's actual workYou said Nick and Gianni would show us the workflows they were running across the project tracker and operations tables, for a number of use cases.
Your direction: look beyond the dashboardAfter meeting Nick, Gianni and Alexis, I wrote back: those workflows fit naturally into the CRM work. I proposed one platform at the account level and coordination with Charlie and Jireh.
My response: consolidate the workSource: our “Automation: Joe – Introduction” email thread, 18 March–10 April 2026. This is the history of the discussion, not a claim that every workflow has shipped or that phases 5 & 6 remain a separate scope.
That is where ANC Labs fits: a dedicated partner team for the platforms and workflows. You set the priorities; we agree the responsibilities and get the work done together.
Connect the work.
Stay with it after delivery.
Creative support,
when ANC needs it.
Alongside the operations idea, I would offer a separate Studio for client work. This is an additional proposal, not something your phase 5 & 6 email asked for.
Existing commitments continue under the current agreement. ANC Labs would need its own agreed responsibilities and terms; this concept does not change existing ownership or obligations.
Your email pointed to several use cases. These examples show how I propose we work through one at a time, with the people who use it.
Start with a workflow from Nick and Gianni’s review. Revisit it with the team, check what is already covered and agree what still needs attention.
The team walks through one real use case and where the handoff breaks down.
Check existing capability, confirm the gap and agree the priority and scope.
Configure the workflow, test it with its users and resolve the friction.
Document the process, support adoption and review whether it helps.
A connected workflow with an owner, a clear next action and fewer manual handoffs.
The model starts with the existing team. We would agree responsibilities together before making commitments about who owns each part.
Bring the priorities, help define a useful result and agree the arrangement.
Lead the agreed delivery, coordinate support and show what is finished and what needs attention.
Stay involved in the migration and the ongoing plan. Agree responsibilities and support together, based on what the work needs.
Show how the work happens, test the proposed changes and confirm whether they help in practice.
Your current priority is helping Charlie with migration. Keep that moving, then sit down with the team to agree which workflows need attention and how we support them going forward.
Walk through the workflows with the team again. Check what already exists, what has changed and which two priorities still need attention.
Output: an agreed planWork through the agreed priorities with their users. Test the complete handoff and put support and guidance around it.
Output: useful, tested changesAsk the team what is easier, what they actually use and what still gets stuck. Agree the next priorities from that evidence.
Output: an informed next stepLet’s get the migration finished with Charlie, revisit the workflows with the team, and agree how I can keep taking this forward with you.
Which of those use cases still needs attention?
What should we each take responsibility for?
What support and arrangement would make this work?