Partner Bootcamp · Session 03
How we run Kylon on Kylon.
Mon Nov 2 · 11am ET
Today · 60 minutes, then 30 for Q&A
- 0:00Who you're building forYou share
- 0:08Fit or not?You vote
- 0:14Score a client togetherYou score
- 0:24Price itYou price
- 0:32How we run Kylon, and your agents across clientsLive demo
- 0:48The partner programYou weigh in
- 0:56What you need from usYou tell us
Keep the Meet chat open. When a slide says "In chat", type your answer there.
Your clients · 8 minutes
Who are you building for?
Everyone types one line in chat. Two partners take 90 seconds each.
1 · ClientIndustry
2 · SizeTeam size
3 · StageFirst call / mapping / building / live
4 · BlockerWhat's slowing you down
In-call messages
ExampleProperty management · 12 people · mapping · owner won't share the inbox yet
ExampleAccounting firm · 6 people · building · not sure which Agent gets client data
ExampleHome services · 30 people · first call · how do I price this?
Anyone already building or live goes first.
We keep this list. It sets the order for Q&A today and what we prepare for Thursday.
In chat: industry · team size · stage · one blocker.
01
Score a client together.
Is it a fit, how strong is it, what would you charge. Then you do the same for your own client.
Round 1 · Fit or not · 6 minutes
Is this a Kylon client?
1Peak Roofing30 staff, 3 sales reps, 2 estimators. About 40 leads a week. Estimates go out and nobody follows up. The owner approves any discount over 10%.
fitnot yetno
2Solo life coach"When someone pays on Stripe, send my welcome email and add them to my calendar."
fitnot yetno
3Family dental group, USWants Agents to read patient charts and treatment notes to prep each visit.
fitnot yetno
4Freight brokerage25 people. Wants to replace their freight software and QuickBooks with Kylon.
fitnot yetno
5Property manager12 staff, 400 units. Maintenance requests come by email and text. A coordinator picks the vendor. Owners approve jobs over $500.
fitnot yetno
In chat: card number and your call, like "3 not yet". One of you explains, then we turn the card.
Round 1 · the answers
Kylon fits work that needs judgment and a person's OK.
1 · Peak RoofingFITMany handoffs, exceptions at every step, and the owner approves. We score this one next.
2 · Life coachNOOne fixed process, built once, for one person. A simple automation tool is enough.
3 · Dental groupNOT YETPatient health data needs HIPAA. It's on the roadmap, not in the next month or two. Hiring or marketing work could still fit.
4 · Freight brokerageNO, AS ASKEDKeep their systems and connect by API. Take on quote follow-ups and carrier check-ins instead.
5 · Property managerFITA judgment call on every request, approvals over $500, and lots of exceptions like after-hours jobs.
Not a fit at all: a fixed process built once, anything that must react in milliseconds, or replacing their ERP or accounting system.
Round 2 · Score it together · 10 minutes
Score Peak Roofing, 1 to 3 on each line.
→

Peak Roofing on Kylon
RRick · owner
DDana · office
3Sales reps
2Estimators
Their tools · their team · 30 staff
Five questions about the workflow1 low · 3 high
RevenueDoes money slip when it's missed?
$14k average roof123
RepeatsHow often does it happen?
25 estimates a week123
PeopleHow many hands touch it?
Rep, estimator, Dana, Rick123
ExceptionsHow often does someone make a call?
Insurance jobs, discounts123
ToolsCan Kylon connect to their tools?
Email, calendar, CRM API123
In chat: your five scores, like "3 3 2 3 2". High scores on all five mean a strong first workflow.
In chat · which workflow do you build first for Peak Roofing?
- aEstimate follow-ups (chasing quotes that got no reply)
- bLead intake and routing
- cAdjuster scheduling
- dWeekly pipeline report
- eReplace QuickBooks
Type a letter. Think value against effort, like the chart from Session 2.
Round 2 · our answer
Start with estimate follow-ups.
A roofer sends a homeowner a price quote. Most go quiet. The follow-up is the check-in that wins the job.
Score 14 / 15Pick: a · Estimate follow-ups
Connections
APIRoofing CRMRep logs the estimate

GmailHomeowner replies

CalendarAdjuster visits

QuickBooks
→
What you build on Kylon

