Example
Coffee shop
- MarketingPosts about the menu and delivery area
- SupportAnswers "do you deliver?" messages
- FinanceWeekly sales and costs
Each helper owns a recurring job: operations, support, finance, marketing, sales, even code. They work on a schedule, report back, and propose the next step. Nothing important happens until you approve it.
Why: "do you deliver to my area?" was the top customer question this week (from Support).
Chat with the Chief of Staff or any helper
What did customers ask about most this week?
Delivery areas, by a wide margin. Marketing has proposed three posts about it. They are in your Inbox.
Make it two posts and add a weekend promo.
Done. Revision 2 is waiting for your approval.
Goals you set, and the jobs that move them
What your helpers know and remember
Last 7 days
Your helpers and what they are doing now
Add a helper from a template, or describe your own
KPIs, each with an owner helper
Rules every helper follows
The AI engines your helpers run on
Apps your helpers can reach
Reusable know-how your helpers share
Where helpers work with files and the web
Example business and data · click around the menu
Helpers propose the work, you decide in one place, and the run happens. Here is the workspace from end to end.
Most growing businesses hit the same wall: the owner is the bottleneck. Omilo takes the repeat work off your plate so your time goes to the decisions only you can make.
Reports, follow-ups, replies and checks get done on schedule without you starting them.
You see a short queue of proposals with the reasoning, and say yes, no, or change this.
Goals, KPIs and every helper’s work in one place, updated by the helpers themselves.
A helper is triggered, gathers context, does the work, then reports with proposals. You decide. The next run carries out what you approved.
A schedule, an event, or you asking in Chat.
Goals, KPIs, memory and last run's notes.
Inside locked permissions and a budget.
What happened, plus proposals.
Approve, or reject with a note it reads.
The next run does the approved work.
The Chief of Staff hands out work toward your goals. Six helpers cover the week. Start with two and add one at a time as you trust them.
| Helper | Runs (default) | Job | Leaves you |
|---|---|---|---|
Ops | Hourly | Checks your site, orders, payments and queues. | Alert if something is off |
Support | Daily 06:30 | Reads yesterday's customer messages and groups them. | Themes + draft replies |
Finance | Mon 07:00 | Updates revenue, costs, churn and runway. | KPI scorecard |
Marketing | Mon 08:00 | Plans the week of posts from real customer questions. | Content proposals |
Sales | Tue · Thu 09:00 | Researches leads and drafts follow-ups. | Drafts, never sent |
Dev | 01:00 · 13:00 | Picks one ready task on your website or app and builds it. | 1 change to review |
Chief of Staff | Fri 16:00 | Reviews the week and tunes how every helper works. | Up to 3 changes |
Schedules run in your own time zone. Change them, pause a helper, or hire a new one for any job that repeats.
Same helpers, different jobs. You decide what each one owns.
Example
Example
Example
You set the goals; the Chief breaks them into jobs. The Work Map traces each job back to its goal.
One queue of decisions. Proposals keep their revision history.
Ask about any run, or rerun a helper with your instructions. Chat can propose; only you approve.
Value, trend, target and source on each KPI, with an owner helper who keeps it current.
A simple dashboard, or a virtual office where you watch helpers work. Only real events move.
Lessons, run logs and company knowledge live as docs you can read and edit.
Hard rules are enforced by a policy engine, not left to a prompt. Every action lands in an audit log.
Pick the engine per helper. Practice mode runs the whole flow with a pretend agent, so you can try it before spending anything.
Runs with your Claude Code login or API key, in a container on your server.
Direct API calls that stop at the limit you set.
A pretend agent walks through every step so you learn the flow.
Omilo is open source, so you can run it yourself for free. When you would rather not do it alone, we set it up with you, support it, or run it for you.
The full platform, free to run on your own server with your own AI.
We map the work that repeats in your business and set up helpers that fit it.
We host, update and back up Omilo for you. Nothing to install.
Consulting, support and cloud are quoted per business while we are in early access.
Tell us what your business does and which work repeats every week. We'll help you set up your first two helpers.
Free and open source to self-host. Onboarding, support and cloud from our team.