Slater New
« back to Blog

Navigating the Future of Slater: A Community Discussion

Slater Team

Choosing a pricing model has been tricky, but we value the community's thoughts. Here are some we've received so far!

Unpacking Pricing Strategies, User Experience, and the Power of Collaboration


In a recent community discussion, the team behind Slater, a tool for web development, engaged in a candid conversation about the platform's future. The dialogue spanned topics from pricing strategies to the importance of team collaboration, revealing the collective vision for Slater's growth and development.

The Slater Pricing Model: A Three-Tiered Approach

Mason, proposed a three-tiered pricing model for Slater. The model includes a basic plan at $10 per month per user, a $100 plan offering additional help and consulting, and a $1000 plan providing on-demand JavaScript service. This structure aims to cater to a wide range of user needs, from basic access to comprehensive support.

Location-Based Pricing: A Consideration for Global Accessibility

Berno brought up the idea of location-based pricing, highlighting the need for cost considerations across different markets. This approach, known as purchase price parity, could make Slater more accessible to users worldwide, particularly in markets where costs often perceived as trivial in the US or Europe may be prohibitive.

The Free Tier: A Gateway to Full Potential

Théo Roland suggested the introduction of a free tier with limited projects, similar to platforms like Code Sandbox and Webflow. This approach would allow users to explore the full scope of Slater's possibilities within a limited project framework, providing a taste of the platform's capabilities before committing to a paid plan.

The Team Aspect: Enhancing the Slater Experience

Kabarza emphasized the importance of the team aspect in using Slater, suggesting that collaborative work is one of the platform's main benefits. He also cautioned against the complexity of pricing models like Webflow's, advocating for a simpler, more straightforward approach for Slator.

Shared Resource Model: A New Approach to JavaScript Support

In response to Kabarza's points, Mason discussed the idea of a shared resource model for JavaScript support. This model would operate as a pooled resource, with capacity fluctuating based on the needs within the pool. The concept aims to balance flexibility with the reality of resource limitations.

Investing in Community: The Power of Collaboration and Education

Mason also touched on the potential for investing in courses created by community members. This approach would not only provide valuable training resources for users but also foster a sense of community and collaboration. Théo Roland, who has created a mini-series on YouTube about Slater, expressed his willingness to contribute to such efforts.

This community discussion illuminated the collective vision for Slater's future, highlighting the importance of user feedback, collaboration, and accessibility in shaping the platform's development. As Slater continues to evolve, these conversations will undoubtedly play a crucial role in its trajectory.

Try it out for yourself

Sign up for a free trial and see if Slater is for you.

Share this post

We are building a first-class development experience that bridges together code and no-code.