On October 6, our early-bird sale closed. The pricing went up, and yes, the future pricing will be higher too, as we promised. We’re a business, that’s reality.

But we wanted to pause and recognize what happened during early bird – because it exceeded our expectations in the best way.

What Early Bird Showed Us

The early bird period confirmed something we hoped for but couldn’t be sure of: there’s genuine hunger for professional visual development environments in WordPress.

You can see it in how our Facebook community of 2,000+ developers has developed – people are actually using Builderius, testing, reporting bugs, making feature requests. First production sites are appearing, people building out components and templates to see what works, some figuring out workflows before we even documented them.

We’re also seeing broader recognition. Our AI integration guide was featured by Search Engine Journal, while approaches we’ve built around since the beginning – like looping over APIs and JSON data, component-first development, and saved named queries – are starting to appear in other builders too.

What we delivered so far

We went from starting development to a complete professional development environment. That meant building out full HTML element access with custom attributes, a complete CSS workflow system with all selectors, CSS Variables, scoping and code mode, custom component creation with properties, a GraphQL dynamic data engine with IDE, advanced template conditions, smart forms, and a completely redesigned admin and builder area with built-in staging and releases – across 5 major releases.

What’s Coming Next

The early bird success gives us confidence to move forward with conviction, and clearer direction on what to focus on.

  • Immediate development priorities: Two-branch system so we can ship regular bug fixes while building new features without interruption. Components V2 and PHP 8.2+ support are next up. Follow our progress on our Roadmap & Changelog page.
  • Development approach: With the core architecture now solid, we can shift to more regular releases with shorter timespans. Instead of building entire systems from scratch, we’re now enhancing and extending what’s already there – which means faster development cycles and more predictable delivery.
  • Development philosophy: Regular releases doesn’t mean rushing features out the door. We’re here for the long run and prefer taking the time to build features you’ll actually want to use in 5 years, not quick implementations chasing whatever’s trending. Steady pace, solid implementation.

How to Get Support

Pro users: Email [email protected] with:

  • Site access credentials, or export a release and attach it
  • Clear explanation of what you’re trying to achieve
  • Screen recording for complex issues

Community (free) users: Use the Facebook group and WordPress.org support forum, we’re there as well as other users.

The more context you provide, the faster we can help solve your problem.

For Community Version Users

Free users are an important part of changing what modern WordPress development looks like. The Community version lets more people experience professional workflows and helps prove that visual development doesn’t have to mean compromising on code quality or flexibility.

We will be creating content specifically for Community users: tutorials on what you can build, best practices, and guidance on when upgrading makes sense. The free version should be a real tool for learning and building, not just a trial.

Community version is updated with every new release, it’s being actively worked on and improved.

Communication and Education Focus

This month marks a shift in how we communicate and educate. You’ll see:

  • Regular updates on what we’re building and why
  • Documentation rewrite focused on getting you productive quickly
  • Video content covering both getting started and advanced workflows
  • Clear roadmap communication so you know what’s coming and when
  • Marketing efforts to reach more developers who need these tools

How You Can Help Builderius Succeed

We all want this project to work. Here’s how you help make that happen:

  • Use it. Start with smaller projects, personal sites, experiments. Every site you build teaches us something about real-world usage we can’t get any other way.
  • Share your honest experience. When people ask about visual builders, tell them what it’s actually like to use Builderius. Authentic user voices carry more weight than any marketing we could do.
  • Help each other. You’ll discover workflows and solutions we never tested. Share that knowledge with other users and with us.

What’s Next

The foundation is solid. The community is growing. The early bird success proved there’s genuine demand for professional visual development tools.

We’re not trying to be everything to everyone. We’re building for people who care about clean code, professional workflows, and tools that grow with their skills. That focus is what got us here, and it’s what will carry us forward.

Early adopters made this possible by believing in the vision when it was still rough around the edges. Now we get to build what comes next.

Time to get back to work – there’s a lot more to create.