For business · Private pilots open
Your own Fumu, working for your business.
Tell us the work you want done. We build the capabilities it needs on your own systems, and run it on a server that is yours alone.
What you get
One core, set up for your use case.
A beauty shop and a software team need different work done. Fumu stays the same; what changes is which systems it connects to and what it may do there.
Your own Fumu
Every business gets its own install: its own server, database and keys. Your customers' data never shares a system with anyone else's.
Built for your use case
Capabilities shaped around the work you describe. We talk it through with you, then connect the services you already use and build what is missing.
Connected to your systems
Services such as Stripe, HubSpot or Slack, your own shop or booking system through its API, your database read-only, and your guides from a folder or wiki.
Where you and your customers are
You on Telegram and the console, your customers in a chat on your website, and routines that run on their own timetable.
Built for your use case
Your work is the starting point, not our list.
Very different work runs on the same core. These two examples are ready to show you running on a walkthrough.
A software team
Issues fixed with tests and pull requests, sites deployed after a look at the price, and release notes drafted.
About the Coding packAn online shop
Customers ask about products and their orders on the website and place orders; the owner gets the day's sales every evening.
About customer chat
And the work your business needs.
We talk with you, understand what you need done, and build every capability around it. A few ideas of what that could be:
A clinic or salon
Clients book and move appointments in a chat, from your booking system; you get tomorrow's schedule the evening before.
A property agency
Enquiries answered from your listings, viewings proposed, and each morning a short list of new leads worth a call.
A delivery company
Customers track their own shipments; delays are flagged to your team with what the customer was told.
Your business
Something else entirely? That is the usual case. Tell us the work, and we build it around your systems.
A sample evening in a beauty shop
Customers served, the owner in control.
Small orders go through on their own and the owner is told. A big one waits for the owner. At eight, the day's sales arrive on the owner's phone. An illustration, with made-up orders.
About customer chat
Hi! Where is my order? And I'd like two of the foam cleansers, please go ahead.
Your order o-5001 has shipped and should arrive on Thursday. Two Gentle Foam Cleansers come to €22.00.
Order o-5003 is placed: two cleansers, €22.00, due by 10 November.
The owner is told: done without asking
Can I order ten Hydra Night Creams?
That comes to €325, above the €200 the owner lets me place on my own. I've asked the team to confirm.
Approval card sent to the owner
Approve.
Your order o-5004 is confirmed: ten Hydra Night Creams, €325.00.
Today: 7 orders, €286.50 in sales. The Berry lipstick is sold out and the night cream is down to 3.
Sent to the owner on Telegram
Your customers
Safe with the public, whatever they type.
A chat on your website talks to strangers. The rules that keep it safe are checked by Fumu itself, before every action, not left to the AI's judgement.
Security and approvals- A customer sees only their own orders, once your website has said who they are. Visitors who are not signed in see none.
- Orders and changes go ahead on their own only within the limits you set. Bigger ones wait for your yes.
- You hear about everything it does without asking, and every action is recorded.
- Customers only ever reach the agent that serves them, never the ones that work for you, and nothing they say becomes something Fumu believes about you.
- The chat answers only on your own website, and nothing else of Fumu is open to the internet.
How a pilot works
From your use case to your own install.
We talk with you, then build and set up everything for your requirements. Setup is usually a day or two of work, with you, before anything goes live.
Stage 1
Discovery
We talk through the work you want done, in your words: three to five real examples, who asks, and what must always wait for you.
You get: a live walkthrough, and a written proposal with the scope and price.
Stage 2
Pilot
We build the capabilities on your own systems, and you decide for each action: it runs on its own, runs within a limit, or always asks. Your examples become test cases, including a customer asking for someone else's data and an order that must ask you.
You get: Fumu on your real work, drafts and low-risk steps running and other changes asking.
Stage 3
Private deployment
If the pilot earned it, your install goes live on a server just for you, in your cloud account or ours. Raise its autonomy where you are happy, and switch any part off at any time.
You get: your own server, database and keys, with the limits and spending caps you set.
Stage 4
Ongoing support
We keep it running and change its capabilities as your work changes. What is covered and how fast we respond are written into your agreement.
You get: updates, backups and one team to talk to.
Costs and who does what
No surprises about what you are buying.
Price depends on the work, so we quote it after the first talk. How it is made up does not change.
Availability
Private pilots, with limited places. We set up each one by hand, so we take on only a few at a time.
Hosting
A server just for you, in your cloud account or ours. Your choice, either way we install and run it.
Maintenance
Ours. We handle updates and backups, and the work of keeping it running.
Setup fee
One-off, for discovery, building your capabilities and testing them. Quoted in writing before any work starts.
Monthly fee
For running, maintaining and supporting your install. Quoted in the same proposal, with the server cost made clear.
AI usage
On your own account with your AI provider, paid directly to them with nothing added by us. Daily and per-task caps keep it in check.
Tell us what your business needs.
Describe the work in your own words, and we will show you how it would run, live. If it fits, we will propose a pilot.
Ask for a walkthrough