Product · Skills
Teach Sherpa how your team works.
- Helios Logistics, $1.2M, Nov 14: the champion left in August. Priya owns it.
- Acme Freight, $960K, Dec 2: no executive contact in 41 days. Dan owns it.
Renewal risk brief
Score every account renewing in the next 180 days, then draft the outreach its owner sends.
Steps
- Pull renewals from Salesforce: ARR, stage and the last executive activity.
- Read usage against plan in
Renewals FY27.xlsx. - Score each account High, Medium or Low with
scoring.md. - For every High, draft an email from
templates/outreach-email.md.
Rules
- Flag any account whose champion left in the last 90 days as High.
- Cite the CRM record or the sheet cell behind every reason.
- Never send anything. Leave drafts for the account owner.
Output
- One table: account, ARR, renewal date, risk, and the reason in one line.
- Lead with the accounts that renew before the quarter closes.
How you teach Sherpa
Skills
Write down how a task is done once, and point Sherpa at it with @ in any chat.
Memory
Sherpa remembers at four levels, each a Markdown file you can read and edit.
Team rules
Rules your whole organization shares, for all work or only for spreadsheets or decks.
Write down how a task is done, once.
A skill is a written method Sherpa follows. Altitude comes with three, and you and your team write your own in the skill editor: personal skills for yourself, organization skills for everyone. Type @ in a chat to point Sherpa at a skill by name.
- Excel editing — Builds and edits workbooks with live formulas.
- PowerPoint editing — Builds decks and edits existing ones in place.
- Research tables — Sets up and fills research tables with cited answers.
- High: Helios Logistics and Acme Freight, each with a draft for its owner.
- Medium: Northwind Traders, Brightline Health and Corvid Energy.
Renewal risk brief
Score every account renewing in the next 180 days, then draft the outreach its owner sends.
Steps
- Pull renewals from Salesforce: ARR, stage and the last executive activity.
- Read usage against plan in
Renewals FY27.xlsx. - Score each account High, Medium or Low with
scoring.md. - For every High, draft an email from
templates/outreach-email.md.
Rules
- Flag any account whose champion left in the last 90 days as High.
- Cite the CRM record or the sheet cell behind every reason.
- Never send anything. Leave drafts for the account owner.
Output
- One table: account, ARR, renewal date, risk, and the reason in one line.
- Lead with the accounts that renew before the quarter closes.
See what Sherpa remembers, and change it.
Sherpa keeps memory at four levels. Each one is a Markdown file you can open, read and edit.
- You — How you like to work, across every chat.
- Project — What matters for one piece of work.
- Automation — What a scheduled run carries between runs.
- Chat — What was settled in a single conversation.
Memories
Durable context Sherpa reads and maintains across work: yours, and the team’s.
How I work
Writing
- Plain sentences. No "leverage", no "synergy".
- Memos open with the recommendation, then the reasons.
- Figures in the table, not the prose, unless one figure is the point.
Sales
- I own the Sales team's renewals: 40 accounts, reviewed every Monday.
- Priya Shah and Dan Ortiz are the account owners I work with most.
- Drafts go to the owner for review. I never send outreach myself.
Set the rules Sherpa follows for everyone.
Team agent rules apply across your whole organization: house style, naming conventions, what never goes in a deck. Scope a rule to all work, or only to spreadsheets or presentations.
- General — Every task Sherpa takes on.
- Excel — Every workbook it builds or edits.
- PowerPoint — Every deck it builds or edits.
Memories
Durable context Sherpa reads and maintains across work: yours, and the team’s.
PowerPoint
Every deck Sherpa builds or edits.
- Start from
Altitude house template.potx. - One message per slide, written as the title.
- No more than one chart per slide.
- Put the source under every chart, in 9pt gray.
- Never put customer names on a slide for an external audience.
You stay in control
You stay in control of how Sherpa works.
Admins decide through team policies who may change what Sherpa follows, so a rule written for everyone stays the one everyone gets.
Who edits team rules
A team policy decides who may edit the rules Sherpa follows for everyone.
Who edits organization skills
A team policy decides who may edit the skills everyone in your organization uses.
Who edits shared templates
A team policy decides who may edit the templates your team starts from.
Nothing remembered out of sight
Every memory is a Markdown file you can open and correct, so nothing Sherpa carries forward is hidden.
Use cases
Write it down once and get it right every time.
Deck house style
An organization skill sets out your deck structure, chart style and sign-off slide, so every deck Sherpa builds starts on-brand.
Q3_board_update.pptx
The update follows the house style: its section order, its chart style and the sign-off slide at the end: Q3_board_update.pptx
Q3 board update
Fabrikam · quarter ended 30 September
Board meeting · 14 October 2026
Cover kept from Q2_board_update.pptx; the quarter and date updated.
Coming
Plugins will bundle skills with the tools they need.
A plugin will package skills together with tools from the systems you connect, so a whole way of working installs in one step. Plugins are on the way.
Built for the way your company is governed.
- SOC 2 Type I
- SOC 2 Type II
- Encrypted in transit and at rest
- No training on customer data