It might feel a bit early to talk about pricing for Flint, but we know it’s a core part of how people evaluate products, even in testing. A free sample of something expensive feels different from one that’s cheap. Price tags shape our perception.

We're dissatisfied with how SaaS pricing has evolved. Complex plan structures, countless add-ons, and hidden extras make understanding the true cost of many products nearly impossible. While we understand the logic behind this complexity, we're committed to taking a simpler approach with Flint.

We operate with limited ambition, which is why we want to create a pricing structure that makes sense for both our users and ourselves from day one. It should reflect the value Flint provides, not your company size or how many seats you need.

Plus, we do not want to fall for the "growth for growth's sake" trap. We're building a radically simple product, and we would not want users to see this simplicity as an indicator of low quality. Flint's unshiny-ness is a deliberate choice on our part. But, at the same time, it hints at how we try to stay within our mindset, not going big or glossy to justify yet another future pricing tier.

During the closed beta, we’ll finalise pricing with input from our beta users and broader network. Once you’ve had a real sense of what Flint offers and where we’re headed, we’ll shape a pricing model that’s transparent, context-free, and built to support Flint's further development.