MonetizeNow is a quote-to-cash platform for BDR teams. It covers 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 get the first deals out the door. Every new customer revealed a pricing model the system had never seen before. The work was less about polishing screens and more about building a platform that could absorb edge cases without breaking what already worked.

The product only works when all five surfaces connect. Company onboarding is the invisible product: before a BDR sends a single quote, the company loads products, pricing tiers, rates, and overrides. Every company's model is different, and designing for that flexibility without breaking the next customer was one of the core challenges.

Quoting is the primary BDR workflow: configure the deal, set rates, schedule changes, send via DocuSign, generate the contract. The quote and contract must stay 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 shaping every design decision.

Three constraints shaped the majority of design work over 2.5 years. They were never fully resolved, which meant every new customer forced a tradeoff between accommodating the request and protecting the platform.

The pattern was consistent: the CEO and CTO brought a customer's pricing model and asked me to accommodate it without breaking existing flows. Absorbing new requirements without regression defined most of the design work. Alongside that, I built a pragmatic design system, mentored a junior designer, and pushed for product decisions that would scale beyond the latest deal.

The system was built to move fast, not to be complete. No documentation site, no Figma library with full coverage. Enough shared foundations that no one rebuilt pages from scratch. The most consequential decision was building explicit interaction states into every component. Junior engineers removed hover and focus states if they were not shown in designs, so I built them directly into components as prototype interactions. Not polish, but the only reliable way to make sure they shipped.

Quoting was only part of the promise. A true quote-to-cash platform has to work after the deal is signed: tracking what closed, what is up for renewal, and whether revenue is landing the way the quote predicted. BDRs care about their own performance. Leadership cares about pipeline health, recognized revenue, and forecast accuracy. Both need visibility, but not the same view.

The dashboards were how we delivered that end-to-end experience. Not a bolt-on report exported to a spreadsheet, but performance and financial visibility inside the same product BDRs already worked in. I designed them so a rep could see how they were doing and a leader could see how the business was doing, without either group leaving the platform to find answers.

Customers compared MonetizeNow favorably to Salesforce, HubSpot, and DealHub on ease of use. Clean without clutter, fast adoption within BDR teams after launch. The clearest lesson from this role: feature requests are not a product strategy. Roadmaps exist so products evolve with intention, not just react to whoever signed last.