Start here

What Kai can do

Everything Kai can do for you, in one place. Kai is one assistant that works across every part of Kaiday — this page shows what that means in practice, with the kind of sentences you'd actually say to make each thing happen.

Every interaction looks the same

You describe what you want, in your own words. Kai figures out how to do it, drafts the work, shows you the result, and keeps a record in Automations so you can always check what happened. You can stay involved at every step or let Kai run with it — your call.

One assistant, many things at once

The per-area lists further down are useful as a checklist. But the real story is what happens when Kai pulls several of them together in a single request. Every card below is one sentence you say to Kai — and what comes out the other end is the kind of work that used to need a whole team.

From your data to a presentation

You say

"Pull last quarter's customer numbers from our database — revenue, customers we lost, customers who grew, top 10 by spend — and build a 12-slide deck in our brand template. Save the raw numbers in a backup sheet too."

Kai does

Kai looks up the numbers, makes the charts, applies your brand template from the Knowledge Base, and saves both the deck and the sheet. Every chart shows exactly how it was calculated, so you can trust it.

From customer complaint to shipped fix

You say

Support email arrives: "checkout is broken in Germany." You: "Is this real? If so, fix it and reply to the customer once it's live."

Kai does

Kai reproduces the bug, finds the cause in your code (a country check), drafts the fix with a test, and gets the customer reply ready. You (or your developer) approve the fix. The reply sends.

From social mentions to a public roadmap

You say

"Read the last 30 days of mentions on X and Reddit. Group the complaints by theme. Build a public roadmap page at roadmap.menoru.com showing what we're working on next."

Kai does

Kai gathers the mentions, groups them by theme, drafts a roadmap, builds the page as a MiniApp, and publishes it on your domain. Your customers see you're listening.

From meeting to action items, without asking

You don't ask Kai to do anything. You just have a Kaiday meeting. By the time it ends, every attendee has a follow-up email with the decisions and next steps. The action items are in Planning with owners and deadlines. The full transcript is searchable in the Knowledge Base.

From subscriptions to invoices to follow-ups

You say

"Every Friday at 5pm, check our customer database for active subscriptions that haven't been invoiced. Generate the invoices, send them by email, and book a follow-up call for any client paying us more than $5,000/month who hasn't paid in 7 days."

Kai does

You set it once. Every Friday at 5pm, it runs. The Automations tab shows you exactly what happened.

From email thread to signed contract

You say

Client thread reaches the "send me the contract" moment. You: "Generate our standard agreement at $4,500/month for 6 months, send it for signature, and mark this client as 'active' in our records when they sign."

Kai does

Kai pulls the agreement template, fills in the deal terms from the thread, sends it for signature, and flips the client record from "lead" to "active client" the moment it's signed.

From a list of clients to a planned route

You say

"For Tuesday, plan a route through every active client in Bavaria I haven't visited in 90 days. Book 45-minute slots starting at 9am with travel time between them. Brief me on each client's last conversation."

Kai does

Kai pulls the clients from Business, finds their locations on the map, plans the best route, creates Calendar events with travel time built in, and attaches a short brief to each.

None of these are templates. None of these are workflows you have to build first. They are just sentences. Kai figures out which parts of Kaiday to touch and in what order.

Communicate

Kai writing, sending, and following up on customer emails.

Email

Draft replies in any thread with full client context (past emails, invoices, MiniApp activity).

Handle multi-message conversations end-to-end. Track what's asked, answered, and still open.

Compose new emails from a one-line description.

Sort incoming emails into categories (new lead, support, billing, noise) so you only see what matters.

Run scheduled follow-up email sequences (every 3 days, every Monday, whatever you describe).

Escalate threads that need you (negotiation, refund, complaint) instead of replying blind.

Messaging

Summarize long threads into actual decisions and open questions.

Draft replies in any channel, in your voice.

Search every channel and DM by meaning, not keyword.

Promote a chat decision into a Planning item, Email, or Calendar invite.

Social

Draft and publish posts on YouTube, X, Instagram, LinkedIn, on a schedule.

Monitor public mentions of you and your competitors; surface what's worth a reply.

Draft replies to comments and DMs; you approve before they go.

Repurpose content across formats (long post → thread → script → newsletter).

Try saying to Kai

