Generated: Q2 2026 | Format: Structured text for LLM/AI ingestion | Coverage: All pages, all sections, all content verbatim

ACRETIX WEBSITE -- COMPLETE SITE REPORT FOR AI CONSUMPTION

TABLE OF CONTENTS

1. Site Overview and Architecture
2. Global Elements (Navigation, Footer, Design System)
3. Page: Home (/)
4. Page: Products Index (/products)
5. Page: Deal Designer (/products/deal-designer)
6. Page: Completion Hub (/products/completion-hub)
7. Page: Outcome Measure (/products/outcome-measure)
8. Page: Outcome Verify (/products/outcome-verify)
9. Page: Outcome Settle (/products/outcome-settle)
10. Page: Platform / How It Works (/platform)
11. Page: Solutions Index (/solutions)
12. Solutions Sub-Pages (7 pages)
    1. Outcome Pricing (/solutions/outcome-pricing)
    2. Verified Delivery (/solutions/verified-delivery)
    3. Revenue Assurance (/solutions/revenue-assurance)
    4. Human Completion (/solutions/human-completion)
    5. Vendor Verification (/solutions/vendor-verification)
    6. AI ROI Verification (/solutions/ai-roi-verification)
    7. Value-Based Compensation (/solutions/value-based-compensation)
13. Page: Trust (/trust)
14. Page: Pricing (/pricing)
15. Page: FAQ (/faq)
16. Page: Contact (/contact)
17. Page: Marketplace (/marketplace)
18. Page: Services (/services)
19. Page: Outcome Assessment (/outcome-assessment)
20. Resources Section (/resources)
    1. Resources Index (/resources)
    2. Blog Index + 5 Posts (/resources/blog)
    3. Guides Index + 4 Guides (/resources/guides)
    4. Tools Index + 4 Tools (/resources/tools)
    5. Events Index + 5 Event Pages (/resources/events)
    6. Benchmarks (/resources/benchmarks)
    7. Newsletter (/resources/newsletter)
21. Legal Pages (Privacy, Terms, Cookies)
22. Design System and Visual Specifications
23. Component Classes
24. Animation System
25. Reusable Components
26. Pricing Summary

1. SITE OVERVIEW AND ARCHITECTURE

1.1 Brand Identity

• Company Name: Acretix
• Tagline: Outcome-Based Deals, Made Executable
• Meta Description: The commercial control layer for outcome-based deals. Design the deal, measure the result, verify what counts, settle the economics, and complete the edge cases.
• Brand positioning: "The commercial control layer for outcome-based deals." Five products cover the full deal lifecycle: Design, Complete, Measure, Verify, Settle (D-C-M-V-S).

1.2 Technology Stack

• Framework: React 18 with TypeScript
• Build Tool: Vite (with SSR/prerender support)
• Styling: Tailwind CSS
• Icons: Lucide React
• Router: Custom hash-based router (client-side SPA) -- RouterProvider, useRouter, Link in src/lib/router.tsx
• Fonts: Outfit (primary sans-serif), Source Serif 4 (accent serif/italic), IBM Plex Mono (monospace/data)
• Backend: Supabase (database, auth) via @supabase/supabase-js
• SEO: react-helmet-async for meta tags and JSON-LD structured data, static prerendering via prerender.js

1.3 Full Route Map

2. GLOBAL ELEMENTS

2.1 Announcement Bar

