We wanted to end the year with a look back on what we shipped and what we learned as we head into 2026.

2025 was about listening to real teams - the people who live in Confluence, Jira, and monday.com every day - and systematically solving the friction points that make their work harder than it needs to be. From the chaos of fragmented calendars to the pain of bulk-approving dozens of pages one at a time, we built solutions for problems that actually matter.

We expanded from Confluence into Jira and monday.com, earned enterprise certifications, won a prestigious developer award, and shipped a platform evolution that fundamentally matured what Capable can do. But more importantly, we proved that a focused team solving real problems can earn marketplace trust, platform recognition, and the foundation for scaled growth.

Here's what 2025 meant for Capable - month by month.

January opened with a focus on the most fundamental problem teams face: information chaos. Documentation pages pile up without organization, team members waste hours digging through outdated content, and approval workflows feel like bureaucracy instead of progress.

Capable shipped Saved Searches to let teams capture complex queries and reuse them - turning recurring searches into saved shortcuts.

Simultaneously, the Progress Bar macro gave visual representation to workflows that were invisible before.

These solved the daily friction that drains productivity by making information more visible and traceable.

In February, it was announced we won first place in Codegeist 2024 in the Teamwork Foundations category, which validated Capable's approach to a specific customer pain point: visual asset sprawl.

Teams maintain brand assets, diagrams, and screenshots across Confluence, but there's no way to organize, control, or reuse them at scale.

Capable Images won because it solved this real problem elegantly. We hosted a webinar with other first-place winners to discuss the lessons learned - and cemented Capable's credibility as a company that understands real team problems.

In March, we launched Publishing Workflows as an included feature for Approval for Confluence and as a standalone product, Publishing for Confluence, which solved the gap between editorial intent and reality.

Marketing teams create content in Confluence, but without approval gates and publish workflows, content sprawls across spaces uncontrolled.

Publishing Workflows created a pipeline: draft → review → publish, with configurable approvers and automatic publication. This brought editorial discipline to knowledge work without adding unnecessary friction.

During April, we attended Atlassian Team '25, where Capable was nominated as a finalist in two categories for the Atlassian Partner Awards 2025: Teamwork Foundations and AI Innovator.

More importantly, Capable participated in Partner Accelerate - the exclusive program for Atlassian's most strategic partners.

This wasn't just recognition; it was access to Atlassian's strategic roadmap, direct feedback on product direction, and validation that Capable had evolved from a point solution into a platform player.

In May, we launched the New and Improved Calendars for Confluence product, which unifies multiple sources into a single source of truth inside Confluence. Marketing deadlines now align with team availability. Project milestones won't collide with scheduled leave.

We also gained the Atlassian Cloud Fortified Certification, which sent a different message: security, compliance, and reliability aren't afterthoughts. Capable passed Atlassian's bug bounty program, demonstrated 99.9% uptime, and committed to 24-hour response times. Enterprise customers could now deploy Capable for mission-critical workflows without worrying about infrastructure vulnerabilities.

In June we released several new features focused on improving your ability to manage content at scale.

Publishing and Approvals Dashboards provided users with a centralized hub for managing their content. They could filter by date, status, or team, identify which approvals were pending, and gain insights into publication patterns or issues, all from one convenient location.

‍Explorer for Confluence solved the inverse problem: instead of asking "what can I find?", teams could ask "what exists and who needs to see it?" Advanced search with filters and bulk actions prevented knowledge bases from becoming dumping grounds. Even better, it's free to use for everyone!

Workflow Hub for monday.com (June 2025) expanded beyond Confluence into monday.com - recognizing that teams using monday for project management also needed approval workflows and automation.

The Diagramming Improvements for Confluence (released in July) addressed the small friction points that compound over time. The update shipped four meaningful improvements:

"Start from Scratch" Screen got a complete redesign - instead of a blank canvas, users now see an intuitive entry point with visual guidance. This matters more than it sounds: when teams create 50 diagrams a month, that entry moment repeated thousands of times either delights or frustrates. The redesigned screen solved "I can't remember how to start a diagram" problem.

Auto-Save for Visual Editor Libraries meant teams no longer lose diagram components between sessions. Previously, if you created a custom shape library for your org, you'd have to reload it each time you edited a diagram. Now libraries persist automatically. For teams building standardized architecture diagrams or process flows, this eliminated repetitive setup work.

AI Support Expanded Beyond Mermaid - Capable added PlantUML and DBML to its AI-assisted diagram capabilities. This was critical because different teams use different diagram languages: systems engineers prefer PlantUML for UML diagrams, database teams use DBML for schemas, and data teams rely on Mermaid. By supporting all three, Capable became the universal diagram tool rather than a Mermaid-only player.

Diagram Rendering Fixes addressed real frustrations. The 'click' functionality in Mermaid diagrams now works correctly, letting users turn flowchart steps into clickable navigation. PlantUML diagrams with multiple root nodes now render properly. These sound technical, but they represent the difference between "the tool almost does what we need" and "the tool does exactly what we need."

In August, we launched new Capable Macros to improve productivity and collaboration in Confluence:

