Cofactr provides infrastructure for hardware teams, helping companies streamline procurement, inventory, and logistics. As they scaled, their pricing evolved from simple subscriptions to modular, usage-based models with minimum commitments, one-time fees, and customer-specific variations.

Their billing stack couldn't keep up. In three years, they went through NetSuite's SuiteBilling, then Metronome, searching for something that could handle the complexity without creating more operational burden.

Neither one worked.

NetSuite couldn't handle modern pricing

Cofactr started with NetSuite's SuiteBilling. It worked for basic subscriptions but fell apart when they needed modular pricing or usage-based billing. The system wasn't built for the kind of flexibility modern SaaS pricing requires.

So they moved to Metronome, hoping a usage-billing specialist would solve the problem.

Metronome created new bottlenecks

Metronome handled usage metering. But it didn't handle everything else Cofactr needed to actually run revenue operations.

The subscription modeling was rigid. Every small pricing variation required creating a completely custom plan per customer. As Phil Brandt, Head of Finance, put it: "The rigid plan structure forced us to create completely custom plans for each customer, even when they were essentially using the same product, making it incredibly inefficient when making updates to pricing."

Upsells and mid-term changes were manual. To change a customer's plan mid-cycle, finance had to cancel the old subscription, create a new plan, adjust revenue recognition manually, and hope nothing broke.

There was no native revenue recognition, which meant the finance team built a patchwork of Google Sheets and Python scripts to track how revenue should be recognized across different contract terms.

There was no CPQ integration, so sales reps couldn't generate quotes or contracts from Salesforce. Every deal required manual work to turn a closed opportunity into an actual subscription.

And the biggest problem: only the CEO could confidently make changes to usage-based plans. The system required such deep technical knowledge and had so many engineering dependencies that it became a single point of failure. When customers needed pricing updates, they had to wait for the CEO to make the change.

What Measure solved

Cofactr needed a platform that could handle usage-based billing and everything that comes after: quoting, contracts, invoicing, revenue recognition, and accounting sync. One system that connected the entire revenue workflow instead of a collection of point solutions held together with scripts.

Measure handled modular pricing without requiring custom plans for every customer. Usage-based billing, minimum commitments, one-time fees, and discounts all worked out of the box.

The built-in CPQ engine let sales reps create quotes and contracts directly from Salesforce. Finance got automated revenue recognition tied to invoice and contract data, with granular control over recognition rules.

Upsells became automatic. Mid-term changes could be scheduled, prorated, and co-termed without manual cancellations or new plan creation.

What changed

Finance stopped building spreadsheets

Revenue recognition, billing reconciliation, and plan management all run through Measure now. The Google Sheets and Python scripts are gone. Phil's team has a scalable foundation that doesn't require custom code every time pricing changes.

Sales can quote without finance

The CPQ integration with Salesforce means sales reps generate quotes and contracts themselves. Deals close faster because they're not waiting for finance to manually build proposals.

Anyone can manage plans

The CEO is no longer the only person who can make subscription changes. Finance and operations can update pricing, handle upsells, and manage customer plans without engineering dependencies.

Integrations just work

Data flows automatically between Salesforce, Measure, QuickBooks, and Avalara. As Phil said: "Measure's native CPQ integration with Salesforce and sync with QuickBooks just makes the data flow automatically between systems, saving us a ton of manual work."

Conclusion

Cofactr went from NetSuite to Metronome searching for billing infrastructure that could keep up with their pricing evolution. What they found was that usage-billing point solutions solve one problem while creating others. Metronome metered usage but didn't connect to the revenue workflow their sales and finance teams actually needed.

Measure gave them the whole stack: usage billing, CPQ, revenue recognition, and accounting integration in one platform. The finance team finally has infrastructure that scales without requiring custom code every time the business changes.