Before you sell managed wifi services, replace the access-point price list with an offer describing the site you will support and the work you will do. Keep the product component at the model's 30% margin, then cost the management work separately. Turning an equipment invoice into a monthly payment doesn't establish a funded service.
Here is what I'd cut first: the claim that every new access point creates attractive recurring revenue. The payment can recur while the delivery work costs more than the fee allows. Count the service effort before treating a growing device list as progress.
Start With the Site Outcome
Use a hypothetical before-and-after. Before the change, the offer names an access point and a monthly amount, while the client assumes it covers every connectivity problem. After the change, the proposal defines the supported site and the responsibilities your MSP accepts, with the product and management economics checked internally.
Ask what the client needs to do over the wireless connection and where that work happens. Give the technical lead those requirements before promising the design. Don't make the number of devices in a quote a substitute for checking the intended service.
Validate requirements and coverage for the platform and environment you actually support. The marketing page should describe the agreed outcome without inventing a universal coverage promise.
Marketing cannot fix an unsuitable design or missing site information. If an engineer needs discovery before a final price, arrange it. A clean per-access-point price on a website doesn't settle the scope for an unfamiliar building.
Put the Boundaries in the Offer
State who owns the relevant equipment and who authorizes changes. Show which surrounding dependencies your MSP supports and which belong with another party. A client should know where to report an issue without having to diagnose its cause first.
| Scope Area | What You Decide | What the Client Receives |
|---|---|---|
| Supported Site | The areas and business use the service is designed and accepted for | A clear site scope and acceptance record |
| Equipment and Ownership | Which supplied devices are included and who owns them | An equipment record and the agreed replacement responsibility |
| Management Work | The monitoring, maintenance, and support work your team will perform | A stated continuing service with its limits |
| Other Dependencies | Responsibility for internet service and the connected infrastructure | An issue-routing process that identifies the responsible parties |
| Changes and Expansion | How a moved workspace or increased requirement is assessed and approved | A route to a scoped change rather than an assumed free expansion |
| Response and Visits | The agreed service window and circumstances requiring onsite work | Clear support expectations and any separately quoted work |
| End of Service | The agreed handoff of equipment, access, and configuration records | A defined exit process appropriate to the arrangement |
Read the scope from the client's side. Practitioner Eric Anthony recommends pricing the expected work of supporting equipment over time, separately from explaining an equipment price as payment for better service. That's his pricing advice; use it to check whether the management promise is funded.
Don't describe outside dependencies as the client's problem and stop there. Define the handoff and the information your MSP supplies to the responsible party. Coordination can be real work even when repairing the underlying service isn't in your scope.
Price Product and Management on Their Own Basis
Use actual supplier charges for the product component. The model's product gross-margin target is 30%, so calculate product selling revenue as cost ÷ (1 − 30%), which is cost ÷ 0.70. Gross margin is the share of revenue remaining after direct cost; the remaining 70% of selling revenue covers that cost.
That differs from adding a 30% markup to cost, which the model notes produces only about 23% margin. Keep the denominator visible in the calculation. A monthly billing label doesn't change that arithmetic.
Recurring product uses the same 30% target under the model's structural choice S18. The model's recurring product line is 21% of total revenue. That mix is a feature of the example MSP, not a target fee for wireless management or proof that this new offer will achieve the same mix.
Keep the 70% resold-services margin out of the recurring product calculation. It belongs to a different model category. Applying it to the product line would materially change the price without changing the commitment you have to fund.
For the management work, include burdened delivery labor and tools and review the model's separate 50% managed-services gross-margin target. Check whether the existing managed agreement already funds any of that work. Don't count the same support commitment as additional contribution twice.
Choose the Monthly Unit After Costing the Site
A per-access-point fee can communicate the variable equipment quantity. A site fee can communicate the service you have defined for that location. Test the chosen unit against what changes cost in the actual arrangement, rather than assuming either unit automatically protects margin.
The model doesn't supply a generic wireless price per access point or site. Build the fee from the actual product costs and the management work you have scoped. Keep site-specific work and any minimum commitment visible when checking the quote.
If the arrangement includes equipment funding or future replacement, price and fund those obligations too. Use the actual term and payment schedule. Don't divide a purchase cost across an invented standard device life and assume the rest of the service is covered.
Keep initial deployment distinguishable from recurring maintenance. The client can see a simple offer while your internal record separates those costs. It should remain possible to explain the result when either the supplier bill or the support effort changes.
Involve Delivery Before the Final Promise
In practitioner sales-to-delivery advice, Brendan Rose recommends involving the relevant engineer early in selected larger proposals. He distinguishes that from the later discovery and detailed scope needed for final pricing, and says not every deal needs the same involvement. That is a conditional suggestion, not a reason to send an engineer to every enquiry.
Use delivery review where the proposed site or service needs it. Confirm what must be checked before the design and commercial commitment are final. Record the client acceptance method instead of assuming an installed access point establishes a successful outcome.
Drop 'fully managed' from the sales handoff unless agreed tasks sit behind it. Give the service lead the actual commitment and the route for a request outside it. A broad label doesn't tell the technician who pays for the next site visit.
Measure the Work Behind the Recurring Fee
Record the accepted monthly fee and scope in the CRM and agreement record. Reconcile the product charges in finance, and track the management work against the same client site in the service records. Keep additions and changes identifiable so a larger invoice isn't mistaken for a margin improvement.
Check what the continuing work consumes before expanding the offer. If actual management direct cost exceeds the model target's 50% allowance, I'd revisit the scoped work and price. The target isn't a break-even rule, but a consistent miss needs a delivery or commercial decision.
Leave access points sold out of the launch report; the count isn't evidence that the recurring service works. Report the funded sites and their actual contribution, with unresolved service gaps visible. A growing quantity can hide an offer whose labor estimate is wrong.
Start with the next suitable site and write the ongoing responsibilities before finalizing the monthly unit. Have delivery check the design and finance check the component costs. Market the fee once the people delivering it can explain what it funds.
mspoutpost.com/articles/managed-wifi-services-scope-and-price-the-site
Written by Owen Gallagher
MSP Outpost publishes information, not legal, financial, insurance, tax or compliance advice, and reading it creates no professional relationship. For decisions about your business, talk to a qualified professional.