Building Strive V2: Prioritising People Who Actually Ship

Building a software product for publishers requires more than just adding buttons to a dashboard. It demands a deep understanding of how professional teams coordinate, review, and publish their work. We are currently developing the next iteration of our plugin to solve the structural problems that plague modern content operations.

What is Strive V2?

Strive V2 is the upcoming evolution of our WordPress plugin, designed to serve as a central hub where publishers and their teams can orchestrate complex publishing workflows.

We are moving beyond the basic constraints of simple scheduling. When we look at how professional teams operate, it is clear that they do not just need another place to dump text. They require a dedicated space to manage the entire lifecycle of an article, from the initial pitch to the final copyedit. This evolution is about providing a structured environment that respects the complexity of professional publishing. We are building an environment where visibility and accountability are baked into the core experience.

For too long, WordPress users have had to cobble together external tools just to know who is working on what. By bringing these operational layers directly into your content management system, Strive V2 aims to eliminate the constant context-switching that drains productivity. It is about creating a workspace that feels native to your writing environment while offering the robust project management capabilities that serious editorial teams demand.

The Current State of Content Operations

The publishing industry has a strange obsession with volume. Everywhere you look, there is a push to generate more articles, faster, with less human involvement. Tools are increasingly focused on mindless automation rather than quality, treating the act of publishing as a mere numbers game. We fundamentally disagree with this approach. Producing a massive amount of low-quality material does not serve your readers, and it certainly does not build a sustainable brand.

Publishers are overwhelmed by disjointed systems. They have one spreadsheet for planning, a separate chat application for coordinating, and a messy WordPress backend for the actual writing. This fragmentation leads to missed deadlines, inconsistent quality, and frustrated teams. When your tools do not communicate with each other, your team cannot communicate effectively either. The friction of moving between different platforms introduces errors and slows down the entire operation.

There is a growing need for structured, reliable workflows. Teams need to know exactly what stage an article is in, who is responsible for the next step, and whether the piece meets their internal standards before it goes live. Without this structure, you are just guessing. We believe that software should enforce these standards naturally, removing the friction from the process and allowing editors to focus on what they do best: shaping excellent material. This is why we are building reliable editorial infrastructure that supports quality over sheer quantity.

Why We Chose the Central editorial hub Model

Content teams need orchestration, not just more features. Adding a dozen new buttons to a dashboard does not make a team more efficient; it just makes the interface more cluttered. What teams actually need is a unified system that governs how work moves from an initial idea to a published piece. An central editorial hub provides this governance, acting as the central nervous system for your publishing efforts.

A editorial hub centralises visibility and accountability. By treating your publishing workflow as a distinct operational layer, you gain a bird's-eye view of your entire operation. You can see bottlenecks before they become crises. You can identify which authors need support and which articles require a final review. It brings order to the inherent chaos of managing multiple writers and editors. When everyone logs into the same system and sees the same truth, accountability happens naturally.

This model respects the complexity of professional publishing. It acknowledges that an article is rarely written in a single sitting by a single person. It goes through drafts, revisions, fact-checking, and final approvals. An central editorial hub provides the scaffolding for this collaborative effort. It is the foundation upon which high-functioning teams build their daily routines, ensuring that nothing slips through the cracks and every piece of content is given the attention it deserves.

Defining Human-Governed AI in Workflows

Artificial intelligence is a tool, not an author. In our view, AI should act as an assistant, not a replacement for editors. The industry's rush to automate the writing process entirely has led to a flood of mediocre, untrustworthy material that clutters the internet. We are taking a different path, focusing on how technology can support the rigorous standards of professional journalism and content marketing.

Human oversight is non-negotiable for trustworthy content. If you want your audience to trust what you publish, a human must be accountable for every word. We are focusing on human-governed AI—systems that assist with research, suggest structural improvements, and help with formatting, but always defer to the judgement of a human editor. The final decision must always rest with a person who understands the nuance of your brand's voice and the specific needs of your audience.

We are building tools that support, rather than bypass, editorial judgement. For instance, AI editorial briefs (which are currently in the works for a future release) will help editors outline articles more efficiently, providing a strong starting point for writers. But these briefs will still require a human to review, refine, and approve them. By keeping the human in the loop, we ensure that the technology serves the editorial process, rather than dictating it. This approach protects the integrity of your publication while still leveraging modern capabilities.

The Role of a Visual Content Calendar

A clear overview is essential for managing multiple authors. When you are coordinating a team of writers, you cannot rely on a standard list of posts in the WordPress backend. You need to see how your publishing schedule looks over the course of a week, a month, or a quarter. Without a visual representation of your pipeline, it is nearly impossible to balance your content mix or spot upcoming gaps in your schedule.

Strive's WordPress content calendar provides immediate clarity. It transforms your backend into a visual workspace where you can see exactly what is scheduled, what is in progress, and what is falling behind. Colour-coded statuses give you a quick read on the health of your pipeline, allowing you to make informed decisions at a glance. You can immediately spot if you have too many opinion pieces scheduled for one week and not enough tutorials.

