Extended Long Term Support Working Group (ELTS)

A call to finalize details of the ELTS program.

• initial pricing and discount model
• decide sales platform (at least short-term) incl. invoicing
• set up sales platform
• starting date
• any legal stuff
• marketing stuff (website, blog post, webinar, ...)
• exact purchase form fields

and for mid-term:

• final sales platform
• enforcement (if any)
• more active selling
• final pricing and discount model

Attendees

• Ruth Cheesley
• Ekke Guembel

Notes from this meeting

• Ruth's designed a page on the new site https://mauticstaging.com/extended-long-term-support-elts/ - Ekke also has something designed on their website to share with clients - https://leuchtfeuer.com/mautic/update-strategie so we can use this content as a basis to start from.
• Initial pricing
• 1 year - USD 2000,-
• 2 years - USD 3000,-
• Initial discount model
• we want to encourage higher membership levels
• we want to motivate members to sell the ELTS
• Community tier: 10% discount per instance
• Bronze tier: 15% discount per instance
• Silver tier: 20% discount per instance
• Gold tier: 25% discount per instance
• Platinum tier: 30% discount per instance
• Diamond tier: 35% discount per instance
• Decide sales platform (at least short-term) incl. invoicing
• minimize extra fees
• hide the discount to end users - just keep the basic 'there is a discount' and have it stated on the membership benefits page
• If we used Open Collective we could make a project with tiers for each corporate membership tier which would allow us to get up and running quickly.
• So... we start with Open Collective .
• set up sales platform
• Open Collective - straight forward.
• Hubspot - for simple support and inquiries
• starting date
• 1.1.2025 for the ELTS
• Start selling it: ASAP
• any legal stuff
• Draft of T&Cs here: https://docs.google.com/document/d/1W5gLr61FB72_sNsjcdf4D2SVzURfdEZ3-rsM_NyDE6o/edit?usp=sharing
• marketing stuff (website, blog post, webinar, ...)
• prior to new website: static page on mautic.org
• blog post to announce availability
• exact purchase form fields
• ask only minimum question during purchase (Open Collectivce default fields anyway)
• follow up with mandatory fields afterwards (like progressive profiling :)
• github handle
• main URL
• instance id