›Handle this booking thread end-to-end, confirm the date, send the deposit link, follow up if they go quiet.
›Reply to every comment on yesterday's launch post in a warm tone.
›Send a 3-email follow-up sequence to leads who filled the intake but didn't book.

Schedule & meet

Calendar

Create events and recurring meetings from a sentence.

Generate booking links scoped to a service, package, or duration.

Reschedule whole sets of meetings ("move all my Wednesdays to next week").

Prep notes before every meeting: who's coming, what changed since last time, what to ask.

Video meetings

Run meetings on Kaiday's own self-hosted video stack. No third-party app to install.

Record meetings automatically.

Transcribe with speaker labels.

Turn a recording into action items, follow-up emails, and Planning items.

Try saying to Kai

›Book a 30-minute intro with the lead from the intake form, prep me with their answers.
›Record this call, send action items to the client after, put follow-ups in Planning.
›Move all my Wednesday meetings to Thursday next week.

Write — documents, sheets, presentations

From a sentence to a saved Knowledge Base document

You say

"Write me a one-page onboarding doc for new clients: what to expect in the first week, how to reach me, where to upload their files."

Kai does

Kai drafts the document, saves it in the Knowledge Base under your workspace, and shows you the link. Open the KB tab and it's already there, searchable, editable, shareable with a client. No copy-paste, no separate file.

GIF placeholder

Ask Kai to create a document → switch to the Knowledge Base tab → the document is already there, named, saved, ready to share.

Documents

Create documents from a description: memos, proposals, contracts, internal guides.

Edit existing documents, rewrite a section, restructure, tighten, expand.

Translate documents into other languages.

Summarize long docs into a one-page brief.

Sheets

Build spreadsheets from a description ("revenue tracker by client, monthly columns").

Run analyses you describe in English; chart the result.

Pull data from a connected database or a CSV file and reconcile it against your records.

Presentations

Generate decks: pitch decks, sales decks, board updates, training material.

Edit slides by talking: "tighten the headline on slide 6, remove slide 4."

Generate decks from meeting notes, a memo, or a one-paragraph brief.

Restyle a whole deck to a new template or brand.

Try saying to Kai

›Generate a 10-slide pitch deck from our company memo. Pull out the product, the traction, and the ask.
›Turn yesterday's strategy meeting transcript into a one-page memo.
›Add a competitive landscape slide to the investor deck from the Knowledge Base.

Build apps for your clients

Build MiniApps from a description: client portals, intake forms, calculators, galleries, booking flows.

Host landing pages and applications under your verified domain (e.g., book.menoru.com).

Update an app by talking: "add a budget question to the intake form."

Connect apps to your data so the form your client fills in updates the same client record you read from in Business.

Change the app whenever you want, just by talking — Kai re-publishes it for you.

See the full MiniApps section.

Try saying to Kai

›Build a private gallery for the Nguyen wedding. They pick favorites and pay the balance.
›Add a budget question to the intake form and route anyone over $10k straight to me.
›Publish the consultation booker at book.menoru.com.

Code — Kai writes pull requests on GitHub

This section is for people who use GitHub

If you don't write code (or work with someone who does), you can safely skip this section. The short version: if you ever do connect a code repository, Kai can read it, fix bugs, and propose changes for your developer to review — never pushing anything live without approval.

Connect a GitHub repository and Kai writes code for you. Not autocomplete — real, end-to-end pull requests. Kai reads your code, figures out the problem, writes the change, runs the tests, and opens a draft pull request for you (or your developer) to review. You review, you merge. Kai never publishes anything to your main branch on its own.

GIF placeholder

★ From customer complaint to shipped fix. Kai doing the engineering you'd otherwise hire for.

Your support inbox now ships fixes

You say

Customer email: "checkout is broken in Germany." You: "is this real? if so, fix it."

Kai does

Kai checks the recent payment logs from your connected database, reproduces the failure, finds the cause in the file that handles checkout, and opens a draft pull request on a fix branch with the three-line fix, a test that prevents the bug from coming back, and a description linking to the customer email. You review, merge, and reply.

Open real pull requests on GitHub. The code change, the tests, and a clear description — all written for you.

Diagnose bugs from a customer complaint, an error message, a screenshot, or just a vague description.

