From Internal Build to Public Release: The Presstack Pre-Launch Roadmap
Presstack didn't start as a product pitch. It started as a real problem to solve, a WordPress site that builds itself, writes its own content, handles its own SEO, and stays ready for the next wave of AI search. That problem turned into a platform. Now the platform is almost ready for you. Here's exactly where things stand, what's already working, and what you need to do if you want in before the doors open properly.
What's Already Built and Running
The core of Presstack isn't a pitch deck or a wireframe sitting in someone's Notion workspace. Cleo, the AI writing engine, is live and producing content in internal testing right now, generating structured blog posts that vary in opening, pacing and format so nothing reads like it came off a production line. The schema layer is equally mature, outputting a unified JSON-LD graph per page that covers organisation, services, articles and FAQs, with entity links back to Wikidata so the site connects to the broader knowledge graph rather than floating in isolation. That's not a feature planned for a later sprint. It's running.
The MCP endpoint, llms.txt output and agent.json manifest are also live. That means AI assistants and answer engines can already surface a site's content and capabilities rather than being walled out. Blueprints, the system that lets you design a page once and clone it across service and location variants automatically, have been tested across multi-location service setups. Content styles, which control whether a post sits in evergreen mode, carries a light brand mention or writes as a problem-solving guide, are configurable and firing on a schedule.
The pieces that tend to take longest in a WordPress AI plugin pre-launch roadmap, the foundational architecture and the AI integrations, are the parts already done.
The Architecture Behind Presstack
Why a single data layer matters
Most tools in this space solve one problem well and leave you to stitch the rest together yourself. You end up with a page builder, a separate SEO plugin, a content tool that knows nothing about your schema, and an AI assistant that has no idea what your business does. Each piece works in isolation, but they never share context, so the left hand has no idea what the right is doing. That fragmentation is exactly what Presstack was built to avoid from the start, and it shaped every architectural decision made during the build phase.
The reason Presstack covers build, content, SEO and the WordPress WebMCP agent surface inside one coherent system is not ambition for its own sake. Those four layers depend on each other in ways that matter at runtime. Schema needs to know what services exist on the site. Content needs to know what keywords are already covered so it does not cannibalise itself. The agent surface needs live access to the same business data that feeds the schema and the copy.
Build all of that in separate products and you spend most of your energy maintaining the bridges between them rather than improving what they do. One shared data layer, one AI with full context across the whole site, is what makes the system reliable rather than just capable.
Presstack Lite vs Full
Starting with what you already have
Presstack Lite arrives as a plugin that drops straight into an existing WordPress installation, sitting alongside whatever page builder you already use, whether that's Elementor, Bricks or something else entirely. It adds the AI and SEO engine without touching your current design or forcing a rebuild. If you've spent months getting your layout right and have no appetite to start over, Lite is the path that makes sense. Your content, widgets and brand setup stay exactly where they are.
Building from scratch
Presstack Full is the complete package, theme, platform and AI in a single coherent system built to work together from the ground up. It suits anyone starting fresh, migrating from a different platform, or who wants the whole stack, including the WordPress WebMCP agent surface, schema mapping, Blueprints and the full widget library, without stitching together separate tools.
The honest distinction is scope rather than quality. Lite gives you the intelligence layer on top of what you own. Full gives you the intelligence layer with the structure designed around it. Most existing site owners will find Lite the lower-friction entry point, while anyone building new will get more from Full from day one.
The Pre-Launch Window
Pricing and what locks in now
Pricing locks at the rates set on launch day. That matters more than it might seem, because once the platform reaches general availability and the feature set broadens, those rates will reflect the fuller product. Joining now means you carry the launch pricing forward, not the post-release one.
Influence over the roadmap
The pre-launch period is where the feedback loop is tightest. When a handful of sites are running on the platform rather than thousands, questions get answered properly and product decisions still bend toward what early users are actually encountering. A local service business that notices a gap in how the WordPress WebMCP endpoint surfaces booking intent, for example, can raise that directly and see it addressed before it becomes a buried support ticket.
That kind of influence over the roadmap disappears quickly once general release opens the doors wider. Getting Presstack running on your site now means you have a working system, locked pricing, and a genuine seat at the table while the product is still listening closely.
How to Secure Early Access
Visit the early access sign-up page and submit your details. You'll receive a confirmation email within a few minutes, and that email is your placeholder in the queue. Onboarding is staged rather than open-door, which means each cohort gets proper setup support instead of being handed a login and left to figure things out alone. If you're already running a WordPress site with an existing page builder, Presstack Lite slots in without forcing a rebuild, so there's no need to clear your schedule for a migration weekend before you can get started.
Within the first 48 hours you'll get access to the platform, a brief onboarding sequence that walks through connecting your site and setting your brand configuration, and your first look at Cleo. At that point she's ready to start writing and optimising, not as a demo but against your actual business.
Early access members also feed directly into the product roadmap. The feedback collected in these first cohorts shapes what gets prioritised before full public release. You get the platform ahead of the crowd; the team gets the real-world signal that makes the finished product sharper for everyone who follows.