Accounts gives sales and customer success teams working memory for active relationships. It installs account briefs, meeting notes, health reads, and a roster next to your own sales approach, so your team and its agents can prepare calls and follow-ups from the context that never fits neatly into a CRM field.
What does the Accounts workflow install?
your-folder/ # The folder where you add the workflow└── accounts/ # Working memory for active customer relationships ├── accounts.md # The roster, owners, stages, and next steps ├── approach.md # Your sales and discovery approach ├── _template/ # The starting point for every new account └── <company>/ # One folder per customer or prospect ├── README.md # Current context and account strategy ├── health.md # Risks, momentum, and recommended attention ├── meetings/ # Dated notes and follow-ups └── shareables/ # Material prepared for the customer- One account brief keeps the current situation and strategy easy to scan.
- A shared roster shows owners, stages, last touch, and next steps across accounts.
- Your own sales approach shapes call prep and discovery instead of a generic playbook.
What does Accounts look like in practice?
Prepare for a customer call
- You ask: "Prep me for the Acme call."
- The agent works from: The account brief, recent meeting notes, the health read, and your sales approach.
- You get: A pre-call brief with the relationship stage, key people, priorities, tailored discovery questions, risks, and a suggested next step.
Log a customer meeting
- You ask: "Log these notes from my Acme check-in."
- The agent works from: The notes you provide and the existing account brief.
- You get: A dated meeting file, refreshed open threads and history, plus an updated last touch and next step in the account roster.
How does Accounts adapt to your sales process?
- Install Accounts from Marketplace in Palette Desktop.
- Your agent finds the right home for the account folder and adapts the sales approach to your company, product, and customers.
- Add an account, log a meeting, or ask for a call brief.
Palette Desktop creates a checkpoint before installation, so you can restore the folder if you want to start over.
What can you do after installing Accounts?
Create an account for Acme Corp. # start the first account
Log these notes from my Acme meeting. # capture notes and follow-ups
Prepare me for the next Acme call. # build a grounded call brief
Refresh Acme's relationship health. # update risks and momentum
Common questions
Accounts FAQ
What does the Accounts workflow install?
It adds an accounts workspace with reusable account and health templates, a shared roster, your sales approach, and a workflow for creating accounts, logging meetings, preparing calls, and refreshing relationship health.
How does Accounts prepare me for a call?
When you ask for call preparation, the workflow reads the account brief, health read, meeting history, next steps, and your sales approach to produce a grounded brief.
Learn the system
Learn how Marketplace setups work
Keep exploring
Related folder systems and workflows
Folder system: GTM OS
By Palette
Keep brand, market, strategy, accounts, campaigns, playbooks, team context, and GTM memory in one folder.
gtm-os/├── accounts/ # customers, prospects├── foundations/ # brand, market, strategy├── playbooks/ # sales, content, launches├── work/ # campaigns, projects├── team/ # per-person context└── log/ # decisions, historyWorkflow: Presentations
By Palette
Turn Markdown drafts into polished HTML slide decks with presenter notes, themes, and PDF export.
presentations/├── presentations.md # your deck history├── snippets.md # reusable branded slides├── drafts/ # outlines and slide notes└── slides/ # browser-ready decks ├── template.html # the reusable deck engine └── <presentation>.html # a generated slide deckFolder system: Company OS
By Palette
Keep company context across accounts, GTM, product, engineering, operations, and people in one shared folder.
company-os/├── accounts/ # customers, relationship health├── gtm/ # brand, playbooks, active work├── product/ # strategy, specs, feedback├── engineering/ # architecture, decisions, runbooks├── ops/ # finance, hiring, admin└── people/ # teammate context