00 / Sales Enablement
Smoy is sales enablement. Every sales team runs on a stack of tools, and somebody has to make them work: the CRM, the cold email setup, the price list, the playbooks. In a small team that somebody is usually the person who should be selling. Smoy takes it: she keeps one list of every tool and how it is wired, keeps one price sheet and checks every price in every draft against it, writes the playbooks down, and when a tool breaks she works out why and writes the fix. This guide sets her up on Hermes Agent, a free and open source agent from Nous Research that runs on your own machine.
The software is free. The model behind it is not always free, and the real work is writing down your prices and your tools once, in one place.
Checked on 2026-11-21. Commands and limits change. Sources are at the bottom.
every command below was copied from the Hermes Agent documentation on that date. We have not test-run them on a fresh machine. If a step does not behave the way it says, see "If a step breaks" near the end: your AI can patch it for you in a minute.
01 / Before you start
| You need | Why | Cost | Checked |
|---|---|---|---|
| A computer that stays on: macOS, Linux, Windows or WSL2 | The morning check only runs while Hermes' gateway is running | Yours already | 2026-11-21 |
| Git and curl | The installer uses them | Free | 2026-11-21 |
| Hermes Agent | Runs Smoy | Free, MIT licence | 2026-11-21 |
| A model with at least 64,000 tokens of context | Hermes rejects smaller models at startup | Depends on the provider you pick. Not measured here | 2026-11-21 |
| Your real prices | She checks against them, so they have to be written | Yours already | 2026-11-21 |
| A list of the tools your sales team uses | CRM, email, calendar, quoting, payments | Yours already | 2026-11-21 |
| Telegram (optional) | To get the morning check on your phone | Free | 2026-11-21 |
On a brand new install the setup wizard may offer a "Free, start now" choice that needs no account. The Hermes docs say it is shown only when it is available, so do not plan around it.
| When | What | Your time |
|---|---|---|
| Day 1 | Install Hermes and get one normal chat working | The Hermes docs say under 5 minutes. Allow 30 |
| Day 1 | Create Smoy and give her a desk folder | 20 minutes |
| Day 1 | Write the price sheet and the tool list | 1 hour. This is the part that decides everything |
| Day 2 | Turn on the morning check | 20 minutes |
| Week 1 | Drop every draft in her folder before it goes out, and fix what she flags | 5 minutes a draft |
The slow part is not the install. It is the price sheet. Most teams have prices in three places and two of them are wrong. Until there is one sheet, there is nothing to check against.
She checks the drafts you give her. A quote that never touches her folder never gets checked, so the habit matters more than the tool.
She does not log in to your CRM or your email tool in this guide. She works from what you write down and paste in, and she writes the fix for you to apply.
The price sheet is only right if you keep it right. When a price changes, change the sheet first.
02 / The build
Do not add anything else until a plain conversation works. The Hermes quickstart is blunt about this, and it is right.
On macOS and Windows the Hermes docs recommend the Hermes Desktop installer from https:/
curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash
Reload your shell, pick a model, and start a chat:
source ~/.zshrc hermes setup hermes
a welcome banner naming your model, and a reply to a simple question. If replies are empty or broken, run hermes model again and confirm the provider, the model and the login. If anything else looks off, run hermes doctor.
Every agent in Hermes gets its own profile: its own settings, memory and identity. Never point two agents at the same profile.
hermes profile create smoy --description "Sales enablement. Keeps the one price sheet and checks every price in every draft against it, keeps the list of sales tools and how they are wired, writes playbooks, fix steps and upgrade specs. Never sends a quote or changes a price. The owner does."
Creating the profile also creates a smoy command. Check it:
smoy chat
the same kind of chat as step 1, now running as the smoy profile.
In Hermes, who an agent is lives in a file called SOUL.md inside that agent's home. For a profile named smoy that is:
~/.hermes/profiles/smoy/SOUL.md
Hermes creates a starter file there. Replace its contents with the text in "Smoy's instructions" below. Keep it about who she is and how she talks. Your prices and your tools go in different files, in the next step.
after starting a new smoy chat, she introduces herself as your sales enablement when asked who she is.
This is the step everybody rushes, and it is the one that makes Smoy useful.
Make a folder for her to work from:
mkdir -p ~/smoy-desk/drafts ~/smoy-desk/checked ~/smoy-desk/playbooks ~/smoy-desk/specs ~/smoy-desk/fixes
Put three files in it. Hermes loads AGENTS.md from the folder you start a chat in, and Smoy reads the others as she works.
~/smoy-desk/AGENTS.md, the rules:
# How Smoy works this desk - price_sheet.md is the only place a price lives. Never use a price from memory, from an old draft, or from a guess. - drafts/ holds quotes, proposals and emails waiting to go out. Check every price, discount and term in each one against price_sheet.md. - For each draft write a short report: every price that matches, every price that does not (what the draft says, what the sheet says), and anything priced that is not on the sheet at all. Save the report in checked/ with the same file name. - Never fix a price yourself. Say what is wrong and let me change it. - stack.md lists every sales tool. When I tell you a tool broke, read its row first, ask me for the exact error, then write the likely cause and the steps to fix it in fixes/. - playbooks/ holds how we work a lead, one file per play. Write them from what I tell you. Do not invent a step. - When a tool needs a change, write a spec in specs/: the problem, what it should do instead, how we will know it works. One page. - If something is not in price_sheet.md or stack.md, say so and ask me once. Never fill a gap with a guess. - Never send a quote, change a price, or log in to a tool. Draft it, save it, and show it to me.
~/smoy-desk/price_sheet.md, the one price sheet:
# Price sheet
Last changed: {date}, by {name}
| Item | Price | Unit (one time, monthly, per user) | Lowest price allowed | Who can approve less |
|---|---|---|---|---|
| {item} | {price} | {unit} | {floor} | {name} |
## Terms that go with every quote
- {payment terms}
- {how long a quote is good for}
## Never offered
- {discounts, bundles or terms nobody may promise}
~/smoy-desk/stack.md, the tool list:
# Sales tools
| Tool | What we use it for | Owner | Feeds into | How to tell it is working | What usually breaks |
|---|---|---|---|---|---|
| {CRM} | {contacts and deals} | {name} | {email tool, quotes} | {a new lead shows up within a minute} | {unknown} |
| {cold email tool} | {outbound sequences} | {name} | {CRM, the rep's inbox} | {replies land in the rep's inbox} | {unknown} |
when you run smoy chat from inside ~/smoy-desk and ask what a product costs, she answers from price_sheet.md or says it is not on the sheet.
Run smoy chat from inside ~/smoy-desk and send her this:
Help me fill in price_sheet.md and stack.md. Ask me for one item at a time: its price, its unit, the lowest price I allow and who can approve less. Then ask me for each sales tool: what we use it for, who owns it, what it feeds into, how I can tell it is working, and what has broken before. Write my answers into the two files exactly as I give them. If I do not know something, write "unknown" and move on.
a price sheet with every item you sell and a tool list with every tool your team touches, in your own words.
Hermes has a built-in scheduler. Give the job Smoy's folder so she reads your price sheet when she runs. The folder must be written as a full path.
hermes -p smoy cron create "weekdays at 8am" \ "Morning check. Read price_sheet.md. Check every file in drafts/ that has no report in checked/ yet. For each one list every price that does not match the sheet (what the draft says, what the sheet says) and anything priced that is not on the sheet. Then list any tool in stack.md marked unknown under how to tell it is working. Change nothing and send nothing. Keep it under 200 words." \ --workdir /Users/you/smoy-desk \ --name "Price and tools check"
Schedules run from a gateway, and each profile has its own. Start Smoy's, and check that her scheduler is alive:
smoy gateway start hermes -p smoy cron status
smoy gateway install keeps it running after a restart.
By default the check is saved on your machine. To get it on your phone, connect Telegram first with hermes gateway setup, then create the job with --deliver telegram added.
One thing to check on your machine: whether your times come out in your own timezone. Hermes reads the schedule in the profile's timezone: setting. Add --timezone America/Los_Angeles (or your zone) to pin it.
a price and tools check waiting for you the next weekday morning.
Save one real quote or proposal you are about to send as a text file in drafts/. From inside ~/smoy-desk run smoy chat and send her this:
Check drafts/{file name} against price_sheet.md. List every price, discount and term in the draft. For each one say whether it matches the sheet, and if it does not, show what the draft says next to what the sheet says. Flag anything below the lowest price allowed and anything that is not on the sheet at all. Save the report in checked/. Do not change the draft.
a short report in checked/. Every price in it is either matched to a row on the sheet or flagged, and the draft itself is untouched.
Paste this into ~/.hermes/profiles/smoy/SOUL.md. Change the parts in braces.
# Who you are
You are Smoy. You are sales enablement for {your business}.
Your job is to make the tools work so the team can sell: there is one price sheet and every quote matches it, every tool is written down with how it is wired, every play is written down, and when something breaks there is a fix on the page the same day.
# How you work
- One price sheet. A price that is not on it does not exist.
- You check every price in every draft against the sheet. You say what the draft says and what the sheet says, side by side.
- You never change a price or a draft yourself. You flag it and your owner fixes it.
- When a tool breaks you ask for the exact error first. Then you give the likely cause and the steps, in order.
- You write things down once, in one place: the sheet, the tool list, the playbook, the spec.
- When you do not know, you say "unknown" and ask once. You never guess a price, a setting or a step.
- You never send a quote, change a price, or log in to a tool. Your owner does.
# How you talk
- Organized, upbeat and matter of fact.
- Lead with what is wrong, then what is fine.
- One line per item: what the draft says, what the sheet says, what to do.
- When you ask a question, ask exactly one.
This persona was written from Smoy's job description for this guide. It is not a copy of the instructions she runs on in our own team.
Run smoy chat from inside ~/smoy-desk and send her this:
List every item on price_sheet.md with its price and its lowest price allowed. Then tell me which rows are missing a price, a unit or a floor. Then list every tool in stack.md where "how to tell it is working" is unknown. Use only what is in the two files. Change nothing.
A good answer repeats your prices exactly as written, names the rows with gaps instead of filling them, and lists the tools you have not written a health check for.
If she states a price that is not on the sheet, tighten the first rule in AGENTS.md and ask her where the number came from.
03 / When it goes wrong
| What you see | Why | Fix |
|---|---|---|
| Empty or broken replies | Model or login is wrong | hermes model, then a plain chat before anything else |
| She does not know your prices | The chat was not started in ~/smoy-desk |
Start smoy chat from that folder |
| She passed a wrong price | The price sheet is out of date, or the draft used different wording for the item | Fix the sheet first, then name the item the same way in both places |
| She quoted a price that is not on the sheet | She guessed | Tighten the "only place a price lives" rule in AGENTS.md and SOUL.md |
| Her fix for a tool is vague | She did not have the exact error, or the tool's row is thin | Paste the full error, and fill in that tool's row in stack.md |
| No morning check | Smoy's gateway is not running, or the job is missing its folder | hermes -p smoy cron status, smoy gateway start, and recreate the job with --workdir |
| The check arrives at the wrong hour | The schedule is running in another timezone | Recreate the job with --timezone set to your zone |
| Anything else | hermes doctor |
Hermes changes fast, so a command here can drift from what your version expects. You do not need us to fix it. Paste this into Hermes itself, or into Claude or ChatGPT, with the error underneath:
I am following a setup guide for a sales enablement agent on Hermes Agent. This step failed. Here is the step, the exact command I ran, and the full error. Check the current Hermes Agent docs at https://hermes-agent.nousresearch.com/docs, tell me what changed, and give me the corrected command.
hermes doctor is worth running first. It catches most setup problems on its own.
hermes model. Every morning check and every draft she reads is model usage. Not measured here, so no number is given.04 / If you would rather not
Nobody stalls on the install. They stall on writing their prices down in one place.
CAMBY Ai sets Smoy up and runs her for you: https:/