@scottvonduhn Thanks, I understand you concerns. SuiteBilling addresses perpetual / evergreen contracts and while it does not "force" and end date for evergreen (as most SaaS modeled companies are aiming to become, including my client which has annual subscription with evergreen clauses), estimated end dates are needed when evaluating multi-element arrangements based on fair values. And estimated end dates are simply estimates - you do not need to contractually perform this obligation until the end dates, enhance not on the contract, but management needs to make assumptions and forecast based on prevailing average customer life. For example - You sold Evergreen SaaS, perp license, and PS, with PS heavily discounted - How do you treat the carve-in and out of rev to PS lines from your SaaS lines, per your fair values? If you are a company with homogenous products/fair values and more retail consumer focus, I understand there may not be a definitive need. But for my enterprise facing clients doing larger dollar deals and/or acquisition heavy companies that acquire multiple product lines (enhance additional FVs by product groups/lines), then subsequently upsell/combine with existing product lines, using ARM is a serious consideration. As far as customers terminating at will, SuiteBilling addresses modifications via Change orders of varying kinds. Multiple changes (pricing, qty, new items), suspensions, terminations, per subscription item per monthly billing cycle are accomplished through change orders, if you date them accurately, and will reflect proper entitlements when renewals are generated (low touch or high touch renewals). Currently en mass change order updates are not yet available via the user interface but it is available for mass updates via csv imports. Automation can be introduced here until NS prod dev rolls out this feature.