← All posts

All About MSP Pulse

Most small MSPs run their business across five to ten different tools that were never designed to talk to each other. A PSA for tickets and billing, a separate documentation platform for runbooks and passwords, a separate remote-access tool, a spreadsheet or two holding together whatever the PSA doesn't cover. Each one is fine on its own. None of them were built with each other in mind, so the MSP spends real time and money gluing them together, and every seam between them is a place where a client's data, or an engineer's afternoon, quietly leaks away.

MSP Pulse exists because that fragmentation isn't a law of nature. It's an artifact of how this market got built up, tool by tool, over twenty years, mostly serving MSPs much bigger than the ones actually buying most of the licences. It's a single operations platform: the service desk, the asset database, the knowledge base, the password vault, quoting, billing, projects and remote access, all living in one place, built as one coherent product rather than a merger of acquisitions wearing a shared login page.

Who it's for

MSP Pulse is built for the small MSP, from a solo owner-engineer up to a team of ten or twenty, not scaled down from something designed for a 200-seat enterprise IT department. That distinction matters more than it might sound. The incumbent tools in this space were largely built for, and are priced and configured around, much larger operations: elaborate permission structures, board-and-queue routing designed for teams with dedicated triage staff, configuration screens that assume someone's full-time job is administering the PSA itself.

At that size, it's all overhead with no payoff. The owner is usually also an engineer, usually also doing sales, usually also the one who notices at 11pm that an invoice didn't go out. What that MSP needs isn't fewer features dressed up as "simple". It's the 20% of PSA functionality that carries 80% of the value, built properly, without the configuration weight of a tool designed for someone else's org chart. That's the idea behind the Lean Mean MSP Machine: lean in what it asks of you to set up and run, genuinely capable in what it does once it's running.

It's worth being specific about what gets left out, not just what gets kept. Big platforms are powerful, but that power usually comes wrapped in layers of configuration, permission schemes and workflow customisation that exist to serve the handful of enterprise accounts who need them, and that every other customer still has to wade through. In practice that often means a dedicated person whose real job is administering the PSA itself, on top of whatever they were actually hired to do. A small MSP doesn't have that person to spare. So that complexity is being deliberately designed out of MSP Pulse rather than carried over and hidden behind a friendlier interface: fewer configuration layers, fewer decisions a setup wizard shouldn't be asking of a small team, and the engineering effort spent on what that team uses every day.

The commercial side matters too. Many MSPs describe the same pain with the larger platforms: multi-year contracts that auto-renew unless a narrow notice window is caught, minimum seat or endpoint counts that keep billing after a client leaves, pricing that only appears after a sales call, and renewal increases that arrive with little room to pass them on. MSP Pulse's terms are a direct reaction to that: a flat per-engineer monthly price, every feature included, no minimum seats, no minimum term, and cancel any time. A platform built to work for the MSP shouldn't also be structured to make it hard to walk away.

Security is in the recipe, not bolted on after

MSPs are an unusually attractive target. Compromise one, and an attacker potentially inherits privileged access into every client that MSP manages. That's not a hypothetical; it's the reasoning a lot of real-world attacks on this sector have followed. A platform built for MSPs that treats security as a feature to add once the core product is working has the priority backwards.

So it's treated as a starting constraint, not a later pass. Every table in the database carries a tenant identifier from day one, and every piece of client-supplied data gets validated against it before it's written. That's the house rule the codebase is built around (though, honestly, a real penetration test still found and fixed some of its sharpest edges, which is exactly what a pentest is for). Credentials in the password vault are never exposed to anything else in the system, including the AI layer, and that exclusion is enforced in the code, not a setting someone could accidentally leave off. Tenants who want it can make their entire slice of the platform unreachable from the open internet (not access-controlled, actually absent from public DNS) through Secure Access, a zero-trust network layer most platforms this size never attempt.

Built around the engineer's actual day

