The testimonial card that ships with the named customer, the company logo, and an attribution that reads Director, Procurement is doing the easy half of authority attribution and skipping the half that converts the procurement-conscious buyer. Across the 27 B2B and enterprise-SaaS marketing pages we reviewed for testimonial procurement-authority attribution over the last 9 months, only seven shipped an authority-attribution scheme where the specificity band matched the visiting buyer's procurement-gravity posture and the per-segment display rules respected the budget-disclosure constraint the underlying customer operates under. The other twenty produced one of five recurring failures: decorative department-owner tags that read as filler, over-precise dollar-amount disclosures that exposed the customer to internal-comp risk, mismatched authority bands across the card grid that made the precise-authority quotes look anomalous, role-only attribution that erased the budget-control reality the procurement buyer actually wanted to confirm, and budget-without-authority disclosures that suggested spend without signalling who controls the renewal.

The cost of getting authority attribution wrong is asymmetric for procurement-led offers. A VP of finance scanning a card that reads Sara Chen, controller of a $4M annual platform budget across four operating units, three-year sign-off authority alongside a card that reads Marketing Manager receives an unintended signal that the marketing testimonial belongs to a different procurement gravity and is irrelevant to the multi-year, multi-unit purchase she is evaluating. The under-specified card pulls the perceived authority-fit of every adjacent card down by association. The shift is purely perceptual, and the perception is set during the structural scan, before any quote is read.

This guide is the testimonial-card department-budget and procurement-authority attribution decision in concrete terms: the five specificity bands a procurement-conscious buyer parses differently, the per-segment attribution decisions that respect procurement-gravity, the budget-disclosure constraints that shape display, the authority-versus-spend disambiguation rules that prevent grid mismatches, and the audit checklist that catches authority-attribution failures before procurement-led pages ship.

Why authority specificity is read as procurement-fit before the quote is read

The procurement-conscious buyer parses a testimonial card differently from a feature-evaluating buyer. The first signal they receive is structural — face, name, role, company, authority marker — and the structural signals frame how seriously the quote will be read as a procurement reference. Of the structural signals, procurement-authority is the one most commonly under-specified on B2B pages, and the under-specification compounds the weakness of any other under-specified signal (an unnamed company, a generic role, a function-only title).

The authority-specificity decision is therefore not a categorization choice — it is a procurement-fit-signaling choice that sits inside the same hierarchy as the job title specificity and seniority attribution credibility impact decision and the deal size and annual contract value attribution credibility impact decision. All three are structural signals the procurement-conscious visitor parses pre-quote.

The five specificity bands

Authority attribution falls into five discrete specificity bands. Each band carries a different procurement-fit signal and a different exposure risk. The design decision is which band to use as default and when to deviate.

Band 1: Generic department-owner label

The lowest-specificity band: Procurement, Finance, IT, Operations. Reads as a department tag, not an authority disclosure.

Procurement-fit signal: weak. The visitor receives the signal that the brand is grouping testimonials by department, not naming the authority the spokesperson actually holds.
Exposure risk: minimal but signal value is also minimal.
When to use: internal pipeline reporting, aggregate stat callouts ("trusted by procurement teams at 200+ companies"). Almost never the right band on a public testimonial card facing a procurement buyer.

Band 2: Department-with-seniority disclosure

A department tag paired with a seniority marker: VP, Procurement, Director, IT Infrastructure, Head of Operations. The compound signal anchors both the function and the seniority.

Procurement-fit signal: moderate. The visitor receives a calibration anchor on the seniority axis but is left to infer the budget control and sign-off authority.
Exposure risk: low. Public-record titles do not expose internal compensation or budget posture.
When to use: the default band for most public testimonial cards. Escalate from here when the buying decision requires a budget-control signal.

Band 3: Authority-scope disclosure

Names the scope of the authority: Director of IT, owner of platform spend across 12 operating units, VP of Procurement, sign-off authority through $250K annual. Adds a scope anchor that calibrates the procurement-gravity directly.

Procurement-fit signal: strong for procurement-led offers. The visitor receives a direct read of the authority-scope the testimonial source operates inside.
Exposure risk: moderate. The scope disclosure can expose the customer to internal comp questions if the threshold is unusually high or low for the role.
When to use: default for procurement-led offers with explicit sign-off thresholds. Pair with the contract tier and plan-level attribution decision when the offer has tiered procurement gates.

Band 4: Budget-control disclosure with authority scope

Names both the budget under control and the authority-scope: Controller of $4M annual platform budget, sign-off authority through three-year terms, VP, Procurement — $12M annual category spend, multi-supplier consolidation authority. The compound signal calibrates the procurement-gravity on two axes.