Read your code to answer questions like "where do we handle refunds?" or "why is this page slow?"

Reorganize code on demand: "this file is too long, split it into smaller files."

Review pull requests your teammates open and flag anything risky before you merge.

Trace a customer's bug report back to the line of code most likely responsible.

Never publishes code directly. Never touches your main branch without you merging it yourself.

A side project, built from your phone

You say

Airport. You message Kai: "add a dark mode toggle to the side project, remember the user's choice. Draft only — don't ship it."

Kai does

You board. By the time you land, the change is waiting for you to review. You approve it from the rideshare. The feature is live before you reach the hotel.

Try saying to Kai

›A customer says checkout is broken in Germany. Find and fix it.
›Review pull request #421 and tell me what's risky.
›Why is the home page suddenly slow? Find the cause and propose a fix.
›Add a 'remember me' checkbox to the login page. Draft only — don't publish it.

Plan, track, and follow through

Create goals and to-dos by describing them in plain words.

Set how often things should be checked on and who owns them. Kai follows up on its own.

Move items forward as the work actually happens — emails sent, apps published, documents finished.

Set rules that keep your planning tidy ("anything not touched in 7 days moves to Review", "every goal needs an owner").

Generate progress reports for any time period.

Try saying to Kai

›Add a Q3 goal: ship the photographer onboarding flow. Weekly check-ins on Fridays.
›What's blocked this week, and what would unblock it?
›Generate a progress report for the partner from the last 30 days.

Ask your data anything, get whatever you need back

Connect your customer database (the place where your customer information lives — most databases work) and Kai treats it like part of your workspace. You ask in plain English. The answer comes back as a number, a chart, a slide, a sheet, an email, or all four at once.

The examples below use SaaS metrics like "churn" (customers leaving) and "retention". Swap them for whatever you measure — appointments per month, average order value, repeat clients, anything.

Tuesday 10am, an answer in 30 seconds

You say

Investor email: "what's your customer retention by cohort over the last 12 months?" You: "Pull customer retention from our database, broken down by month they signed up, last 12 months. Chart it. Send the chart as a reply to her email."

Kai does

The reply goes out in 30 seconds. The chart is correct. The conversation continues.

Answer questions about your data in plain English. No SQL, no BI tool.

Turn data into the format you actually need. A chart for a meeting, a slide for a deck, a sheet in the Knowledge Base, a chart inside a reply email.

Build recurring reports that run themselves on a schedule and land wherever you want them.

Reconcile two sources: "does Business match what's in our customer database for our top 20 clients?"

Show exactly how each number was calculated, so you can trust it (and explain it to anyone who asks).

Read-only by default. Kai never changes your database unless you explicitly turn that on per connection.

Friday 5pm, the weekly digest writes itself

You say

You set it once: "Every Friday at 5pm, check the database for the week's customer losses, customer growth, and new signups by source. Build a 1-page summary, post it in #revenue, and email the same summary to the board."

Kai does

Every Friday at 5pm forever after, you don't think about it. The team sees it. The board sees it. You went home.

Try saying to Kai

›Pull last quarter's customer numbers from our database and build a 12-slide board deck. Show how each number was calculated.
›Customer retention by signup month, last 12 months. Chart it and reply to this email with the chart.
›Every Friday at 5pm, post a summary of customers lost and gained this week in #revenue.
›Compare Business against our customer database for our top 20 clients. Flag any mismatches.

Maps — already loaded with the world

Kaiday comes with a full world map built in. No Google Maps account, no per-use billing, nothing to set up.

Drop pins for clients, suppliers, prospects, or field work. Kaiday finds each one on the map automatically from their address.

Search any address, business, or landmark anywhere in the world — no API keys needed.

Link pins to records in Business so your territories and accounts stay in sync.

Plan routes between pins and turn them into Calendar events with travel time built in.

Generate territory views ("every client in the Berlin metro area").

Try saying to Kai

›Drop a pin for every client in Bavaria and link them to their Business record.
›Plan a route for Tuesday's field visits and create Calendar events.
›Show prospects within 30km of the new office.

Run your business operations

Create client records from an email signature, a MiniApp submission, or a contract upload.

Generate and send invoices.

Surface overdue invoices and draft a follow-up sequence to clients who haven't paid.

