Stacks

Track two kinds of stacks: the tools your MSP uses to deliver service, and the tools each client runs their business on.

Why two stacks

When Kyle (MSPGeek) reviewed the beta, he called out that the stack concept in most MSP tools is flat — just “what tools does this client use?” But an MSP actually cares about two stacks, and they serve different workflows:

MSP Stack

Edit your MSP Stack at Settings → MSP Stack. Each tool has a name, optional vendor, category, description, and a Core tool flag for the stack you deploy on most engagements (starred in the list).

Categories are free-text with suggestions: RMM, PSA, Documentation, EDR / Antivirus, Backup, Patch Management, Remote Access, Security Training, Password Management, SIEM, M365 Management, Billing / QuoteWerks. Use whatever makes sense for your team — the list is yours.

Your MSP Stack surfaces in onboarding handoff, prospect discovery conversations, and anywhere your team needs a shared reference for “what do we use for X?”

Client Stack

The Client Stack is set per account. Two ways to edit it:

• •From My Breadbox. Click an account card to open the pop-out. The Client Stack section is inline with an Add button — type the product, pick a category, save. Zero navigation.
• •From the account detail page. In the right sidebar, expand More → Client Stack to open a side panel with the full editor.

Each item has a required product name and optional vendor, category, and version. Items are grouped by category in the display. Hover a row to reveal edit and delete buttons.

How it's different from Standard Stack

Don't confuse these three concepts — they look similar but serve different purposes:

• MSP Stack — tools your team uses internally (org-wide, Settings).
• Standard Stack — the CLIENT stack your MSP prefers (used by assessments to flag deviation). Configured in Settings → Standard Stack.
• Client Stack — what a specific client actually uses (per-account, editable inline).

Assessments compare Client Stack against Standard Stack to compute deviation. MSP Stack is independent — it's about your internal tooling, not the client's.

Activity logging

Every client stack change is logged to the account's Activity feed — adds, edits, and removals. You can see who added what and when from the account detail timeline.