---
title: "Validation rules, contact roles, and the ARR field the CRM won't give you"
type: case-study
evidence_type: proof
category: "CRM Architecture & Migration"
publisher: "LeanScale"
date_modified: 2026-08-08
word_count: 349
topics: ["revenue-operations"]
canonical_url: https://knowledge.leanscale.team/customers/opportunity-lifecycle-and-revenue-recognition-architecture/
source: "LeanScale Knowledge Hub — https://knowledge.leanscale.team"
license: "Free to quote and cite with attribution to LeanScale."
---

# Validation rules, contact roles, and the ARR field the CRM won't give you

**Evidence type:** proof (what happened)

A growth-stage AI company was adding sellers faster than process. LeanScale pushed opportunity-stage and contact-role validation rules into production and designed the amount architecture needed to report ARR separately from total contract value on multi-year prepaid deals.

## The challenge

The company was scaling its go-to-market without a revenue operating system underneath it. Opportunity stages had no entry requirements, so deals advanced on assertion; the buying committee was captured inconsistently or not at all; and the amount model conflated annual recurring revenue, total contract value and implementation fees, which made prepaid multi-year commitments impossible to report on cleanly. Top-of-funnel lead stages and the post-sale lifecycle had never been defined at all.

## The approach

Stage gates pushed to production
Built and pushed opportunity-stage validation rules to production — a proposal link required at the late-stage gate, signed-contract enforcement on closed-won, and a conditional revisit trigger on closed-lost so lost deals get a defined follow-up instead of disappearing from the system.

Contact-role governance simple enough to be used
Deployed contact-role validation rules that reduce the buying committee to three roles — champion, economic buyer, signatory — on the reasoning that a short list gets filled in accurately while a long one gets skipped entirely.

Amount and revenue-recognition architecture
Scoped a clean opportunity amount model separating ARR, total contract value and implementation fees, then diagnosed that the CRM's standard amount field is effectively locked to total contract value and recommended a dedicated ARR field plus per-year ARR fields to support prepaid multi-year commitments.

Top-of-funnel lifecycle logic
Mapped lead-stage transition logic, scoring and automation triggers for the top of the funnel, which had no defined stages before.

Post-sale lifecycle scoped with the CS owner
Scoped a customer lifecycle from qualified opportunity through to customer alongside the customer-success lead, so the handoff has defined stages on both sides of it rather than a gap at closed-won.

## Outcomes

Stage validation live in production
Opportunity-stage validation rules were pushed to the production org within the window, moving stage discipline from documentation into enforcement.

Contact-role governance deployed
Contact-role validation rules were built and deployed, enforcing champion, economic buyer and signatory on the opportunity record.

A workable revenue model recommended
The amount architecture recommendation was delivered and the field build began in the following weeks; the unblocking use case was prepaid multi-year commitments, which the standard amount field could not represent.

## Quotes

> Great progress this week. Just dropped comments on your doc for contact roles, thanks for that + the Loom.
>
> — Customer, GTM Operations


## Canonical

https://knowledge.leanscale.team/customers/opportunity-lifecycle-and-revenue-recognition-architecture/