← All posts

Best Practice: Setting Up Client Agreements in MSP Pulse

A badly structured agreement doesn't just cost you a few percentage points of margin — it quietly decides, every single month, whether you're running a business or subsidising one client's IT department. Most of the revenue leakage in managed services doesn't come from a single dramatic mistake. It comes from a dozen small defaults left unexamined: a licence cost that was never updated, a scope line nobody wrote down, an engineer rate that doesn't reflect what the engineer actually costs.

This guide is a working checklist for setting up a new client agreement in MSP Pulse, or auditing an existing one. It's written for whoever in your business owns agreements — usually the owner/admin — and assumes no prior PSA experience. Each section maps a decision you need to make onto the specific MSP Pulse feature that implements it.

1. Choose the right billing model before you build anything else

Every other decision in this guide sits on top of this one. Picking the wrong model for a client doesn't just make billing fiddly — it makes the resulting numbers meaningless, because you'll be comparing revenue against the wrong kind of cost.

Model Best for How it prices Set it up in MSP Pulse as
Recurring (managed services) Predictable monthly scope: licences, monitoring, a fixed support allowance Flat monthly/annual charge, billed whether or not the client calls A billing agreement with recurring catalogue items (monthly or annual billing)
Time & Materials (T&M) Ad hoc or occasional clients with no ongoing scope Actual logged hours × the resolved rate No agreement needed — leaving the agreement unselected bills your tenant's standard rates; only add an agreement if this client gets a different hourly rate
Fixed / project A defined piece of work with a known endpoint One locked price regardless of hours worked A quote line set to Fixed billing — hours are quoted once and locked when the quote is sent or won
Block hours A client who wants predictability without full managed services — a pre-paid hours allowance that tops up to T&M once exhausted A monthly bucket of hours for specific roles; overage bills at the normal rate Billing agreement block-hours settings (role + modifier combinations you choose to include)

A client can combine more than one of these on the same agreement — for example, recurring licences plus a block-hours allowance for support, with anything outside both falling through to T&M. Decide this combination deliberately, before you touch the catalogue or the rate card. Don't let a client drift onto a model by accident because it was easiest to set up at the time.

2. Set the default agreement and get rates right

A client can have several active agreements, but exactly one must be marked default. Quote labour lines price from whichever agreement they're attached to — not automatically from the default — so check this explicitly on every new quote rather than assuming it's correct.

Rates come from labour roles. Each role has a base rate, adjusted by location (remote/onsite) and time (office/after-hours) combinations, so onsite and out-of-hours work is priced correctly instead of being flattened to one number. Set the tenant-wide combinations once, then use agreement overrides (below) for clients who differ.

On agreement rate overrides: if a client gets a different rate than your tenant standard (a grandfathered price, a volume discount), set it as an explicit override on their agreement — never by quietly editing the tenant-wide rate card, which would silently change every other client's pricing too.

"No agreement" is a real choice, not an oversight. A quote or client with no agreement selected bills your tenant's standard rates by default. That's appropriate for a true T&M client who doesn't need a dedicated agreement record. Don't create an empty placeholder agreement just for the sake of having one — it adds a record to maintain with no pricing benefit.

3. Structure recurring items and licences so they stay maintainable