Tie payments back to the goal or project that earned them.

Generate financial summaries: revenue by client, quarter, service.

Try saying to Kai

›Invoice Acme $4,500 for the November retainer and email it to billing@acme.com.
›Chase every invoice more than 30 days overdue, escalating tone if it's been more than 60.
›Revenue by client this quarter, biggest first.

Automate everything else

Build a workflow from one sentence. Kai turns "when X happens, do Y" into a real automation.

Schedule recurring tasks (daily summaries, weekly reports, monthly invoicing).

Trigger an action somewhere in Kaiday whenever something happens in one of your apps (a new lead, a payment, a submission).

Retry, cancel, or jump back to the chat for any task that didn't work.

Try saying to Kai

›When a new lead fills the intake form, DM me and create a Planning item.
›Every Monday at 7am, post a digest of last week's wins to #team.
›Anything that fails twice in a row, escalate to Messaging and ping me.

Manage your team and your companies

Onboard new teammates. Send the invite, set their role, walk them through the first run.

Manage multiple companies. Each is a separate workspace with separate memory and data.

Switch context: a question on workspace A returns workspace A's data, not B's.

Hand off work between teammates. Kai keeps the thread of context.

Try saying to Kai

›Invite Jane Smith as an admin and onboard her into the photography workspace.
›Switch me to my consulting company and show me what's pending there.
›Hand off the Nguyen wedding thread to my second shooter with all the context.

The boundary

What Kai will not do

Publish code changes directly without your review.

Send money or move funds without your approval.

Delete records permanently without a confirmation.

Talk to systems you have not explicitly connected.

Concepts Add a domain

Start here

What Kai can do

Every interaction looks the same

One assistant, many things at once

From your data to a presentation

You say

Kai does

From customer complaint to shipped fix

You say

Support email arrives: "checkout is broken in Germany." You: "Is this real? If so, fix it and reply to the customer once it's live."

Kai does

Kai reproduces the bug, finds the cause in your code (a country check), drafts the fix with a test, and gets the customer reply ready. You (or your developer) approve the fix. The reply sends.

From social mentions to a public roadmap

You say

"Read the last 30 days of mentions on X and Reddit. Group the complaints by theme. Build a public roadmap page at roadmap.menoru.com showing what we're working on next."

Kai does

Kai gathers the mentions, groups them by theme, drafts a roadmap, builds the page as a MiniApp, and publishes it on your domain. Your customers see you're listening.

From meeting to action items, without asking

From subscriptions to invoices to follow-ups

You say

Kai does

You set it once. Every Friday at 5pm, it runs. The Automations tab shows you exactly what happened.

From email thread to signed contract

You say

Kai does

Kai pulls the agreement template, fills in the deal terms from the thread, sends it for signature, and flips the client record from "lead" to "active client" the moment it's signed.

From a list of clients to a planned route

You say

Kai does

Kai pulls the clients from Business, finds their locations on the map, plans the best route, creates Calendar events with travel time built in, and attaches a short brief to each.

None of these are templates. None of these are workflows you have to build first. They are just sentences. Kai figures out which parts of Kaiday to touch and in what order.

Communicate

Kai writing, sending, and following up on customer emails.

Email

Draft replies in any thread with full client context (past emails, invoices, MiniApp activity).

Handle multi-message conversations end-to-end. Track what's asked, answered, and still open.

Compose new emails from a one-line description.

Sort incoming emails into categories (new lead, support, billing, noise) so you only see what matters.

Run scheduled follow-up email sequences (every 3 days, every Monday, whatever you describe).

Escalate threads that need you (negotiation, refund, complaint) instead of replying blind.

Messaging

Summarize long threads into actual decisions and open questions.

Draft replies in any channel, in your voice.

Search every channel and DM by meaning, not keyword.

Promote a chat decision into a Planning item, Email, or Calendar invite.

Social

Draft and publish posts on YouTube, X, Instagram, LinkedIn, on a schedule.

Monitor public mentions of you and your competitors; surface what's worth a reply.

Draft replies to comments and DMs; you approve before they go.

Repurpose content across formats (long post → thread → script → newsletter).

Try saying to Kai

›Handle this booking thread end-to-end, confirm the date, send the deposit link, follow up if they go quiet.
›Reply to every comment on yesterday's launch post in a warm tone.
›Send a 3-email follow-up sequence to leads who filled the intake but didn't book.