Peak Roofing workspace
AppNew estimate in the CRM becomes a record
Automation8am daily · Agent drafts when no reply in 3 days
EstimatesApp
M. AlvarezFull replacement$16,400Draft ready
J. OrtizStorm · insurance$9,800Adjuster Thu
K. BrooksFull replacement$13,900Signed
→
A person approves
RepApproves the follow-up. Sends from their Gmail.
RickAny discount over 10%.
DanaInsurance jobs and adjuster visits.
Not doing: replacing QuickBooks. Ask the room: whose score was furthest from ours, and why?
Round 3 · Price it · 8 minutes
What would you charge Peak Roofing?
Three numbers in chat. An Agent tallies the low, median and high while we talk.
1 · One-offDiagnosticMap the work with each person, rank it, one Blueprint.
$ ____
2 · Scoped feeBuildEstimate follow-ups live on real data.
$ ____
3 · MonthlyRunRead the Room weekly, update the rules, ship v2, v3.
$ ____ /mo
Highest and lowest explain. What did you assume about scope and size?
Kylon's own cost starts at $50 a month on Core. You decide if the client pays it or you bundle it.
In chat: three numbers, like "2,500 / 6,000 / 1,500".
Your turn · this week
Now do the same for your client.
1Fit checkJudgment, exceptions, a person who approves. If not, say why.
2Score the five linesRevenue, repeats, people, exceptions, tools.
3Pick the first workflow and price itDiagnostic, Build and Run, the way we just did.
4Build itOne App and one Automation, running on real data.
Wed Nov 4Post steps 1 to 3In your pod chat. Two of them open Thursday's session.
Thu Nov 5Session 04, 3pm ETBring what you're stuck on.
Fri Nov 6Milestone 2The App and the Automation, live for your client.
In chat: the client and the workflow you'll build first.
From here on · your client, with us
Tell us about your client. We'll help with the first build.
Send us
ClientIndustry, team size, country
First workflowThe one you picked, and its score
ToolsWhat they use today
Who approvesThe person who says OK
StageFirst call, mapping, building or live
Stuck onAnything blocking you
What we do with it
1Review your workflow mapWhat to build first, what to leave out.
2Give you a starter skillHome services and law firms are ready. Tell us your industry.
3Build the first App and Automation with youOn a working session with our team.
4Join a client callWhen the client needs to hear it from us.
By Wed Nov 4: post it in your pod chat. The client's name is optional.
02
We run the company on Kylon.
11 people and 100 Agents in one workspace. One workflow, start to finish.
Our own workspace
One workspace. A Room for each team and workflow.

Kylon
GTM
# outreach
# crm
# partner-bootcamp
# creator-communications
# ads
Ops
# vendor-payment
# issues
Agents

Ryan
GTM
Jaguar
Outreach
Penny
Accounts payable
11people across the US and Singapore
100Agents, many of them Claude Code, Codex and Hermes on our own machines
~70Rooms, one for each team, workflow or project
Every workflow is built from the same four parts · example: bootcamp applications
A RoomWhere the people and Agents on it talk#partner-bootcamp
+
An AppHolds the records the work is aboutBootcamp Applications
+
AutomationsStart the work when something happensRuns on every form submit
+
A personApproves what goes outChristina accepts partners
Workflow 01 · Bootcamp applications
All applications in one tracker. Christina decides.
Starts
A partner appliesThe form on kylon.io/lp/bootcamp
AutomationApplication intakeRuns on every form submit
Bootcamp ApplicationsNew record, status Reviewing
Partner ManagerPartner record, tagged bootcamp
Confirmation emailSent from Christina, replies go to her
Bootcamp applications · thread

Ryan Agent
New application
NameSam Lee · Northwind Ops
ClientsInsurance agencies
FitImplements, has a client ready
A personChristina sets AcceptedThe acceptance email waits as a draft until she approves it
36 partners accepted into 5 pods. No side spreadsheet, no copying between tools.
Workflow 02 · our CRM
We built our own CRM as a Kylon App.
Feeds in

kylon.io forms

Cal.com bookings

New signups
AIMeeting notes

Client email

Emails we send

Billing
→
Kylon CRM · one App
Kylon CRMCompaniesPeopleWorkspaces
CompanyTypePlanNext step
Northwind OpsPartnerCoreProposal Fri
Harbor RealtyCustomerTrialCheck-in
Peakline RoofingCustomerCoreLive
Northwind Ops · record threadAgent: Added Thursday's meeting notes. Two to-dos: send the proposal (Nan, Fri), share a starter skill (Ryan).
→
Who built it

Ryan · Kylon AgentDesign, connections, Automations

Claude Code + CodexNan's own agents build and review
How it improves
Agent proposes a field→Nan OKs→Logged
Every field keeps its source. Agents write through the CRM's own API; people approve and handle exceptions.
03
Your agents. Many clients.
How your own Agents and every client you take on fit together in Kylon.
Your agents, many clients
Your Claude Code joins the client's team.

Claude CodeOn your laptop

CodexOn a Mac mini

Kylon AgentsRun by Kylon
# partner-bootcamp
Christina
Ryan
Carl · Brought by Nan
Ian · Brought by Nan