Name products generically, not by vendor, unless the vendor name is load-bearing for the client (Microsoft 365 is usually fine to name outright; a backup tool is better called "Managed Backup" than the vendor's product name). If you ever switch vendors, a generic name lets the line item survive the switch instead of becoming a permanent misnomer or forcing a contract rebuild.

Keep catalogue items and their pricing current. A licence's cost to you changes — sometimes with little warning. If the resale price on a recurring item isn't revisited when the underlying cost moves, the margin on that line erodes silently and shows up nowhere until someone goes looking. Treat a vendor price-change notice as a trigger to check every agreement carrying that item, not just update it going forward.

Recurring licences need their next invoice date set to actually bill — an agreement with recurring items showing in the UI but no invoice ever generating usually means this date was never set. Check it as part of initial setup, not after the client asks why they haven't been billed.

4. Decide what's out of scope — and route it somewhere

Every agreement should answer one question explicitly: when work falls outside what's covered, where does it go? Left unanswered, the default is that it gets absorbed into the recurring charge for free, and nobody decides that on purpose — it just happens because the alternative wasn't set up.

For work that's structurally outside an agreement's scope (a role that isn't included, after-hours work a client's plan doesn't cover), the cleanest approach is to simply not include it in that agreement's rate overrides or recurring items at all — it then resolves against your tenant's standard rates automatically and bills as T&M. You don't need a separate "exclusions" mechanism for this; it falls out naturally from only configuring what's actually covered.

For work that's covered under specific conditions (onsite travel, work tied to a particular site), use the existing scheme logic — site → agreement → tenant — so the charge/no-charge decision and any free allowance are explicit and consistent, not re-decided case by case on each ticket.

The rule to hold yourself to: if a client could reasonably ask "is this covered?", the agreement should already have an answer, and that answer should be enforced by configuration, not remembered by whoever's doing the billing that month.

5. Use block hours for the gap between recurring and T&M

Block hours exist for the client who doesn't want (or can't justify) full managed services, but also doesn't want the unpredictability of pure T&M. The design lets you scope the allowance precisely — you choose which combinations of role and work condition draw from the bucket. A common pattern: include standard Engineer time (office hours, remote and onsite) in the bucket, but leave Consultant time and after-hours Engineer work outside it, billing those at the normal rate from the first hour.

When setting one up, you'll need to decide, per agreement:

Once exhausted, time logged against an included combination simply bills at the agreement's normal resolved rate — there's no separate overage rate to configure. The invoice will show which entries were covered by the allowance and which weren't, so the client can see exactly why a given line was or wasn't charged.

6. Use deposits and staged billing for project work

For project or fixed-fee work, don't treat the whole amount as due on completion by default — most clients expect some portion upfront, and MSP Pulse's deposit billing handles this correctly rather than leaving you to track it manually.

Set a billing event on the quote as a deposit (an advance) rather than a fixed milestone charge when you want money upfront. The deposit invoices immediately; when you later invoice the actual work, the deposit is automatically credited back as a negative line (with matching negative tax, so VAT nets out correctly) — the client is billed the net amount, never double-charged.

Use a milestone billing event instead when a charge should trigger on a defined point in the work (phase complete, a specific deliverable signed off) rather than upfront.

One thing to watch: a deposit retires the automatic "bill outstanding on project closure" charge — that's intentional, so a deposit-only schedule doesn't also spawn a separate closing balance on top of the deposit. If you want both a deposit and a closing balance, make sure there's also at least one milestone event defined, since the closure remainder is computed from milestones, not deposits.

7. Keep the agreement accurate over time

An agreement that was correct on day one and never revisited is, quietly, now wrong. Two things decay without you noticing:

Vendor costs change. Licence costs move — sometimes with little warning. If your resale price isn't revisited alongside the cost change, margin erodes silently on every billing cycle until someone happens to check. Treat every vendor price notice as a trigger to review every agreement carrying that item.

Engineer costs change. As wages rise, promotions happen, or your team changes, the loaded cost of delivering a contract rises with it — but revenue doesn't move unless you move it. A contract can look fully profitable purely because nobody updated what it actually costs you to staff it.

Set a renewal cadence and hold to it. Review agreements on a fixed schedule rather than waiting for them to lapse — annually is a reasonable default, aligned to each agreement's own renewal date so the conversation happens naturally rather than being forced by an expiring record. Start that conversation with the client well before the renewal date, not on it — enough lead time to handle signatures, scope changes, or a client who's away. Treat the renewal as a genuine checkpoint: is this still profitable, does the scope still match what we're actually doing, has anything changed that the agreement hasn't caught up with — not a formality where you just extend the end date.

8. Structuring agreements for durability

A client can have several agreements, and it often makes sense to split them by kind — a default agreement for labour/MSA terms, a separate agreement for monthly licences, separate agreements for annual items like domains, hosting, or warranties. That structure is fully supported:

The ticket, not the client, carries the working agreement. Every ticket is stamped with the client's default agreement the moment it's created — from the app, the client portal, inbound email, or an inbound alert, all through one consistent path. Time-entry rates, SLA, and expense recharge all follow whichever agreement is on the ticket. This is why the default matters so much: it has to be your labour/MSA agreement, not the licence or annual-items agreement, or every ticket's SLA and rate resolution will be reading the wrong one.

A ticket's agreement can be changed (the change is logged), and moving a ticket to a different client re-stamps the new client's default automatically. Billing a single time entry under a different agreement than the ticket's is restricted to owner/admin — an engineer can't quietly shift billing by picking a different agreement on one entry.

Payment terms resolve narrowest-first: agreement → client → tenant default → 30 days. Leave payment terms blank on your licence and annual-items agreements unless they genuinely need different terms — an unset value simply inherits the client's. Credit limit does not follow this chain; it stays a client-level figure, since it's measuring total exposure across everything, not one agreement's slice of it.

Setting different terms on different agreements now genuinely produces separate invoices. If your labour agreement is Net 30 and your annual-items agreement is Due on Receipt, Load Pending will generate two invoices for that client rather than blending them — grouped by resolved terms, not by agreement or item type. If every agreement shares the same terms (the common case), nothing changes: one combined invoice as before. Use this deliberately — it's the lever for a client who needs upfront payment on one category of charge but standard terms on everything else.

Edge-case fallbacks, by design, not gaps to close:

All three are single, predictable fallbacks for cases outside the normal per-client split — not places where behaviour is undefined. One practical note: the first time you set differing agreement-level terms for a client, check the resulting invoices before relying on it across your client base.

Pre-flight checklist for a new agreement