Schedule & meet

Calendar

Create events and recurring meetings from a sentence.

Generate booking links scoped to a service, package, or duration.

Reschedule whole sets of meetings ("move all my Wednesdays to next week").

Prep notes before every meeting: who's coming, what changed since last time, what to ask.

Video meetings

Run meetings on Kaiday's own self-hosted video stack. No third-party app to install.

Record meetings automatically.

Transcribe with speaker labels.

Turn a recording into action items, follow-up emails, and Planning items.

Try saying to Kai

›Book a 30-minute intro with the lead from the intake form, prep me with their answers.
›Record this call, send action items to the client after, put follow-ups in Planning.
›Move all my Wednesday meetings to Thursday next week.

Write — documents, sheets, presentations

From a sentence to a saved Knowledge Base document

You say

"Write me a one-page onboarding doc for new clients: what to expect in the first week, how to reach me, where to upload their files."

Kai does

GIF placeholder

Ask Kai to create a document → switch to the Knowledge Base tab → the document is already there, named, saved, ready to share.

Documents

Create documents from a description: memos, proposals, contracts, internal guides.

Edit existing documents, rewrite a section, restructure, tighten, expand.

Translate documents into other languages.

Summarize long docs into a one-page brief.

Sheets

Build spreadsheets from a description ("revenue tracker by client, monthly columns").

Run analyses you describe in English; chart the result.

Pull data from a connected database or a CSV file and reconcile it against your records.

Presentations

Generate decks: pitch decks, sales decks, board updates, training material.

Edit slides by talking: "tighten the headline on slide 6, remove slide 4."

Generate decks from meeting notes, a memo, or a one-paragraph brief.

Restyle a whole deck to a new template or brand.

Try saying to Kai

›Generate a 10-slide pitch deck from our company memo. Pull out the product, the traction, and the ask.
›Turn yesterday's strategy meeting transcript into a one-page memo.
›Add a competitive landscape slide to the investor deck from the Knowledge Base.

Build apps for your clients

Build MiniApps from a description: client portals, intake forms, calculators, galleries, booking flows.

Host landing pages and applications under your verified domain (e.g., book.menoru.com).

Update an app by talking: "add a budget question to the intake form."

Connect apps to your data so the form your client fills in updates the same client record you read from in Business.

Change the app whenever you want, just by talking — Kai re-publishes it for you.

See the full MiniApps section.

Try saying to Kai

›Build a private gallery for the Nguyen wedding. They pick favorites and pay the balance.
›Add a budget question to the intake form and route anyone over $10k straight to me.
›Publish the consultation booker at book.menoru.com.

Code — Kai writes pull requests on GitHub

This section is for people who use GitHub

GIF placeholder

★ From customer complaint to shipped fix. Kai doing the engineering you'd otherwise hire for.

Your support inbox now ships fixes

You say

Customer email: "checkout is broken in Germany." You: "is this real? if so, fix it."

Kai does

Open real pull requests on GitHub. The code change, the tests, and a clear description — all written for you.

Diagnose bugs from a customer complaint, an error message, a screenshot, or just a vague description.

Read your code to answer questions like "where do we handle refunds?" or "why is this page slow?"

Reorganize code on demand: "this file is too long, split it into smaller files."

Review pull requests your teammates open and flag anything risky before you merge.

Trace a customer's bug report back to the line of code most likely responsible.

Never publishes code directly. Never touches your main branch without you merging it yourself.

A side project, built from your phone

You say

Airport. You message Kai: "add a dark mode toggle to the side project, remember the user's choice. Draft only — don't ship it."

Kai does

You board. By the time you land, the change is waiting for you to review. You approve it from the rideshare. The feature is live before you reach the hotel.

Try saying to Kai

›A customer says checkout is broken in Germany. Find and fix it.
›Review pull request #421 and tell me what's risky.
›Why is the home page suddenly slow? Find the cause and propose a fix.
›Add a 'remember me' checkbox to the login page. Draft only — don't publish it.

Plan, track, and follow through

Create goals and to-dos by describing them in plain words.

Set how often things should be checked on and who owns them. Kai follows up on its own.

