# Ideal customer profile for procurement software > Identify accounts that have both a reason and the capacity to adopt procurement software. A practical procedure with a worked scenario, category-specific checks and an editable worksheet. Source: https://saas-marketing.net/industries/procurement/ideal-customer-profile/ Topic: B2B SaaS Marketing 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/ideal-customer-profile/ ## Short answer Begin with a company with distributed purchasing authority. The useful commonality is the need to approve purchases with supplier and budget context, not simply employee count. ## Key takeaways - Define fit through work, not a company-size label. - Separate need, urgency and readiness. - Write a negative profile that sales can use. - Do not use managed purchase request as a complete fit score. Volume is only one part of an account's suitability. --- 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. ## Define fit through work, not a company-size label Begin with a company with distributed purchasing authority. The useful commonality is the need to approve purchases with supplier and budget context, not simply employee count. Two equally sized organizations can have different process maturity, integration requirements and purchasing authority. Write inclusion criteria that a researcher or salesperson can observe. An account belongs in the first test segment only when the underlying work and its constraints are present. Keep company-size bands as supporting context rather than treating them as the explanation for fit. ## Separate need, urgency and readiness The trigger untracked software and service purchases bypass approval indicates a possible need for change. It does not prove that the account can buy or implement now. Readiness also depends on access to ERP, identity directory and contract repository, an accountable head of procurement, and time from the department requester. Score these dimensions independently. Otherwise an enthusiastic prospect with no implementation path can outrank a quieter account that is ready to proceed. Use an unknown state where evidence is missing rather than quietly assigning an optimistic score. ## Write a negative profile that sales can use A negative profile describes conditions that make the proposed workflow unsuitable. Examples include no owner for the connected systems, a requirement outside the product's verified scope, or an inability to test submit a purchase request and complete the required approval path. These conditions should lead to a useful next action: defer, refer elsewhere or narrow the evaluation. Avoid using a negative profile as a catch-all explanation for every lost deal. Some losses reveal a poor offer or a difficult implementation, not a bad prospect. ## Use a small evidence set before buying a large list Review a manageable set of won, lost, stalled and retained accounts. For procurement software, compare whether each account could perform the core work after purchase. A won account that never adopted may teach more about poor fit than a polite prospect that declined immediately. Record which facts were known before purchase and which only became visible afterward. This prevents the profile from depending on information that a marketing team could never have used for targeting. ## Connect the profile to a qualification conversation Ask the head of procurement how the team currently uses email requests and disconnected vendor lists and what changed. Ask the department requester to describe one recent failure or workaround. Then test the readiness assumptions with specific implementation questions. The objection "Approval rules will slow routine work" can reveal who else must participate. Qualification should produce evidence and a next step, not merely a completed form. Keep sensitive operational details out of broad marketing exports. ## Review fit against adoption and retained value The longer-term test is whether requests follow agreed approval rules and preserve supplier records. Compare similar start cohorts and allow them enough time to reach that behavior. Avoid redefining the profile around a single large contract or an unusually vocal customer. If a segment buys but repeatedly fails implementation, change the offer, onboarding support or targeting criteria. Document which change you made so later performance can be interpreted against the profile actually used at acquisition. ## 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 Consider two prospects with the same apparent company size. Account A matches a company with distributed purchasing authority, has an owner for ERP, identity directory and contract repository and can arrange time with the department requester. Account B wants a general presentation but cannot identify who owns implementation. Both may have a need, but they are at different readiness stages. Route A toward a bounded evaluation and B toward a requirements conversation. Do not invent a numerical lead score to hide that distinction. Review later whether each account could submit a purchase request and complete the required approval path and use that evidence to refine the profile. ## Working worksheet | Working item | Category-specific starting point | Question to resolve | | --- | --- | --- | | Workflow fit | approve purchases with supplier and budget context | What evidence confirms the work exists? | | Urgency | untracked software and service purchases bypass approval | Is there a dated consequence? | | Readiness | ERP, identity directory and contract repository | Who owns access and implementation? | | Buying authority | head of procurement | Who approves and who can block? | | Adoption test | requests follow agreed approval rules and preserve supplier records | What happens after the contract? | 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 Do not use managed purchase request as a complete fit score. Volume is only one part of an account's suitability. Also check this category constraint: 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 [seo content map guide](/industries/procurement/seo-content-map/) when that is the next unresolved task, or return to the [procurement software marketing overview](/industries/procurement/) to choose a different route. The [b2b saas marketing hub](/b2b-saas-marketing/) 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 ideal customer profile for procurement software start? Identify accounts that have both a reason and the capacity to adopt procurement software. 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.