Cost Estimator - Software Subscription Payment Term Options

Thanks, John Ferguson.
It's always great to see suggestions for improving our Cost Estimator. 🙂

Adding payment terms could be useful, but a lot of times, those terms are dependent on the MSP and their licensing vendor (i.e. Microsoft (direct), Pax8, Sherweb, etc.).

Out of curiosity, are you using the Cost Estimator quote to present it to your customer as-is or are you making a formal presentation similar to this one that Tony shared? Azure Proposal Template – Nerdio Help Center (getnerdio.com)

Hey Dave,

We're Microsoft direct but I would assume by adding various terms it would be possible to account for the majority of cases.  It would be great to be able to define our default term length in the Cost Estimator Defaults.

Currently, we do not present estimates directly out of Nerdio because it has the Pay-Up-Front pricing and this is usually a portion of the scope of services we are quoting a client.

Thank you

Thanks, John. 
Are you thinking something like this where you're able to set specific terms at each line-item level or more terms for the quote as a whole?

Dave Stephenson & John Ferguson I've had one or two other partners in just the last week or so asking for this to be added to the Cost Estimator!

Hey Dave,

In your SQL example, the options we have are:  3-Year (paid upfront), 3-Year (paid annually), 1-Year (paid upfront), 1-Year (paid monthly).  I'm not sure if this information can be pulled, then displayed, in the calculator?   If not, then we may want to keep it consistent such as Microsoft 365 and have options for Monthly, Annual, and add Triennial? 

Thanks, Frank and John!

I like the idea of just adding a 3rd radio button for tri-annual. That helps keep it consistent.

As long as we can pull those payment terms from the API, it "shouldn't" (famous last words, I know 🤣) be too difficult to display that information.
Worse-case we could do a simple calculation (i.e.Total/Time-Frame) to display the upfront vs yearly/monthly. The onus for honoring those payment terms would be on the partner/distributor to work out on the billing side. 

Frank Albani/John Ferguson, in any of the use cases you're describing, was there any request for payment terms on 3rd-party/custom line items or just the Azure items, for now?