Cards Macro solved a visual organization problem. Teams need clean, grid-based layouts for content—product tiles, team member profiles, service offerings - but Confluence's native options were limited or required custom HTML. Cards Macro provided drag-and-drop card layouts with automatic responsive behavior. Suddenly, marketing teams could create product showcase pages without engineering support. Sales teams could build client comparison pages without design cycles. The simplicity was powerful.

Web Extract Macro addressed data duplication. Operations teams pull data from external websites and APIs and paste it manually into Confluence for status updates. This copy-paste creates drift: someone updates the external system but forgets the Confluence page, or the data ages silently. Web Extract Macro embedded live data directly - pull current metrics from external APIs, websites, or services. Status pages stayed synchronized without manual maintenance.

Advanced Table Macro fixed the limitation that Confluence's native tables lack sorting, filtering, and pagination. Data teams managing large datasets in Confluence hit this wall constantly: a pricing table with 100 SKUs, a features comparison with dozens of dimensions, a customer list that grows monthly. Advanced Table added Excel-like functionality directly in Confluence—sort by column, filter by criteria, paginate large datasets, export to CSV. Suddenly, teams stopped treating Confluence as a documentation tool and started using it for light data management.

These three macros fix the friction points many teams face in Confluence and result in less switching tools.

September signaled Capable's transformation from Confluence-centric to multi-platform.

Diagrams for Jira solved a critical developer problem: engineers need to create flowcharts, system diagrams, and architecture views without context-switching. Now they can drag-and-drop diagrams directly into Jira issues, with full Excalidraw, Mermaid, and PlantUML support - enterprise-grade, just like the Confluence version.

Markdown for Jira addressed technical documentation chaos. Engineers write markdown in one place, but when they need to reference it from multiple Jira issues, they copy-paste and create drift. Markdown for Jira lets teams write once, embed everywhere - with live preview and Mermaid diagram support.

Bulk Approve/Reject tackled the most egregious workflow pain: approving dozens of Confluence pages one at a time. Now teams batch-process in seconds while maintaining complete audit trails. For knowledge base managers, this cuts hours of tedium per week.

October was a month of validation, we gained Atlassian Rising Star status on the Atlassian Marketplace and we solidifed our leadership in Confluence diagramming.

Atlassian Rising Star Status meant Capable had proven rapid growth, strong adoption, and consistent user satisfaction. The designation positioned Capable as a candidate for Spotlight status—recognition reserved for market leaders.

Diagram Library Leadership established Capable as the standard for Confluence diagramming by supporting every major diagram format (Excalidraw, Mermaid, PlantUML) with unmatched library integration.

The launch of Capable for Confluence 2.0 in November wasn't incremental, we released a lot of requested features that had been requested over previous months and improved reliability:

GitHub File Embedding solved developer friction: code documentation now lives in Confluence, synchronized with GitHub, with syntax highlighting intact. No more stale markdown files drifting out of sync with source repositories.

Approval Authentication Tokens with TOTP addressed enterprise compliance: approvals require verification codes from authenticator apps, preventing impersonation or unauthorized changes. For regulated industries—finance, healthcare, legal - this became a compliance requirement, not a nice-to-have.

Granular Capability Control let enterprises customize interfaces - hiding unused features, reordering capabilities. This eliminated the "we don't use half these tools" complaint that plagues complex apps, making the interface feel tailor-made rather than bloated.

Bulk Publishing with Orchestration transformed from "hope this works" to "reliably publish hundreds of pages with audit logs and retry logic." Large-scale content operations became viable when you could publish 500 pages with automatic retry on failure and detailed logging of what happened.

Capable Diagram AI 'Ask' feature added intelligence: "What step comes next?" and "Generate a flowchart from this process description." Not flashy, but genuinely useful for teams drowning in undocumented processes.

Approval Data Integrity with tamper detection addressed audit requirements: approval records can't be forged or altered retroactively. Compliance becomes auditable when the system guarantees integrity.

Migration Tools for competing apps (Mermaid/Stratus, AppFox, GitHub Macros) removed switching barriers. Teams could leave competitors without data loss or manual migration hell.

Performance across the board made everything snappier, reducing the friction that compounds over time and erodes user adoption.

This was platform maturation - the difference between a growing app and a professional solution enterprises deploy for critical work.

By December, Capable had expanded to three platforms (Confluence, Jira, monday.com), achieved enterprise certifications, earned marketplace recognition, and built the foundation for scaled growth.

We spent December focusing on strategy and planning for the following year, with a change freeze from December 1 - January 8 on new features while we plan the year ahead.

The Pattern Behind 2025

Capable didn't ship features; it solved problems at the point of friction:

Chaos → Clarity (saved searches, dashboards, explorer)
Fragmentation → Unification (calendars, bulk workflows, markdown integration)
Friction → Automation (macros, bulk operations, AI-assisted diagrams)
Trust gaps → Certification (Cloud Fortified, approval data integrity, tamper detection)
Switching costs → Migration tools (removed barriers to adoption)

The year demonstrated a company that listened to real teams, understood where their work broke down, and built solutions at scale across multiple platforms. By December, Capable had evolved from a promising Confluence extension into an enterprise platform trusted for mission-critical workflows.