Guide
Rolling out Botchi is not an IT project — it's six steps. Map the work worth automating, connect the tools, load the knowledge, build the first specialists, put the routines on a schedule and hand every employee their assistant.
Rollout plan
Acme workspace
Everything downstream — agents, knowledge, automations, policies — falls out of the two or three processes you choose in step one. Choose well and the rest is configuration.
Before touching any software, list the recurring work: where the hours go, who does it, which tools it touches. Support triage, renewal prep, weekly reporting and onboarding are the usual suspects. Pick two or three processes that are frequent, rule-friendly and owned by someone who wants them off their plate.
OutcomeA shortlist of 2–3 processes, each with a business owner
Open the dashboard at web.botchi.ai, create the workspace and connect the tools those processes touch — email, calendar, drive, docs, sheets, project systems. Connections use account-owned credentials, never a teammate's personal login, and every tool starts governed by policies you control.
OutcomeAn approved tool catalog the whole account shares
Upload what the processes run on: playbooks, pricing, policies, help docs, templates. Knowledge is encrypted per account and granted per agent — the sales specialist reads pricing, the support specialist reads help docs, and neither sees the rest.
OutcomeThe ground truth your agents will answer from
Create one or two agents for the processes you mapped. Give each its instructions (how your team actually works), its knowledge grants and only the tools it needs — with ask-first policies on anything outbound. Test with real asks and tighten the instructions until the drafts come back right.
OutcomeA specialist doing real prep work, with a human on the send button
Whatever repeats on a clock becomes a deterministic automation: the same steps, in the same order, on a schedule. Runs are account-billed and every step leaves a trace, so the morning triage that used to eat the first hour now finishes before anyone logs in — and you can audit exactly what it did.
OutcomeScheduled pipelines with auditable run traces
Invite members from the dashboard and assign roles — viewer, editor, owner — so access matches responsibility. Then everyone installs the mobile app and simply asks Botchi in plain language: routing to the right specialist happens automatically, and nobody needs to learn which tool or agent to use.
OutcomeEvery employee with their own assistant, day one
The rollout doesn't end at go-live. The dashboard gives you the levers to see what works, tighten what doesn't and repeat the pattern in the next function.
The dashboard charts Spark consumption day by day and ranks top consumers, so you see which processes actually earn their keep.
Ask-first policies queue sensitive actions for a human OK. What gets approved without edits is a candidate for automatic mode.
Every agent run and automation records what it did and what it cost. Use the traces to tighten instructions and policies.
Once sales or support runs smoothly, clone the pattern: new specialist, scoped knowledge, scoped tools. The governance is already there.
The workspace itself takes minutes. A realistic first rollout — two or three processes mapped, one or two specialists tuned, the team onboarded — is measured in days to a couple of weeks, driven mostly by how quickly you gather knowledge and iterate on instructions.
Frequent, repeatable work with clear rules and a visible owner: support triage, sales call prep, recurring reports, onboarding checklists. Avoid starting with rare, judgment-heavy edge cases.
Very little. Teammates talk to Botchi in plain language from the mobile app, web, or Slack — routing to the right specialist is automatic. The setup work (agents, knowledge, policies) is done once, in the dashboard, by whoever owns the rollout.
Yes — that's the recommended path. Start with one function and a couple of specialists, keep sensitive actions on ask-first approvals, then expand as the run history builds confidence.
Prefer to see the plans first? Pricing & Sparks