Usage-Pricing Configuration Director

The mandate

The firm wants to introduce usage-based packages for data ingestion, protected workloads and response automation, but its teams use different definitions of each measure. Sales contracts cap, pool and reset consumption inconsistently; telemetry loses customer context; and billing adjustments conceal disputes. The defined problem is to create pricing configuration that expresses an intelligible customer value metric and can be quoted, metered, invoiced and changed without recurring manual interpretation.

The deliverables are a metric decision framework, offer-and-configuration model, metering control design, contract-language requirements, quote-to-bill scenario set, migration segmentation and operating governance. The design must address aggregation, identities, retries, late events, regional data boundaries, minimum commitments, overage, credits, bundles and disputed usage. It must also separate experimentation from generally available terms and preserve contracted arrangements during migration.

Three milestones govern four months: by week four, accept candidate metric evidence and failure modes; by week ten, approve the configuration, metering and commercial-control design through end-to-end scenarios; and by week seventeen, deliver customer migration paths, operating roles, investment requirements and the executive launch decision. The engagement is billed against these three milestones after acceptance.

Acceptance requires product and finance to agree what customer behaviour creates billable usage, engineers to reproduce invoices from immutable events for a demanding scenario set, sales operations to configure representative deals without private spreadsheets, and customer success to explain estimates and disputes. The chief financial officer also requires documented controls for completeness, cut-off, credits and contract divergence before recommending launch.

The client provides pricing research, product telemetry, event schemas, sample contracts, CPQ and billing configurations, invoice disputes, credit notes, unit costs, customer interviews and accounting-policy interpretations. The consultant does not set final price points, give accounting or legal opinions, implement metering code, configure production billing, negotiate renewals or approve launch. Design exclusions and unresolved executive choices will be recorded explicitly.

Why this is external work

Product teams favour metrics that express technical consumption, finance favours auditable units and sales favours flexibility for strategic accounts. Previous workshops selected labels without proving the event and contract mechanics beneath them. External leadership can test the full economic and operational chain, reject measures that cannot survive customer scrutiny and prevent the company from scaling discounts and credits around a fundamentally ambiguous meter.

What you will own

• Evaluate candidate usage metrics for customer value, predictability, controllability, cost correlation, observability and resistance to gaming.
• Define event identity, aggregation, deduplication, timing, regional treatment, correction and retention required for billable evidence.
• Model packages covering commitments, pools, tiers, overage, credits, bundles, trials and negotiated protections without uncontrolled branching.
• Trace sample offers through contract, CPQ, provisioning, meter, rating, invoice, revenue control and customer dispute resolution.
• Segment existing customers by contract rights, consumption shape, economic impact, telemetry fitness and migration communication risk.
• Establish metric-change, exception, experiment and credit governance with owners, thresholds, evidence and expiry conditions.
• Deliver the architecture, validated scenarios, migration paths, control requirements and decisions needed before technical implementation.

Candidate qualifications

• Has designed usage-based pricing operations for enterprise SaaS from value metric through metering, billing and customer explanation.
• Understands event completeness, identity, aggregation, retries, cut-off, corrections and dispute evidence in high-volume product telemetry.
• Has constrained sales exceptions through configurable patterns while preserving legitimate enterprise contract and migration requirements.
• Can connect product behaviour, unit economics, CPQ, billing controls and revenue-policy inputs without substituting for accountable specialists.
• Has tested proposed measures with customers who could reduce reported usage without receiving less value or creating less cost.
• Produces end-to-end scenarios detailed enough for engineering, commercial, finance and customer teams to reach consistent outcomes.

Non-negotiables

• Can attend fortnightly Dublin design rooms and the scheduled customer validation council despite remote delivery.
• Will disclose relationships with cybersecurity vendors, usage-metering providers, billing platforms, pricing firms and selected customers.
• Brings implemented usage-pricing architecture; price research or CPQ configuration alone does not meet the mandate.
• Will not recommend launch where billable events, corrections and customer disputes cannot be independently reconstructed.

1. 49 words maximum. Which attractive SaaS usage metric did you reject because customers could not predict or control it?
2. 49 words maximum. How would you reconstruct a disputed invoice when usage events arrive late and duplicated?
3. 49 words maximum. What existing-customer characteristic should determine the first migration cohort?