A lot of what makes a PSA painful isn't missing features, it's friction. Switching between five tabs to close one ticket. Re-entering the same client details three times across three modules. A billing decision an engineer has to stop and work out mid-call because the system won't do it for them. None of that is value; it's tax.

A few commitments run through the whole product as a result:

Engineers don't make billing decisions. Which rate applies, whether travel is chargeable, how a quoted task bills: all of it resolves from configured rules. The engineer's job is to do the work and log it accurately; the system's job is to work out what that's worth. That also keeps billing consistent across the whole team instead of depending on whoever happened to be on the ticket.

Automation is visible, never silent. When the system does something on an engineer's behalf, such as suggesting a knowledge-base article, drafting an update or turning an alert into a ticket, it's clearly attributed as automated, never presented as if a person did it.

AI assists; it doesn't decide. The AI layer drafts, summarises and suggests. It prepares work for a human to review and send, through the same forms and validation a person would use, every time. It's also kept away from the vault and payroll data as a hard architectural rule rather than a policy anyone has to remember to follow.

Taken together, the aim isn't a flashier interface. It's fewer moments in an engineer's day where the tool is the obstacle rather than the help.

One platform instead of ten tabs

Every module in MSP Pulse shares the same clients, configuration items, engineers and underlying data, because it's one application, not five vendors' products stitched together behind a single login screen. A ticket, the asset it's about, the runbook that fixes it, the credential needed to log in, and the invoice it eventually generates all live together and reference each other directly, not through an integration that might silently fall out of sync.

The modules: Service Desk for incidents and service requests, with SLA tracking and a customer portal for your clients' own staff; CMDB for configuration items and assets; a unified Knowledge Base & Runbooks reachable from the ticket, the asset or the client; a Password Vault with full access logging; Quoting that flows into tickets, projects and billing once a quote is won; Billing & Invoicing with time tracking and a single invoicing path, pushing to Xero or QuickBooks Online; Projects for larger, multi-phase work; Remote Access running over Secure Access; and a role-aware Reporting & Dashboard layer over all of it.

An operations hub, not a monitoring tool

All-in-one is a trap if it's taken too literally. MSPs already have strong, hard-won opinions about which RMM, which antivirus and which backup product they trust with a client's infrastructure. Replacing all of that with in-house equivalents would mean competing with specialists at their own specialty, and asking every MSP to abandon tools they've already chosen.

One conversation with the owner of a much larger MSP made the cost of the other approach concrete. They'd committed early to one of the big vendor stacks, the kind that bundles RMM, backup and SIEM as a single ecosystem, and the honest admission was that they were now locked out of the best tool in any of those categories individually, because switching one piece meant unpicking a bundle the rest of the business had been built around. They weren't using those tools because they'd judged them best in class; they were using them because the commitment had been made, and the cost of reversing it kept rising.

So MSP Pulse draws a deliberate line. It's where the MSP runs the business: the work, the client relationship, the billing, the knowledge. It stays out of reinventing monitoring, security and endpoint management. Those stay with whichever best-of-breed vendor each MSP already uses, and feed in through inbound alerts that are matched to the right asset and client and open a triaged ticket automatically, rather than sitting in a console nobody checks. Any tool that can send a webhook can feed the service desk today; ready-made connectors for named vendors are being added one at a time. The platform is the hub; the specialist tools are the spokes each MSP chooses.

Where things stand today

MSP Pulse runs in production across the modules above, and some pieces are further along than others. A few are live but still being proven with real customers, and we say so where it applies. The team runs its own MSP on the platform, day to day, for its own real work, which is the most direct test there is of whether it holds up.

It's currently in invite-only early access, so you register your interest rather than sign up and start. The commercial model is the one it's designed for: €49 per engineer per month, every feature included, no minimum seats, no minimum term, and cancel any time.

That's the shape of it: one platform, built for the MSP that's closer to twenty engineers than two hundred, with security treated as a starting condition rather than a feature, built to get out of an engineer's way rather than add another tab to it, and deliberately not trying to be everything. Just everything an MSP needs to run the business, with room left for the tools they've already chosen for everything else.