Why Envello locks your price for 24 months
Your tier price is locked for 24 months from the day you sign up. Not a promotional rate that reverts after three months, the actual price, held for two years. This is published on the pricing page, not something you find out about after a renewal notice lands in your inbox.
What happens after 24 months
Any future price change comes with 6 months' notice and a grandfathering option, meaning you can choose to stay on your old price rather than being forced onto the new one immediately. That's the actual mechanism, not a vague "we'll let you know" policy.
Why this is worth publishing specifically
Providers in this space have been known to double prices overnight, with little warning and less recourse. Teams building long-lived integrations remember that, and it shapes which vendors they're willing to build deep dependencies on. Publishing specific numbers (24 months, 6 months' notice, a grandfathering option) rather than a general trust statement is the point: a vague promise costs nothing to make and nothing to break.
What the pledge doesn't cover
Worth being precise about the boundary: the pledge locks your tier's price, not the tier's included volume or feature set forever. If a tier's included email volume or feature list changes, that's a product change, not a price change, and it isn't covered by the same 24-month clock. What is covered: the euro amount you pay for the tier you're on, for as long as the pledge's terms hold.
It also doesn't cover usage-based overage rates moving independently of the base tier price. Overage pricing is published separately (see the hidden-costs post on this blog) and reviewed less frequently than most SaaS billing line items, but it isn't contractually frozen under this specific pledge the way the base tier price is.
How this compares to a typical SaaS repricing
The more common industry pattern looks like this: existing customers get moved to new pricing at the next renewal with 30 days' notice, sometimes less, and no option to stay on the old rate. That's technically "notice," but 30 days rarely gives an engineering team enough runway to renegotiate a contract, migrate to a competitor, or even get budget sign-off for the new number before it takes effect.
Six months and a grandfathering option changes the shape of that decision entirely. A team on a 6-month runway can plan a migration deliberately if the new price doesn't work for them, or simply choose to stay grandfathered and keep building. The mechanism matters more than the marketing language around it: a pledge is only as good as the specific numbers backing it.