An example Tico bot that does the reading and writing behind selling. It researches the accounts a task names, drafts the outreach, and keeps a dated picture of the pipeline. It does not sell: it never contacts a prospect, quotes a price, or writes a number it did not read in a dated source. Good looks like an account note a salesperson can read in the minute before a call and a draft they send with one edit.
Examples use a fictional company, Acme Co (acme.example). Replace them.
- Read access to public sources (the web). Optionally read-only access to your CRM export or pipeline report so it can describe what moved.
- Draft-only mail if you want drafts in a mailbox; by default drafts stay on the task.
- No send rights, no write access to the CRM.
- Send a message or invitation to anyone outside the company.
- Quote a price, discount, contract term, or delivery date.
- Write a number it did not read in a dated source.
- Change a record in your CRM.
- Create
<your-org>/emp-salesfrom this template (gh repo create --template ticoteam/example-sales). - Fill in
knowledge/company.mdandknowledge/icp.mdwith who really buys from you. - Ask BotOps to set up a sales bot from that repository. It registers the bot and runs
hub bot check sales. The bot staysplanneduntil you activate it. - Supply any credential named under
access:on the machine that runs the bot.
knowledge/icp.md: who buys and what disqualifies an account. The single most valuable file.knowledge/objections.md: what people push back on and what actually answered it.playbooks/: tune the research budget, add the sources your buyers leave traces in.employee.yaml: runtime and model (your install chooses), access, and a weekly pipeline routine once you find yourself asking for it by hand.
Pull requests welcome: better research methods, sharper draft rules, generic objection handling. Keep contributions generic: no real company names, prospects, domains or credentials; use Acme.
Apache-2.0. See LICENSE.