Drag-and-drop functionality makes rescheduling effortless. If a breaking news story requires you to push a planned feature to next week, you simply drag the card to the new date. The system updates the underlying WordPress data automatically. This visual approach removes the friction from managing a dynamic schedule, ensuring that your team can adapt to changes quickly without losing track of their overall strategy.

What is in the Works for V2

We are entirely focused on building tools for people who actually ship. This means prioritising features that solve real, everyday problems for editors and publishers who are in the trenches managing content pipelines. We are not interested in building flashy gimmicks; we want to build robust systems that make your daily work easier and more predictable.

We are currently developing workflow-aware automation to reduce repetitive tasks. This is on the roadmap and will allow the system to handle routine actions—like notifying an editor when a draft is ready for review—based on the specific stage of your pipeline. It is about automating the process, not the writing. By removing the manual administration of moving a piece through the pipeline, your team can spend more time focusing on the actual text.

Here is a look at what we are prioritising on our roadmap:

1. Workflow-aware automation: Triggering notifications and state changes automatically as articles move through the pipeline (in the works).
2. AI editorial briefs: Assisting editors in creating structured outlines directly within the WordPress interface, always under human supervision (on the roadmap).
3. Content Refresh Radar: Identifying decaying articles that need updating to maintain their relevance and accuracy over time (coming to Strive).
4. Editorial readiness review: A pre-flight check system to ensure all requirements are met before an article is permitted to go live (in the works).
5. Enhanced interoperability: Deepening our integration with the WordPress core and custom post types to ensure seamless data flow.

These upcoming features are designed to enhance your existing processes, providing a more robust foundation for your publishing efforts.

Here's how you'd do this in Strive

While we are busy building the future, Strive already offers a comprehensive suite of tools to manage your workflow today. Let us look at how you can manage your pipeline right now using our Editorial Post Statuses.

Instead of relying on WordPress's default "Draft" and "Pending Review," Strive allows you to implement a custom editorial pipeline. You can define statuses that reflect your actual process—such as "Not Started," "Writing," "Editing," and "Ready to Publish." This granular control means your software finally matches your reality.

When a writer finishes their draft, they simply change the status to "Editing." This updates the visual calendar, changing the colour of the post card and instantly signalling to the editor that the piece is ready for their attention. You can pair this with our Repeatable Post Checklists to ensure the writer has completed all necessary steps—like adding a featured image, formatting headers correctly, and writing an excerpt—before handing it off. This shipped capability brings immediate order to your operations, ensuring everyone knows exactly where every article stands at any given moment. You can learn more about configuring these pipelines and checklists in our Knowledge Base.

Our Commitment to Editorial Readiness

Every feature we build is designed to ensure content is truly ready before publishing. We do not believe in hitting the publish button and hoping for the best. Professional publishing requires rigorous quality assurance. When an article goes out to your audience, it carries your brand's reputation with it. That is a responsibility we take seriously, and our software reflects that gravity.

We prioritise systems that enforce standards naturally. Whether it is through checklists that must be completed before an article can be scheduled, or visual indicators that highlight missing elements, our goal is to make it difficult to publish a mistake. We want to give editors the confidence that when a piece goes live, it represents their absolute best work. Publish-ready quality is not just a final check; it is a philosophy that permeates every stage of the writing process.

We are building infrastructure that scales with your editorial ambitions. As your team grows and your publishing frequency increases, your tools need to keep pace. By focusing on stringent quality controls, we ensure that your standards do not slip as your volume grows. We are creating a system that supports your pursuit of excellence, providing the structure and visibility required to maintain a high-quality publication week after week, month after month.

Frequently asked questions

What makes Strive different from basic scheduling plugins? Strive operates as a comprehensive central editorial hub that manages the entire lifecycle of an article. Rather than just assigning a date to a post, it governs how work moves from planning and writing to editing and final publication, providing deep visibility into your entire operation.

Does Strive write articles for me? No. We champion human-in-the-loop AI. While we are exploring AI tools for outlining and research—which are currently on the roadmap—we firmly believe that human editors must remain in control of the actual writing and final approval. Technology should assist, never replace, the human editor.

Can I customise the workflow stages to match my team? Yes. Strive includes custom editorial post statuses that allow you to map the software exactly to your team's specific process. This ensures everyone knows exactly what stage an article is in, eliminating confusion and reducing the need for constant status updates.

Will Strive V2 work with my existing WordPress setup? Absolutely. We are building V2 to deeply integrate with the WordPress content model. This ensures seamless interoperability with your existing themes, custom post types, and block editor configurations without requiring you to rebuild your site.

How does the visual calendar help my team? The calendar provides a unified, colour-coded overview of your entire publishing schedule. It allows you to drag and drop posts to reschedule them effortlessly, giving you immediate clarity on your pipeline's health and helping you spot bottlenecks before they delay your publications.

Ready to plan, review, and ship? Start your 14-day free trial.