Team Channels, and a Pricing Page That Finally Makes Sense
Slack-style channels with @mentions for the whole team, plus a ground-up pricing reset — four plans that say exactly what they include.
Update, 29 September 2026: Team Comms (direct messages, channels, calls and meetings) is now part of the Enterprise plan only. See Plenix 2026.09.2.
Two changes this quarter were less about new capability and more about the platform simply making more sense — for the teams using it, and for anyone trying to figure out what plan they actually need.
Team Channels
Direct messages and group conversations have been part of Plenix for a while — quick, searchable, and able to link straight to a ticket or company record instead of living as a disconnected side-conversation. What was missing was a way to have an ongoing, topic-based conversation that the whole team could dip in and out of, without it being tied to a specific person-to-person thread.
Team Channels close that gap. On Business and Enterprise plans, a new Channels tab sits right alongside Direct Messages on the Team Messages page:
- Create a channel around a project, a team, or an ongoing situation — public to the whole org, or private and invite-only
- @mention a specific person in a channel, and they're notified even if they haven't opened it yet
- Full search across channel history alongside DMs and groups, so nothing gets lost just because it happened in a channel instead of a direct thread
Direct messages and groups moved to be a Professional-plan feature as part of this change, with the fuller channel experience reserved for Business and up — internal team chat now scales with how the rest of the platform is tiered, rather than being an all-or-nothing feature.
A pricing page that says what it means
Alongside that, we reset the pricing structure from the ground up. The honest version of what changed: Accounting moved out of Starter entirely. Giving away full accounts-receivable, accounts-payable, and general-ledger functionality at the old Starter price wasn't sustainable, and it also wasn't fair to Professional customers paying more for a plan that didn't look meaningfully bigger. FSM, Inventory, Purchasing, and Procurement moved out of Professional and into Business — these are operationally heavier modules that don't fit a lean, services-only tier, and bundling them into Professional was diluting what that plan was supposed to be for.
What stayed put: Compliance, GDPR/QMS tooling, Reporting, the full REST API, and the automation engine all remain on Professional, because those are genuinely mid-market capabilities, not enterprise-only ones.
The new structure:
| Plan | Price (monthly) | What it's for |
|---|---|---|
| Starter | £59 | Core CRM, ticketing, ERP basics, email — running a small service business |
| Professional | £179 | The above, plus accounting, compliance, automation, and the full API |
| Business | £449 | The above, plus FSM, inventory/purchasing, HCM, LMS, e-signatures, OKRs, RMM, and Team Channels |
| Enterprise | £999 | The above, plus autonomy/AI, white-labeling, and the full security suite |
All four plans keep the 20% annual discount, and every plan field — pricing, seats, device allowances, module lists — is self-serve editable from the admin billing console, so this structure can keep evolving without a code deploy every time.
Why this round of changes matters
A pricing page is a promise. If the platform doesn't enforce it exactly — if a feature leaks onto a lower tier by accident — that promise breaks quietly, and usually the customer notices before you do. Getting Team Channels correctly gated at Business, and getting the module boundaries between Starter/Professional/Business precisely right, was as much about restoring that promise as it was about shipping something new.