A proposal from Ahmad

You saw more
we could
connect.

Joe, 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.

Follow the story
Discussion concept · October 2026
DIRECTIONANC sets the prioritiesYour people. Your business. Your decisions.
ANCLABSLed by Ahmad
01OperateKeep work moving
02ImproveConnect the workflow
03CreateSeparate option
THE IDEA IN ONE LINE

ANC Labs: a small external team I lead, working with your people to carry this forward.

01 / Your email. Our next step.

It started with services.
Then the picture got bigger.

You brought the framework and the people. Here is how that conversation developed.

0118 MARCH 2026 · YOUR FRAMEWORK

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 work
026 APRIL 2026 · PHASE 5 & 6

Bring the other
workflows into view.

You 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 dashboard
0310 APRIL 2026 · MY RESPONSE

Connect it through
the CRM.

After 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 work

Source: 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.

02 / My proposal

Put a team around
the work we started.

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.

BUILT AROUND YOUR WORKFLOWS01

Operations

Connect the work.
Stay with it after delivery.

  • Platform continuityLook after the CRM, proposals and service operations as the team uses them day to day.
  • Workflow improvementStart with the use cases your people bring. Check what exists, then connect or improve the parts that need attention.
  • Team adoptionWalk through the changes with the people doing the work, support them and follow up on what still gets in their way.
Proposed ongoing arrangementAgreed responsibilities, support coverage and a visible delivery plan.
A SEPARATE OPTION02

Studio

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.

  • Presentations & client experiencesHelp turn a brief into a clear, polished client story.
  • Graphics & productionAdd capacity for agreed creative deliverables and revisions.
  • Reusable creative toolsExplore templates and products the team can use repeatedly.
Separately scoped workDeliverables, pricing and any licensing agreed for each engagement.

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.

03 / From the conversation to the work

Start with a use case.
Follow it all the way through.

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.

ILLUSTRATIVE EXAMPLE · PROPOSED PROCESS

Pick up one of the team’s use cases.

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.

  1. 01

    Show the process

    The team walks through one real use case and where the handoff breaks down.

  2. 02

    Agree the change

    Check existing capability, confirm the gap and agree the priority and scope.

  3. 03

    Build & test

    Configure the workflow, test it with its users and resolve the friction.

  4. 04

    Keep it working

    Document the process, support adoption and review whether it helps.

THE INTENDED RESULT

A connected workflow with an owner, a clear next action and fewer manual handoffs.

04 / With the people already involved

Build this together.
Agree who owns what.

The model starts with the existing team. We would agree responsibilities together before making commitments about who owns each part.

JOE + ANC LEADERSHIP

Choose what matters.

Bring the priorities, help define a useful result and agree the arrangement.

AHMAD + PROPOSED TEAM

Carry the work forward.

Lead the agreed delivery, coordinate support and show what is finished and what needs attention.

CHARLIE

Work it out together.

Stay involved in the migration and the ongoing plan. Agree responsibilities and support together, based on what the work needs.

NICK, GIANNI, ALEXIS + USERS

Bring the real workflow.

Show how the work happens, test the proposed changes and confirm whether they help in practice.

Continuity by designShared documentation, defined support coverage and a small team behind the lead.
05 / Where we start

Finish the migration.
Agree what comes next.

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.

PROPOSED FIRST 90 DAYS · FROM AN AGREED START DATE
01–30DAYS

Revisit the use cases

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 plan
31–60DAYS

Finish useful work

Work through the agreed priorities with their users. Test the complete handoff and put support and guidance around it.

Output: useful, tested changes
61–90DAYS

See what helps

Ask 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 step
THE CONVERSATION TO HAVE

“Joe, let’s pick up
where that conversation left off.”

Let’s get the migration finished with Charlie, revisit the workflows with the team, and agree how I can keep taking this forward with you.

01

Which of those use cases still needs attention?

02

What should we each take responsibility for?

03

What support and arrangement would make this work?