Services catalog, compare matrices, and scope boundaries

Included / Not included (scope boundaries at a glance)

This table is intentionally explicit. It helps align expectations and reduces “assumed deliverables”. For deeper scope rules see Policies → Scope and Boundaries & exclusions below.

Preparation checklist (what to gather before we start)

If you can share most of these, the review becomes more accurate and faster to implement. If you’re missing items, we can still proceed, but we will flag assumptions in the deliverable. See also Process → Intake.

1. 1

   Intake & goals (what “good” looks like)

   We define the primary reader (customer, support, procurement) and the core confusion to remove. See Intake.

2. 2

   Collect artifacts (pages, invoices, policy text)

   We annotate what exists, what’s missing, and where you currently disclose fees and billing events. Use Preparation checklist.

3. 3

   Model the billing lifecycle

   Trial → conversion → renewal → changes → cancellation → refunds. We align terms with your actual events and invoices. Reference: Billing events glossary.

4. 4

   Draft tables and matrices

   We produce tables you can reuse: included/not-included, evaluation factors, plan grid, and (when relevant) the vendor matrix template. See Templates → Tables.

5. 5

   Write customer-facing language (plain English)

   We propose wording that matches your actual mechanics (no overpromising). For tone patterns, see Templates → Policy language.

6. 6

   Review cycle (assumptions & edge cases)

   We mark assumptions explicitly and highlight edge cases that require your confirmation (taxes, credits, proration). See Review cycles.

7. 7

   Handoff: “what to change where”

   You receive a structured package: tables, notes, and a short implementation guide for your web/app/help center. See Handoff.

8. 8

   Validation: readability + internal consistency

   We check that the same term means the same thing across pricing page, invoices, receipts, and policies. Reference: Definitions table.

9. 9

   Optional: update cadence & governance

   We suggest where to record “source of truth” and how to keep docs updated when pricing changes. See Policies → Updates.

Boundaries & exclusions (what we don’t do)

We focus on documentation, clarity, and operational alignment. These exclusions protect both sides from mismatched expectations. See also Policies → Limitations and FAQ: legal.

Service sections (anchorable)

Each section includes deliverables, typical inputs, and internal links to supporting materials. For a quick choice, return to the scenarios matrix.

Fee & pricing model review

Pricing basics Invoice structure Billing events

Document-style review of your pricing page, fee disclosures, invoice structure, and plan naming to reduce confusion and support tickets.

Primary deliverables

• • Annotated pricing page notes (structure + terminology)
• • Fee disclosure map (where and how fees appear)
• • Invoice readability recommendations (line items, date ranges)
• • Plan naming & limits consistency notes

Related: plan grid template

Best-fit situations

• • Customers ask “what is this charge?”
• • Fees are disclosed inconsistently across pages
• • Invoice doesn’t match pricing page language
• • Plan names don’t reflect limits clearly

Compare in matrix

Typical inputs

• • Pricing page URL(s)
• • Sample invoice (redacted)
• • Checkout screenshots
• • Current definitions (if any)

Use preparation checklist

Request a review Read: fee disclosure patterns FAQ: invoices Scope table

Billing transparency checklist

Refunds Cancellation Proration

A readiness checklist for trials, renewals, proration, taxes, and refunds, with included/not-included boundaries and customer-facing wording.

Primary deliverables

• • Lifecycle checklist (trial → renewal → changes → cancel → refund)
• • Included/not-included boundaries (customer-facing + internal)
• • Suggested wording snippets for key moments
• • “Edge case” flags for internal confirmation

See scope table on this page

Best-fit situations

• • Disputes about renewal timing or cancellation behavior
• • Trial conversion confusion
• • Inconsistent refund explanations
• • Growing self-serve needs governance

How checklists work

Typical inputs

• • Billing event definitions you use today
• • Cancellation/renewal UI screenshots
• • Support macro examples (optional)
• • Refund workflow constraints

FAQ: refunds

Request the checklist Read: trials policy basics Acceptance criteria Exclusions

Vendor comparison matrix (no competitor brand claims)

Matrix template Procurement Definitions

A neutral feature-and-fee matrix template to help customers compare options using consistent factors and clear definitions. Your team can populate columns with your own verified information.

Primary deliverables

• • Matrix structure (factors + definitions)
• • “How to use” guidance for Sales/CS
• • Fee & billing event factors you can standardize
• • Neutral phrasing patterns (no brand claims)

See evaluation factors

Best-fit situations

• • Procurement asks the same questions repeatedly
• • Sales needs consistent comparison talking points
• • Customers need a selection guide without hype
• • You want standardized definitions across teams

Resources: procurement appendix

Typical inputs

• • Your product’s plan grid and usage model
• • The factors you care about (we provide defaults)
• • Any customer decision criteria you’ve observed
• • Preferred output format (doc/table)

Definitions table template

Request the matrix template FAQ: comparisons Open template Scope table

Popular related links (keep exploring)

This hub is meant to connect the “why” (resources) with the “how” (templates) and “rules” (policies).