# Pricing and packaging for procurement software > Evaluate whether the pricing structure for procurement software matches customer value, operating cost and purchase predictability. A practical procedure with a worked scenario, category-specific checks and an editable worksheet. Source: https://saas-marketing.net/industries/procurement/pricing-packaging/ Topic: SaaS Pricing Type: field-guide Published: 2026-09-17 Last updated: 2026-09-17 Publisher: SaaS Marketing (saas-marketing.net) License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/industries/procurement/pricing-packaging/ ## Short answer A possible commercial unit is managed purchase request. Test whether it increases with customer value, whether buyers can forecast it and whether it resembles the cost of serving the account. ## Key takeaways - Treat the charging unit as a hypothesis. - Map package boundaries to meaningful requirements. - Model the complete cost of adoption. - A pricing model is incomplete when it ignores the cost of handling this category risk: a shorter cycle can result from skipped reviews rather than better workflow. --- This field guide uses a company with distributed purchasing authority as its working context. The buying conversation involves the head of procurement, while the department requester needs to approve purchases with supplier and budget context. Adapt the scope when those roles, dependencies or operating conditions differ. ## Treat the charging unit as a hypothesis A possible commercial unit is managed purchase request. Test whether it increases with customer value, whether buyers can forecast it and whether it resembles the cost of serving the account. These are separate questions. A unit that is convenient to meter can still discourage desirable product use. Ask the head of procurement to estimate an ordinary period and a busy period using the proposed model before deciding that the pricing page is clear. ## Map package boundaries to meaningful requirements Different packages should reflect differences in the work or support required, not a random distribution of features. For a company with distributed purchasing authority, requirements around ERP, identity directory and contract repository or responsibility for implementation may be more meaningful than an arbitrary feature count. Keep essential safety and access controls appropriately available. A buyer should be able to identify which package supports the intended workflow without discovering a critical restriction only after a sales conversation. ## Model the complete cost of adoption Include subscription charges, expected usage, setup effort, migration, training and ongoing administration. The current baseline is email requests and disconnected vendor lists, which also has costs even when no vendor invoice exists. Do not convert all staff time into immediate cash savings. Distinguish time that may be reassigned from spending that can actually be removed. Show which assumptions come from the buyer and which are illustrative planning inputs. ## Use a scenario table to reveal surprises Build a small scenario set: an ordinary account, a growing account and an account with unusually demanding requirements. For each, record managed purchase request, required capabilities, implementation effort and the expected invoice method. Ask where the model becomes difficult to predict. The objection "Approval rules will slow routine work" may reveal a need for support or evidence rather than a discount. A concession should not be used to avoid explaining a material limitation. ## Research willingness to pay with context Describe the customer task and the actual offer before asking for a price reaction. A respondent evaluating a vague category is not pricing the same product as someone considering a verified workflow. Separate qualitative objections, purchase intent and observed purchasing behavior. Small exploratory interviews can reveal language and uncertainty, but they do not establish a precise market-wide demand curve. Keep the segment and research method visible beside any conclusion. ## Plan changes for current customers A packaging change can alter access, incentives and support requirements. Explain who is affected, what changes, when it takes effect and how an account can evaluate its options. Test the billing behavior before announcing it. A price increase should not be described as harmless simply because the average account looks unaffected. Review the distribution, especially accounts whose use of procurement software differs from the assumed pattern. ## Category-specific review A purchasing request changes as the supplier, amount, category and risk become clearer. A single approval path may not fit every purchase. Ask how an ordinary low-risk request differs from a new vendor requiring additional review, and which information the requester must supply. Demonstrate two requests with different review needs and inspect the reason for each routing decision. Confirm that exceptions have an owner. A shorter cycle is useful only when the required review was completed rather than silently bypassed. ## Worked situation Compare a small account and a larger account using managed purchase request. Use their own quantities and the actual proposed prices to calculate the ordinary invoice and a high-usage case. Then add implementation and administration effort as separate assumptions. If the larger account needs additional help with ERP, identity directory and contract repository, that requirement belongs in the comparison. Do not hide it inside an unexplained enterprise price. The scenario is useful when the head of procurement can identify which input would make a different package or a different product more suitable. ## Working worksheet | Working item | Category-specific starting point | Question to resolve | | --- | --- | --- | | Value unit | managed purchase request | Does the buyer understand and forecast it? | | Required outcome | approve purchases with supplier and budget context | What value is being purchased? | | Package dependency | ERP, identity directory and contract repository | Which requirements change the package? | | Adoption evidence | submit a purchase request and complete the required approval path | What must happen before value is plausible? | | Commercial concern | Approval rules will slow routine work | Is this a price issue or a product issue? | Add your evidence, owner and next action to each row. Read the [worksheet instructions](/resources/#using-worksheets) before completing the file. ## Run the review with the people who do the work Bring the department requester into the review of a low-risk request and a higher-risk purchase taking appropriate paths. Ask them to identify the input they would actually have, the exception they expect to encounter and the person who receives the output. Then ask the head of procurement which unresolved issue could change the decision. Keep the two answers separate until the team understands whether the obstacle is workflow fit, implementation readiness or commercial priority. Record any dependency on ERP, identity directory and contract repository beside the affected worksheet row. A dependency should have an owner and an observable completion condition. If it changes the scope of the offer, revise the public description before the next campaign. This prevents a useful planning exercise from turning into a promise the delivery team cannot meet. ## When to change the plan A pricing model is incomplete when it ignores the cost of handling this category risk: a shorter cycle can result from skipped reviews rather than better workflow. If new evidence changes the audience, required workflow or acceptance conditions, update the brief and explain why. Compare later results against the version of the plan that was actually used. ## Continue with the next decision Use the [migration offer guide](/industries/procurement/migration-marketing/) when that is the next unresolved task, or return to the [procurement software marketing overview](/industries/procurement/) to choose a different route. The [saas pricing hub](/saas-pricing/) provides the broader method. ## Reference and scope The [primary category reference](https://www.zip.co/) is a starting point for checking product terminology and current capabilities. This page provides an original planning framework. It does not imply a vendor endorsement, firsthand product test, original market survey or guaranteed commercial result. ## Frequently asked questions ### Where should pricing and packaging for procurement software start? Evaluate whether the pricing structure for procurement software matches customer value, operating cost and purchase predictability. Confirm the customer situation and the evidence needed for the next decision before selecting a channel, format or tool. ### What category-specific concern should the team investigate? The concern "Approval rules will slow routine work" needs an observable test or a clear limitation. Also account for the dependency on ERP, identity directory and contract repository; do not assume it is already resolved. ### What does the worksheet include? It contains the working items and category-specific starting points shown on this page. Add your own evidence, owner, status and next review decision. The examples are constructed, not reported results or industry benchmarks. ### How does this connect to customer value? The customer needs to approve purchases with supplier and budget context. A meaningful first checkpoint is to submit a purchase request and complete the required approval path; the ongoing condition is that requests follow agreed approval rules and preserve supplier records. Choose the stage appropriate to this piece of work rather than combining all three into one metric.