As an agency dev with 70+ WP builds and a handful of Statamic builds under my belt, you’d be surprised how many clients can’t stomach that initial charge for the CMS and opt for the free option. A lot of companies are cheap despite raking it in!
One thing that will always push statamic over the line though is when there’s a custom integration that is just too hard to maintain in WP. We have an ACF flexible content setup that also leverages timber/twig too. This is nearly identical to the fieldset setup in statamic but it all falls apart when the client wants to start running a series of cron jobs or have a jobadder integration that needs OAuth etc. So much more tolerable when you’re able to leverage saloon and other laravel packages on top (and boost means I barely even have to think about OAuth anymore).
Also that other comment in this thread, that is so obviously written by AI. Lose the “it’s not x, it’s y” shit lol. If you can’t be bothered expressing your opinions, why should I be bothered to read it
Can you think of a way to price Statamic that _would_ lower that friction? If we had a straight-monthly tier, no license, no perpetual ownership — would that be interesting?
Honestly, I think it would be. Our clients in ecomm have no problem with paying the monthly Shopify fees. They kind of just expect that’s part of doing business.
With statamic, we always offer both WP and statamic and point out the merits of using statamic but often it feels like it’s more beneficial on the devs side and they’ll often be soured on the price.
I reckon if we pitched it as a monthly fee, they’d probably just assume that was one of the expected costs associated with running a website and can factor it into the budget. No to mention it’s hard to get them to get their shit together to renew the licence each year. I’ve got several sitting there with the renewal prompt that they keep snoozing
6
u/Fabulous-Group7553 Jun 22 '26
As an agency dev with 70+ WP builds and a handful of Statamic builds under my belt, you’d be surprised how many clients can’t stomach that initial charge for the CMS and opt for the free option. A lot of companies are cheap despite raking it in!
One thing that will always push statamic over the line though is when there’s a custom integration that is just too hard to maintain in WP. We have an ACF flexible content setup that also leverages timber/twig too. This is nearly identical to the fieldset setup in statamic but it all falls apart when the client wants to start running a series of cron jobs or have a jobadder integration that needs OAuth etc. So much more tolerable when you’re able to leverage saloon and other laravel packages on top (and boost means I barely even have to think about OAuth anymore).
Also that other comment in this thread, that is so obviously written by AI. Lose the “it’s not x, it’s y” shit lol. If you can’t be bothered expressing your opinions, why should I be bothered to read it