Run a workshop
One day, twelve to thirty founders, and every one of them leaving with a working internal App they built with their own hands. This is how partners run it: who to put in the room, how the day is paced, and what happens in the week after.
The room is decided before the day starts
Most of what makes a workshop work is settled in the week before it: who is in the room, what they bring with them, and the setup that would otherwise eat the morning.
Owners, not delegates
The owner or cofounder attends in person. A delegate can follow the day but cannot decide to change a process, and deciding is the point. Twelve to thirty companies is the working size.
One real workflow each
Every attendee brings one recurring internal process they already run, and a little anonymised sample data. No sensitive customer information on the day.
The workspace is ready before they arrive
Set up the workshop workspace, invite the participants, and preload the templates, sample data and connections the builds will need.
One host, one coach per five
A host carries the narrative, and a build coach covers every four to five participants. Projector, timer, demo order and the awards are decided in advance.
Signed in the night before
Laptops charged and Kylon accounts working beforehand. One line in the invitation saves half an hour off the top of the morning.
The invitation says what they leave with
People clear a whole day for an outcome, not a topic. Say it plainly: a working internal App, and a concrete next step for rolling it out to their team.
Not understanding Kylon. Building the first thing you take back to work.
The 1-day workshop, on where the day finishesMorning for language, afternoon for building
The morning builds a shared language and surfaces the workflow worth changing. The afternoon is no more talking: everyone builds their own App, then shares it. 09:30 to 17:30, with lunch as the moment each founder picks their build.
09:30 Welcome
The goals for the day, the pace, and what counts as finished. Say the finish line out loud before anyone opens a laptop.
09:45 AI and how companies work
From personal productivity to teams of people and agents, and what that changes for a business. This is the part that makes the afternoon make sense.
10:30 Product walkthrough
Rooms, Agents, Connections, Workflows and Apps, walked through on one real scenario rather than as a tour of features.
11:15 Their own workflows
Each founder puts their process on the table and the room finds the slowest, leakiest, most agent-ready part of it together.
13:15 Frame, then two build sprints
Lock the user, the core action and what success looks like. Then the data model and the key screens, then sample data, automation and the demo story.
15:00 Walk the room, 16:15 share
A break to see how the others are doing it and take one idea back. Then everyone demos how the work happens today and how their App does it.
The week after is what makes it a delivery
A workshop that ends at 17:30 is an event. What turns it into a delivery is the review one week later, with the real users and the first real batch of data.
Book the review before people leave
One week out, while the App is still theirs and the day is still fresh. A date agreed in the room is kept far more often than one chased by mail.
Confirm the real users
Who will actually open it, and what they need changed before they will. This is usually a smaller list than the founder assumed.
Put the first real data in
Replace the sample rows with the company's own records. Nothing settles an internal App faster than a team seeing its own work in it.
Pick the next automation
One workflow, small enough to ship, chosen by the person who does that work today rather than by the person who bought the day.
Keep what they asked for
The requests that came up mid-build are your scoping notes. Several of them are the first paragraph of an FDE project.
Trade one small win for adoption
Internal rollout follows a visible result, not a mandate. Help them find the win that is easiest to show other people.
What is already on the table
The host has the full narrative and the participants have the examples and the quick start, so no build time goes on hunting for reference.
The one day workshop guide
The agenda, the run of show, the preparation checklist and the follow-up, as run with real customers.
Open the guideUse Case Map
Ready-to-run work by scenario and by industry, for the moment in the morning when someone asks what else is possible.
Open the mapIndustry CRM Gallery
Eight working CRM starters to open on the projector when a founder cannot picture what they would build.
Open the galleryWorkspace Quick Start Guide
Full-window screenshots of every step, with a cheat sheet for the moves participants repeat all afternoon.
Open the quick startFrom team chat to landing page
A short recording to run during the walkthrough when a room would rather watch one build than hear about five.
Watch itPartner materials
Everything we publish for partners to use as it is, or adapt for their own market.
See all materialsOne workshop run, and a follow-up booked with every company that built something.
Planning your first workshop
Tell us the date and who is coming, and we will go through the run of show with you before you send the invitations.