The task, worked through.
A saved workflow or reusable template, with a tool-choice map and enough context for someone else to run it.
Workshops with Vince DiPaola
From AI access to measured AI adoption
I help business teams use AI on the work they already own: a weekly report, a support handoff, the task that keeps eating an afternoon. We build and check a reusable workflow together, using your approved tools.
For People, Operations, and Enablement leads who want their teams to use the tools they've already bought.
A good fit
The tools are there. The working habit isn't.
A few people use AI every day. Others tried it twice and went back to the old process. Your engineers have a product to build, and your business teams need somewhere to practice.
I work with People, Finance, Ops, Support, Legal, and Strategy teams. Mixed comfort levels are welcome: we'll use a task people recognize and a result they know how to judge.
Bring a recurring task, access to an approved tool, and someone who reviews the work. I'll help you choose a safe example and set a useful finish line.
What leaves the room
Something your team can use again.
We turn the task into a workflow, write down how to run it, and decide how you'll know whether it helps.
Who checks what.
A Loop Engineering Canvas or skill-request card that names the inputs, permitted actions, and person responsible for review.
A way to check the difference.
Record the baseline, time to a usable result, quality, and review effort. Where there isn't enough evidence yet, name the uncertainty and what to measure next.
Download the blank measurement card. It includes a separately labeled synthetic example; it doesn't report a client result.
See a worked example: improving a support handoff
Support-call review
illustrative example01 · Observe the handoff
Start with the evidence that actually exists.
- Inputs
- Completed support-call records, redacted transcripts, and the fields in the current intake form.
- Gap
- Some handoffs arrive without a reason, next owner, or approved escalation path.
- Boundary
- Review the records; don't change the live agent.
If the evidence conflicts or the gap isn't clear, send it to the support lead.
02 · Build the bounded draft
Draft the repair without publishing it.
- Action
- Group the handoff problems and draft changes to the intake form so it captures the missing information.
- Context
- Keep each suggestion tied to its transcript, source version, and approved escalation policy.
- Blocked
- No production change and no live-agent edit.
Keep the proposed fields, supporting call records, and open questions together for the reviewer.
03 · Measure before release
Check the draft independently.
- Verifier
- A required-field check against an independently reviewed test set.
- Question
- Are the handoff reason, next owner, and escalation path present and valid?
- Decision
- The support lead approves, revises, or stops the proposed change.
Agent confidence isn't the check. Uncertain cases escalate for human review.
Illustrative example from the workshop worksheet. Open the contract · Read the workshop source
Formats · start where your team is
Choose the size of the first step.
Start with one team and one workflow, or make room for several functions to practice together. Every format includes hands-on work, a measurement card, and a recommended next step.
Working session Start here
One recurring workflow, rebuilt live. A short pre-survey helps us choose it. You leave with the workflow, a mini tool-choice map, a measurement card, and a recommended next step.
From $5,000 · credits toward any larger format booked within 60 days
Foundations + discovery
A shared baseline for a bigger group: tool-choice judgment, safe-context habits, and hands-on labs across functions. Discovery runs alongside, so leadership gets a ranked map of which workflows are worth building first.
Leaves behind: ranked workflow opportunity map
Operator bootcamp
Day one builds the baseline. Day two breaks out by function: People, Finance, Ops, Support, Legal, each drafting workflows on their own work, with specs your AI team can actually build from.
Leaves behind: drafted workflows, skill-request specs, measurement cards
Applied adoption clinic Recommended
The full arc, through agent literacy. Then follow-ups at weeks 2, 4, and 6 while the new workflows meet reality, ending in a leadership readout: what lifted, what stalled, what to request next.
Leaves behind: measurement findings, leadership readout
The working session starts at $5,000 and credits toward a larger engagement. Pricing for the day formats is scoped on the call. Travel billed at cost.
The scope depends on how many people are participating, the workflows we'll practice, the preparation involved, and the follow-through you want. We'll agree on those details and the total price before you book.
Day formats run onsite-first. Remote delivery is available for distributed or non-US teams.
Why work with me
I've done the work. I build the tools. I teach both.
You work directly with me, from choosing the task to reviewing what your team makes.
At Cision, I carried a $1.6M ARR book across 125+ accounts while building the team's 50+ entry Skills library and running AI workflow sessions at the company summit. I know what adoption asks of someone who still has a day job to do.
I now build prototypes and teach with these tools daily. Prompt Runner, my personal sales-workflow prototype, shows how I turn a task I know into a tool someone can inspect and use.
Public workshop · Loop Lab
A teaching practice you can inspect.
I taught Build Your First Agent Loop at Vonage and TechWalk's NYC AI Builder Nights at Fabrik DUMBO. Participants used the companion exercise shown above to define a task, an independent check, and a point for human approval.
Read the workshop case study · Organizer's event record
My Vonage Developer Blog article applies the same approach to reviewing voice AI.
Working together
Short explanation. Time to practice. A useful readout.
- Choose the task before the session. A short pre-survey surfaces recurring work, an AI win, and a failed attempt. We agree on the examples and your team's review rules.
- Work in small blocks. Expect 10–15 minutes of explanation, 30–45 minutes of hands-on work, and a 10-minute readout. Experienced users help their tables; beginners get room to practice.
- Keep the boundaries visible. Use sanitized or fictional inputs. Sensitive data stays out of exercises, meaningful outputs get a reviewer, and new requests follow your AI team's governance path.
- Check what sticks. Every format leaves measurement cards. The 3-day clinic includes check-ins at weeks 2, 4, and 6; smaller formats can add follow-up sessions.
I'm based in Brooklyn and work with teams worldwide. The scoping call confirms the format, time zone, and any on-site arrangements.
Common questions
FAQ
Can we start small?
Yes, that's what the working session is for. One team, one workflow, 2.5 hours, no procurement cycle. If it lands, the fee credits toward any larger format you book within 60 days. You're not betting the quarter on a workshop.
Onsite or remote?
The working session runs remote or onsite in NYC, whichever fits your team. The day formats run onsite-first because the lab energy is the point, with remote delivery available for distributed or non-US teams.
How many people per format?
Up to 12 for the working session, one team at a time. The day formats run from about 10 to about 50 people, with the foundations day best up to about 40, and function breakouts once the group is bigger than one room's conversation.
What about procurement, NDAs, and vendor onboarding?
They run in parallel with prep. NDAs, security questionnaires, and vendor onboarding happen while the pre-survey and scoping work are underway, so the session doesn't wait on paperwork.
What does our company need to provide?
Three things: tool access for participants on whatever your teams already use, the language of your AI-adoption goals so the labs aim at them, and 1 or 2 internal support people who can unblock access questions on the day.
Is follow-through available for the smaller formats?
The 6-week follow-through is built into the 3-day clinic. For the working session and the day formats you can add follow-up sessions, and every format leaves measurement cards behind, so the check-ins have structure either way.
Book a scoping call · Step 1 of 2
A few quick details
One call, 30 minutes. You bring the adoption goal and the teams that are stuck. I bring the format recommendation and the scope. You get a written proposal within two days. Not sure which format fits? Compare the formats first.
Step 2 of 2
Pick a time
I'll read your notes before the call. If nothing here works, email [email protected] and we'll find a time.
Prefer plain email? Write me at [email protected]. Two or three sentences about the team and the goal is plenty.