AnnouncementBar component renders above the nav at the very top of the page. Reports its height via onHeightChange callback so the fixed navigation and all page content offset correctly. Styled: bg-[#1A1D26] text-white text-sm py-2.5 px-4. Contains a link styled in brand green (#1A7F64) to /outcome-assessment. The bar is always visible (not dismissible). Used to promote the free outcome assessment offer.

2.2 Navigation Bar

Position: Fixed top, z-index 50. Transparent on load; on scroll past 20px: semi-transparent off-white (#FAFAF8 at 92% opacity) with 16px backdrop blur and bottom border (#E4E2DD).

Left side links:

• Logo: AcretixLogo SVG component, links to /
• Products dropdown (hover, 150ms close delay):
  • Deal Designer -- /products/deal-designer
  • Completion Hub -- /products/completion-hub
  • Outcome Measure -- /products/outcome-measure
  • Outcome Verify -- /products/outcome-verify
  • Outcome Settle -- /products/outcome-settle
  • View all products -- /products
• Solutions dropdown (hover, 150ms close delay):
  • Outcome Pricing -- /solutions/outcome-pricing
  • Verified Delivery -- /solutions/verified-delivery
  • Revenue Assurance -- /solutions/revenue-assurance
  • Human Completion -- /solutions/human-completion
  • Vendor Verification -- /solutions/vendor-verification
  • AI ROI Verification -- /solutions/ai-roi-verification
  • Value-Based Compensation -- /solutions/value-based-compensation
  • View all solutions -- /solutions
• Platform -- /platform
• Resources dropdown:
  • Blog -- /resources/blog
  • Guides -- /resources/guides
  • Tools -- /resources/tools
  • Events -- /resources/events
  • Benchmarks -- /resources/benchmarks
  • Newsletter -- /resources/newsletter
• Pricing -- /pricing

Right side:

• "Log in" -- outlined button, links to /contact
• "Schedule a Demo" -- green-bordered CTA, links to /contact (hidden on mobile below sm breakpoint)

Mobile:

Hamburger icon (Menu/X from Lucide). Full-width dropdown with all nav items. Dropdowns expand inline with chevron toggle. Mobile CTA "Schedule a Demo" and "Log in" at bottom (sm:hidden).

2.3 Footer

Background: #EEEDEA with top border (#E4E2DD). 4-column grid (2-col mobile, 4-col md+). pt-16 pb-12.

• Col 1 (brand): AcretixLogo SVG (h-9 w-auto, links to /) + tagline "The commercial control layer for outcome-based deals." (text-[14px] text-text-secondary mt-4 max-w-[200px])
• Col 2 (Products): Label "Products" (text-[13px] font-semibold uppercase tracking-wider text-text-tertiary). Links: Deal Designer (/products/deal-designer), Completion Hub (/products/completion-hub), Outcome Measure (/products/outcome-measure), Outcome Verify (/products/outcome-verify), Outcome Settle (/products/outcome-settle)
• Col 3 (Solutions): Label "Solutions". Links: Outcome Pricing (/solutions/outcome-pricing), Verified Delivery (/solutions/verified-delivery), Revenue Assurance (/solutions/revenue-assurance), Human Completion (/solutions/human-completion), Vendor Verification (/solutions/vendor-verification)
• Col 4 (Company): Label "Company". Links: Platform (/platform), Pricing (/pricing), Marketplace (/marketplace), Services (/services), FAQ (/faq), Contact (/contact), SiteReport AI (/sitereportai)

Bottom bar: border-t border-border pt-8 mt-8. Text-[13px] text-text-tertiary. "© 2026 Acretix" on left. Links on right: Privacy (/privacy), Terms (/terms), Cookies (/cookies). All footer links: text-[14px] text-text-secondary hover:text-brand-green transition-colors.

3. PAGE: HOME (/)

SEO title: "Acretix — Outcome-Based Deals, Made Executable"

SEO description: "The commercial control layer for outcome-based deals. Design the deal, measure the result, verify what counts, settle the economics, and complete the edge cases."

JSON-LD: Organization schema (name: Acretix, url: https://acretix.io, logo: /A_web_logo.svg) + WebSite schema.

Hero Section

Layout: pt-[140px] pb-[100px]. Radial gradient top-right (rgba(26,127,100,0.08), 600x600 circle, top -200px right -200px).

Headline: "Outcome-based deals, made executable" — "made executable" in text-brand-green (#1A7F64). Font: clamp(40px,6vw,64px), font-bold, letter-spacing -0.04em.

Subhead: "You have a deal where payment should depend on results. We make that deal executable." text-[18px] text-text-secondary mt-5 max-w-[520px].

CTA row (flex-col sm:flex-row gap-3):

• Email input (placeholder "Enter your work email") + "Model your first deal" button with ArrowRight icon. On click: calls submitEmailLead(email) then navigates to https://spark-build-wonder.lovable.app.
• Secondary button "How it works" (btn-secondary, navigates to /platform).
• Mobile-only: "Schedule a demo" button (sm:hidden, navigates to /contact).

The Problem Section

Background: bg-page-surface (#F4F3F0). Badge: "The Problem". Title: "Outcome-based deals break in four places". Subtitle: "Most companies can price seats, usage, or transactions. Very few can confidently sell on outcomes."

Four problem cards (2-col grid, max-w-[900px]):

• 1 — The deal is not structured precisely enough. "Outcome definitions are vague. Measurement methodology is unspecified. Exclusions and edge cases are left to future negotiation. The contract creates an agreement but not an operating specification. When disputes arise—and they will—there is no shared, unambiguous reference for how outcomes should be measured, what counts, and what does not."
• 2 — The data is messy or disputed. "Each side has different numbers. The source systems use different schemas. Nobody agreed on the baseline. When the vendor says 1,200 outcomes and the buyer says 800, there is no shared evidentiary record to resolve the gap. Without a common factual foundation, every data point becomes a negotiation."
• 3 — The workflow still needs human judgment. "The AI does most of the work, but edge cases require a human—a licensed professional, a domain expert, someone with approval authority. Without a completion layer, the vendor cannot guarantee the full result. They sell a tool instead of a solution, priced per seat instead of per outcome."
• 4 — Finance cannot turn approved outcomes into invoices and records. "Variable revenue requires pricing formula execution, financial controls (caps, floors, holdbacks, clawbacks, true-ups), billing integration, and ASC 606-compliant revenue recognition. Manual settlement does not scale. Without financial automation, the CFO becomes the bottleneck."

Bottom note: "Acretix solves all four. One platform. Five products. From deal design to verified settlement."

Platform Pillars Section (D-C-M-V-S)

Background: bg-page-bg. Badge: "Platform". Title: "Design. Complete. Measure. Verify. Settle." (5-col grid on lg+).

Five pillar cards (letter badge in bg-brand-green-light, text-brand-green):

• D — Design: "Structure the deal. Define what counts, model the economics, generate contract-ready rules." Links to /products/deal-designer.
• C — Complete: "Handle the edge cases. Route human review, provide managed experts when AI can't finish alone." Links to /products/completion-hub.
• M — Measure: "Create the factual record. Connect to data, ingest evidence, calculate the raw metrics." Links to /products/outcome-measure.
• V — Verify: "Determine what counts. Apply the deal rules, adjudicate disputes, produce the trusted determination." Links to /products/outcome-verify.
• S — Settle: "Turn it into money. Execute pricing formulas, generate invoices, handle financial controls." Links to /products/outcome-settle.

Solutions Section

Background: bg-page-surface. Badge: "Solutions". Title: "What customers use Acretix for". Layout: 4-col grid (first 4 cards) + 3-col grid (last 3 cards).

Seven solution cards (eyebrow + title + audience + description + CTA link):

• For vendors — Outcome Pricing (audience: Software and AI vendors): "Price on what you deliver. The full infrastructure from deal design to verified invoice — independent measurement, trusted determination, automatic settlement." CTA: "Explore outcome pricing" → /solutions/outcome-pricing.
• For vendors and buyers — Verified Delivery (Both sides of outcome deals): "Both parties see the same independently verified record of what was delivered. No version dispute. No parallel measurement." CTA: "Explore verified delivery" → /solutions/verified-delivery.
• For finance — Revenue Assurance (Finance and revenue operations): "Every dollar traced from verified outcome to invoice line. Financial controls applied automatically. Full audit trail for revenue recognition." CTA: "Explore revenue assurance" → /solutions/revenue-assurance.
• For AI products — Human Completion (AI vendors with edge cases): "Your AI starts the work. A credentialed professional finishes it. Sell a complete solution with an SLA, not a tool with a disclaimer." CTA: "Explore human completion" → /solutions/human-completion.
• For buyers — Vendor Verification (Procurement and sourcing teams): "Know what you paid for. Independent measurement from your own data. Structured dispute process. Payment tied to verified delivery." CTA: "Explore vendor verification" → /solutions/vendor-verification.
• For AI vendors — AI ROI Verification (AI vendors and their customers): "Stop claiming ROI. Start proving it — from the buyer's own data, using a methodology both parties agreed to before the deal started." CTA: "Explore AI ROI verification" → /solutions/ai-roi-verification.
• For executives, teams & users — Value-Based Compensation (Executives, implementation teams, and users): "Pay the people who make value happen — executives who sponsor initiatives, teams who implement them, and users who drive adoption — based on independently verified outcomes." CTA: "Explore value-based compensation" → /solutions/value-based-compensation.

How It Works Section

Background: bg-page-bg. Badge: "How it works". Title: "From deal design to verified settlement". Timeline layout (numbered 01–04, max-w-[680px]).

• 01 — Before the deal: "Deal Designer defines the rules—what outcome is being sold, how it is measured, what is included and excluded, how the economics work. The output is a signed deal specification that publishes directly into the rest of the platform. Every definition, every formula, every rule flows downstream without re-entry. The deal as designed is the deal as executed."
• 02 — During execution: "If the AI workflow requires human judgment at any step, Completion Hub handles it—routing tasks to available reviewers based on domain expertise and credentials, managing approval queues with SLA enforcement, providing credentialed experts when the customer does not have their own. Completion records flow back into Outcome Measure as evidence."
• 03 — After a result is claimed: "Outcome Measure connects to the buyer's system of record and produces the factual account of what happened—events, evidence, raw metrics, confidence scores. Outcome Verify then applies the deal's criteria to each measured outcome, producing the definitive count/no-count determination with reason codes, decision history, and complete audit trail."
• 04 — When money needs to move: "Outcome Settle executes the pricing formula against the verified outcome count, generates invoices with line-item detail, enforces financial controls (caps, floors, holdbacks, clawbacks, true-ups), and hands off settlement data to billing and ERP systems. Every dollar is traceable from the raw measured event through the verification decision to the invoice line item."

Final CTA Section

Background: bg-brand-green (#1A7F64). Title: "Ready to make your outcomes executable?" Description: "Deal Designer is free. No credit card, no sales call." Primary CTA: "Design your deal — free" (white button with ArrowRight, links to https://spark-build-wonder.lovable.app). Secondary CTA: "Talk to our team" (outlined white button, navigates to /contact).

4. PAGE: PRODUCTS INDEX (/products)

SEO title: "Products — Five Products for the Full Outcome Deal Lifecycle"

SEO description: "Deal Designer, Completion Hub, Outcome Measure, Outcome Verify, and Outcome Settle. Five modular products sharing one outcome deal object."

Page Header

Label: "Products". Title: "Five products. One platform." Description: "Each product handles a distinct job in the outcome deal lifecycle. Design the deal. Measure the result. Verify what counts. Settle the economics. Complete the edge cases."

Product Nav Bar

Horizontal scrollable link bar below PageHeader: Deal Designer | Outcome Measure | Outcome Verify | Outcome Settle | Completion Hub. Active route highlighted in brand green with underline border.

Five Product Cards (2-col grid, last card md:col-span-2)

• 01 — Deal Designer (tagline: "Structure the promise"): "Define what outcome is being sold, how it is measured, what is included and excluded, how the economics work. Model pricing, compare scenarios, generate contract-ready rules. Free to use — no login required." Features: Outcome definition builder | Pricing and structure modeling | Baseline and exclusion design | Fallback / hybrid pricing logic | Contract-ready rules summary | Deal spec publishing into the platform. Link: /products/deal-designer.
• 02 — Outcome Measure (tagline: "Establish what happened"): "Connect to the buyer's system of record, ingest evidence from any source, normalize events, calculate raw metrics, detect anomalies, and produce the measured outcome record. This is the factual layer — it answers 'what happened?' without making commercial judgments." Features: Data connectors and evidence ingestion | Evidence normalization across sources | Baseline comparison | Raw metric calculation | Anomaly detection and confidence scoring | Measured outcome records with evidence packets. Link: /products/outcome-measure.
• 03 — Outcome Verify (tagline: "Decide what counts"): "Apply the deal's criteria to each measured outcome. Determine count or no-count. Handle exclusions, reversals, attribution. Manage disputes with full evidence and audit trail. This is the commercial truth layer — the center of the platform." Features: Count / no-count rules engine | Exclusions, reversals, and attribution review | Manual adjudication with decision support | Dispute intake, counter-evidence, and appeals | Final determination with reason codes | Complete audit trail and decision history. Link: /products/outcome-verify.
• 04 — Outcome Settle (tagline: "Turn it into money"): "Execute the pricing formula against verified outcomes. Generate invoices, calculate shared savings, handle caps, floors, holdbacks, clawbacks, and true-ups. Integrate with billing and ERP systems. Produce settlement statements with full financial lineage." Features: Pricing formula execution | Invoice and payout logic | Caps, floors, holdbacks, clawbacks, true-ups | Billing / ERP handoff (Stripe, NetSuite, SAP) | Settlement statements with financial lineage | Variable consideration and rev-rec support. Link: /products/outcome-settle.
• 05 — Completion Hub (tagline: "Handle what AI can't finish"): "Route tasks to human reviewers when AI alone cannot safely finish or approve the work. Use your own team with Workflow, or tap Acretix's managed experts with Managed. Not every deal needs this — but for AI products that require a human step, it's the difference between selling a tool and selling a complete solution." Features: Workflow: routing, approval queues, SLA management | Managed: credentialed professionals provided by Acretix | Policy checks and exception handling | Specialist escalation | Sign-off capture and completion records. Link: /products/completion-hub. (Renders md:col-span-2 — full-width card.)

Bottom CTA (bg-brand-green)

"See how it all works together" — "From deal design through verified settlement — four phases, five products, one platform." Button: "View platform" (links to /platform).

5. PAGE: DEAL DESIGNER (/products/deal-designer)

SEO title: "Deal Designer — Structure Outcome-Based Deals | Acretix"

SEO description: "Define what outcome is being sold, model the economics, and generate contract-ready deal specifications. Free to start — no credit card required."

JSON-LD: SoftwareApplication (name: Deal Designer, price: 0 USD) + BreadcrumbList.

Page Header

Label: "Products". Title: "Deal Designer". Description: "Structure the promise. Define what counts, model the economics, generate contract-ready rules."

Header CTAs: "Start designing your deal — free" (PenTool icon, bg-brand-green, links to https://spark-build-wonder.lovable.app) + "Talk to our team" (btn-secondary, navigates to /contact).

Intro Section

Section title: "Every outcome-based deal begins with a question most companies cannot answer precisely"

Body copy (3 paragraphs):

1. "What outcome is being sold? Not in abstract terms—in operational terms. What counts and what doesn't? What happens when the data is ambiguous? What fallback protections exist for both sides? What evidence is required? What approvals are needed before a result is accepted?"
2. "Deal Designer is the structuring layer that converts these questions into precise, machine-readable deal specifications. It is where sales, pricing, legal, finance, and delivery teams collaborate to define the commercial model before a deal is signed. The output is a living deal specification that publishes directly into Outcome Measure, Outcome Verify, and Outcome Settle—becoming the operating rules for the entire engagement."
3. "Most companies do this in spreadsheets, slide decks, and legal redlines. That approach breaks down the moment the deal goes live. Deal Designer closes that gap. It makes the promise executable from the moment it is signed."

Highlight cards (right column): "Free to start" — No credit card, no sales call. Model your first deal in minutes. | "Contract-ready output" — Definitions, formulas, and rules that publish directly into the platform. | "Scenario modeling" — Test upside, downside, and breakeven across pricing structures before you commit.

Capabilities Section

Badge: "Capabilities". Title: "Everything you need to structure the deal". Six capability cards:

• Outcome definition builder (TrendingUp icon): "Define what outcome is being sold, what evidence qualifies, and what approvals are needed. Structured templates for common outcome types—cost reduction, deflection, resolution, accuracy improvement—with configurable parameters for each. Start from a blank canvas or select a template based on your industry and outcome type."
• Pricing & economics modeling (FileText icon): "Model expected revenue, downside exposure, upside capture, and breakeven points. Compare pure outcome pricing against hybrid models (base subscription plus outcome component). Run sensitivity analysis across win-rate assumptions, outcome volume scenarios, and pricing tier configurations. Share interactive models via URL with deal stakeholders."
• Baseline & exclusion design (Scale icon): "Define the baselines that outcomes are measured against—historical performance, control groups, agreed benchmarks. Specify what events are excluded from measurement, what reversal windows apply, and what holdback provisions protect both parties. Independently measured baselines eliminate the most common source of post-deal disputes before they start."
• Fallback & hybrid pricing logic (Share2 icon): "Design pricing models that reflect commercial reality. Most outcome-based deals are not pure pay-for-performance—they are hybrid structures with base fees, outcome components, caps, floors, guaranteed minimums, and tiered rates. Deal Designer supports the full range of commercial structures."
• Contract-ready rules summary (BookOpen icon): "Generate a structured summary with measurement methodology, baseline definitions, attribution windows, calculation formulas, review periods, dispute resolution procedures, and financial terms. Export to PDF or share via link. This is the specification that legal reviews and both parties sign."
• Deal spec publishing (Layers icon): "Publish the signed deal specification into the rest of the Acretix platform. The outcome definitions become the measurement configuration for Outcome Measure. The count/no-count rules become the verification logic for Outcome Verify. The pricing formulas become the settlement logic for Outcome Settle. One definition, used everywhere, with no manual re-entry."

In the Platform Section

Badge: "In the platform". Title: "How Deal Designer connects to everything else"

"Deal Designer is the origin point. Every definition, rule, and formula created here flows downstream into the other four products. When you define an outcome in Deal Designer, Outcome Measure knows what evidence to collect. When you specify count/no-count criteria, Outcome Verify knows how to adjudicate. When you set pricing formulas, Outcome Settle knows how to calculate. Nothing is re-entered. Nothing drifts. The deal as designed is the deal as executed."

"As more deals flow through Deal Designer, the template library grows. Common outcome types accumulate best practices. Pricing models are refined with real-world data. A vendor designing their fifth AI support outcome deal benefits from the experience of every previous deal on the same outcome type."

How It Works Section

Badge: "How it works". Title: "From blank page to signed specification". Three steps:

• 01 — Model the economics: "Enter your base deal parameters. See revenue under your current pricing alongside the hybrid model. Share via URL with your CFO, sales team, or prospect. No login required."
• 02 — Define what counts: "Specify the outcome definition, baseline methodology, attribution window, exclusions, and reversals. Both parties review and agree on the criteria before any measurement begins. The agreed definitions become the operating rules—neither party can unilaterally change them after the deal is live."
• 03 — Generate the deal package: "Deal Designer produces the contract-ready rules summary, a structured term sheet, and an interactive business case. Both parties sign off within the platform. The signed spec publishes directly into Outcome Measure, Outcome Verify, and Outcome Settle as their operating configuration."

Bottom CTA (bg-brand-green)

Badge pill: "Free to start — no credit card required". Title: "Design your first outcome-based deal today". Description: "Model the economics, define what counts, and generate a contract-ready specification — in minutes." Primary CTA: "Start designing — it's free" (PenTool, links to https://spark-build-wonder.lovable.app). Secondary: "Talk to our team" (outlined white). Footer note: "No sales call. No credit card. No commitment."

6. PAGE: COMPLETION HUB (/products/completion-hub)

SEO title: "Completion Hub — Human Experts for AI Workflow Edge Cases | Acretix"

SEO description: "Route tasks to credentialed reviewers, provide managed experts when AI can't finish alone. Attorneys, CPAs, engineers — SLA-backed, with every completion as auditable evidence."

Page Header

Label: "Products". Title: "Completion Hub". Description: "Handle what AI can't finish. Route human review, provide managed experts for edge cases."

Header CTAs: "Start with Deal Designer — free" (PenTool, green) + "Talk to our team" (btn-secondary).

Intro Section

Section title: "This is distinct from verification"

Body copy (3 paragraphs):

1. "Completion Hub is not about whether the outcome counts commercially. It is about getting the work done correctly — handling approvals, exceptions, and human judgment before a result is even claimed. Most AI products hit a ceiling: the AI handles the bulk of the work, but a percentage of tasks require human judgment. A clause that could be read two ways. A claim with unusual circumstances. A permit that doesn't fit standard categories."
2. "Without a structured way to handle these cases, the product either fails silently, creates manual work for your team, or gets stuck waiting for the customer to figure it out. Completion Hub closes that gap. It turns edge cases from a liability into a managed, auditable workflow."
3. "Completion Hub provides two modes. Workflow gives you the software — routing, approval queues, policy checks, exception handling, SLA management, sign-off capture with credential verification. Use it when you have your own reviewers and need the infrastructure to manage them. Managed gives you the experts — credentialed professionals provided by Acretix, domain-matched to your task types. Use it when you need expert completion without building your own operations team. Both modes produce completion records that flow into Outcome Measure as evidence."

Highlight cards: "Two modes" — Workflow (software for your reviewers) and Managed (Acretix provides the experts). | "Credentialed experts" — Attorneys, CPAs, licensed engineers — domain-matched, SLA-backed, no hiring required. | "Evidence flows downstream" — Every completion is ingested by Outcome Measure as an evidence event — auditable and billable. | Green card: "Task specs defined in Deal Designer" — Completion Hub is configured by the Task Specs you build in Deal Designer — what triggers human review, what credential is required, what turnaround time applies.

Capabilities — Workflow Section

Badge: "Capabilities — Workflow". Title: "The routing and approval software". Four capability cards:

• Routing and approval queues (GitMerge icon): "Route tasks to the right reviewer based on task type, domain, credentials, or configurable policy rules. Manage approval queues with SLA enforcement, escalation paths, and overflow handling. Queue visibility is real-time — managers see what is pending, what is late, and what has been completed."
• Policy checks and exception handling (Shield icon): "Apply policy rules at each workflow step. Flag exceptions automatically based on configurable criteria — high-value transactions, unusual characteristics, conflict-of-interest checks. Route edge cases to specialist reviewers with full context and supporting evidence."
• Specialist escalation (AlertOctagon icon): "Escalate high-risk or high-complexity tasks to specialist reviewers with the appropriate credentials. Maintain full chain of custody and audit trail through every escalation level. Escalation paths are defined in Deal Designer and enforced automatically."
• Sign-off capture and completion records (FileCheck icon): "Capture human sign-offs with credential verification and timestamp. Produce structured completion records that flow into Outcome Measure as evidence events — creating an auditable, billable record of every human step in the workflow."

Capabilities — Managed Section

Badge: "Capabilities — Managed". Title: "Credentialed experts, provided by Acretix". Two capability cards:

• Managed reviewer teams (Users icon): "Acretix provides credentialed reviewers matched to your domain and task type. Attorneys, CPAs, certified engineers, licensed professionals in your vertical. No hiring, no training, no HR overhead. Reviewers are available within your defined SLA windows."
• Domain-matched expert completion (Star icon): "Match each task type to the appropriate credential pool. Contract review routes to licensed attorneys. Tax preparation routes to credentialed CPAs. Permit processing routes to certified engineers. Each expert is matched to the specific credential requirement defined for the task type."

AI Workflow Diagram

Badge: "How it works in an AI workflow". Title: "Your AI starts it. A professional finishes it." Four-step flow (left column): 1. Your AI processes the input → 2. AI reaches step requiring judgment → 3. Credentialed expert reviews and signs off (highlighted green) → 4. Complete result returned to your product. Example cards (right column): Contract review (AI flags clauses → licensed attorney validates ambiguous language) | Tax preparation (AI calculates return → CPA reviews and signs as preparer) | Permit processing (AI triages application → credentialed engineer approves).

In the Platform Section

"Completion Hub operates during deal execution — before Outcome Measure even begins counting. Task completions from Completion Hub are ingested by Outcome Measure as evidence events. The deal rules in Deal Designer determine which tasks require human completion and what quality standards apply. Completion Hub is optional — not every deal requires it — but for AI products that need a human step, it is the difference between selling a tool and selling a complete solution."

How It Works Section (4 steps)

• 01 — Define the Task Spec: "Specify what triggers human review, what the expert evaluates, what quality standards apply, and what turnaround time is required. Task Specs are defined in Deal Designer as part of the deal specification."
• 02 — Integrate via API: "The ISV integrates via a single API endpoint. When the AI workflow reaches a step requiring judgment, the platform receives the task automatically. No manual handoffs."
• 03 — Expert reviews and signs off: "The task routes to a credentialed professional from the appropriate pool. The expert reviews the AI's output, applies their judgment, and signs off. The customer never sees the handoff."
• 04 — Result flows back and is ingested: "The complete result returns to the ISV's product. The completion is ingested by Outcome Measure as an evidence event. The AI workflow continues with a complete, expert-verified output."

Bottom CTA (bg-brand-green)

Badge: "Everything starts with a deal spec". Title: "Turn your AI product into a complete solution". Description: "Define your task specs and human review requirements in Deal Designer — then Completion Hub handles the routing, experts, and evidence automatically." Primary CTA: "Start with Deal Designer — free". Secondary: "Talk to our team". Footer: "No credit card. No commitment."

7. PAGE: OUTCOME MEASURE (/products/outcome-measure)

SEO title: "Outcome Measure — Independent Evidence and Metrics | Acretix"

SEO description: "Connect to buyer systems of record, ingest evidence, normalize data, and calculate raw outcome metrics. Read-only access, reusable connectors, anomaly detection."

Page Header

Label: "Products". Title: "Outcome Measure". Description: "Establish what happened. Connect to data, ingest evidence, produce the factual record."

Intro Section

Section title: "The evidence and calculation layer"

Body copy (3 paragraphs):

1. "Before anyone can argue about whether an outcome counts, someone has to establish what actually happened. That is Outcome Measure's job. It connects to the buyer's systems of record and produces the measured outcome record: a structured, timestamped, evidence-backed factual account of every event that might constitute an outcome."
2. "Outcome Measure does not decide whether an event counts commercially. That is Outcome Verify's job. Outcome Measure answers a narrower, more fundamental question: what happened? It collects the evidence, normalizes it, calculates the raw metrics, flags anomalies, and produces the factual record that the rest of the platform relies on."
3. "This separation matters. When measurement and commercial judgment are combined in one system, disputes become intractable. By isolating the factual layer, Outcome Measure gives both parties a shared evidentiary foundation. If the numbers are wrong, fix the data. If the classification is wrong, take it up with Outcome Verify."

Highlight cards: "Question answered" — What happened? | "Read-only access" — Connects to buyer systems without write permissions. No risk to production data. | "Reusable connectors" — Every integration built for one engagement becomes a template for the next.

Capabilities Section

Badge: "Capabilities". Title: "Evidence infrastructure, not just a connector". Six capability cards:

• Data connectors & evidence ingestion (Database icon): "Pre-built connectors for Zendesk, Salesforce, ServiceNow, AWS Cost Explorer, NetSuite, Jira, and HubSpot. Support for API-based, event-stream, file-upload, and manual evidence submission. Read-only access to buyer systems—Acretix never writes to your customers' production environments."
• Evidence normalization (Activity icon): "Normalize incoming data across different sources, schemas, and formats into a consistent evidence model. Handle field mapping, type coercion, deduplication, timezone reconciliation, and data quality validation. Pipeline configuration is versioned and auditable."
• Baseline comparison (GitBranch icon): "Compare incoming events against the independently established baseline defined in Deal Designer. Track cumulative progress relative to the agreed starting point. Detect baseline drift and flag when underlying conditions have changed materially. Baselines are independently measured—not vendor-reported figures."
• Raw metric calculation (Search icon): "Calculate the raw outcome metrics—event counts, aggregate values, rates, durations, and derived calculations—before any commercial rules are applied. These are the numbers before Outcome Verify applies count/no-count logic. The calculation methodology is defined in Deal Designer and applied automatically."
• Anomaly detection & confidence scoring (AlertTriangle icon): "Flag unexpected shifts in event volume, timing patterns, or data characteristics. Score the confidence level of each measured outcome based on data completeness, source reliability, and consistency with historical patterns. Surface potential data quality issues before they become commercial disputes."
• Measured outcome records (FileCheck icon): "Produce a structured evidence packet for each measured event: the source data, the transformation applied, the raw metric calculated, the confidence score, and all supporting citations. This is the factual input that Outcome Verify uses to make the commercial determination. Each record is immutable once produced."

In the Platform Section

"Outcome Measure sits between Deal Designer and Outcome Verify. It receives the outcome definitions and measurement methodology from Deal Designer—what to look for and how to calculate it. It produces the measured outcome records that Outcome Verify uses to make count/no-count decisions. When Outcome Verify flags a data discrepancy during adjudication, it routes back to Outcome Measure for re-measurement or additional evidence. The evidence model is shared across the entire platform—Outcome Settle references the same underlying data when generating settlement statements."

How It Works Section (4 steps)

• 01 — Connect: "Deal Designer publishes the deal specification. Outcome Measure uses it to know what to look for. The data connection is established — CSV or live API to the buyer's system of record."
• 02 — Ingest and normalize: "Events arrive from the buyer's system. Outcome Measure normalizes them, checks for anomalies, handles duplicates and missing data, and produces clean evidence records."
• 03 — Calculate and score: "Raw metrics are calculated against the deal specification. Confidence scores are assigned. Low-confidence records are flagged. The measured outcome records are ready for Outcome Verify."
• 04 — Produce the factual record: "Outcome Measure produces the measured outcome record with a complete evidence packet for each event. This is the factual foundation that Outcome Verify uses to make the commercial determination."

Bottom CTA (bg-brand-green)

Badge: "Deal Designer is the starting point". Title: "Every measurement starts with a deal spec". Description: "Define what to measure in Deal Designer — free. Outcome Measure is configured automatically from your deal specification." Primary CTA: "Start with Deal Designer — free". Footer: "No credit card. No commitment."

8. PAGE: OUTCOME VERIFY (/products/outcome-verify)

SEO title: "Outcome Verify — Determine What Counts in Every Deal | Acretix"

SEO description: "Apply deal rules to every measured outcome record. Count/no-count rules engine, dispute resolution ladder, and full audit trail from raw event to final determination."

Page Header

Label: "Products". Title: "Outcome Verify". Description: "Decide what counts. Apply deal rules, adjudicate disputes, produce the trusted determination."

Intro Section

Section title: "The commercial truth layer"

Body copy (3 paragraphs):

1. "Outcome Measure tells you what happened. Outcome Verify tells you whether it counts. This is the commercial truth layer—the center of the Acretix platform and the product where trust lives. Every measured outcome passes through Outcome Verify, where the deal's criteria are applied to produce a definitive count or no-count determination."
2. "These are the questions that kill outcome-based deals when handled informally. A disputed email chain. A spreadsheet that each side interprets differently. A quarterly review that devolves into arguments about edge cases. Outcome Verify replaces all of that with a structured, auditable decision process."
3. "When disputes arise—and in outcome-based deals, some always will—Outcome Verify provides three levels of resolution. Level 1 uses the platform's rules engine for clear cases (minutes). Level 2 routes to trained analysts for ambiguous cases (3–5 days). Level 3 engages an independent CPA firm for the highest-stakes determinations (2–3 weeks)."

Highlight cards: "Question answered" — Does it count? | "Full audit trail" — Every determination is traceable—from raw event through measurement to final decision. | "Three levels of resolution" — Platform rules (minutes). Analyst review (3–5 days). Independent CPA (2–3 weeks).

Capabilities Section

Badge: "Capabilities". Title: "From evidence to trusted determination". Six capability cards:

• Count/no-count rules engine (CheckSquare icon): "Apply the deal's criteria to each measured outcome record. The rules are defined in Deal Designer and executed automatically against the evidence produced by Outcome Measure. Clear cases are classified instantly. Ambiguous cases are flagged for manual review with full supporting evidence. The rules engine handles conditional logic, multi-factor criteria, and time-based conditions."
• Exclusions, reversals & attribution (XCircle icon): "Apply exclusion rules (events that match the outcome pattern but do not qualify under the agreed terms), reversal windows (outcomes that are subsequently undone), holdback provisions, and attribution logic (isolating the vendor's contribution from external factors). Multi-vendor environments and shared-outcome scenarios are supported."
• Manual adjudication with decision support (Users icon): "For events that cannot be automatically classified, Outcome Verify routes them to manual review with full evidence packets and decision support. Adjudicators see the measured event, the applicable rules, the evidence, and a recommended classification—then apply human judgment. Monthly adjudication quota included (50–200 per month depending on tier)."
• Dispute intake & Resolution Ladder (MessageSquare icon): "Either party can submit counter-evidence, dispute a determination, or request reconsideration. Three escalating levels: Level 1 Platform Resolution (automated, minutes), Level 2 Analyst Resolution (human review, 3–5 business days), Level 3 Independent CPA Verification (attested under professional liability, 2–3 weeks)."
• Final determination with reason codes (Shield icon): "Produce the definitive count/no-count determination with reason codes, decision rationale, and complete audit trail. Once a determination is finalized, it is immutable—the historical record cannot be altered, only appealed through the defined process."
• Decision history & audit trail (Clock icon): "Every event, every rule application, every manual decision, every dispute, and every resolution is logged with timestamps, actor identifiers, and reason codes. When both parties can inspect every determination, the incentive to dispute drops dramatically. Transparency is the trust mechanism."

In the Platform Section

"Outcome Verify is the center of gravity. It receives outcome definitions and count/no-count rules from Deal Designer. It receives measured outcome records from Outcome Measure. It produces verified determinations that Outcome Settle uses to generate invoices and settlement statements. When Completion Hub handles a human review step during workflow execution, the completion record becomes evidence that Outcome Measure ingests and Outcome Verify evaluates. Everything flows through Outcome Verify. It is the product that determines commercial truth."

How It Works Section (4 steps)

• 01 — Receive measured records: "Outcome Verify receives measured outcome records from Outcome Measure — each with a complete evidence packet. The deal rules from Deal Designer are already loaded as the operating configuration."
• 02 — Apply the rules: "The rules engine applies the deal's criteria to each record. Count or no-count. Exclusions checked. Attribution evaluated. Reversals applied where triggered. Automatic classification where the rules are unambiguous."
• 03 — Adjudicate edge cases: "Events that cannot be automatically classified route to adjudication. Full evidence packets and decision support surface for human review. The adjudicator records their reasoning with reason codes."
• 04 — Handle disputes: "Either party can dispute any determination. Counter-evidence is submitted through a defined process. The case follows the dispute ladder with defined timelines and a defined endpoint. The final determination is binding."

Bottom CTA (bg-brand-green)

Badge: "Deal Designer is the starting point". Title: "Define the rules before the deal goes live". Description: "Outcome Verify enforces the criteria you define in Deal Designer. Start there — free, no credit card." Primary CTA: "Start with Deal Designer — free". Secondary: "Explore the Resolution Ladder" (links to /trust). Footer: "No credit card. No commitment."

9. PAGE: OUTCOME SETTLE (/products/outcome-settle)

SEO title: "Outcome Settle — Automated Settlement for Verified Outcomes | Acretix"

SEO description: "Execute pricing formulas, apply financial controls, generate invoices, and integrate with billing and ERP systems. Every dollar traceable to its verified outcome."

Page Header

Label: "Products". Title: "Outcome Settle". Description: "Turn verified outcomes into money. Execute pricing formulas, generate invoices, handle financial controls."

Intro Section

Section title: "The monetization and finance layer"

Body copy (3 paragraphs):

1. "When Outcome Verify produces a determination, the commercial question is answered: did it count? Outcome Settle answers the financial question: what money and records follow from that? It executes the pricing formula defined in Deal Designer against the verified outcome count — per-outcome fees, tiered rates, shared savings percentages, success fees — and generates the invoice-ready output."
2. "Outcome Settle handles the financial complexity that kills outcome-based deals at scale: caps, floors, holdbacks, clawbacks, true-ups, reversals, guaranteed minimums, maximum exposure limits. These controls are defined in Deal Designer and enforced automatically at settlement."
3. "The output is not just an invoice. It is a settlement statement with full financial lineage — every dollar traceable from the raw measured event through the verification decision to the invoice line item. Both parties receive the same statement. When the numbers match, settlement is automatic. When they do not, the lineage tells you exactly where the discrepancy is."

Highlight cards: "Question answered" — What money and records follow from that decision? | "Full financial lineage" — Every dollar traceable from the raw measured event through the verification decision to the invoice line item. | "Billing & ERP integration" — Connects to Stripe, Metronome, Zuora, NetSuite, and SAP for automated settlement.

Capabilities Section

Badge: "Capabilities". Title: "Financial settlement infrastructure". Six capability cards:

• Pricing formula execution (DollarSign icon): "Execute the pricing formula defined in Deal Designer against the verified outcome count from Outcome Verify. Per-outcome fees, tiered rates, shared savings percentages, success fees — any structure defined in the deal spec. The formula executes automatically; no manual calculation, no spreadsheet reconciliation."
• Invoice and payout generation (FileText icon): "Generate invoice-ready outputs from verified outcomes. Calculate exact amounts due, apply adjustments, produce structured invoice data for billing system integration. Invoice line items trace back to specific verified outcome events — every line is explainable and auditable."
• Shared savings and success-fee calculations (Sliders icon): "Handle shared savings deals where the buyer and vendor split the value created. Calculate success fees with configurable split ratios. Apply guaranteed minimums and maximum exposure limits. Multi-party settlement distributions are supported."
• Caps, floors, holdbacks, clawbacks, true-ups (BarChart3 icon): "Handle the financial complexity that kills outcome-based deals at scale. Caps on maximum outcome fees per period. Floors guaranteeing minimum revenue. Holdbacks pending performance confirmation windows. Clawbacks for reversed or disqualified outcomes. Period-end true-ups reconciling estimates against actuals."
• Billing and ERP integration (Link2 icon): "Integrate with billing platforms (Stripe, Metronome, Zuora) and ERP systems (NetSuite, SAP) for automated settlement. Settlement outputs flow directly into your existing billing and revenue recognition workflows. API-based and file-based integration options."
• Settlement statements with financial lineage (BookOpen icon): "Produce settlement statements with full financial lineage — tracing every dollar from the measured event through the verification decision to the invoice line item. ASC 606-compliant variable consideration support. Both parties receive the same statement, eliminating reconciliation disputes."

In the Platform Section

"Outcome Settle is the downstream endpoint of the platform. It receives verified outcomes from Outcome Verify, applies the pricing formulas defined in Deal Designer, and produces the financial outputs that go to billing and ERP systems. Settlement outputs feed into the customer's billing platform (Stripe, Metronome, Zuora) and ERP system (NetSuite, SAP) for invoicing and revenue recognition. The settlement statement provides full financial lineage — every invoice line traceable back to a specific verified outcome event, back through the adjudication decision, back to the raw evidence. When Completion Hub contributes a human-reviewed completion, that evidence flows through Outcome Measure and Outcome Verify into Outcome Settle's count. The chain of custody is complete."

How It Works Section (4 steps)

• 01 — Receive verified outcomes: "Outcome Settle receives the verified outcome count from Outcome Verify and the pricing rules from Deal Designer. Both inputs are required before settlement can execute."
• 02 — Execute the formula: "The pricing formula runs against the verified count. Per-outcome fees calculated. Shared savings computed. Caps applied. Floors checked. Holdbacks calculated. True-up amounts determined."
• 03 — Generate settlement outputs: "Invoice data produced. Settlement statement generated with full financial lineage. Variable consideration amounts calculated for revenue recognition. ERP and billing system integration packages prepared."
• 04 — Hand off to billing and finance: "Settlement outputs flow into the customer's billing platform and ERP system. Stripe, Metronome, Zuora, NetSuite, SAP integrations execute. Revenue recognition entries are generated. The settlement is complete."

Bottom CTA (bg-brand-green)

Badge: "Model your pricing in Deal Designer first". Title: "Turn your verified outcomes into revenue". Description: "Define your pricing formulas, caps, and settlement rules in Deal Designer — then Outcome Settle handles the rest automatically." Primary CTA: "Model your deal economics — free". Secondary: "Talk to our team". Footer: "No credit card. No commitment."

10. PAGE: PLATFORM / HOW IT WORKS (/platform)

SEO title: "Platform — Five Products, One Outcome Deal Object | Acretix"

SEO description: "From deal design to verified settlement — five products covering the full outcome deal lifecycle. One shared data model connecting Deal Designer, Measure, Verify, Settle, and Completion Hub."

Also accessible at: /how-it-works (alias route).

Page Header

Label: "Platform". Title: "The commercial control layer for outcome-based deals". Description: "Five products. One shared data model. One outcome deal object at the center."

How It Works Section

Badge: "How it works". Title: "From deal design to verified settlement". Subtitle: "Four temporal phases — showing when products activate, not what they are." Timeline layout (max-w-[700px]).

Four phases (numbered 01-04, each with explore links):

• 01 — Before the deal: "Deal Designer defines the rules — what outcome is being sold, how it is measured, what is included and excluded, what the economics look like. Both parties collaborate on the specification before signing. The output is a living deal specification that publishes directly into Outcome Measure, Outcome Verify, and Outcome Settle as their operating configuration. The deal as designed is the deal as executed." Explore link: Deal Designer.
• 02 — During execution: "If the AI workflow requires human judgment at any step, Completion Hub handles it — routing tasks to reviewers based on task type and required credential, managing approval queues with SLA enforcement, providing credentialed experts when the customer does not have their own. Every completion is captured as an evidence event that flows into Outcome Measure." Explore link: Completion Hub.
• 03 — After a result is claimed: "Outcome Measure connects to the buyer's system of record and produces the factual record — evidence, raw metrics, anomaly detection, confidence scores. Then Outcome Verify applies the deal's criteria to determine whether each measured result counts. Both products reference the same deal specification from Deal Designer. The determination includes reason codes, decision history, and full audit trail." Explore links: Outcome Measure, Outcome Verify.
• 04 — When money needs to move: "Outcome Settle executes the pricing formula against the verified outcome count, applies financial controls (caps, floors, holdbacks, clawbacks, true-ups), generates invoices with line-item detail, and integrates with billing and ERP systems. Every dollar is traceable from the raw measured event through the verification decision to the invoice line item." Explore link: Outcome Settle.

Bottom CTA (bg-brand-green)

"Explore the products" — "Five products covering the full outcome deal lifecycle." Primary: "Model your first deal — free" (links to https://spark-build-wonder.lovable.app). Secondary: "View products" (links to /products).

11. PAGE: SOLUTIONS INDEX (/solutions)

SEO title: "Solutions — Outcome Deals for Every Role | Acretix"

SEO description: "Outcome pricing for vendors, verified delivery for both sides, revenue assurance for finance, human completion for AI products, and vendor verification for buyers."

Page Header

Label: "Solutions". Title: "What customers use Acretix for". Description: "Outcome-based deals across every commercial relationship — vendor, buyer, employer, or regulator."

Seven Solution Cards (3-col grid, first 6; 7th centered in row 2)

• Outcome Pricing (audience: "For vendors selling on results"): "Price on what you deliver. Charge when you've proven it. The full infrastructure from deal design to verified invoice." → /solutions/outcome-pricing
• Verified Delivery (audience: "For firms proving outcomes"): "Both parties see the same independently verified record of what was delivered. No version dispute. No reconciliation." → /solutions/verified-delivery
• Revenue Assurance (audience: "For finance and revenue operations"): "Every dollar traced from verified outcome to invoice line. No manual reconciliation. No revenue leak." → /solutions/revenue-assurance
• Human Completion (audience: "For AI products needing expert judgment"): "Your AI starts the work. A credentialed professional finishes it. Sell a complete solution, not a tool." → /solutions/human-completion
• Vendor Verification (audience: "For procurement teams and buyers"): "Know what you paid for. Verify it was delivered. Pay only for what was independently counted." → /solutions/vendor-verification
• AI ROI Verification (audience: "For AI vendors and their customers"): "Stop claiming ROI. Start proving it — from the buyer's own data, using a methodology both parties agreed to." → /solutions/ai-roi-verification
• Value-Based Compensation (audience: "For executives, teams & users"): "Pay executives, implementation teams, and users based on the value they create — independently measured, transparently calculated." → /solutions/value-based-compensation (centered, col-start-2 on lg)

12. SOLUTIONS SUB-PAGES

12.1 Outcome Pricing (/solutions/outcome-pricing)

SEO title: "Outcome-Based Pricing — Price on What You Deliver | Acretix"

Label: "Solutions". Title: "Outcome-based pricing". Description: "Price on what you deliver. Charge when you've proven it."

Intro title: "The problem with license pricing"

Intro paragraphs: "Software vendors have been selling the same way for decades: charge for access, not results. It worked when software was infrastructure. It breaks down when software is supposed to deliver measurable outcomes." | "Outcome pricing should be the natural model for any product that produces a measurable result. But it requires infrastructure that most vendors don't have: a way to measure independently, verify what counts, handle disputes, and settle automatically." | "That infrastructure is what Acretix provides."

Problem points: (1) Customers resist paying for software they haven't seen deliver value yet. (2) Seat-based pricing commoditizes products and invites competitive displacement. (3) Usage-based billing creates friction without connecting to actual customer outcomes. (4) Every renewal becomes a negotiation because there is no shared record of what happened.

Solution points: "Price on what you deliver, not what you license" — Define the outcome metric that matters: cost reduction, revenue gained, hours saved, errors eliminated. Structure the pricing formula against it. | "An independent measurement layer" — Outcome Measure connects to the buyer's system of record. The count is produced from their own data, not your claim. Both parties see the same number. | "Trusted commercial determination" — Outcome Verify applies the agreed criteria. Count or no-count. Disputes handled with full evidence. Both parties trust the determination because neither controls it. | "Settlement that runs itself" — Outcome Settle executes the pricing formula, generates the invoice, and handles caps, floors, and true-ups. No manual reconciliation. No end-of-quarter surprises.

How it works (4 steps): 01 — "Define the outcome metric and pricing formula" (Deal Designer, both parties agree before go-live). 02 — "Measure from the buyer's system of record" (Outcome Measure from their source of truth, not your platform). 03 — "Verify what counts against the agreed criteria" (Outcome Verify, every result count or no-count with reason). 04 — "Settle automatically" (Outcome Settle executes formula, customer receives settlement statement).

Products used: Deal Designer (define outcome and pricing formula) | Outcome Measure (produce independent measurement) | Outcome Verify (determine what counts commercially) | Outcome Settle (execute pricing and generate invoices).

Bottom CTA: "Ready to price on outcomes?" — "Start with Deal Designer — free, no login required."

12.2 Verified Delivery (/solutions/verified-delivery)

Label: "Solutions". Title: "Verified delivery". Description: "Both parties see the same independently verified record of what was delivered."

Intro title: "The verification problem"

Intro paragraphs: "When a vendor says they delivered outcomes, the buyer has two choices: trust the vendor's report, or run their own parallel measurement. Neither is satisfying." | "Trust without verification creates disputes at renewal. Parallel measurement creates operational overhead and usually produces a different number — leading to exactly the dispute it was meant to prevent." | "The solution is a shared infrastructure that produces an independent measurement both parties trust before the deal even starts."

Problem points: (1) Vendors claim outcomes. Buyers can't verify them independently. (2) Internal reports come from the vendor's system — making it impossible to dispute what you can't measure yourself. (3) Contract language about "delivered outcomes" has no operational definition that both parties can verify. (4) At renewal, the conversation becomes a negotiation instead of a review of facts.

Solution points: "Measurement from the buyer's data" — Outcome Measure connects to the buyer's system of record. Evidence comes from their own data — not the vendor's platform. | "Criteria agreed before the deal starts" — Deal Designer defines exactly what counts as delivered: inclusions, exclusions, baselines, attribution rules. Both parties agree in writing before go-live. | "Count or no-count with full reasoning" — Outcome Verify applies the agreed criteria. Every determination includes the reason code and evidence. Nothing is hidden. | "Audit trail that survives disputes" — Every evidence event, every adjudication decision, every determination stored with full lineage.

How it works (4 steps): 01 — "Define the outcome criteria together" (Deal Designer, both parties agree on metric, inclusions, exclusions, baseline). 02 — "Connect to the buyer's system of record" (Outcome Measure from buyer's own data source). 03 — "Apply the criteria and produce the determination" (Outcome Verify, count or no-count, same for both parties). 04 — "Settle on verified facts" (Outcome Settle, both parties receive same settlement statement).

Products used: Deal Designer | Outcome Measure | Outcome Verify. Bottom CTA: "Start building verified delivery" — "Design the deal in Deal Designer. Both parties agree before go-live."

12.3 Revenue Assurance (/solutions/revenue-assurance)

Label: "Solutions". Title: "Revenue assurance". Description: "Every dollar traced from verified outcome to invoice line. No reconciliation. No revenue leak."

Intro title: "The revenue operations problem"

Intro paragraphs: "Variable revenue models are operationally hard. The contract says one thing. The billing system does another. Finance reconciles the difference manually, every quarter, hoping nothing was missed." | "The deeper problem is that most billing infrastructure was built for fixed or usage-based pricing. Outcome-based pricing — with verified counts, financial controls, and compliance requirements — requires a different foundation." | "Acretix connects the verified outcome to the invoice automatically, with full lineage and without manual reconciliation."

Problem points: (1) Variable revenue models require billing logic that finance teams can't easily audit. (2) Manual invoice reconciliation creates end-of-quarter delays and disputes. (3) Caps, floors, and true-ups are tracked in spreadsheets that don't match the contract. (4) ASC 606 compliance requires linking revenue to verified performance obligations — which most systems can't do.

Solution points: "Revenue rules encoded at deal design" — Deal Designer captures pricing formulas, caps, floors, holdbacks, clawbacks, and true-up schedules at deal structuring. | "Settlement tied to verified outcome counts" — Outcome Settle only runs the formula against verified outcome counts from Outcome Verify. No manual entry. No reconciliation step. | "Financial controls applied automatically" — Caps, floors, holdbacks, and clawbacks enforced programmatically at settlement. Finance doesn't manually apply adjustments. | "Full audit trail for revenue recognition" — Every invoice line traces back to a verified outcome event. Supports ASC 606 and IFRS 15 compliance.

How it works (4 steps): 01 — "Encode the deal economics at design time" (pricing formula, controls, billing cadence — all in Deal Designer). 02 — "Outcome count is verified independently" (Outcome Verify produces definitive count, same for both parties). 03 — "Settlement executes the formula" (Outcome Settle, no manual steps, no spreadsheets). 04 — "Full lineage available for audit" (every invoice line traces to verified outcome event, back to raw evidence).

Products used: Deal Designer | Outcome Verify | Outcome Settle. Bottom CTA: "Close the gap between outcome and invoice" — "Outcome Settle runs the formula. You get the lineage."

12.4 Human Completion (/solutions/human-completion)

Label: "Solutions". Title: "Human completion". Description: "Your AI starts the work. A credentialed professional finishes it."

Intro title: "The 20% problem"

Intro paragraphs: "Most AI products hit a ceiling. The AI handles the bulk of the work reliably — but a percentage of tasks require human judgment. A clause that could be read two ways. A claim with unusual circumstances. A permit that doesn't fit standard categories." | "Without a structured way to handle these cases, the product either fails silently, creates manual work for your team, or gets stuck waiting for the customer to figure it out themselves." | "Completion Hub provides the infrastructure to handle the 20% — without building an operations team."

Problem points: (1) AI handles 80% of the work — but the 20% requiring judgment breaks the product promise. (2) Manual handoffs to internal reviewers create delays, inconsistency, and audit gaps. (3) Hiring credentialed professionals (attorneys, CPAs, engineers) for edge cases is expensive and slow. (4) Without sign-off capture, you can't prove the human step happened for compliance or billing.

Solution points: "Your AI handles the volume" — Completion Hub only activates for tasks requiring human judgment. | "Credentialed experts handle the edge cases" — Domain-matched professionals: licensed attorneys, CPAs, certified engineers. No hiring, no onboarding. | "Sign-off capture and audit trail" — Every completion captured with credential verification and timestamp, flows into Outcome Measure as evidence. | "Sell a complete solution, not a tool" — Contractually commit to completing the work with an SLA, not just assisting.

How it works (4 steps): 01 — "Define which tasks require human completion" (Deal Designer: trigger, credential required, quality standard, turnaround time). 02 — "Integrate via a single API endpoint" (platform receives task automatically when AI reaches judgment step). 03 — "Expert reviews and signs off" (credentialed professional from appropriate pool; customer never sees the handoff). 04 — "Completion is captured and ingested" (result returns to product; ingested by Outcome Measure as evidence event; deal counts it; you bill for it).

Products used: Completion Hub | Deal Designer | Outcome Measure | Outcome Verify. Bottom CTA: "Tell us about your workflow" — "We'll help you identify where human judgment is needed and how to structure it."

12.5 Vendor Verification (/solutions/vendor-verification)

Label: "Solutions". Title: "Vendor verification". Description: "Know what you paid for. Verify it was delivered. Pay only for what counts."

Intro title: "The buyer's dilemma"

Intro paragraphs: "When you buy software or AI services on outcome terms, the vendor controls the measurement infrastructure. They define the metrics, run the reports, and tell you what was delivered." | "Even when vendors act in good faith, there is an inherent conflict of interest in any vendor-controlled measurement. The buyer cannot independently verify without running parallel measurement — which costs time, creates its own discrepancies, and still doesn't produce a shared authoritative record." | "Acretix provides a neutral infrastructure layer that neither party controls — producing the shared record that makes outcome deals work for buyers, not just vendors."

Problem points: (1) Buyers pay upfront or on milestones — without any mechanism to verify the vendor delivered. (2) Vendor-provided reports use vendor-defined metrics from vendor-controlled systems. (3) Disputes are slow, adversarial, and lack shared evidentiary standards. (4) Outcome commitments in contracts have no operational enforcement mechanism.

Solution points: "Measurement from your own data" — Outcome Measure connects to your system of record. Vendor cannot influence the measurement. | "Criteria you jointly agreed" — Both parties agree in Deal Designer on exactly what counts as delivered before the deal starts. | "Structured dispute resolution" — Outcome Verify provides a formal process: counter-evidence, adjudication, appeal. Every step documented. | "Financial terms that reflect delivery" — Outcome Settle executes against the verified count. Caps, floors, and clawbacks protect against overstatement.

How it works (4 steps): 01 — "Co-define the outcome criteria" (Deal Designer, before contract signed). 02 — "Measurement runs from your data" (Outcome Measure from buyer's system of record; vendor receives same count). 03 — "Verify what counts against the agreed rules" (Outcome Verify, defined process to challenge). 04 — "Payment follows verified delivery" (Outcome Settle, settlement statement with full lineage).

Products used: Deal Designer | Outcome Measure | Outcome Verify | Outcome Settle. Bottom CTA: "Require independent verification in your next deal" — "Ask your vendor to structure the deal on Acretix."

12.6 AI ROI Verification (/solutions/ai-roi-verification)

Label: "Solutions". Title: "AI ROI verification". Description: "Stop claiming ROI. Start proving it — from the buyer's own data."

Intro title: "The ROI credibility problem"

Intro paragraphs: "Every AI vendor produces an ROI study. They use their own models, their own assumptions, and their own data. Buyers know this — and discount it accordingly. The ROI claim has become table stakes that no one believes." | "The problem isn't that vendors overstate value. It's that there is no shared methodology for measuring it. Without a jointly agreed measurement framework, any ROI figure is just a number one party produced and the other party questions." | "Acretix provides the infrastructure to produce a verified ROI figure that neither party can dispute — because both parties agreed on the methodology before the deal started."

Problem points: (1) AI vendors claim ROI figures derived from their own models and assumptions. (2) Buyers have no way to independently verify whether the AI actually delivered the claimed value. (3) ROI studies use pre/post comparisons with no controls for confounding factors. (4) At renewal, the vendor presents a case for value — the buyer has no independent evidence to compare against.

Solution points: "Define the ROI metric before the deal starts" — Deal Designer captures the exact metric: hours saved, errors reduced, revenue attributable, cost avoided. Both parties agree on the definition before go-live. | "Measure from the buyer's system of record" — Outcome Measure connects to the buyer's operational data — not the vendor's analytics layer. Baseline and post-implementation from the same source, independently. | "Verify the attribution" — Outcome Verify applies the attribution rules agreed at deal design. Separates what the AI contributed from what would have happened anyway. Auditable and jointly trusted. | "A shared ROI record both parties can use" — Vendor uses it as case study. Buyer uses it for internal reporting. Neither party needs to argue about the number.

How it works (4 steps): 01 — "Define the ROI metric and attribution model" (Deal Designer, before implementation begins). 02 — "Establish the baseline from the buyer's data" (Outcome Measure captures pre-implementation baseline). 03 — "Measure the post-implementation outcomes" (same source, same methodology; delta calculated independently). 04 — "Verify the attributed ROI" (Outcome Verify applies attribution rules; verified ROI figure with full audit trail, jointly trusted).

Products used: Deal Designer | Outcome Measure | Outcome Verify. Bottom CTA: "Turn your ROI claim into a verified fact" — "Agree on the methodology before the deal. Let the data do the rest."

12.7 Value-Based Compensation (/solutions/value-based-compensation)

Label: "Solutions". Title: "Value-based compensation". Description: "Pay the people who make value happen — executives, implementation teams, and users — based on what was independently verified, not who made the assessment."

Audiences section: "Who this is for" — "Three groups who create value. One infrastructure to pay them for it." Three audience cards: Executives (paid for the value they sponsor — tied to verified outcomes of initiatives, not tenure or subjective assessments) | Implementation Teams (paid for the value they make happen — consultants, engineers, project leads compensated based on independently verified outcomes) | Users (paid for the value they drive — end users who adopt tools and drive measurable improvements earn a stake).

Intro title: "The value creation credibility problem"

Intro paragraphs: "Executives who drive transformative initiatives rarely share in the value those initiatives create. Implementation teams are paid for delivery, not results. Users who adopt and champion new tools — generating real, measurable improvements — receive nothing for it." | "The missing piece is not motivation. It's measurement. Without an independent layer that can verify what was created, by whom, and when, every compensation claim becomes a negotiation — and the people closest to the value creation have the least leverage." | "Acretix provides the infrastructure to define, measure, verify, and settle value-based compensation across all three tiers — with a shared evidentiary record that all parties trust."

Problem points: (1) Compensation tied to "performance" relies on internally-produced metrics that no one trusts. (2) Executives sponsor initiatives without clear paths to personal value capture when they succeed. (3) Implementation teams are paid for delivery, not for the value that delivery creates. (4) Users who drive adoption and generate measurable outcomes are not rewarded for it. (5) Disputes about whether a target was hit become HR and legal problems without a shared evidentiary record.

Solution points: "Criteria defined before the period begins" — Deal Designer captures outcome metric, measurement methodology, attribution rules, and compensation formula before work starts. For executives, teams, and users alike. | "Independent measurement from operational data" — Outcome Measure connects to relevant systems. Measurement is independent of the people who decide compensation — making the number trustworthy for all parties. | "Transparent calculation for every tier" — Outcome Settle applies the compensation formula to the verified outcome count. Every tier sees exactly what was measured, what counted, and how payment was calculated. | "Audit trail that holds up" — Every measurement, determination, and compensation calculation stored with full lineage. Disputes have a factual record.

How it works (4 steps): 01 — "Define who gets paid for what" (Deal Designer: value metric, measurement approach, attribution logic, compensation formula for each tier). 02 — "Measure the value created" (Outcome Measure from operational data — same systems used for running the business). 03 — "Verify what counts for each tier" (Outcome Verify, count/no-count with full reasoning for each recipient group). 04 — "Calculate and distribute" (Outcome Settle applies compensation formula, produces compensation statements for all tiers; transparent lineage).

Products used: Deal Designer | Outcome Measure | Outcome Verify | Outcome Settle. Bottom CTA: "Give value creators a stake in what they build" — "Define the criteria. Measure independently. Pay everyone who made it happen."

13. PAGE: TRUST (/trust)

SEO title: "Trust & Verification — How Acretix Stays Independent"

SEO description: "Structural independence in outcome deals: flat fees never tied to settlement amounts, buyer-system data, jointly agreed criteria, and an independent CPA backstop at Level 3."

Page Header

Label: "Trust & Verification". Title: "The Resolution Ladder". Description: "Three levels of resolution. Deployed only when needed. Both parties see the same numbers. When trust breaks down, the ladder restores it."

Intro

"Most outcome deals never need manual intervention. The platform produces the determination, both parties see the same audit trail, and settlement runs automatically. The Resolution Ladder exists for the cases where questions arise — and it is structured to resolve them efficiently, with escalation available but not required."

Resolution Ladder (three cards with top green border)

• Level 1 — Platform Resolution (timeline: "Minutes"): "The Outcome Verify rules engine continuously classifies every event with full audit trail. When a question arises, either party can request a re-run: the platform applies the agreed criteria to the specific event, explains exactly why it was classified the way it was, and cites the specific rule provisions and evidence records. Handles individual flags, batch-level concerns, and data discrepancy questions. Resolves the majority of disputes without human intervention."
• Level 2 — Analyst Resolution (timeline: "3–5 business days"): "If the platform explanation is not sufficient, either party can escalate to Analyst Resolution. An Acretix analyst independently reclassifies the disputed events, examines data lineage, checks for systemic issues in the measurement pipeline, and produces a written findings memo shared with both parties. The analyst has access to the raw evidence, transformation logs, and decision history."
• Level 3 — Independent CPA Verification (timeline: "2–3 weeks"): "If either party is not satisfied with the analyst's findings, an independent CPA from Acretix's certified network performs agreed-upon procedures or SSAE 18 attestation on the disputed determinations. The CPA's findings on factual matters are binding — they represent the final word on what happened and whether it counted. Auto-triggered for deals above $500K in aggregate value or where enterprise procurement requires independent attestation."

Why This Structure Works

"Verification cost scales with disagreement, not deal size. Most questions are resolved at Level 1 in minutes — no human involvement, no cost. The CPA backstop keeps everyone honest at the lower levels: neither party has an incentive to be unreasonable when an independent professional is one request away. Mid-market deals that cannot justify quarterly CPA audits are now viable on outcome terms, because the backstop only costs money if someone chooses to escalate."

14. PAGE: PRICING (/pricing)

SEO title: "Pricing — Deal Designer Free, Core Platform from $24K/yr | Acretix"

SEO description: "Deal Designer is free. Core Platform starts at $24K/year. Premium with Outcome Settle starts at $60K/year. Flat fees, never tied to settlement amounts."

Page Header

Label: "Pricing". Title: "Start free. Scale when you're ready." Description: "Deal Designer is free. Add measurement, verification, and settlement as your outcome deals go live."

Pricing Tiers (3-col grid)

Deal Designer — Free (badge: "Free", featured with green border + green top bar)

Price: $0 forever. Subtitle: "Design and model outcome-based deals". Features:

• Outcome definition builder
• Pricing and economics modeling
• Baseline and exclusion design
• Scenario analysis (upside, downside, breakeven)
• Contract-ready rules summary (PDF / link)
• Deal spec publishing to platform

CTA: "Start today" (btn-primary green, navigates to /contact).

Core Platform (badge: "Core Platform")

Price: "Contact sales". Note: "Outcome Measure + Outcome Verify". Subtitle: "Trusted measurement and commercial verification". Features:

• Data connectors and evidence ingestion
• Real-time measured outcome records
• Count / no-count rules engine
• Dispute intake and Resolution Ladder
• Full audit trail with decision history
• Manual adjudication quota included
• Per-event fee above included quota

CTA: "Talk to sales" (btn-secondary, navigates to /contact).

Premium (badge: "Premium")

Price: "Contact sales". Note: "Adds Outcome Settle". Subtitle: "Financial settlement and billing integration". Features:

• Everything in Core Platform
• Pricing formula execution
• Invoice and payout generation
• Caps, floors, holdbacks, clawbacks, true-ups
• Billing / ERP integration (Stripe, NetSuite, SAP)
• Settlement statements with full financial lineage
• ASC 606 variable consideration support

CTA: "Talk to sales" (btn-secondary, navigates to /contact).

Completion Hub — Add-on (card below main tiers, full width)

Badge: "Add-on". Subtitle: "Human judgment for edge cases". Two modes side by side:

• Workflow (software module): Routing, approval queues, SLAs | Exception handling, escalation | Sign-off capture. Price: "Contact sales".
• Managed (service): Credentialed experts provided by Acretix | Domain-matched professionals | SLA-backed review. Price: "Per task".

CTA: "Tell us about your workflow" (btn-secondary, navigates to /contact).

Services Section

Title: "Services to get you live and keep you running". Four service cards:

• Launch Studio: "Get live on your first deal. Includes first-deal design, connector setup, measurement configuration, rules definition, workflow design, and pilot launch. Most customers are live within four to six weeks."
• Outcome Ops: "Ongoing operational support. Adjudication support for complex edge cases, dispute operations management, escalation handling, and periodic outcome reporting for both parties."
• Expert Coverage: "Managed expert capacity through Completion Hub. Credentialed domain experts — attorneys, CPAs, licensed engineers — provided by Acretix. No hiring, no training. SLA-backed review for your AI workflows."
• Finance & Governance: "Enterprise-grade financial infrastructure. Settlement policy design, dispute governance framework, audit trail design, ASC 606 revenue recognition support, and enterprise procurement integration."

15. PAGE: FAQ (/faq)

SEO title: "FAQ — Common Questions About Acretix and Outcome Deals"

SEO description: "Answers to common questions: what Acretix does, who it's for, how it differs from billing platforms, pricing, implementation timeline, and the Resolution Ladder."

JSON-LD: FAQPage schema with all 12 Q&A pairs.

Page Header

Label: "FAQ". Title: "Common questions". Description: "Everything you need to know about Acretix and outcome-based agreements."

Accordion layout (ChevronDown icon, max-w-[680px]). Each item: question (text-[16px] font-medium, hover green) + answer (text-[15px] text-text-secondary, max-h-[500px] animated open/close).

FAQ Items (12 questions)

1. What is Acretix? — "A commercial control layer for outcome-based deals. Five products cover the full lifecycle: Deal Designer structures the deal before it is signed. Outcome Measure produces the factual record of what happened. Outcome Verify determines what counts commercially. Outcome Settle turns verified outcomes into invoices and financial records. Completion Hub provides human judgment and expert completion when AI cannot finish alone. The products share a single data model — the outcome deal object — so every determination is traceable from raw evidence through verification to the invoice."
2. Who is Acretix for? — "Any company where payment depends on results. Software vendors selling on outcomes rather than seats. AI companies needing human completion for edge cases. Consulting firms proving engagement value. Procurement teams evaluating vendor performance. Consumer-facing companies guaranteeing results. If your deal has a variable component tied to a measurable result, Acretix makes it executable."
3. How is Acretix different from a billing platform? — "A billing platform processes invoices. Acretix determines what belongs on the invoice. Before you can bill for an outcome, someone has to define the outcome, measure whether it happened, verify that it counts under the deal terms, and handle disputes when the parties disagree. That is the work Acretix does. The settlement output feeds into your existing billing and ERP systems."
4. Do I need all five products? — "No. Most customers start with Deal Designer (free) to structure and model deals, then add Outcome Measure and Outcome Verify when they go live. Outcome Settle is added when you need automated financial settlement and billing integration. Completion Hub is relevant only when your AI workflow requires human judgment at certain steps — not every deal needs it. Start where you are. The products are modular and integrate through a shared data model."
5. What does it cost? — "Deal Designer is free — design and model your first outcome deal without a credit card or sales call. The Core Platform (Outcome Measure + Outcome Verify) starts at $24K/year. Premium (adds Outcome Settle) starts at $60K/year. Completion Hub is an add-on priced per workflow (software) or per task (managed experts). Fees are flat and never tied to settlement amounts."
6. How long does implementation take? — "Most customers are live on their first deal within four to six weeks of signing. Launch Studio handles the implementation: deal design finalization, connector setup, measurement configuration, rules definition, workflow design, and pilot launch. You do not need a dedicated integration team — we handle the technical work."
7. What is the Resolution Ladder? — "A three-level dispute resolution system built into Outcome Verify. Level 1 is Platform Resolution — the rules engine re-runs the determination with full evidence, resolving most questions in minutes. Level 2 is Analyst Resolution — an Acretix analyst independently reviews disputed events and produces a findings memo (3-5 business days). Level 3 is Independent CPA Verification — an independent CPA performs agreed-upon procedures with binding findings on factual matters (2-3 weeks). Most disputes resolve at Level 1."
8. How is Acretix independent? — "Independence is structural, not just a claim. Four things make it real: (1) The fee is flat — never tied to the settlement number, so we have no incentive to inflate or deflate counts. (2) The data comes from the buyer's system of record, not the vendor's platform. (3) The outcome criteria are jointly agreed by both parties in Deal Designer before measurement begins. (4) Level 3 of the Resolution Ladder engages an independent CPA firm, not Acretix analysts — the final backstop is outside our organization."
9. What systems does Acretix integrate with? — "Pre-built connectors for Zendesk, Salesforce, ServiceNow, AWS Cost Explorer, NetSuite, Jira, and HubSpot. Support for API-based, event-stream, file-upload, and manual evidence submission. Outcome Settle integrates with Stripe, NetSuite, and SAP for billing and ERP. All connections are read-only — Acretix never writes to the buyer's production systems."
10. What is the difference between Completion Hub and Outcome Verify? — "Different products for different problems. Completion Hub handles human work during execution — routing tasks to reviewers, managing approval queues, providing credentialed experts. Outcome Verify handles commercial determination after execution — deciding whether a measured result counts under the deal terms. Completion Hub produces evidence. Outcome Verify consumes evidence. One is about getting the work done. The other is about deciding whether the work counts."
11. How is Acretix different from Paid.ai or other outcome billing tools? — "Most outcome billing tools start at the invoice. Acretix starts at the deal. Deal Designer structures the outcome definition, measurement methodology, and pricing formula before any measurement begins. This means the measurement criteria, verification rules, and financial controls are all defined in advance and flow downstream automatically. The difference is between billing for outcomes and making outcomes executable end-to-end."
12. How do we get started? — "Design your first deal for free in Deal Designer — no credit card, no sales call required. Model the economics, define the outcome criteria, and see what a contract-ready specification looks like. When you are ready to go live, Launch Studio handles implementation: connector setup, rules configuration, workflow design, and pilot launch."

16. PAGE: CONTACT (/contact)

SEO title: "Contact Acretix — Schedule a Demo or Get in Touch"

SEO description: "Schedule a demo, ask a question, or start a conversation about outcome-based deals. Reach the Acretix team directly."

Page Header

Label: "Contact". Title: "Talk to us". Description: "Exploring outcome-based pricing or ready to start? Tell us about your deal."

Contact Form (max-w-[480px], centered)

Fields (all required): Name (text input, placeholder "Name") | Email (email input, placeholder "Email") | Company (text input, placeholder "Company") | "Tell us about your deal" (textarea, 4 rows, placeholder "Describe your outcome-based deal..."). Submit button: "Send message" with Send icon (btn-primary full-width), disabled during loading with text "Sending…".

Error state: red text "Something went wrong. Please try again." Success state: centered, Send icon in bg-brand-green-light circle, h3 "Message sent", p "We'll be in touch within one business day."

Form submissions saved to Supabase via submitContactForm({name, email, company, message}). Function in src/lib/supabase.ts.

17. PAGE: MARKETPLACE (/marketplace)

Component: MarketplacePage (acretix-site.jsx). Branding: "OUTCOMEVERIFY" — Outcome-based pricing directory. 100+ vendors who tie revenue to measurable customer outcomes.

Functionality

• Full-text search across vendor name, category, pricing, trigger text
• Filter tabs by outcome category (All + per category)
• Expand/collapse vendor cards showing base cost and description

Outcome Categories (sample)

Customer problem resolved, Money saved, Pipeline generated, Sale or conversion, Position filled, Vulnerability found, Revenue collected, Clinical encounter documented, Claim processed, Miles driven, Deal closed, Graduate employed, Invoice processed.

Notable Vendors

• Intercom Fin — $0.99/resolution, 67% avg resolution rate, 50% minimum guaranteed
• Zendesk AI Agents — $1.50 committed / $2.00 PAYG per resolution
• ProsperOps — % of savings, no base fee, only paid when you save
• App Academy — 15% of income x 36 months (ISA), cap $31K
• HackerOne — $2K–$10K per critical vulnerability
• Athenahealth — 4–7% of collections

18. PAGE: SERVICES (/services)

SEO title: "Services — Launch Studio and Ongoing Support | Acretix"

SEO description: "Acretix implementation services: Launch Studio gets you live on your first outcome deal in 4-6 weeks. Ongoing support, analyst services, and enterprise professional services."

Page Header

Label: "Services". Title: "Get live and stay running". Description: "Software gets you the platform. Services get you live, keep you running, and provide expert capacity when you need it."

Service Lines Section

Badge: "Service lines". Title: "Four services, each tied to a product need". 2-col grid.

• Launch Studio (Rocket icon, pricing: "Fixed fee"): "Get live on your first deal. Includes first-deal design assistance, connector setup, measurement configuration, rules definition, workflow design, and pilot launch." Deliverables: Deal design finalization with both parties | Data connector setup and validation | Measurement configuration and baseline calibration | Rules engine configuration and testing | Workflow design (if Completion Hub is used) | Pilot launch and monitoring. Timeline: "Most customers are live within four to six weeks of signing."
• Outcome Ops (Headphones icon, pricing: "Monthly retainer"): "Ongoing operational support for live deals. Adjudication support for complex edge cases, dispute operations management, escalation handling, and periodic outcome reporting for both parties." Deliverables: Adjudication support for complex determinations | Dispute operations and escalation management | Periodic outcome reporting for vendor and buyer | Measurement pipeline monitoring | Rules refinement based on operational patterns | Quarterly business reviews. Timeline: "Continuous engagement from deal go-live."
• Expert Coverage (Users icon, pricing: "Per task"): "Managed expert capacity through Completion Hub. Credentialed domain experts provided by Acretix. No hiring, no training, no HR overhead. SLA-backed review for your AI workflows." Deliverables: Credentialed professionals matched to your domain | Attorneys, CPAs, licensed engineers, and specialists | SLA-backed turnaround times | Quality assurance and credential verification | Completion records for audit and billing | Scalable capacity without fixed headcount. Timeline: "Available within defined SLA windows from integration."
• Finance & Governance (Shield icon, pricing: "Contact sales"): "Enterprise-grade financial infrastructure for complex outcome-based deals. Settlement policy design, dispute governance framework, and compliance support." Deliverables: Settlement policy design and documentation | Dispute governance framework | Audit trail design and compliance review | ASC 606 revenue recognition support | Enterprise procurement integration | Financial controls configuration. Timeline: "Scoped per engagement."

Product-to-Service Mapping

Badge: "Product-to-service mapping". Title: "Every product has a corresponding service". Subtitle: "The software gives you the capability. The service helps you operate it."

• Deal Designer → Launch Studio: "First-deal design, template customization, scenario modeling review"
• Completion Hub → Expert Coverage: "Credentialed professionals, SLA management, quality assurance"
• Outcome Measure → Outcome Ops: "Connector monitoring, data quality review, pipeline support"
• Outcome Verify → Outcome Ops: "Adjudication support, dispute operations, Resolution Ladder management"
• Outcome Settle → Finance & Governance: "Settlement policy, financial controls, audit trail design"

Bottom CTA (bg-brand-green)

"Ready to get started?" — "Design your first deal for free, or talk to our team about implementation." Primary: "Design your deal — free" (links to spark-build-wonder.lovable.app). Secondary: "Talk to our team" (links to /contact).

19. PAGE: OUTCOME ASSESSMENT (/outcome-assessment)

SEO title: "Free Outcome Assessment — Is Your Deal Ready for Outcome Pricing?"

SEO description: "Answer 8 questions to find out if your deal structure is ready for outcome-based pricing. Get a personalized assessment with specific next steps from the Acretix team."

Hero Section (bg-page-surface, pt-[100px] pb-16)

Badge: "Free assessment". Headline: "See how your product could be priced on outcomes." (clamp 32px-52px, -0.04em tracking). Description: "Enter your website URL. Our team will send you a custom report on the outcome-pricing models that might fit your product — and what it would take to operationalize them."

Form (left column, 1fr in lg:grid-cols-[1fr_380px])

Required fields: Website URL (url input, placeholder "yourcompany.com") | Work email (email input) | Your name (text input) | Your role (select dropdown).

Role options: CEO/Founder | VP Sales/CRO | VP Product/CTO | Head of Pricing | CFO/Finance | Other.

Optional fields: "What outcomes do you think your product delivers?" (textarea, 3 rows, placeholder "Optional — tell us in your own words...") | "Anything else we should know?" (textarea, 3 rows).

Submit button: "Send me my assessment" (bg-brand-green, self-start). Footer note: "No credit card. No sales call required. No automated follow-up sequence."

On submit: calls submitOutcomeAssessment() with form data + referring_page, utm_source, utm_medium, utm_campaign. On success: navigates to /outcome-assessment/thank-you. On error: shows "Something went wrong. Please try again." in red.

Analytics: window.acretix.track('assessment_page_view') on mount; window.acretix.track('assessment_submitted') on success.

FAQ (below form, mt-14)

Title: "Questions". Accordion (ChevronDown/ChevronUp icons). 5 items:

1. How long does it take? — "3–5 business days for the initial assessment."
2. Is this really free? — "Yes. No cost, no catch, no required follow-up."
3. Why do you need my email? — "We send the report by email. We don't use it for anything else unless you ask us to."
4. What if my product doesn't fit outcome pricing? — "We'll tell you. An honest 'this doesn't fit' is more useful than a forced recommendation."
5. Will you sell me something? — "Only if you ask. The assessment is the end of the interaction unless you want more."

Sidebar (380px right column)

Three white cards:

• "What you'll get" — "A 2–4 page custom assessment delivered by email within 3–5 business days. Includes:" (1) Outcome-pricing models that might fit your product (2) Specific outcome metrics you could price on (3) Baseline methodology suggestions (4) Honest assessment of what it would take to operationalize.
• "Who reviews your submission" — "The assessment is written by the Acretix team, not generated by an automated system. Every assessment is custom. We read your website, your pricing page, your product documentation, and we write specifically for your situation."
• "What happens after" — "If the assessment is useful and you want to explore further, we'll offer a 30-minute conversation. No pressure, no follow-up sales sequence. If the assessment isn't useful, tell us and we'll improve the process."

Footer note: "We use your email only to send your assessment. We don't share your URL or email with anyone. Privacy policy."

Data Persistence

Submissions saved to Supabase outcome_assessments table via submitOutcomeAssessment() in src/lib/supabase.ts. Fields saved: website_url, email, name, role, outcomes_description, additional_context, referring_page, utm_source, utm_medium, utm_campaign. Thank-you page at /outcome-assessment/thank-you.

20. RESOURCES SECTION

20.1 Resources Index (/resources)

Hub page linking to Blog, Guides, Tools, Events, Benchmarks, Newsletter.

20.2 Blog (/resources/blog)

SEO title: "Blog — Field Notes on Outcome-Based Deals | Acretix". PageHeader label: "Resources". PageHeader title: "The Acretix Blog". PageHeader description: "Field notes on outcome-based deals, AI monetization, and the commercial infrastructure of trust."

Blog index lists 5 posts as cards with category tag, title, author, date, read time, excerpt, and link. Featured first post shown as large card; remaining 4 in a 3-column grid. Category filter tabs: All | Outcome Pricing | AI Monetization | Revenue Recognition | Trust & Verification | Case Studies.

Blog Post 1: The Outcome Pricing Transition: A Field Guide for AI Companies

Route: /resources/blog/outcome-pricing-transition-field-guide | Category: Outcome Pricing | Author: Acretix Team | Date: April 14, 2026 | Read time: 12 min read

SEO description: "How AI companies can shift from seat-based pricing to outcome-based models — deal design, measurement, dispute resolution, and what goes wrong in the transition."

Zendesk, Intercom, Sierra, and others have publicly committed to outcome-based pricing in the past year. Gartner forecasts that by 2027, a majority of enterprise AI agreements will include outcome components. But the companies making the move are struggling to operationalize it. This post is for the VP Sales, CRO, or Head of Pricing who has been asked to make the shift and doesn't know where to start.

Why outcome pricing stalls: Outcome pricing fails in specific, predictable places. The deal is not structured precisely enough — outcome definitions are vague, measurement methodology is unspecified, exclusions and edge cases are left to future negotiation. The data is messy or disputed. The workflow still needs human judgment the vendor doesn't control. Finance cannot turn approved outcomes into invoices and records. Each of these is solvable — but only if you name it explicitly and design for it. Most companies trying to shift to outcome pricing fail because they treat the pricing change as a sales and marketing problem. It's an operational problem. And it requires operational infrastructure.

The four-phase structure: Every durable outcome-based deal has four phases: structuring (before signing), execution (during the engagement), verification (after outcomes are claimed), and settlement (when money moves). Most companies collapse these phases mentally, which is why their deals break. Treating them as distinct — with distinct tooling, distinct ownership, and distinct checkpoints — is the first operational insight that separates companies that make outcome pricing work from companies that can't get past the pilot stage.

The measurement question: Who measures the outcome? If the vendor measures, they have an incentive to count high. If the buyer measures, they have an incentive to count low. If either party operates the measurement system, the other party cannot fully trust the output. The resolution is independent third-party measurement — the model DoubleVerify pioneered for digital advertising and which now applies to outcome-based software deals. Neither party controls the measurement. Both parties see the same number. That number becomes the basis for payment.

Structuring the deal: The first document you need is a signed deal specification. Not a term sheet. A structured document that defines the outcome being sold, the measurement methodology, the baselines, the exclusions, the fallback pricing, the evidence requirements, and the dispute resolution process. This becomes the operating rules for everything downstream. The deal specification is not a legal document. It's an operational document that happens to be signed. Its purpose is to give both parties a shared reference point when anything is ambiguous — which will happen.

Common mistakes in the first deal:

• Baselines defined after the deal is live. Too late. The baseline must be established from the buyer's data before the engagement begins, or the "improvement" you're claiming has no reference point.
• Outcome definitions that rely on the vendor's internal dashboards. Not independent. The measurement must come from the buyer's system of record, not the vendor's reporting layer.
• Pricing formulas that don't account for reversal windows. Creates unlimited exposure. Define the window during which outcomes can be reversed or clawed back.
• No agreed dispute resolution path. Every disagreement escalates to legal. A defined escalation path — counter-evidence submission, adjudication, appeal — prevents escalation by giving both parties a process to follow.

What to ship first: Most companies try to transition their entire book to outcomes in one move. Wrong approach. Pick one deal — ideally a lighthouse customer who already wants outcome pricing — and use it to build your infrastructure. The first deal is your pilot, not your growth engine. The first deal will be harder than it needs to be. That's expected. The second deal will be easier because you'll have a specification template, a baseline methodology, and measurement infrastructure that's already proven. By the fifth deal, the infrastructure is compounding.

Outcome pricing is becoming table stakes: Companies that build the infrastructure — measurement, verification, settlement — before they need it will outcompete companies that don't. The window to be ahead of this shift is closing.

Bottom CTAs: "Outcome Pricing solution" → /solutions/outcome-pricing | "The 30-Day Playbook" → /resources/blog/first-outcome-deal-30-day-playbook

Blog Post 2: Why Your AI ROI Isn't Credible (and What to Do About It)

Route: /resources/blog/why-your-ai-roi-isnt-credible | Category: AI Monetization | Author: Acretix Team | Date: April 7, 2026 | Read time: 8 min read

SEO description: "AI ROI claims based on vendor-reported figures lack credibility. Here's why independent measurement from buyer systems is the only defensible standard — and how to get there."

Your company is spending heavily on AI. The board wants to know what you're getting for it. You have dashboards your own team built, metrics your own team chose, and methodology your own team invented. The whole apparatus is, by construction, not independent. Every executive running an internal AI initiative faces the same problem: how to prove ROI credibly to a skeptical CEO, CFO, or board. Internal dashboards are self-reported by definition. Consulting studies cost $200K and take six months. Analytics vendors sell better dashboards, not better independence. The credibility gap is structural.

The five failure modes of internal AI measurement:

• The team that built the AI also measures its impact. Structural conflict of interest, regardless of intent.
• The baseline is not independently established. Without a credible baseline, any improvement claim is unfalsifiable.
• Attribution is unclear. Did the AI cause the outcome, or did other factors? Most internal reports don't answer this.
• The sample is cherry-picked or the time window is too short. A 30-day test window almost always looks better than the 12-month reality.
• The methodology is opaque or undocumented. If you can't show your work, your audience can't trust it.

Each of these is survivable individually. Combined, they make the ROI story impossible to defend under scrutiny.

What credible measurement actually looks like: Methodology documented before measurement begins. Evidence drawn from company systems of record with an audit trail. Baselines established independently of the team running the initiative. Attribution analysis that honestly acknowledges confounds. Findings presented with full evidentiary backing, not just summary statistics. This is not a higher bar than most companies can clear. It's a different kind of work than most companies do. The difference is structuring the measurement as if you expected it to be audited — because, increasingly, it will be.

The personal stakes: Acknowledge the uncomfortable truth: executives championing AI initiatives have career stakes in the outcome. Bonuses, promotions, budgets, and political capital all depend on the ROI story being credible. That's not a reason to skip verification — it's a reason to do it right. Executives who proactively submit their AI initiatives to independent verification end up in stronger positions, not weaker ones. They're the ones whose ROI stories survive board-level scrutiny. They're the ones who get more budget, not less.

How independent verification changes the conversation: When the ROI report comes from an independent party applying documented methodology to evidence from company systems, the conversation with the board shifts. The executive is no longer asking the board to trust a dashboard. They're showing the board a verified record the board can inspect, challenge, or share with auditors. That shift — from "trust me" to "here's the record" — is worth more than any specific ROI number. It's the difference between an initiative that gets cut in the next cost review and one that gets expanded.

The solution isn't better dashboards: The AI ROI credibility problem isn't solved by building better dashboards. Better dashboards are still self-reported. The problem is solved by structural independence: an entity with no financial stake in the outcome, measuring from your systems of record, applying methodology both parties agreed to before the measurement began.

Bottom CTAs: "AI ROI Verification solution" → /solutions/ai-roi-verification | "Get a free assessment" → /outcome-assessment

Blog Post 3: ASC 606 and Variable Consideration: A Field Guide for AI Companies

Route: /resources/blog/asc-606-variable-consideration-field-guide | Category: Revenue Recognition | Author: Acretix Team | Date: March 31, 2026 | Read time: 10 min read

SEO description: "How ASC 606 constrains revenue recognition for outcome-based contracts and what AI companies need to do — deal design, measurement documentation, and audit trail requirements."

Variable consideration under ASC 606 is not optional math. If your AI or software company is selling on outcomes, your finance team owns a set of disclosures and estimates that your auditor will probe. Most AI and software companies selling on outcomes are handling this in spreadsheets. That's fine until the audit cycle, at which point it becomes an urgent problem.

What counts as variable consideration: Any portion of a transaction price that depends on future events. Performance bonuses. Shared savings. Penalties. Discounts tied to usage. Outcome-based fees. Clawbacks and reversals. If your contract has any of these, you have variable consideration, and ASC 606 has a prescribed approach to recognizing it. The prescribed approach is not optional. Your auditor will ask whether you've applied it. The answer cannot be "we recognize revenue when we think we've earned it."

The two estimation methods: ASC 606 requires one of two approaches: the expected value method (probability-weighted average of possible outcomes) or the most likely amount method (the single most likely outcome). Choose based on which better predicts the consideration you'll be entitled to. Both require documentation. Choose the wrong method — or switch methods without documentation — and you'll get an audit comment. Choose the right method but document it poorly and you'll get an audit comment. The documentation is not an afterthought.

The constraint: Even after estimating variable consideration, ASC 606 requires you to constrain the estimate — recognize only the amount that's probable will not result in a significant reversal. This is where most companies get into trouble. They estimate aggressively, fail to apply the constraint, and face audit adjustments. The constraint requires judgment. Your auditor will probe that judgment. The defense is documented: what factors did you consider, what comparable transactions did you look at, and why did you conclude this amount meets the "probable no significant reversal" standard?

Period-end adjustments: Variable consideration estimates must be updated at each reporting period as circumstances change. This is not a one-time exercise. Your finance team needs a recurring process for reviewing estimates, documenting changes, and producing the audit trail. If your outcome-based revenue is material and you don't have a period-end review process, you have an audit finding waiting to happen.

The evidence trail: Your auditor will ask how you know the estimate is reasonable. The answer cannot be "our sales team believes so." It needs to be documented evidence — historical performance data, contractual terms, market benchmarks, or independent verification. Independent verification — outcome counts from a third party with no financial stake in the number — is the strongest possible evidence for a variable consideration estimate. It's also the evidence that takes the auditor's judgment about your judgment out of the picture.

What good looks like: A finance team with an ASC 606 methodology memo. Sample workpapers showing estimation and constraint analysis. Period-end review documentation. Integration between the outcome measurement system and the revenue recognition system. An audit trail that connects every dollar of recognized variable consideration back to specific verified outcomes. This is achievable. It requires treating outcome measurement as a finance function, not just a sales function.

Bottom CTAs: "Revenue Assurance solution" → /solutions/revenue-assurance | "ASC 606 Readiness Check" → /resources/tools/asc-606-readiness

Blog Post 4: The DoubleVerify Analogy: What Digital Advertising Can Teach AI About Trust

Route: /resources/blog/doubleverify-analogy-ai-trust | Category: Trust & Verification | Author: Acretix Team | Date: March 24, 2026 | Read time: 9 min read

SEO description: "Digital advertising solved the fraudulent impressions problem with independent verification infrastructure. AI needs the same structural fix for ROI claims. Here's the parallel."

In 2008, digital advertisers didn't trust platform-reported impression numbers. The platforms were marking their own homework. Today's AI industry is in the same position — and the solution is the same one the ad industry landed on.

The 2008 problem: Advertisers were paying ad platforms based on impression, click, and conversion numbers reported by the platforms themselves. Structurally, the entity being paid was reporting the numbers that determined payment. The result was systematic overcount, fraud, and loss of trust. By 2008, major advertisers had stopped trusting platform-reported numbers. They had no alternative verification source, so they either stopped buying digital advertising or accepted the numbers under protest. The market was stuck.

The DoubleVerify solution: DoubleVerify, founded in 2008, inserted itself between advertisers and ad platforms as an independent verification layer. They had no financial stake in the numbers being high or low. They collected data independently of the platforms, applied documented methodology, and produced verified ad performance numbers both sides trusted. Today DoubleVerify is a $5B+ public company. The market they created — independent ad verification — is now a standard line item in every major advertiser's media budget. The entity that was once optional has become infrastructure.

Why the same problem exists in AI today: AI vendors selling on outcomes report the outcome numbers that drive their own payment. The buyer has no independent way to verify. The measurement methodology is often undocumented or vendor-defined. The evidence comes from vendor systems. The incentive structure is identical to 2008 digital advertising. The counterargument — "but our AI vendor is trustworthy" — is the same counterargument advertisers made in 2005. Trust is not a substitute for verification. Even honest vendors make methodological choices that favor their numbers. Even well-intentioned measurement systems have blind spots. Independence is not about distrust; it's about shared ground truth.

Why buyers will demand independence: Buyers burned once will demand independent verification the second time. Procurement teams are learning to require third-party verification in outcome-based contracts. Enterprise buyers are starting to write "independent measurement" into their RFP requirements. Within three to five years, independent verification will be table stakes for outcome-based AI deals. The question is whether your company gets ahead of this demand or waits until buyers force it.

What independence actually requires:

• Revenue not tied to the settlement amount
• Data collected from buyer systems, not vendor systems
• Methodology documented and agreed to before measurement begins
• Dispute resolution handled by escalating neutral parties
• Professional attestation available for high-stakes determinations

What vendors should do: Getting ahead of the independence requirement is a competitive advantage. Buyers prefer vendors who proactively offer independent verification over vendors who make buyers negotiate for it. Build the infrastructure now while it's a differentiator, not later when it's a cost of doing business.

What buyers should do: Write independent verification into your outcome-based contracts from the start. Don't let the vendor dictate measurement methodology. Don't let vendor-reported numbers drive invoices without verification. The cost of independent verification is a rounding error compared to the cost of being misled.

Bottom CTAs: "Vendor Verification solution" → /solutions/vendor-verification | "Verified Delivery solution" → /solutions/verified-delivery

Blog Post 5: The First Outcome Deal: A 30-Day Playbook

Route: /resources/blog/first-outcome-deal-30-day-playbook | Category: Outcome Pricing | Author: Acretix Team | Date: March 17, 2026 | Read time: 7 min read

SEO description: "A step-by-step 30-day plan for closing and launching your first outcome-based deal — from deal design through measurement configuration to live settlement."

Your sales team just closed your first outcome-based deal. Everyone is celebrating. But someone on the finance or product team is quietly panicking — the contract terms require measurement, verification, and settlement capabilities the company doesn't have. The next 30 days will determine whether this deal is a win or the beginning of a disaster.

Week 1 — Lock the specification: Translate the signed contract into an operating specification. What outcome is being measured? What evidence qualifies? What's the baseline? What exclusions apply? What's the pricing formula? What's the dispute resolution path? The contract likely has gaps in each of these — gaps that need to be filled before measurement begins. Fill them now, in writing, with the customer's agreement. Gaps that feel harmless in Week 1 become disputes in Week 12.

Week 2 — Establish baselines: You cannot measure improvement without a baseline. Week 2 is about establishing the baseline independently, using data from the customer's systems of record. This is also when you discover whether the data you need actually exists and is accessible. It frequently doesn't. The customer's CRM doesn't have the field you need. The measurement event hasn't been tracked historically. The system doesn't have API access. You need to know this in Week 2, not Week 6.

Week 3 — Build the measurement pipeline: Connect to the customer's systems. Configure the data ingestion. Normalize the incoming events. Run a test measurement against a known time period to validate the pipeline. Document what you're measuring and how. The documentation matters. When a dispute arises — and it will — the documented pipeline is the evidence that the measurement was done correctly. Without it, every dispute is a credibility contest.

Week 4 — Ship verification and settlement: Apply the count/no-count rules from the specification. Run a full cycle on test data. Produce a sample settlement statement. Review with the customer's finance team. Make sure both sides see the same numbers and agree on the methodology. Only then does the deal go live. This conversation — "here's how we'll count outcomes, here's how we'll invoice" — is one of the most valuable conversations in the early customer relationship. Do it before the first invoice, not after.

What breaks most often:

• The baseline takes longer than expected because the data isn't where you thought it was.
• The measurement methodology has ambiguities that require customer conversations you didn't plan for.
• The customer's IT team is slow to grant data access. Start this conversation in Week 1, not Week 3.
• The pricing formula in the contract has edge cases nobody thought about. Run a test cycle before go-live to find them.

Why 30 days is possible: Most companies think standing up outcome infrastructure takes months. Using Acretix's Launch Studio compresses the timeline because the patterns are reusable. The first mapping to a customer system takes 15–20 hours. The fifth mapping takes 3–5 hours. The infrastructure you build for the first deal becomes the infrastructure that makes every subsequent deal faster.

Your first deal is your pilot: Ship it well and everything downstream is easier. Ship it badly and you lose the customer and damage the reputation of outcome pricing internally. The 30 days of careful work that make the first deal clean are worth more than the revenue from the deal itself.

Bottom CTAs: "Outcome Pricing solution" → /solutions/outcome-pricing | "The transition field guide" → /resources/blog/outcome-pricing-transition-field-guide

20.3 Guides (/resources/guides)

SEO title: "Guides — Long-Form Playbooks for Outcome-Based Deals | Acretix". PageHeader label: "Resources". PageHeader title: "Guides". PageHeader description: "Long-form, structured playbooks for specific outcome-based deal situations." Audience filter tabs: All | AI Vendors | Enterprise Buyers | CFOs | Sales Teams. Guides displayed as 2-column card grid. Each card shows audience tag, length tag, gated/free tag, title, description, and "Download PDF" or "Read guide" CTA.

Guide 1: The Outcome Pricing Playbook

Route: /resources/guides/outcome-pricing-playbook | Audience: AI Vendors | Length: 40–60 pages | Gated: Email required

SEO title: "Outcome Pricing Playbook — A Complete Field Guide | Acretix". SEO description: "Step-by-step playbook for AI and software vendors transitioning to outcome-based pricing: deal design, measurement, dispute resolution, and settlement mechanics."

About this guide: The Outcome Pricing Playbook is the most comprehensive resource available for AI companies attempting the shift from seat-based to outcome-based pricing. It covers every stage of the deal lifecycle: structuring, baseline methodology, pricing formula design, contract language, verification, settlement, and revenue recognition. This guide is written for practitioners — VP Sales, Head of Pricing, RevOps leaders, and founders who are actively working on outcome deals, not just curious about them. It does not hedge. When there is a right answer, we give it.

Description from index: "The definitive guide to structuring, pricing, selling, and operating outcome-based deals. Covers deal structuring, baseline methodology, pricing formulas, contract language, verification, settlement, and revenue recognition."

Table of contents (10 chapters):

• 01 — Why Outcome Pricing Now: The market forces making outcome-based pricing a competitive necessity for AI vendors — and why the window is opening.
• 02 — The Anatomy of an Outcome Deal: Every element of a well-structured outcome deal: outcome definition, measurement methodology, pricing formula, exclusion rules, and settlement process.
• 03 — Defining the Outcome: How to write an outcome definition that is measurable, defensible, and acceptable to procurement and legal on both sides.
• 04 — Establishing the Baseline: Baseline methodology options, how to select the right approach, and how to document the pre-AI state in a way that holds up.
• 05 — Measurement Infrastructure: Which party collects data, from which systems, how reconciliation works, and how to handle discrepancies.
• 06 — Pricing Formula Design: Base fees, per-outcome rates, caps, floors, volume tiers, and how to model the economics before signing.
• 07 — Contract Language: Sample contract clauses for outcome definition, measurement, dispute resolution, and pricing adjustment. What to push for and what to accept.
• 08 — Revenue Recognition: ASC 606 variable consideration applied to your specific deal structure. Methodology documentation, constraint analysis, and disclosure requirements.
• 09 — Selling the Deal: How to present outcome-based pricing to procurement, legal, and finance. Common objections and how to address them.
• 10 — Operating the Deal: The month-to-month operational cadence — data collection, reconciliation, invoicing, and dispute resolution.

Who this is for:

• VP Sales and Head of Pricing at AI vendors structuring outcome deals
• Founders deciding whether and how to move to outcome-based pricing
• RevOps and Deal Desk leaders supporting the transition
• Finance and legal teams reviewing outcome deal contracts for the first time

Download mechanism: Email gated. User enters work email. PDF sent to email immediately. User added to mailing list. Success state: CheckCircle icon + "Check your inbox." + "We've sent The Outcome Pricing Playbook PDF to your email."

Guide 2: The Buyer's Guide to Outcome-Based AI Procurement

Route: /resources/guides/buyers-guide-outcome-based-procurement | Audience: Enterprise Buyers | Length: 20–30 pages | Gated: Email required

SEO title: "Buyer's Guide to Outcome-Based Procurement | Acretix". SEO description: "How procurement and sourcing teams can evaluate, structure, and manage outcome-based vendor contracts — from deal design through payment verification."

Subtitle: "How to evaluate, contract with, and verify outcomes from AI vendors offering performance-based pricing."

About this guide: More AI vendors are offering outcome-based or performance-based pricing. Some of those proposals are credible. Many are not. The difference lies in the details of the outcome definition, the measurement methodology, and who controls the data. This guide helps enterprise procurement, legal, and IT teams evaluate vendor proposals, negotiate better terms, and build contracts that protect the buyer's interests — while still being fair to vendors delivering real results.

Description from index: "How to evaluate, contract with, and verify outcomes from AI vendors offering performance-based pricing. Includes sample RFP language, contract clauses, and red flags."

What's covered (7 sections):

• 01 — Understanding outcome-based contracts: What outcome-based pricing is, how it differs from SLAs, and why more vendors are offering it.
• 02 — Evaluating vendor proposals: How to assess whether a vendor's outcome proposal is credible. Red flags, green flags, and questions to ask.
• 03 — Negotiating the outcome definition: How to push for a precise, measurable definition — and why vague definitions always favor the vendor.
• 04 — Measurement and data rights: Why measurement must use your data systems, not the vendor's. What data rights to require in the contract.
• 05 — Sample RFP language: Ready-to-use RFP language for requesting outcome-based pricing proposals from AI vendors.
• 06 — Contract clauses to require: Specific contract language for outcome definition, measurement methodology, dispute resolution, and pricing.
• 07 — Red flags in vendor proposals: The specific language and structures that signal a vendor is protecting themselves at your expense.

Download mechanism: Email gated. Success state: "Check your inbox." + "We've sent the Buyer's Guide PDF to your email."

Guide 3: The CFO's Guide to Variable Consideration

Route: /resources/guides/cfo-guide-variable-consideration | Audience: CFOs | Length: 20–30 pages | Gated: Email required

SEO title: "CFO Guide to Variable Consideration Under ASC 606 | Acretix". SEO description: "Revenue recognition for outcome-based contracts: how ASC 606 variable consideration rules apply, what documentation you need, and how to build a compliant audit trail."

Subtitle: "ASC 606 variable consideration handled correctly. Methodology documentation, sample workpapers, and audit-ready evidence trails."

About this guide: If your company has outcome-based revenue, you have variable consideration under ASC 606. And variable consideration accounting is harder than most finance teams expect — not because the rules are complicated, but because the documentation and estimation requirements are demanding and the auditor scrutiny is real. This guide is written for CFOs and Controllers who need to get the accounting right the first time. It includes everything from the basic estimation methods to complete workpaper templates that can be used immediately.

Description from index: "ASC 606 variable consideration handled correctly. Methodology documentation, sample workpapers, period-end adjustment templates, and audit-ready evidence trails."

What's covered (8 sections):

• 01 — Variable consideration under ASC 606: the basics: What variable consideration is, when it applies to outcome-based revenue, and the two estimation methods.
• 02 — The constraint: when to include and when to exclude: The mechanics of the variable consideration constraint, how to document the analysis, and common mistakes.
• 03 — Estimation methodology documentation: What the methodology document must contain, who must approve it, and how it must be maintained.
• 04 — Evidence-based estimation: How to build an estimation approach that is evidence-based, consistent, and audit-ready.
• 05 — Period-end adjustment process: How to run the period-end close for variable consideration — data collection, review, approval, and posting.
• 06 — Disclosure requirements: What must be disclosed in the notes to the financial statements and what auditors will probe.
• 07 — Sample workpapers: Complete workpaper templates for methodology documentation, constraint analysis, and period-end adjustment.
• 08 — Audit preparation: How to prepare for an auditor review of variable consideration — what to expect and what to have ready.

Includes sample workpapers: (1) Variable consideration methodology documentation template; (2) Period-end constraint analysis workpaper; (3) Cumulative revenue adjustment calculation template.

Download mechanism: Email gated. "Enter your work email to receive the PDF immediately. Includes the workpaper templates." Success state: "Check your inbox." + "We've sent the CFO's Guide PDF to your email."

Guide 4: From Pitch Deck to Paid Invoice: The 90-Day Outcome Deal

Route: /resources/guides/pitch-deck-to-paid-invoice | Audience: Sales Teams | Length: 10–15 pages | Gated: Free, no email required

SEO title: "Pitch Deck to Paid Invoice — The Outcome Deal Journey | Acretix". SEO description: "How an outcome-based deal moves from initial pitch through deal design, measurement setup, verification, and first settlement. A complete end-to-end guide."

Subtitle: "A step-by-step guide from signed outcome-based deal to the first collected invoice."

About this guide: The contract is signed. Your customer is expecting results. And right now, you probably don't have the full infrastructure to measure, verify, and settle outcome-based deals at scale. This guide walks through the first 90 days of an outcome deal — week by week — across sales, delivery, finance, and legal. It's practical, opinionated, and based on how the deals that actually collect payment are run.

Description from index: "A step-by-step guide from signed outcome-based deal to the first collected invoice. Covers week-by-week activities across sales, delivery, finance, and legal."

Timeline (5 periods):

• Week 1 — Measurement infrastructure setup (Owner: Delivery + Engineering): Identify which data systems will be the measurement source of record; Confirm buyer-side data owner and their contact for monthly reconciliation; Establish baseline export process from buyer's system; Document the outcome definition one more time — confirm the contract language matches operational reality; Set up the Acretix measurement connection or equivalent data pipeline.
• Week 2 — Baseline establishment (Owner: Delivery + Finance): Export pre-AI historical data from buyer's systems for the baseline period defined in the contract; Calculate and document the baseline metric using the methodology in the contract; Share the baseline calculation with the buyer's designated approver; Get baseline signed off — both parties agree on the starting point before the AI goes live; Store the signed baseline in the contract file.
• Week 3 — AI deployment and first measurement period (Owner: Delivery): Deploy AI into the buyer's environment; Run the first measurement data pull at end of week to confirm the pipeline works; Identify and document any edge cases not covered by the exclusion rules; Flag any issues to the account team — do not wait until invoicing; Confirm the first measurement period end date with buyer operations.
• Week 4–8 — First full measurement period (Owner: Delivery + Account Management): Collect measurement data weekly; identify anomalies early; Run the first formal reconciliation at end of month 1; Resolve any discrepancies using the process defined in the contract; Prepare the first invoice based on verified outcomes; Send invoice with the reconciliation data attached — transparency accelerates payment.
• Month 3 — First collected invoice + renewal groundwork (Owner: Finance + Account Management): Confirm payment received — if delayed, investigate the cause (AP process, dispute, or data question); Review the first 60 days of outcome data with the buyer — is the deal working as modeled?; Document any operational improvements to the measurement process; If the deal is performing above the cap, initiate discussion about cap removal or deal expansion; Begin documenting the case study — with buyer permission.

Bottom CTA section (brand-green background): "Need the measurement infrastructure?" — "Acretix provides the platform that makes these 90 days operational: measurement, reconciliation, verification, and settlement. Built for outcome-based AI deals." CTAs: "See the platform" → /products | "Talk to the team" → /contact

20.4 Tools (/resources/tools)

SEO title: "Tools — Free Calculators and Assessments | Acretix" (from ToolsPage). PageHeader label: "Resources". PageHeader title: "Tools". PageHeader description: "Free interactive calculators and assessments for outcome-based deal practitioners." Four tools displayed as cards with type tag, time estimate, gated/free tag, title, description, and CTA.

Tool 1: Outcome Deal Economics Calculator

Route: /resources/tools/outcome-deal-calculator | Type: Calculator | Free, no email required

SEO title: "Outcome Deal Calculator — Model Revenue vs. Risk | Acretix". SEO description: "Free calculator: model your expected revenue, downside exposure, and breakeven under outcome-based pricing. Compare pure outcome vs. hybrid pricing structures."

Subtitle: "Model the economics of a proposed outcome-based deal."

Description: Interactive calculator. Formula: Monthly fee = Base fee + (Outcome volume × Per-outcome rate), subject to floor and cap. Analytics track: tool_view event with slug 'outcome-deal-calculator'.

Deal parameters (7 inputs):

• Base fee ($) — default: $50,000
• Per-outcome rate ($) — default: $25
• Expected outcome volume — default: 2,000
• Revenue cap ($) — default: $200,000
• Revenue floor ($) — default: $30,000
• Downside scenario (%) — default: 50%
• Upside scenario (%) — default: 150%

Results displayed (4 outputs):

• Expected revenue (highlighted in brand-green) — calc(expectedVolume)
• Downside (downside% volume) — calc(expectedVolume × downside/100)
• Upside (upside% volume) — calc(expectedVolume × upside/100)
• Breakeven volume — outcomes needed to reach the floor

Disclaimer: "This calculator is for modeling purposes. Actual results depend on your specific deal terms, measurement methodology, and customer behavior."

Tool 2: AI ROI Self-Assessment

Route: /resources/tools/ai-roi-self-assessment | Type: Assessment | Gated: Email required to view report

SEO title: "AI ROI Self-Assessment — Score Your AI Claims | Acretix". SEO description: "Free interactive assessment: score your AI ROI claims across five dimensions — measurement methodology, data sources, baseline quality, attribution logic, and audit trail."

Subtitle: "10 questions. Score the credibility of your AI ROI reporting across five dimensions."

About: "Most AI ROI reporting is not credible. Not because the AI isn't working — but because the measurement apparatus has structural problems that make the numbers unverifiable. This 10-question assessment scores your current AI ROI reporting on five dimensions of credibility: Measurement Independence, Baseline Quality, Outcome Definition, Financial Linkage, and Auditability. The assessment takes under five minutes. Your report is immediate, free, and gated only by email — so we can send you a PDF copy."

Stats: 10 questions / 5 min or less | 5 dimensions / scored independently | Free report / email required

Flow: intro → questions (one at a time, progress bar) → email gate → report

Five dimensions: Measurement Independence | Baseline Quality | Outcome Definition | Financial Linkage | Auditability

All 10 questions with 4 answer options each (score 1–4):

• Q1 (Measurement Independence) — Who defines the metrics used to measure AI ROI at your organization? Options: "The AI vendor defines and reports the metrics" (1) | "Our internal team defines metrics, based on vendor guidance" (2) | "Our internal team defines metrics independently" (3) | "A third party defines or audits the metrics" (4)
• Q2 (Measurement Independence) — Who collects the data used to calculate AI performance? Options: "The vendor collects and reports it" (1) | "We rely on vendor-provided APIs and dashboards" (2) | "We pull data from our own systems" (3) | "We pull from our own systems and reconcile with vendor data" (4)
• Q3 (Baseline Quality) — How was the pre-AI baseline established for the processes AI is now handling? Options: "No formal baseline was established" (1) | "Estimated from memory or anecdotal reporting" (2) | "Historical data from internal systems" (3) | "Documented historical data, externally validated or audited" (4)
• Q4 (Baseline Quality) — How are confounding factors (team changes, seasonality, product changes) accounted for in your ROI calculation? Options: "They are not accounted for" (1) | "Noted qualitatively but not adjusted for" (2) | "Adjusted using internal judgment" (3) | "Controlled with a documented methodology" (4)
• Q5 (Outcome Definition) — How precisely is the AI outcome defined in your organization? Options: "Loosely defined (e.g., 'faster' or 'better')" (1) | "Defined in general terms (e.g., 'reduced support volume')" (2) | "Defined with a specific metric and unit (e.g., tickets resolved per week)" (3) | "Defined with a specific metric, unit, and documented measurement methodology" (4)
• Q6 (Outcome Definition) — Is there a documented definition of what counts as a successful AI outcome — agreed to before the AI was deployed? Options: "No" (1) | "Informally agreed, not documented" (2) | "Documented internally, not in the vendor contract" (3) | "Documented and included in the vendor contract" (4)
• Q7 (Financial Linkage) — How directly is the AI ROI figure connected to a financial statement? Options: "Not connected — ROI is an operational metric only" (1) | "Loosely tied to budget savings narratives" (2) | "Mapped to specific cost or revenue line items" (3) | "Mapped to specific financial statement lines, reviewed by finance" (4)
• Q8 (Financial Linkage) — Has your CFO or finance team reviewed and approved the AI ROI methodology? Options: "No — finance is not involved" (1) | "Finance has seen the numbers, but not reviewed the methodology" (2) | "Finance has reviewed the methodology informally" (3) | "Finance has formally reviewed and approved the methodology" (4)
• Q9 (Auditability) — If an external auditor asked to review your AI ROI calculation, how ready would you be? Options: "Not ready — no documentation exists" (1) | "Partially ready — some documentation, not organized" (2) | "Mostly ready — documentation exists, needs some work" (3) | "Ready — full audit trail with methodology, data, and outputs" (4)
• Q10 (Auditability) — Can you produce a reproducible calculation — same inputs, same outputs — for any historical reporting period? Options: "No" (1) | "Partially — for recent periods only" (2) | "Yes, for most periods" (3) | "Yes, for all periods with a clear audit trail" (4)

Scoring: Overall score 0–100 (from sum of answers 10–40, converted). Labels: below 30 = "Low credibility" (red) | 30–54 = "Moderate credibility" (orange) | 55–74 = "Developing credibility" (amber) | 75+ = "High credibility" (green). Each dimension scored 2–8 (sum of 2 questions). Dimension labels: 2–3 = "Critical Gap" | 4–5 = "Weak" | 6–7 = "Developing" | 8 = "Strong". Lowest-scoring dimension marked as "Top priority". Report shows: overall score bar, dimension breakdown with per-dimension action text, highest-leverage improvement CTA. Bottom CTAs: "See AI ROI Verification" → /solutions/ai-roi-verification | "Talk to the team" → /contact

Dimension action text verbatim:

• Measurement Independence (gap): "Your ROI numbers are being produced by the party with the most to gain from a favorable result. No external board, investor, or regulator should accept these figures at face value." Priority: "Shift data collection to internal systems. Establish an internal owner for the ROI methodology who is not the vendor relationship owner."
• Baseline Quality (gap): "Without a defensible pre-AI baseline, your ROI claim has no numerator. Any productivity improvement figure is unverifiable." Priority: "Document the pre-AI state of each AI-impacted process. Use historical system data, not estimates."
• Outcome Definition (gap): "Vague outcome definitions let the evaluation drift toward whatever the AI did well. Precise definitions must be set before deployment." Priority: "Write a one-page outcome definition document for each AI initiative. Get vendor sign-off before the next renewal."
• Financial Linkage (gap): "ROI that never touches a financial statement is a narrative, not a business case. Finance must own the translation from operational metric to dollar impact." Priority: "Map each AI ROI metric to a specific P&L or balance sheet line. Schedule a finance review of the methodology."
• Auditability (gap): "If you cannot reproduce a prior period's calculation, your ROI figures are not auditable. This is a liability in any M&A, fundraising, or regulatory process." Priority: "Build a calculation workbook that can be reproduced from raw data. Document the methodology in a durable format."

Tool 3: ASC 606 Variable Consideration Readiness Check

Route: /resources/tools/asc-606-readiness | Type: Checklist | Gated: Email required to view report

SEO title: "ASC 606 Readiness Checker — Variable Consideration Assessment". SEO description: "Free checklist: assess your readiness to recognize revenue under ASC 606 for outcome-based contracts with variable consideration. Identify gaps before your next audit."

Subtitle: "15 yes/no questions. Evaluate your audit readiness across three dimensions."

About: "If your company has outcome-based revenue, you have variable consideration under ASC 606. And if you have variable consideration, your auditors will ask for three things: a documented methodology, a defensible estimation approach, and a systematic period-end process. This 15-question checklist assesses where you stand across all three areas. It takes about four minutes. Your report is gated only by email."

Stats: 15 questions / yes/no format | 3 sections / weighted scoring | Action plan / by priority

Flow: intro → questions (all 15 shown at once, yes/no per question, progress bar) → email gate → report

Three sections (15 questions total, yes/no each):

• Section 1 — Methodology Documentation (weight: 35%): "Whether the variable consideration estimation methodology is documented, consistent, and defensible."
  • Q1: You have a written methodology document describing how variable consideration is estimated for each outcome-based contract.
  • Q2: The methodology was approved by your CFO or Controller before it was applied to any contract.
  • Q3: The methodology has been reviewed by external auditors or a technical accounting advisor.
  • Q4: The same methodology is applied consistently across all contracts in the same category.
  • Q5: The methodology document is updated when there are material changes to deal structures or outcome definitions.
• Section 2 — Estimation Approach & Constraint Application (weight: 35%): "Whether the probability-weighted or most-likely-amount method is applied correctly, and whether the constraint is documented."
  • Q6: You have documented which estimation method (expected value or most likely amount) you use for each contract type, and why.
  • Q7: For each variable consideration estimate, you have documented the evidence used to support the estimate (historical data, comparable contracts, etc.).
  • Q8: You apply the variable consideration constraint and have documented your analysis of whether a significant reversal is probable.
  • Q9: The constraint analysis is updated at each reporting period, not just at contract inception.
  • Q10: You have documented the factors that could cause a significant reversal, specific to each contract.
• Section 3 — Period-End Adjustment Process & Audit Readiness (weight: 30%): "Whether period-end adjustments are handled systematically and whether the complete file is audit-ready."
  • Q11: You have a defined period-end close process for reviewing and adjusting variable consideration estimates.
  • Q12: Adjustments to cumulative revenue (i.e., catch-up adjustments) are reviewed and approved before they post.
  • Q13: For each contract, you maintain a file that includes the contract, the methodology, the estimate, and the constraint analysis.
  • Q14: You can produce a complete accounting file for any active contract within 48 hours of a request.
  • Q15: Your finance team has walked through this process with your external auditors and received no material findings.

Scoring: Overall readiness score 0–100 (weighted). Labels: below 35 = "Not audit-ready" (red) | 35–59 = "Partial readiness" (orange) | 60–79 = "Developing readiness" (amber) | 80+ = "Audit-ready" (green). Section ratings: below 40% yes = "Critical gap" | 40–69% = "Developing" | 70%+ = "Audit-ready". Lowest-scoring section marked "Priority action". Report includes: overall score bar, section results with action text, "Items to address" list of all "No" answers. Bottom CTAs: "Read the CFO's Guide" → /resources/guides/cfo-guide-variable-consideration | "Talk to the team" → /contact

Section action text verbatim:

• Methodology Documentation (critical): "Methodology documentation is the foundation of variable consideration accounting. Without it, every estimate is arbitrary and every audit is a negotiation. Priority action: Assign a technical accounting owner and produce a methodology document this quarter."
• Methodology Documentation (developing): "Your methodology exists but has gaps in approval, review, or consistency. Priority action: Get CFO sign-off on the current methodology and schedule an external advisor review."
• Methodology Documentation (strong): "Your methodology documentation is solid. Maintain it as deal structures evolve and ensure it stays current with each renewal cycle."
• Estimation Approach (critical): "Without documented estimation methods and constraint analyses, your variable consideration balances cannot be defended. This is the most common audit finding. Priority action: Build a contract-level estimation template and apply it to every active contract."
• Estimation Approach (developing): "Your estimation approach is partially documented. The constraint analysis and period-end update process are the most common gaps. Priority action: Formalize the constraint analysis as a standard workpaper for each contract."
• Estimation Approach (strong): "Your estimation approach is well-documented. Focus on keeping the constraint analysis current at each period-end."
• Period-End Process (critical): "Without a defined period-end process, variable consideration adjustments are ad hoc and unauditable. This creates restatement risk. Priority action: Define a period-end close checklist and assign an owner for each contract."
• Period-End Process (developing): "Your period-end process exists but the contract file and audit-readiness gaps are material. Priority action: Build a standard contract file template and ensure it is complete for every active contract."
• Period-End Process (strong): "Your period-end process and audit readiness are strong. Maintain the contract file discipline as deal volume grows."

Tool 4: Outcome Deal Template Library

Route: /resources/tools/deal-templates | Type: Template library | Free, no email required

SEO title: "Deal Template Library — Outcome-Based Contract Structures | Acretix". SEO description: "Downloadable deal specification templates for common outcome types: cost reduction, deflection, resolution rate, accuracy improvement, and custom outcome structures."

Subtitle: "Sample outcome deal structures by industry and outcome type. Each template includes the outcome definition, measurement methodology, pricing formula, and exclusion rules."

Filter controls: Industry filter (All industries + 6 industry options) | Outcome type filter (All outcome types + 6 type options). Grid: 3-column card grid. Each card shows industry tag, outcome type, title, summary, and "View template" CTA.

Six deal templates:

• Template 1 — AI Support Resolution Deal (AI Support Tools | Cost per resolved ticket): Summary: "Pay-per-resolution structure for AI-powered customer support. Vendor earns per verified ticket resolved without human escalation." Outcome definition: A "resolved ticket" is a support inquiry that meets all three of the following criteria: (1) the AI agent provided a substantive response, not a redirect or form letter; (2) the customer did not reopen the ticket within 72 hours; and (3) the ticket was not escalated to a human agent at any point during the interaction. Each ticket counts once, regardless of the number of AI interactions required to resolve it. Measurement methodology: Resolution measurement is drawn from the buyer's CRM (not the vendor's platform). At month-end, the buyer exports a ticket-level data file with ticket ID, open date, close date, escalation flag, and reopen flag. The vendor's system provides a corresponding file with AI interaction logs. The two files are reconciled on ticket ID. Reconciliation is performed by the buyer's operations team using the Acretix reconciliation module. Discrepancies above 2% are escalated to joint review. Pricing formula: Monthly fee = Base retainer + (Verified resolved tickets × Per-resolution rate). Base retainer covers platform access and is credited against per-resolution fees if per-resolution fees exceed retainer. Floor = Base retainer. Cap = 3× Base retainer per month, reviewed quarterly. Per-resolution rate steps down at volume tiers: 0–1,000 tickets at standard rate, 1,001–3,000 at 90% of standard rate, 3,001+ at 80% of standard rate. Exclusion rules: tickets opened by internal test accounts; tickets resolved via canned macro without AI processing; tickets where the customer email domain matches the vendor's domain (self-support); tickets resolved in under 60 seconds (likely bots); and tickets in languages not supported by the deployed AI model at time of resolution.
• Template 2 — FinOps Shared Savings Deal (FinOps Platforms | Percentage of verified cloud cost savings): Summary: "Vendor earns a percentage of verified cloud cost reductions against an independently established baseline." Outcome definition: A "verified saving" is a reduction in total cloud spend in a billing period relative to the agreed baseline, after controlling for workload changes. Savings are measured at the cost allocation unit level agreed in the contract. Savings attributable to infrastructure decommissions, product shutdowns, or team reductions initiated independently of vendor recommendations are excluded. Measurement methodology: Baseline is established using the 90-day average spend in each cost allocation unit prior to vendor deployment, normalized for any known workload changes. Monthly savings are calculated as: Baseline spend (adjusted) minus Actual spend. Workload adjustment methodology is documented in Appendix A and must be re-validated if allocated workload changes by more than 15% from baseline. Pricing formula: Monthly fee = 20% of verified savings, subject to a floor of $0 (vendor earns nothing if savings are zero or negative) and a cap of 40% of the baseline spend for that period. The savings percentage is fixed for the initial contract term and renegotiated at renewal. Exclusion rules: savings in cost centers not included in the agreed scope; savings from reserved instance or committed use discount purchases not recommended by the vendor; credits or refunds issued by cloud providers; and any billing adjustments retroactively applied by the cloud provider.
• Template 3 — AI Contract Review Outcome Deal (AI Contract Review | Cycle time reduction + accuracy rate): Summary: "Dual-outcome structure: vendor earns on both contract review cycle time reduction and accuracy rate against human attorney benchmark." Outcome definition: Two outcomes measured independently — (1) Cycle time: Average calendar days from contract receipt to completed first review, measured across all contracts in scope. (2) Accuracy: Percentage of AI-flagged issues that are confirmed by reviewing attorney as material. Baseline for each is established in the first 30-day calibration period. Measurement methodology: Cycle time is measured using timestamps in the buyer's matter management system. Accuracy is measured by a sample review: each month, 10% of completed AI reviews are re-reviewed by a designated attorney and scored against the AI output. Sample size floor is 20 contracts per month. Pricing formula: Monthly fee = Base platform fee + Cycle time bonus + Accuracy bonus. Cycle time bonus: For each percentage point of cycle time reduction above 20%, vendor earns an additional 2% of base platform fee (capped at 30% of base fee). Accuracy bonus: For each percentage point of accuracy above 85%, vendor earns an additional 1.5% of base platform fee (capped at 15% of base fee). Exclusion rules: contracts flagged as rush (same-day required); contracts requiring regulatory review outside AI scope; contracts where attorney-side delays account for more than 50% of cycle time; contracts voided before completion; contracts in pilot categories not yet in production model.
• Template 4 — AI Coding Assistant Productivity Deal (AI Coding Assistants | Developer productivity uplift): Summary: "Pay-for-productivity structure tied to independently measured developer output metrics, not vendor-reported usage stats." Outcome definition: Productivity uplift is measured as the change in the buyer's internal engineering productivity score — a composite of: (1) story points completed per developer per sprint, normalized for team size; (2) deployment frequency; and (3) mean time to restore (MTTR). The composite methodology is documented in the contract and cannot be changed without mutual agreement. Measurement methodology: Productivity data comes from the buyer's engineering toolchain (Jira, GitHub, PagerDuty or equivalent). Baseline is established using the 60-day average prior to AI deployment, normalized for team size changes. Quarterly measurement periods are used to smooth sprint variability. Pricing formula: Annual fee = Base license + Productivity premium. Productivity premium: (Measured uplift % − 10%) × Base license, subject to a floor of 0 (no premium if uplift is below 10%) and a cap of 50% of base license. If uplift is negative for two consecutive quarters, buyer has the right to reduce the base license by 25% at the next annual renewal. Exclusion rules: periods of organizational restructuring affecting more than 20% of measured engineers; sprint periods where more than 30% of engineers were on leave; feature work explicitly excluded from the engineering productivity program.
• Template 5 — HR AI Outcomes Deal (Time-to-Hire) (HR Technology | Time-to-hire reduction): Summary: "Vendor earns on demonstrated reduction in average time-to-hire across targeted roles, measured against documented historical baseline." Outcome definition: Time-to-hire is defined as calendar days from job requisition approval to signed offer letter, for roles in the agreed scope. Roles in the scope are defined by job family and seniority level in Exhibit A of the contract. Only roles that complete the full cycle within the measurement period are included. Measurement methodology: Time-to-hire data is pulled from the buyer's ATS (not the vendor's platform). Baseline is the 12-month average prior to deployment, segmented by role family. Monthly measurement uses a rolling 90-day average to smooth seasonal variation. Pricing formula: Annual fee = Base fee + Performance bonus. Performance bonus: If average time-to-hire reduction exceeds 15% versus baseline, buyer pays an additional 15% of base fee. If reduction exceeds 25%, buyer pays an additional 30% of base fee. Reductions are measured annually at contract anniversary. Exclusion rules: roles filled via agency; roles where the hiring manager bypassed ATS; roles where requisition was on hold for more than 30 days; executive-level searches (VP and above); and roles where the offer was declined.
• Template 6 — Professional Services Outcome Fee (Professional Services | Project milestone completion): Summary: "Milestone-gated fee structure for professional services engagements. A portion of the fee is contingent on verified milestone completion." Outcome definition: Each milestone is defined in the Statement of Work with: (1) a specific, measurable deliverable; (2) an acceptance criteria checklist signed by both parties; and (3) a named buyer-side approver. A milestone is "complete" when the buyer-side approver signs the acceptance checklist within the acceptance window defined in the SOW. Measurement methodology: Milestone completion is determined by the signed acceptance checklist. Disputes over whether acceptance criteria are met are resolved by a defined escalation path: (1) project leads (5 business days); (2) executive sponsors (5 business days); (3) binding expert determination by a mutually agreed third party (15 business days). Pricing formula: Total fee = Fixed base (60% of total) + Milestone fees (40% of total, divided equally across milestones). Milestone fees are invoiced within 5 business days of milestone acceptance. If a milestone is delayed by buyer-caused delays, the milestone fee is not affected but the overall timeline adjusts accordingly. Exclusion rules: milestone fees are not reduced for delays caused by third-party dependencies documented in the SOW; changes in buyer requirements; unavailability of buyer-side resources for scheduled reviews; or force majeure events. Fees are only adjusted if the service provider fails to deliver the defined deliverable within the adjusted timeline.

Bottom CTA: "Need a template for a different deal type?" — "We work with vendors and buyers to structure bespoke outcome deals across every AI use case. If your deal type isn't here, reach out." CTA: "Talk to the team" → /contact

20.5 Events (/resources/events)

SEO title: "Events — Webinars, Workshops, and Office Hours | Acretix". PageHeader label: "Resources". PageHeader title: "Events". PageHeader description: "Live conversations on outcome-based deals, AI monetization, and commercial infrastructure." Layout: 1fr + 300px sidebar grid. Sidebar cards: "Get event reminders" (email signup for 48-hour pre-event reminders) + "Host an event with us" (partner inquiry → /contact).

Events index lists 4 upcoming events as cards. Past events section links to /resources/events/past (shows placeholder until live).

Event 1: Founder Office Hours

Route: /resources/events/founder-office-hours | Format: Live video · 30 min | Cadence: Recurring — Every other Thursday, 11:00 AM PT

SEO title: "Founder Office Hours — Live Q&A with Acretix | Acretix". SEO description: "Monthly live sessions where founders and practitioners can ask questions about outcome-based deal design, measurement, verification, and settlement directly to the Acretix team."

About this session: Open Q&A with the Acretix founding team on any topic — outcome pricing, deal structuring, verification methodology, AI monetization, or how Acretix fits into your stack. Come with questions. This isn't a product demo — it's a working session. If you have a live deal you're trying to structure, bring the details. If you have a conceptual question about outcome-based pricing, bring that too.

What people ask about (8 topics):

• How to structure a baseline for a new AI deployment
• What to put in the outcome definition clause
• How to handle edge cases and exclusions in the pricing formula
• ASC 606 treatment of specific deal structures
• How to get procurement and legal aligned on outcome-based terms
• How Acretix measurement works for a specific use case
• How to model the economics before signing
• What the first 90 days of an outcome deal look like operationally

Format:

• 30-minute video call, every other Thursday at 11:00 AM Pacific
• Open to anyone — no prior Acretix relationship required
• Questions accepted in advance or live during the call
• Recording not available — sessions are off-the-record
• No pitch or product demo unless you want one

Registration sidebar: Email input → "Register" button. Success state: CheckCircle icon + "You're registered." + "We'll send the video link to your email before the next session." Source tag: 'event-founder-office-hours'.

Event 2: The Outcome Pricing Workshop

Route: /resources/events/outcome-pricing-workshop | Format: Virtual workshop · 90 min | Cadence: Monthly | Capacity: Seats limited to 12

SEO title: "Outcome Pricing Workshop — Hands-On Deal Design | Acretix". SEO description: "A hands-on workshop for vendors building their first outcome-based deal: structuring the outcome definition, modeling economics, and configuring measurement from the ground up."

About this workshop: A hands-on workshop for VP Sales, Head of Pricing, and RevOps leaders. Bring a real deal you're trying to structure on outcomes. Walk away with a modeled deal specification, measurement methodology, and a draft pricing formula. This is not a webinar. Seats are limited to 12 so every participant gets working time on their specific deal. The session is facilitated by the Acretix team but structured as a working session among peers.

What you'll walk away with (4 items):

• A modeled deal specification: A structured document describing the outcome definition, measurement methodology, and pricing formula for your deal.
• A draft pricing formula: Base fee, per-outcome rate, caps, floors, and sensitivity ranges modeled in the Outcome Deal Calculator.
• A measurement methodology: Which data sources, which party collects them, how reconciliation works, and what the exclusion rules are.
• Peer frameworks: How other companies in the room have solved similar structuring problems — approaches you can adapt.

Who should apply:

• VP Sales or Head of Pricing at an AI vendor actively structuring outcome deals
• RevOps or Deal Desk leaders supporting outcome-based pricing programs
• Founders at early-stage companies trying to launch their first outcome deal
• Anyone with a specific deal on the table who needs to solve the structuring problem

Application sidebar: Fields: name (required), email (required), role (optional). Button: "Apply for a seat". Success state: CheckCircle + "Application received." + "We'll review your application and reach out within 2 business days with next steps." Source tag: 'event-outcome-pricing-workshop'.

Event 3: The CFO Roundtable on Variable Consideration

Route: /resources/events/cfo-roundtable | Format: Virtual roundtable · 60 min | Cadence: Quarterly | Access: Invite-only | Rules: Chatham House

SEO title: "CFO Roundtable — Revenue Recognition for Outcome Deals | Acretix". SEO description: "A private roundtable for CFOs and finance leaders on ASC 606, variable consideration, and building audit-ready revenue recognition processes for outcome-based contracts."

About this roundtable: Closed-door conversation for CFOs and Controllers managing ASC 606 variable consideration on outcome-based deals. No vendor pitches. Chatham House rules. Share what's working, what isn't, and what your auditor is asking for. This session exists because the accounting and disclosure questions around outcome-based revenue are genuinely hard, and there are very few places where CFOs can compare notes honestly.

Topics covered (8 items):

• Variable consideration estimation methodology
• Constraint application and documentation
• Period-end adjustment processes
• What auditors are asking about in 2026
• Disclosure requirements and approaches
• Contract modification accounting for deal amendments
• How to handle multi-year outcome deals
• Benchmark data on what peers are doing

Ground rules:

• Chatham House rules: participants may use what is discussed, but may not attribute statements to individuals
• No vendor pitches or product demos
• Attendance is by application — we review every request
• Participants are CFOs, Controllers, or VP Finance-level only
• Facilitated by Acretix; Acretix does not sell during the session

Request sidebar: Fields: name (required), email (required), organization (optional). Button: "Request to attend". Success state: CheckCircle + "Request received." + "We'll review your request and be in touch within 3 business days." Source tag: 'event-cfo-roundtable'.

Event 4: AI Monetization in 2026: What We're Seeing

Route: /resources/events/ai-monetization-2026 | Format: Panel webinar · 45 min | Cadence: Annual

SEO title: "AI Monetization Summit 2026 — Acretix Event". SEO description: "A live event on AI monetization strategy, outcome pricing models, and the infrastructure shift from seat-based to results-based revenue. Hosted by Acretix."

About this event: A panel of AI vendor executives, enterprise buyers, and finance leaders discussing the state of AI pricing — what models are emerging, what buyers are demanding, and what the next 12 months look like. Moderated by Acretix. The AI pricing market is moving fast. Seat-based models are under pressure. Outcome-based deals are being demanded by more buyers and attempted by more vendors. This panel assembles people with direct, current experience on all sides of the negotiation table.

Topics on the agenda (4 items):

• What AI pricing models are actually winning deals in 2026: The models buyers prefer, the models vendors are comfortable with, and where the gap is.
• The buyer perspective: what procurement is asking for: Performance-based terms, SLAs with teeth, independent verification — what enterprise buyers are requiring in 2026.
• The CFO lens: what finance needs to see: How finance leaders are thinking about variable consideration, AI cost justification, and board-level ROI reporting.
• What the next 12 months look like: Where the market is going based on deal activity, investor expectations, and regulatory signals.

Format:

• 45-minute panel webinar, live and on-demand
• Panel of 3–4 speakers: AI vendor executives, enterprise buyers, finance leaders
• Moderated Q&A in the final 15 minutes — questions accepted in advance
• Recording and full transcript available to registrants after the event
• Annual event — held once per year

Registration sidebar: Email input → "Register". Success state: CheckCircle + "You're registered." + "We'll send you the event link and any updates before the panel." Disclaimer: "We use your email only to send the event link and recording. No spam." Source tag: 'event-ai-monetization-2026'.

Event 5: Past Events

Route: /resources/events/past | SEO title: "Past Events — Acretix Webinars and Workshops Archive". SEO description: "Recordings and summaries from past Acretix events: outcome pricing workshops, CFO roundtables, founder office hours, and AI monetization sessions."

Current state: Placeholder page. Headline: "No past events yet". Body: "Recordings, slide decks, and written summaries of past events will appear here once we hold our first sessions. Register for an upcoming event to be among the first." CTA: "See upcoming events" → /resources/events

20.6 Benchmarks (/resources/benchmarks)

SEO title: "Benchmarks — Verified Outcome Data from the Network | Acretix". SEO description: "Anonymized benchmarks from real outcome deals: typical outcome rates, dispute frequencies, resolution timelines, and settlement accuracy across industries."

PageHeader label: "Resources". PageHeader title: "Benchmarks". PageHeader description: "Anonymized data on what outcome-based deals actually deliver, drawn from the Acretix network."

Hero callout (brand-green background, centered): "The first industry-wide view of verified outcomes." Subtext: "We're building the benchmark data nobody else can: verified outcomes from real settlements, not vendor marketing claims."

What's coming: "Quarterly benchmark reports, starting with four verticals. Anonymized and aggregated across the Acretix network." Four planned benchmark categories:

• AI Support Tools: Cost-per-resolution, deflection rates, human escalation rates across outcome-based contracts.
• FinOps Platforms: Shared savings rates, cost attribution accuracy, baseline methodology variations.
• AI Contract Review: Completion rates, review accuracy, cycle time reduction, human sign-off rates.
• AI Coding Assistants: Productivity uplift, code quality metrics, and usage-outcome correlation.

Why this data is unique: "The data comes from verified settlements — actual measured outcomes on real deals, not vendor-reported numbers. No single participant can replicate this aggregate view. The benchmarks aren't what vendors claim they deliver. They're what was independently measured and settled."

How participation works: "Every customer using Acretix's Core Platform can opt in to contribute anonymized data to the benchmark network. In return, they receive access to the full benchmark reports — the first look at verified outcome performance across the industry."

Notification signup (Bell icon): "Be notified when benchmarks launch" — "First-report subscribers get early access and a summary briefing with the Acretix team." Email input + "Notify me" button. Success state: "You're on the list. We'll be in touch." Source tag: 'benchmarks'.

20.7 Newsletter (/resources/newsletter)

SEO title: "Newsletter — Monthly Digest on Outcome-Based Deals | Acretix". SEO description: "Monthly field notes on outcome pricing, AI ROI verification, revenue recognition, and the practice of building executable outcome-based deals. Subscribe free."

PageHeader label: "Resources". PageHeader title: "The Outcome Layer". PageHeader description: "A monthly digest of what's happening in outcome-based commerce. Research, benchmarks, and frameworks in your inbox."

Layout: 1fr + 400px sidebar grid. Left: "What you'll get" (4 items) + cadence card. Right: subscription form (sticky).

What you'll get (4 items):

• New benchmark data: When we publish new verified outcome benchmarks, subscribers see the summary and key findings first.
• Deal structure case studies: Anonymized breakdowns of actual outcome deals — what worked, what didn't, what the companies learned.
• Framework updates: New thinking on outcome pricing, variable consideration, AI ROI verification, and related topics.
• Industry signal: What we're seeing across the Acretix network that might matter for your business.

Cadence and format:

• Monthly send, on the first Thursday of each month
• Brief format: 800–1,200 words, 4–6 minute read
• Plain text-heavy design, not marketing-heavy
• No affiliate content, no paid placements

Subscription form: Newsletter name: "The Outcome Layer". Form label: "Subscribe to The Outcome Layer". Subtext: "Monthly. Free. No spam." Email input + "Subscribe" button. Disclaimer: "We use your email only to send the newsletter. Unsubscribe at any time. [Privacy policy link → /privacy]" Success state: CheckCircle + "You're subscribed." + "Look for The Outcome Layer in your inbox on the first Thursday of next month." Source tag: 'newsletter_page'.

21. LEGAL PAGES

Privacy Policy (/privacy)

Last updated: April 1, 2026. Covers: information collected (account, assessment, contact, payment, device/browser, usage, cookies), how used, organizational opt-in (voluntary, anonymized, revocable), sharing (service providers, legal, business transfers — no selling), retention, rights (access/correction/deletion/portability), security (TLS 1.2+, encryption at rest), international transfers (SCCs), children (under 16 not permitted). Contact: [email protected].

Terms of Service (/terms)

Last updated: April 1, 2026. Covers: acceptance (16+), services description, accounts, assessment data accuracy, organizational use (anonymized, opt-in, no mandating), ISV independence guarantee (fees fixed, never tied to results — non-negotiable), intellectual property (Acretix owns platform/methodology/benchmarks/reports), prohibited conduct, payment (auto-renewal, non-refundable), warranties (AS IS), liability (12 months fees cap), indemnification, termination, governing law (California, San Francisco County). Contact: [email protected].

Cookie Policy (/cookies)

Last updated: April 1, 2026. Strictly necessary: __session, sb-access-token, sb-refresh-token, csrf_token. Functional: acx_preferences, cookie_consent. Analytics: _ga, _ga_* (Google Analytics). Marketing: not currently used. Third-party: Google Analytics, Supabase. DNT signal respected. Contact: [email protected].

22. DESIGN SYSTEM AND VISUAL SPECIFICATIONS

22.1 Color Palette

22.2 Typography

23. COMPONENT CLASSES

24. ANIMATION SYSTEM

Scroll Reveal

Elements with class "reveal" start at opacity:0, translateY(24px). On intersection (threshold 0.08, IntersectionObserver), class "revealed" added, animating to opacity:1 translateY(0) over 700ms with cubic-bezier(0.16,1,0.3,1).

Stagger Delays

Layout Patterns

• Max content width: 1120px (.content-width)
• Narrow content: 800px (.content-narrow)
• Horizontal padding: 32px (px-8)
• Section vertical padding: 80px (py-20)
• Hero top padding: 140px
• PageHeader top padding: 100px

25. REUSABLE COMPONENTS

AcretixLogo

SVG wordmark/lettermark. ViewBox "400 850 1270 370". Fill rgb(30,91,34) for marks, #FAFAF8 for knockouts. Accepts className (e.g., h-9 w-auto footer, h-10 w-auto nav). aria-label="Acretix".

PageHeader

Props: label, title, description. bg-page-surface, border-b, pt-[100px]. badge-green label. Title clamp(32px,5vw,48px), font-bold, -0.03em tracking, max-w-[680px]. Description text-[17px] text-text-secondary max-w-[600px].

FeatureList

Props: items (string[]). Vertical flex list gap-3 mt-5. Each: Check icon (size 16, text-brand-green) + span text-[15px] text-text-secondary.

SEO

Props: title, description, canonical, jsonLd. Uses react-helmet-async. Renders title tag, meta description, canonical link, and JSON-LD script tags for structured data (Organization, WebSite, Article schemas).

Navigation

Fixed top, scroll-aware transparency. Hover dropdowns for Products, Solutions, Resources (150ms close delay). Mobile hamburger (lg:hidden). Active route in brand green. Right: "Log in" + "Schedule a Demo" (both /contact).

Footer

4-column grid. Brand + Products + Solutions + Company columns. Bottom: copyright + Privacy/Terms/Cookies. Includes "SiteReport AI" link to /sitereportai in Company column.

AnnouncementBar

Top-of-page announcement strip. Reports height via callback so nav and page content offset correctly.

26. PRICING SUMMARY

Non-negotiable: Acretix fees are flat and never tied to settlement amounts. This is the ISV independence guarantee — built into every tier and non-negotiable per the Terms of Service.

Professional Services: 4 service lines — Launch Studio (deal-to-live in 30 days), Outcome Ops (ongoing managed operations), Expert Coverage (verified human-in-the-loop coverage), Finance & Governance (ASC 606 documentation and audit prep).

END OF REPORT

This document contains the complete content, structure, layout specifications, and design system of the Acretix website as of Q2 2026. All text is verbatim from source code. Designed for AI/LLM consumption and automated processing.

The commercial control layer for outcome-based deals.