I help you streamline and create working systems.
Most consultants hand off a slide deck. These engagements hand off working systems. Actual workflows in your environment, owned by your team, with hours saved you can measure.
Built for the people running events, not Fortune 500 procurement.
The systems, workflows, and tools are scoped to the way event teams and bureaus actually work. If your week revolves around RFPs, timelines, stakeholder comms, post-event surveys, or speaker pipeline, you're the right fit.
In-house event teams
Corporate event leads, association staff, and university event offices running 10+ events a year who need AI inside their existing process.
Event agencies and production companies
Agencies pricing on hours who want to protect margin as clients ask for more, faster. I focus on the workflows that compound across every event you deliver.
Associations and member orgs
Lean teams supporting a board, a conference, and year-round programming. AI here extends the staff you have without changing the experience members expect.
Speaker bureaus
I run Silicon Valley Speakers and have built the AI stack that powers it. Lead intake, contract automation, speaker matching, and post-event follow-up are all on the table for other bureaus that want the same leverage.
What the work actually looks like.
Hands-on working sessions, built around your team and your workflows. You'll ship the systems live, with someone who's done this before, and your team owns and maintains them after the engagement ends.
- 0:00Standup. What shipped this week, what didn't, why.
- 0:10Sponsor recap system. Debug the last three events.
- 0:35Iterate the v2 workflow live with the team.
- 1:05Test against last quarter's data.
- 1:20Decide: ship or hold for one more week.
Live working sessions
Every session ends with something shipped or a clear next-step owner. Your real workflows, your team, your decisions on what to keep.
- Event Timeline Generator2,000+ event pros using it
- 0-10 AI Readiness ScorecardAudit any workflow
- Sponsor Recap DrafterCustom-built for your brand voice
- RFP First-Pass ComposerCustom-built for your contracts
Frameworks people can run with
Every engagement leaves you with reusable systems, workflows, and decision rules that stay useful after the sessions end.
Assess, build, sustain.
One ladder, three rungs. Most teams start with the Sprint to see where AI fits, move into a build once the plan is clear, then keep the systems healthy on retainer. Start on whichever rung matches where you already are.
audited
Top three workflows identified and scoped. Ready for the build phase.
Two-Week AI Readiness Sprint
A scored audit and a 30-day starter plan in two weeks. The gateway engagement: a clear-eyed read on where AI fits before you commit to building anything. Assessment only, no systems built yet.
What's included
- 60-min kickoff to map workflows, current AI footprint, and where past attempts stalled
- Async team survey where each owner reports their top recurring tasks (about 15 minutes each)
- 0-10 AI Readiness Scorecard placing every workflow on the adoption ladder against its realistic 10, with the gap and the hours it can give back
- Team profile and breakdowns: a per-person adoption read, duplicated work between desks, shared tools worth integrating, and where the hours actually live
- An individual playbook for every team member with their before-and-after per workflow and the first move to make
- 30-day starter roadmap naming the top three workflows to build next, with named owners, rough effort, and projected hours saved
- 60-min findings call, plus a stakeholder-ready business case: recoverable hours, cost of doing nothing, and where you rank
Best for
Teams who've tried AI piecemeal and want a defensible plan before committing budget to a build
workflows shipped
Six-Week Implementation Coaching
Ship three production AI systems in six weeks. Weekly small-team sessions where we build the systems live, and your team learns to run and maintain them. This is where the Sprint's roadmap gets built.
What's included
- Six weekly 90-minute working sessions, screen-to-screen
- Three production AI systems shipped by week six, fully owned by your team
- Documented workflows and maintenance runbooks scoped to your tooling and brand voice
- Adoption plan for rolling each system to the rest of the team
- Async review of work between sessions
- Retrospective with measured time-saved against baseline
Best for
Teams that have the plan (from the Sprint or their own) and want a coach in the room while they ship
Two thoughts on the timeline generator before you ship: the budget field needs guardrails, and the 'final review' step drifts past 8 events. Quick patch — happy to walk it through.
Both make sense, pushing the patch now. Office hours Thursday?
See you then. Want to bring the sponsor recap workflow too? It's ready to QA.
Monthly AI Advisory Retainer
An AI systems lead on call without the headcount. Keeps the systems you've shipped healthy and adds new ones as the work demands.
What's included
- Two 60-minute strategy calls per month with leadership
- Weekly office hours open to the full team
- Async Slack / email access for system reviews and workflow questions
- Quarterly portfolio review of every AI system in production: what's healthy, what's drifting, what to retire
- Early access to new systems and frameworks from the Silicon Valley Speakers network
- Vendor evaluations and build-vs-buy recommendations as needed
Best for
Teams already running AI in production who want a senior thought partner maintaining and extending it
Running a business of one?
Freelance planners, solo producers, and fractional event leads don't need a team survey. This is a 1:1, done-with-you build: I audit your workflows and ship the custom GPTs and automations for your highest-leverage tasks, so you operate like a leveraged team of one.
What you walk away with
- Your own workflows audited for AI leverage
- Custom GPTs and automations built for your top tasks
- Yours to run, edit, and extend after we finish
Need something custom built?
Some workflows need custom software, not just a GPT. If you're after custom AI implementation, I bring in developers from my vetted network to build it and stay in the general-contractor seat, so you get working software without hiring or managing engineers yourself.
How I run it
- Scope the build with you and turn it into a clear spec
- Match the right developers from my vetted network
- Manage the build end to end and keep you in the loop
How an engagement actually runs.
A written scope up front, a working session every week, and something shipped or owned by the end of each one. Same cadence whichever rung you're on.
Discovery call
30 minutes to map your workflows, current AI footprint, and the two or three outcomes that would make this worth doing.
Scope proposal
Written scope within 48 hours: which engagement, what's in and out, deliverables, timeline, and pricing. You see the full scope and the number before you commit.
Kickoff and weekly cadence
Async kickoff, then a recurring working session. Every session ends with something shipped or a clear next-step owner.
Handoff
Tools and documentation live in your environment, owned by your team. You can keep me on retainer or not.
Things teams ask before the discovery call.
Does it matter what AI ecosystem we're already in?
+−
No. I work in whatever you already use. ChatGPT shop? We build custom GPTs. Claude or Microsoft Copilot shop? Same workflows, same outcomes, in your tools. The model matters less than the workflow you're trying to fix.
Do we need to buy more tools before we start?
+−
Almost never. Most teams already have everything they need (often a ChatGPT or Copilot subscription plus the SaaS they already pay for). We add tools only when something is clearly blocking, and only after you've seen what's possible with what you have.
What if we tried AI before and it didn't stick?
+−
That's the most common starting point. The sprint audit usually finds the same three failure modes: too generic to fit a real workflow, no clear owner, or no measurable outcome to defend the time spent. The engagement is built around fixing those, not adding more tools.
How technical does my team need to be?
+−
Not very. If your team can edit a Google Doc and follow a documented workflow, they can run and maintain these systems. The engagement is scoped to event ops, marketing, and program teams. I handle the technical lift; your team owns the operational rhythm and the systems themselves.
Will leadership need to sign off?
+−
Eventually, yes. The sprint deliverable includes a stakeholder-ready business case with measured time-saved and projected ROI, so the conversation with leadership is data-led rather than aspirational. Most clients use that document to fund the next phase.
How does pricing work?
+−
Every engagement is scoped in writing after the 30-minute discovery call, with the full deliverable list and the price before you commit. Pricing tracks the engagement and your team's size, so you get a real number tied to real scope rather than a menu guess.
Can you work with bureaus and agencies, or only in-house teams?
+−
Both. I run Silicon Valley Speakers myself, so the bureau workflows (lead intake, contract automation, speaker matching, post-event follow-up) are ones I've already built for my own business. Agencies get the same approach focused on client-facing workflows.
What about data privacy and security?
+−
I work inside your stack, with your accounts. Nothing leaves your environment unless you decide it should. For teams under SOC 2, HIPAA, or specific procurement requirements, the engagement scope respects those boundaries from day one.
Question that's not here? Bring it to the discovery call.
Let's TalkNot sure which engagement fits?
Most teams know they want AI working harder for them but aren't sure whether they need a sprint, a coach, or a monthly advisor. A 30-minute conversation sorts it out.
