Introducing: https://www.revinci.ai/ Every pricing leader I've talked to in the last 12 months is wrestling with the same four questions: 1. How do I quantify the value my AI agent actually delivers — and turn that into a billable unit? 2. How do I price it when my COGS is a moving target on every API call? 3. How do I model 20+ pricing variants — flat, tiered, token, outcome, hybrid — without CPQ and billing drifting out of sync? 4. How do I see my margin in real time, not eight weeks later when finance closes? For 20 years, value-based pricing has been the holy grail no SaaS platform could operationalize, because SaaS value is invisible — you can't meter "the CRM helped close a deal." Agents are different. Every agent action is a measurable outcome event. Tickets resolved. Hours saved. Meetings booked. Bugs triaged. Documents drafted. For the first time, the value an AI delivers is instrumentable — and that means value-based pricing is finally executable. Revinci is built around exactly that shift. The three engines pricing pros should care about: Revinci runs on a unified Sell + Bill platform, and the heart of it is three engines that move together on every event: - Value Engine — model what each agent creates for the customer. Hours saved, tickets resolved, meetings booked, manual-labor cost displaced, time-to-resolution compressed. Every outcome becomes a first-class, meterable, billable unit. This is the engine that turns "we save you 40% of agent handle time" from a sales claim into a contract clause. - SmartCost — real-time cost-to-serve per agent, workflow, customer, and model. Tokens, compute, storage, API calls. COGS visible as revenue is created. - SmartMargin — live gross margin per deal, per customer, per agent. Guardrails auto-flag below-floor transactions. Leakage detection. Profitability scorecards. In pricing terms: value, cost, and margin are no longer three separate spreadsheets owned by three separate teams. They're one continuous signal, evaluated on every event, every quote, every invoice line.

I talked to an engineering manager today about monitoring issues in production. He mentioned an open-source platform his company uses to increase reliability: Temporal. I went to check it out and realised how hugely popular it's become. Long story short, it lets you define workflows that automatically survive crashes, restarts, and network failures: without you writing retry or recovery logic yourself. It made me realise how easy it is to take reliability for granted when dealing with pricing / billing complexities. Every major billing platform - Stripe, Chargebee, Metronome, Polar etc. is reliable on its own. None of them, however, owns the layer between your CRM, your usage events, invoices, and your warehouse in a way that survives failed event delivery, events arriving out of order, and missed reconciliations. That layer is yours to build. If you or your team have never explicitly built this layer, it's most likely not there. This is most likely quietly costing you money in ways your dashboard won't show. PS: You don't have to use Temporal. Inngest, Restate, AWS Step Functions, Kafka, or even a well-behaved queue with idempotency keys can get you there. The pattern matters more than the tool. PPS: This is the work I do. Happy to nerd out in the comments or DMs.

I’ve been thinking about how pricing is evolving in the context of AI agents, and I’d really value your perspective. Historically, pricing has often been a bottleneck in the sales process—but over time, we’ve built systems (CPQ, billing, usage-based models) that make pricing more structured and scalable. With AI agents, it feels like we’re facing a new version of that challenge—not in pricing execution, but in defining and measuring value. While costs (tokens, infra, etc.) are relatively transparent, the value created by agents is much harder to quantify consistently. We’re currently exploring ways to decode this as part of our product journey. I’d love your thoughts on a few open questions: 1. Defining value: What key parameters or signals should be captured to quantify the value created by an AI agent (e.g., time saved, revenue impact, quality improvements)? 2. Data accessibility: In your experience, how willing are customers to share internal metrics required to measure value? What has worked (or failed) in getting this data? 3. Human-in-the-loop (HITL): How should we think about attributing value when humans are partially involved in the workflow? This seems like one of the hardest aspects to standardize. 4. Customer success criteria: How do you recommend aligning pricing with what “success” actually means to the customer, given that this can vary widely? 5. Product vs. sales responsibility: Should value measurement and tracking be embedded within the agent/product itself, or handled externally in the sales/pricing layer (e.g., CPQ, analytics tools)? If you’ve seen strong frameworks, patterns, or even failed approaches in this space, I’d be very interested to learn from them. Thanks in advance for your time—I’d really appreciate any guidance you can share.