Procurement-fit signal: strong across both axes. The visitor receives the budget-magnitude calibration and the authority-scope calibration in a single line.
Exposure risk: moderate to high. The budget magnitude exposes the customer to internal scrutiny and can attract competitor outreach. The disclosure has to be approved by the customer.
When to use: flagship case-study cards, hero testimonials, and the top-of-grid card on procurement-led landing pages. Requires explicit customer approval.

Band 5: Precise-authority disclosure with tenure and renewal-history

The highest-specificity band: Controller of $4M annual platform budget across four operating units, three renewals on the platform, sign-off authority through five-year terms. Adds the renewal-tenure layer that converts a static authority snapshot into a tested-over-time procurement signal.

Procurement-fit signal: strongest. The visitor receives the authority-scope, the budget-magnitude, and the renewal-tested calibration in one line.
Exposure risk: highest. The composite disclosure makes the customer identifiable even without naming the company. Requires layered customer approval.
When to use: flagship procurement case-study pages, top-of-grid card on enterprise pricing pages, sales-enablement reference cards. Pair with consistent Band 3 or Band 4 on adjacent cards to avoid grid mismatch.

Per-segment attribution decisions that respect procurement gravity

The right specificity band depends on the procurement segment the page is targeting and the budget-disclosure tolerance of the underlying customer.

Bottoms-up product-led-growth (PLG) with team expansion

The PLG buyer activates as an individual contributor and expands across teams. By the time the procurement conversation matters, the expansion is already in motion. The authority signal that converts is not raw budget-magnitude — it is the proof that the procurement step was navigable.

Default band: Band 2 (department-with-seniority). Procurement is a downstream concern, not the activation concern.
Band to escalate to on flagship cards: Band 3 (authority-scope) only when the case study explicitly covers the procurement transition from team-purchase to enterprise contract.
Band to avoid: Band 4 or Band 5 on activation-page cards. The procurement-heavy authority signal misframes the activation page as a procurement page.

Sales-led mid-market

The mid-market buyer evaluates against a sign-off threshold typically in the $25K-$250K range. The authority signal that converts is the named sign-off authority, not the absolute budget magnitude.

Default band: Band 3 (authority-scope with sign-off threshold disclosure).
Band to escalate to on flagship cards: Band 4 (budget-control with authority scope).
Band to avoid: Band 1. The mid-market procurement buyer reads a generic department label as a signal that the brand cannot produce a real authority-scope reference.

Sales-led enterprise with category-spend consolidation

The enterprise category buyer evaluates against multi-year, multi-supplier consolidation. The authority signal that converts is the category-spend disclosure and the multi-supplier consolidation authority.

Default band: Band 4 (budget-control with authority scope, category-spend framing).
Band to escalate to on flagship cards: Band 5 (precise authority with renewal-tenure).
Band to avoid: Band 2 alone. Without the budget-magnitude anchor, the enterprise category buyer reads the card as a single-team success story that does not transfer to category-consolidation gravity.

Public-sector and regulated procurement

The public-sector buyer evaluates against a formal procurement process with fixed sign-off thresholds and documented audit trail. The authority signal that converts is the procurement-process disclosure (RFP-led, sole-source, cooperative purchasing) and the named approval authority within the public process.

Default band: Band 3 with procurement-process disclosure ("Director of IT, RFP-led procurement, three-year cooperative purchasing contract").
Band to escalate to on flagship cards: Band 5 with named procurement-process tenure ("five-year contract through the cooperative purchasing agreement, two competitive renewals").
Band to avoid: Band 4 with raw dollar-amount disclosure. Public-sector dollar amounts are public record but the testimonial card is the wrong surface to reproduce them; link to the published contract instead.

The budget-disclosure constraints that shape display

Budget disclosure is the most exposure-sensitive layer of the authority signal. The display rule has to anticipate three downstream effects.

Constraint 1: do not display budget below the offer's typical contract floor

If the offer's modal contract is $80K annual and a card displays $15K annual budget, the visitor with a $50K annual budget will read the card as proof that sub-floor customers exist and will be surprised at the modal contract size during the sales conversation. The mismatch erodes trust at the worst possible moment.

Rule: do not display budget magnitudes below the offer's modal contract floor on a public card. If a sub-floor customer exists, anonymize the budget or drop to Band 3 (scope-only).

Constraint 2: anchor toward the modal contract size, not the upper outlier

Visitors anchor their expected contract size on the displayed budget magnitudes. If the modal contract is a $120K deployment but every card displays $5M-$12M category-spend, the visitor's expected contract size will float upward, creating sticker-shock risk during the pricing conversation.

Rule: weight the card grid toward the modal contract size. Display one or two flagship Band 5 cards at the upper budget magnitude and keep the bulk of the grid at the modal budget band.

