About Revenue Mechanics

Building the bridge between Jira and Salesforce.

Our Mission

Revenue Mechanics was founded with a simple observation: Salesforce teams spend enormous time manually verifying that their orgs match what their Jira stories require. Acceptance criteria get written, developers build the configuration, but nobody systematically checks that the metadata, validation rules, and page layouts actually align with the spec.

We set out to fix this with TrueStory — a Jira-native tool that reads your acceptance criteria, maps them to Salesforce components, and runs deterministic checks against your live org. No AI guessing. No probabilistic outputs. Just reliable, reproducible verification results.

What We Believe

  • Determinism over prediction — Every check should produce the same result given the same input. We use regex-based constraint detection and Tooling API queries, not LLMs.
  • Verification should live where teams work — TrueStory runs inside Jira Cloud as a Forge app. No separate login, no context switching, no extra browser tabs.
  • Traceability is non-negotiable — Every pass, fail, or partial result links back to the specific AC line, constraint type, and Salesforce metadata that was queried. This creates an auditable trail for compliance-heavy industries.
  • Developer experience matters — Write AC in plain language. Reference fields by label or API name. TrueStory handles the translation and orchestration.

Two Tiers, One Experience

TrueStory works in two modes, automatically detected based on your configuration:

  • Standard (Team) — All constraint detection, check generation, and narration are rule-based and deterministic. No LLM required. 19 constraint types, behavioral testing, sprint dashboard, regression suite, and professional narration.
  • Pro (BYOK AI) — Everything in Team, plus AI-powered analysis, intelligent test plan generation, and conversational follow-up. Uses your own API key (Anthropic, OpenAI, or Google) via a multi-provider proxy. No AI data leaves your control.

The Product

TrueStory supports 19 constraint types including required fields, conditional requirements, picklist values, formula fields, validation rules, page layouts, and security configurations. It runs two layers of verification:

  • Metadata checks — Queries the Salesforce Tooling API and REST describe endpoints to verify field existence, types, nillable flags, and layout membership.
  • Behavioral tests — Creates test records with invalid data and confirms your validation rules actually fire. This catches cases where a rule exists but is inactive, or where error conditions don't match.

Contact

We're in early access and actively onboarding Salesforce teams. If you're interested in automating your release verification, reach out at sales@revmech.ai.