Launch your first
AI-driven project
Leave with a workflow that runs itself every week, a clear owner for its results, and a plan to review it in a week.
Leave with a workflow that runs itself every week, a clear owner for its results, and a plan to review it in a week.
Lessons 1 to 4 built the parts. This one links them into a workflow that runs every week.
A process on paper shows only the happy path. Real work branches at every step: the Agent reads the situation, asks a person when unsure, and remembers the call for next time.
Example: from new lead to booked meeting. An Automation starts it, each step is logged in the Leads App, and the Agent remembers every call.
On paper
In real work
The demo plays on its own. Click a step on the right to pause there. Click again to resume.
Example: the Sales Room has four Automations. Open Daily new leads: every day at 9, Ada reviews new leads and drafts invites for good fits.
Kylon also runs fixed-step workflows (code Automations). More: kylon.io/help/create-an-automation
Example: Daily quote follow-up in the Sales Room. The Sales Agent runs it at 9 every day and posts the list back to the Room.
More: kylon.io/help/create-an-automation
Example: quote follow-ups live in the Sales Room. Payment reminders live in Finance's private Room, seen only by finance and the owner.
Archiving a Room pauses its Automations. More: kylon.io/help/create-an-automation
Example: the sales lead says in the Sales Room, "Every day at 9, review new leads, draft invites for good fits, post a summary here."
No forms. Say when, what, and where results go.
Three kinds of trigger. Include a time zone.
Run it once and check all three before saving.
Email and X posts start as drafts. A person clicks Send.
Run now runs for real and can send messages or change records. More: kylon.io/help/create-an-automation kylon.io/help/review-automation-sample
Example: Wednesday's run failed. Check what it already sent or changed before deciding to rerun.
Every run is logged. Three failures in a row and it stops.
See what it already did, ask the Agent, then edit while paused.
One person's call or a two-person decision. The workflow fills out with use.
Pausing stops future runs. It doesn't undo past ones. More: kylon.io/help/pause-automation kylon.io/help/automation-result-missing
You've seen scenario 01, lead to meeting. Each of the next three gets a page: on paper on the left, in real work on the right.
No missed renewals. Quiet accounts get a timely check-in.
Spend only on the right creators.
No budget moves without the owner's OK.
The owner gets: no missed renewals. Week one: a Customer Success Room, an Agent on the inbox, a Customers App.
On paper
In real work
The owner gets: spend only on the right creators. Week one: a Creators Room, one Agent, a Creators App.
On paper
In real work
The owner gets: a dashboard built around their own questions. Week one: an Ads Room, a daily report, a Dashboard App.
On paper
In real work
The company from Lesson 2: sales, ops, finance, and the owner.
Then fill in the next page.
Repeats weekly and lives in someone's head.
Which Room? Which Agent runs it?
Where does the Agent stop? What stays with a person?
Who owns it? What do you check in a week?
| Spell out | Notes | Example: Daily quote follow-up |
|---|---|---|
| Workflow name | One line anyone understands | e.g. Daily quote follow-up |
| Which Room, run by whom | Where it's discussed, and the Agent there | e.g. Sales Room, Sales Agent |
| When does it start | Include a time zone. What if there's nothing? | e.g. Daily 9:00 SGT. If nothing, say so |
| What the Agent does | What it reads, how far it goes | e.g. List quotes silent for 7 days, draft follow-ups |
| Where results go, who sends | Where reports post, who sends emails | e.g. List to Sales Room, sales lead sends |
| Owner, and the one-week metric | Who keeps improving it. Pick one number | e.g. Sales lead. Extra follow-ups |
Example: the sales lead owns Daily quote follow-up. After a week, she reviews it.
Sample numbers. Use your own in class.
Example: the sales lead owns quote follow-ups. Six more follow-ups in a week, few draft edits, so she moves on to the ops team's weekly project report.
Reviews results, gathers feedback, decides changes.
Build another, or roll out to other teams.
Add it to the Skill or the workflow's instructions.
Switch to something people use more.
Without an owner, a workflow drifts until no one tends it.
More: kylon.io/help/automation-or-reminder kylon.io/help/automation-result-missing kylon.io/help/create-an-automation
A business analysis, a company design map, an AI employee on the job, Apps and Skills, a weekly workflow.
Together, they're version one of your AI-native company.
We'll check in about a week later to review your pilot.