MonetizeNow — Nicole Boac

Quote to cash, built from zero

MonetizeNow is a quote to cash platform for BDR teams. It covers the full revenue workflow: complex quoting with multi-year rates and scheduled price changes, contract generation via DocuSign, billing with dunning management, and usage monitoring for consumption-based products.

When I joined there were two customers, a junior designer, no design system, and a product built to launch rather than scale.

Before State

Early state of the product showing the inconsistency before the design system.

Four surfaces, each with its own complexity

Company onboarding is the invisible product. Before a BDR sends a single quote, the company loads all products, pricing tiers, rates, and overrides into the system. Every company's pricing model is different. Designing for that flexibility without breaking the next company's experience was one of the core design challenges.

Quoting is the primary BDR workflow. Configure the deal, set rates, schedule changes, send via DocuSign, generate the contract. The quote and the contract must remain in parity because the quote is a binding document that exports as a PDF. As deal complexity grew, maintaining that parity without degrading the live experience became an ongoing constraint.

Billing handles dunning and payment setup, including a native Stripe integration. Usage monitoring tracks consumption against quoted limits, visualized through dashboards for the customer.

Quoting Flow

Core BDR workflow. Most complex surface in the product.

Company Onboarding

Pricing and rate configuration. The invisible product.

Where design met product complexity

Quote to contract parity

The same data needed to work as a live interactive tool for the BDR and as a formatted exportable PDF contract. Every increase in deal complexity put pressure on both. As multi-year scheduled changes and custom rates became standard, keeping the two in sync without degrading either became an ongoing constraint.

Company onboarding had no ceiling on edge cases

Each new customer revealed a pricing model that needed to be absorbed without breaking what already worked for everyone else. Automatic overrides on top of manual overrides on top of tiered rates. The system had to be robust enough to accommodate all of it while remaining self-service.

No roadmap, only customer requests

The product direction changed with every new customer signature. Two founders had different views on building a defined roadmap versus responding to requests. Designing for scale requires stability in direction. That tension was unresolved when I left and it shaped every design decision in between.

Quote to Contract Flow

A flow or diagram showing the complexity of quote to contract parity or onboarding configuration.

Pragmatic over comprehensive

The system was built to move fast, not to be complete. No documentation, but enough shared foundations that no one was rebuilding pages from scratch.

The most consequential decision was building explicit interaction states into every component. Junior engineers on the team removed hover and focus states if they were not shown in the designs. I built them directly into components as prototype interactions. Not as polish but as the only reliable way to make sure they shipped.

Design System Components

Component library showing interaction states, autolayout structure, or the foundations built.

The design counterpart the team needed

The pattern was consistent. The CEO and CTO would bring a customer's pricing model and ask me to accommodate it without breaking existing flows. Absorbing new requirements without regression defined the majority of the design work over 2.5 years.

The founders pushed back on inline formula support in quoting. I believed BDRs needed to calculate rates directly in the quote. It shipped. Users told the founders it was their favorite feature.

Inline Formula Feature

The inline formula feature in the quoting UI. The POV moment.

From manual to self-service

3 wks

To onboard a mid-size company. Down from 3 months.

25+

BDRs per company onboarded in that window

Customer growth over 2.5 years

Customers compared MonetizeNow favorably to Salesforce, HubSpot, and DealHub on ease of use. Clean without clutter, fast adoption within BDR teams after launch. The feedback was consistent across every new customer.

Ten percent craft, ninety percent everything else

Design lead, design practice builder, and product contributor. The getting your hands dirty part was ten percent of this role. Planning, communicating, and strategizing was where the work actually lived.

The clearest thing this taught me is that feature requests are not a product strategy. Roadmaps exist so products can evolve with intention, not just react to whoever signed last. Design has a bigger influence on that than most teams realize until it is missing.