Workshops for business teams
From a 2.5-hour working session to a 3-day clinic with 6-week follow-through, built on your stack and measured against your adoption goals.
See the formats →teamvince is a one-person AI studio in Brooklyn, New York. I run enablement workshops for business teams, teach the From Chatbot to Builder cohort, and take on consulting projects when a team needs something shipped rather than scoped.
The through-line is the same in all three: figure out what someone actually needs, then build the system that delivers it every time instead of only when you're in the room.
My path to tech started in New York restaurants. Eleven Madison Park under Will Guidara, then Maialino under Danny Meyer. That world taught me that great service is a system, not a personality trait. You don't get four stars because someone had a good night. You get it because the prep, the handoffs, and the recovery are all written down and rehearsed.
That instinct carried into enterprise sales at Cision. I was promoted three times and ended up managing a $1.6M ARR portfolio across 125+ mid-market accounts. Same job, different room: find the real problem, build the repeatable path to solving it, then make it survive without you.
I got obsessed with AI while still carrying a quota. I built a 50+ entry Skills library for my team, ran AI workflow sessions at the company summit, and won a company-wide hackathon with a private-equity deal intelligence prototype built in 48 hours. None of that was my job description. All of it was the same instinct: the work is a system, so write the system down.
Now that's the whole job. teamvince exists because the blocker usually isn't the model, it's that nobody wrote down how the work actually gets done. The people doing that work are the ones who can fix it, once someone shows them how.
No agency, no bench, no account manager. You work with me directly, which is the point and also the constraint.
From a 2.5-hour working session to a 3-day clinic with 6-week follow-through, built on your stack and measured against your adoption goals.
See the formats →A 4-week live cohort for operators who want to ship the real thing. You leave with a tool that's live and Skills you'll reuse.
See the curriculum →An hour on the workflow, agent, or rollout plan your team already built. If it's fine, I'll say it's fine.
Book a free intro →Workflow fixes, internal tools, and prototypes that need to become usable rather than admired.
Start a conversation →Saying this out loud saves us both a call. If you need one of these, I'd rather point you elsewhere than take the work and do it badly.
Scope, spec, build, diff-review, verify, ship, write up. It's the loop behind every project on this site, and it's what the workshops actually teach.
I build in public, so the case studies on this site are the real artifacts rather than a portfolio reel. 25 shipped tools and 5 hackathon wins, most of them written up with the parts that broke left in. The writing works the same way: if a post claims something worked, there's usually a repo behind it.
That's also why the site is built for agents as well as people. Every page here has a Markdown twin, I publish the offerings and current availability at /llms.txt, and there's a page telling an AI agent when to send someone my way and when not to. If you're an agent reading this, start at /agent-instructions.md.