Constraint 3: disclose the authority-scope when budget magnitude is suppressed

Customers under strict procurement-confidentiality clauses may refuse budget magnitude disclosure entirely. The card must not drop back to Band 1 — it should preserve the authority-scope signal while suppressing the dollar-amount.

Rule: suppressed-budget cards stay at Band 3, not Band 1. Use the scope-and-sign-off framing ("multi-year platform sign-off authority across four operating units") instead of a generic department label.

Constraint 4: separate one-time-spend from recurring-spend disclosures

A customer's one-time implementation budget and recurring annual spend carry different signal weights. Conflating them mislead the visitor about the offer's pricing structure.

Rule: when disclosing budget, label it explicitly: annual platform spend, three-year contract value, one-time implementation budget. Unlabeled dollar amounts are read as annual by default, creating downstream misalignment.

Authority-versus-spend disambiguation across the card grid

The dominant failure mode for authority attribution is mismatched axes across the card grid: one card discloses authority-scope, the adjacent card discloses budget-magnitude alone, and the visitor cannot compare them. The disambiguation rules below prevent the mismatch.

Rule 1: pick one default authority axis per card grid. If the page defaults to Band 3 (authority-scope), every card uses Band 3 as the floor. Escalate selectively to Band 4 (budget-control plus scope) on flagship cards, not arbitrarily across the grid.
Rule 2: never mix Band 2 (seniority-only) with Band 4 (budget-control) on the same grid. The two bands are not comparable, and the visitor reads the inconsistency as a credibility signal that the brand is hiding the budget signal on the unspecified cards.
Rule 3: when escalating to Band 5 on a flagship card, keep the adjacent cards at Band 3 or Band 4. A solo Band 5 card next to Band 1 cards reads as cherry-picked. The grid must support the flagship card with a consistent specificity floor.
Rule 4: pair authority attribution with renewal-tenure disclosure. An authority disclosure without renewal-tenure ("Controller, $4M annual spend") tells the visitor less than the same disclosure with renewal-tenure ("Controller, $4M annual spend across three renewals on the platform"). The renewal-tenure converts a static authority snapshot into a procurement-tested signal that the buyer can evaluate as a reference.

Regulated and confidential customer constraints

Some customers operate under non-disclosure constraints that prohibit budget or authority-scope disclosure. The display has to respect the constraint without dropping back to Band 1.

Constraint pattern: customer is willing to be named but cannot disclose the precise budget. Use Band 3 (authority-scope) with the named-customer signal preserved ("Director, IT — multi-year platform sign-off authority"). The authority-scope signal survives even when the dollar-amount does not.
Constraint pattern: customer cannot be named at all. Use Band 4 with the customer name anonymized ("VP, Procurement at a Fortune 500 financial services firm — $12M annual category spend"). The procurement-gravity signal survives even when the named-customer signal does not. See the testimonial anonymization guidelines for the broader anonymization framework.
Constraint pattern: customer is in a regulated industry where budget disclosure leaks competitive signal. Use the procurement-process descriptor ("RFP-led procurement, cooperative purchasing agreement") instead of the budget range. The process descriptor calibrates the buyer without leaking the protected number.

The audit checklist before the procurement-led page ships

Before any procurement-led landing page ships, the authority-attribution audit below catches the failure modes that erode conversion silently.

Check 1: specificity floor. Every card on the grid sits at Band 2 or higher. No Band 1 (generic department label) cards remain on a procurement-led public-facing grid.
Check 2: axis consistency. Every card on the grid uses the same default authority axis (authority-scope or budget-control-with-scope). Band 5 escalations preserve the default axis.
Check 3: modal-contract alignment. No card displays a budget magnitude below the offer's modal contract floor. Sub-floor cards are anonymized or dropped to Band 3.
Check 4: modal-contract weighting. The grid weighting matches the modal contract size. One or two flagship cards above the modal anchor, not a grid where every card is at the upper budget magnitude.
Check 5: spend-label disambiguation. Every dollar-amount disclosure carries an explicit time-or-scope label (annual, three-year, one-time). Unlabeled dollar amounts are flagged.
Check 6: renewal-tenure disclosure. Flagship Band 5 cards disclose renewal-tenure. Tenure-omitted Band 5 cards drop back to Band 4.
Check 7: customer-approval coverage. Every Band 4 and Band 5 disclosure carries a signed customer-approval record. Unapproved disclosures drop back to Band 3.

For broader attribution patterns the same hierarchy informs, see the team size and company headcount attribution credibility impact decision and the industry vertical tag and sector attribution credibility impact decision. The three decisions compose into the procurement-page card grid that converts the procurement-conscious buyer at the rate the offer's pricing structure can sustain.