Move items forward as the work actually happens — emails sent, apps published, documents finished.

Set rules that keep your planning tidy ("anything not touched in 7 days moves to Review", "every goal needs an owner").

Generate progress reports for any time period.

Try saying to Kai

›Add a Q3 goal: ship the photographer onboarding flow. Weekly check-ins on Fridays.
›What's blocked this week, and what would unblock it?
›Generate a progress report for the partner from the last 30 days.

Ask your data anything, get whatever you need back

The examples below use SaaS metrics like "churn" (customers leaving) and "retention". Swap them for whatever you measure — appointments per month, average order value, repeat clients, anything.

Tuesday 10am, an answer in 30 seconds

You say

Kai does

The reply goes out in 30 seconds. The chart is correct. The conversation continues.

Answer questions about your data in plain English. No SQL, no BI tool.

Turn data into the format you actually need. A chart for a meeting, a slide for a deck, a sheet in the Knowledge Base, a chart inside a reply email.

Build recurring reports that run themselves on a schedule and land wherever you want them.

Reconcile two sources: "does Business match what's in our customer database for our top 20 clients?"

Show exactly how each number was calculated, so you can trust it (and explain it to anyone who asks).

Read-only by default. Kai never changes your database unless you explicitly turn that on per connection.

Friday 5pm, the weekly digest writes itself

You say

Kai does

Every Friday at 5pm forever after, you don't think about it. The team sees it. The board sees it. You went home.

Try saying to Kai

›Pull last quarter's customer numbers from our database and build a 12-slide board deck. Show how each number was calculated.
›Customer retention by signup month, last 12 months. Chart it and reply to this email with the chart.
›Every Friday at 5pm, post a summary of customers lost and gained this week in #revenue.
›Compare Business against our customer database for our top 20 clients. Flag any mismatches.

Maps — already loaded with the world

Kaiday comes with a full world map built in. No Google Maps account, no per-use billing, nothing to set up.

Drop pins for clients, suppliers, prospects, or field work. Kaiday finds each one on the map automatically from their address.

Search any address, business, or landmark anywhere in the world — no API keys needed.

Link pins to records in Business so your territories and accounts stay in sync.

Plan routes between pins and turn them into Calendar events with travel time built in.

Generate territory views ("every client in the Berlin metro area").

Try saying to Kai

›Drop a pin for every client in Bavaria and link them to their Business record.
›Plan a route for Tuesday's field visits and create Calendar events.
›Show prospects within 30km of the new office.

Run your business operations

Create client records from an email signature, a MiniApp submission, or a contract upload.

Generate and send invoices.

Surface overdue invoices and draft a follow-up sequence to clients who haven't paid.

Tie payments back to the goal or project that earned them.

Generate financial summaries: revenue by client, quarter, service.

Try saying to Kai

›Invoice Acme $4,500 for the November retainer and email it to billing@acme.com.
›Chase every invoice more than 30 days overdue, escalating tone if it's been more than 60.
›Revenue by client this quarter, biggest first.

Automate everything else

Build a workflow from one sentence. Kai turns "when X happens, do Y" into a real automation.

Schedule recurring tasks (daily summaries, weekly reports, monthly invoicing).

Trigger an action somewhere in Kaiday whenever something happens in one of your apps (a new lead, a payment, a submission).

Retry, cancel, or jump back to the chat for any task that didn't work.

Try saying to Kai

›When a new lead fills the intake form, DM me and create a Planning item.
›Every Monday at 7am, post a digest of last week's wins to #team.
›Anything that fails twice in a row, escalate to Messaging and ping me.

Manage your team and your companies

Onboard new teammates. Send the invite, set their role, walk them through the first run.

Manage multiple companies. Each is a separate workspace with separate memory and data.

Switch context: a question on workspace A returns workspace A's data, not B's.

Hand off work between teammates. Kai keeps the thread of context.

Try saying to Kai

›Invite Jane Smith as an admin and onboard her into the photography workspace.
›Switch me to my consulting company and show me what's pending there.
›Hand off the Nguyen wedding thread to my second shooter with all the context.

The boundary

What Kai will not do

Publish code changes directly without your review.

Send money or move funds without your approval.

Delete records permanently without a confirmation.

Talk to systems you have not explicitly connected.

Concepts Add a domain