Christina
@Carl can you tighten the hero copy on the bootcamp page?

Carl Agent
Done. Draft is ready, nothing is live until you publish.
Review draft
It runs on your machineWith your own model account and local files.
It works like every other AgentSame Rooms, threads, permissions and approvals.
The client sees one teamNo separate tool for them to learn.
Live: we ask an Agent running on a laptop for a change in this Room.
Your agents, many clients
One workspace for you. One for each client.
Your workspace
Your partner HQ

Your AgentsIncluding your own Claude Code or Codex

Your playbook as skillsDiscovery, build, weekly review

A client tracker AppEvery client, stage and next step

Your teamBuilders and contractors you add
Kylon CLI
skills · Apps
your Agents
A
Acme DentalClient workspace
Owned by the clientTheir Rooms and peopleYour private partner Roomintake skill v3Their plan
B
Brightside RealtyClient workspace
Owned by the clientTheir Rooms and peopleYour private partner Roomintake skill v3Their plan
H
Harbor Freight Co.Client workspace
Owned by the clientTheir Rooms and peopleYour private partner Roomintake skill v3Their plan
One workspace per client keeps their data, people and bill apart. You are invited in, and a private partner Room keeps your own notes out of their view.
Your agents, many clients · scaling
Build it once. Every new client starts from there.
You build once, reuse everywhere
- SkillsHow your Agents run discovery, intake, follow-ups
- App designsRebuilt in each client's workspace with one CLI command
- Room guidelinesYour house rules as a starting point
- Your AgentsThe same Claude Code works in every client you're invited to
Stays with each client
- Their recordsBookings, leads, invoices live in their Apps
- Their connectionsWhoever signs in owns it, so have the client sign in
- Their peopleTheir team, their approvals
- Their billOne plan per workspace, paid by them or by you
Client 1Build it by handMap, build, fix the exceptions
After it worksTurn it into a skill and an AppSave what you learned once
Client 2 onwardStart from the skillTune it to their exceptions, not from zero
Already keep one Claude Code folder per client? Each folder maps to one client workspace. Live: we move a sample folder and preview it before anything is built.
04
How the partner program works.
This is a proposal. We want your input before it's final.
Ways to partner
Refer, build, or both.
Proposal · terms set in the agreement
01
Refer a client
You doIntroduce a company through your partner link. Kylon runs the onboarding.
Good forAdvisors and communities
Terms · set in the agreement
02
Build and run it
You doScope the workflows, build the Agent team, stay on to tune it.
Good forAgencies and implementation partners
Your fees · 100% yours
03
Take our leads
You doSet up companies that come to us and want hands-on help.
Good forPartners who do onboarding
Your setup fee · paid by the client
Everyone who finishes the bootcamp and ships a client build gets the certified partner badge.
Pricing a client
Two ways to bill a client. Pick one per client.
Option A
The client pays Kylon
Client
plan
Kylonfrom $50/mo
You billSetup and retainer only.
WhySimple to start. The client sees what they spend.
WatchYou earn on service only.
Option B
You bill the client
Client
one fee
Youbuild + usage
plan
Kylon
You billOne fee for the build and the usage.
WhyOne invoice. You keep the margin.
WatchHeavy use is your cost.
Start a client on Core and move up once you see real use. Plans: kylon.io/pricing
In chat · 5 minutes
- Would you bundle Kylon into your fee, or let the client pay Kylon?
- What would make you bring your next client to Kylon?
- What has to be in the agreement before you sign?
In chat · what would help most with your client this week?
- aA demo built around your client's industry
- bOne of us on a call with your client
- cA connection or integration we don't have yet
- dPricing or contract answers
- eSomething else: type it
Every answer goes on our list with a name next to it. We report back in your pod chat.
Q&A · you asked on Thursday
Your questions from Thursday, answered first.
FreddyCan I build in a workspace the client created?Yes. The client owns it and invites you. Many clients prefer it.
MatthewDo I rebuild their existing systems?No. Connect Agents to them by API. Small teams can keep records in a Kylon App; large data sets stay in their own database.
OliverIs there an audit log of what the AI did?Not as a feature yet. Room history is searchable through the CLI, so you can put a report together.
MatthewCan every partner use the demo workspace?Yes, read-only for exploring. Build custom demos in your own workspace.
Still openWhite label and GoHighLevelBeing worked on. We share terms when they're approved, not before.
In chatWho wants a GoHighLevel session?Type GHL. Enough votes and we schedule it.
Join the Kylon Partner CommunityScan to join us on WhatsApp
Next: Thu Nov 5 · 3pm ET
Onboarding the client team
1 / 21