IT Support for Nonprofits: Price the Work and Scope

Choose the Client Before Writing the Campaign

Start by asking what the organization needs to keep operating. Find out which systems support that work and which people use them. Don't assume the nonprofit label tells you the environment or the service hours they need.

Check whether your standard stack fits and whether the client will accept the changes needed to use it. If the proposed work needs specialist expertise you don't have, resolve that before selling the agreement. A nonprofit page on your website can't make your team qualified to support an unfamiliar system.

Here is what I'd cut: the claim that you serve every charity. Name the service you can deliver and let discovery establish whether this organization fits. A broad mission statement doesn't help the person preparing the quote decide what to include.

Ask the people who run the work what a service failure would affect. Record their answer in the client notes rather than guessing from the organization's public cause. That gives your technicians a useful starting point for the actual service.

Keep the Monthly Price Intact

The model's rule is to preserve recurring fees when winning a client. Its usual concession is onboarding: quote that fee and include it free for the signed agreement. Fund the onboarding work in your plan even though you aren't collecting that fee.

Check the all-in seat price, which is recurring revenue divided by seats. The model counts the larger of users or devices and sets a US floor of $150 per seat each month. The floor is a danger line. It doesn't prove the account will earn your intended margin.

Record the proposed recurring revenue and seat count with the opportunity in your CRM. If the resulting US all-in seat price is below $150, I'd send the quote back for review rather than celebrate another nonprofit client. Use the service cost calculation as well; clearing the floor doesn't finish the pricing decision.

Here is what I'd cut next: the automatic recurring discount attached to nonprofit status. Work through scope and funding with the buyer instead. If you can't offer a service they can fund, give them a clear answer before your technicians inherit the promise.

Verify Vendor Offers Before Putting Them in the Budget

Have the client confirm eligibility for any proposed nonprofit software offer through the vendor's current process. Price the actual products needed for the people using them. Don't build the quote around a remembered donation program or assume every user qualifies for the same offer.

Confirm the client's available offer before treating it as a cost in a signed proposal.

Keep the MSP's service price distinguishable from the supplier purchase. A lower license charge doesn't document less account work or training. Explain what your management fee covers without implying that the client must buy extra software to justify it.

Name who maintains the eligibility and renewal information. Check the arrangement again when the relevant terms change. Your account team needs to know whether a proposed cost still applies before presenting the next budget.

Find the Person Who Can Approve the Agreement

Ask the executive contact how the purchasing decision works. If board approval is required, find out what the board needs and when the decision can happen. Don't treat a friendly conversation with a volunteer as approval to begin work.

Keep the board paper plain. Explain the service and the reason for the recommendation, then show the recurring cost separately from project work. The decision-makers shouldn't need a sales presentation to work out what the organization is committing to.

Don't promise a start date before the client has completed its approval route. Have your project scheduler confirm availability when approval arrives. A board meeting date and an engineer's available start date are different entries in the plan.

Treat Grant Funding as a Question to Resolve

If the client proposes to use a grant, ask its finance lead to confirm what the grant can fund and when the money is available. You aren't establishing that from the grant's title. Keep an expected award distinguishable from funding the client has confirmed.

Ask how ongoing service will be paid after the project funding ends. Record the client's plan without presenting a hoped-for renewal as committed cash. You can discuss a service they can sustain rather than a monthly promise built around a temporary source.

If the budget can't fund the proposed offer, inspect the actual work with the client. There may be a separately scoped project you can deliver without taking on ongoing management. Keep its price and acceptance clear instead of disguising an unsupported managed plan as an introductory arrangement.

Don't promise that a shorter proposal will solve a funding gap. Marketing can explain the choice, but the buyer still needs an authorized source for the commitment. Your sales record should show what remains undecided.

Judge the Delivered Account Alongside the Win

Once the service starts, compare actual delivery effort with the quote. Keep the cost of account and board discussions visible as part of the work. Missing time records don't establish that a client is inexpensive to serve.

The model calls for quarterly client grading on margin and fit. Use that review to inspect the service you actually delivered and resolve scope drift. Don't wait until renewal to notice that the team is supporting more than the agreement describes.

Track which nonprofit inquiries match the service and which become funded agreements in the CRM. A growing list of interested organizations isn't the same as a workable client base. Read the sales result beside the delivered economics before expanding the campaign.

Choose a prospective client and confirm its approval and funding route. Build the costed offer around the work your team can support. Then let that concrete proposal decide whether the relationship fits both businesses.