1. Positioning & Outcomes

Ideal Customer Profile

Segment: Everyone

Primary buyer persona(s): Technical personnel, management

Primary app use case category:

• Content formatting & data visualization

• Software development

• Reporting & analytics

Top 3–5 use cases

• Visualize system architecture, sequence flows, and data models directly within Confluence documentation

• Standardize technical diagramming across engineering teams using text-based, version-controllable diagram source

• Eliminate diagram drift by keeping diagrams and documentation in the same page, automatically reflecting source updates

• Accelerate onboarding for developers and architects with always-current visual documentation of systems and workflows

• Support compliance and audit documentation with reproducible, text-defined diagrams (e.g., process flows, data flow diagrams)

Business outcomes / value drivers

• Business outcomes / value drivers

  • Time saved: Teams typically save several hours per week by editing diagrams as text instead of manually redrawing them every time a system or process changes — especially valuable for teams maintaining architecture docs, runbooks, or onboarding material.

  • Risk reduction / compliance gains: Keeps technical documentation trustworthy by ensuring diagrams stay in sync with the underlying design — reducing the risk of teams making decisions off outdated or inaccurate visuals.

  • Cost avoidance / consolidation: Removes the need for separate diagramming licenses (Visio, Lucidchart, standalone diagram servers) by rendering diagrams natively inside Confluence, consolidating tooling and cutting recurring software spend.

  • Consistency at scale: Standardizes how diagrams look and are structured across teams, projects, and departments — no more mismatched styles or one-off drawing tools per team.

• Industry-specific appeals:

  • Software & engineering organizations: A natural fit — architecture, sequence, and system diagrams are core to how engineering teams document and communicate design decisions.

  • Financial services & regulated industries: Appeals to teams that need clean, reproducible, audit-friendly documentation of processes and systems as part of governance and compliance workflows.

  • Public sector & enterprise IT: Useful for large organizations standardizing documentation practices across many teams and legacy systems.

Discovery Questions Recommendations

• "How does your team currently create and maintain technical diagrams (architecture, sequence, process flows) — and how do you keep them updated as systems change?"

• "Are your diagrams living in a separate tool from your documentation, and if so, how much effort does it take to keep them in sync?"

• "Does your team use text-based or code-like workflows (e.g., version control, CI/CD, docs-as-code) that a text-defined diagramming approach would fit naturally into?"

• "Who typically owns diagram creation today — is it developers, architects, or non-technical staff — and how comfortable are they with a syntax-based approach vs. drag-and-drop drawing?"

• "Do you have compliance, audit, or onboarding needs where consistent, reproducible technical diagrams matter?"

Bundling & attach guidance

Atlassian Collections fit:
What value does the app add to the Atlassian collections? How would you frame that value differently for the needs of each collection. Use the table below.

List typical attach patterns:

• • Often used alongside Confluence Premium/Enterprise, where documentation depth and technical content matter most.

  • Common in engineering-heavy Confluence spaces (architecture docs, runbooks, design specs).

  • Pairs well with other documentation/reporting apps, but avoid overlap with other diagramming-focused Marketplace apps.

2. Differentiation & Competition

What makes this app special

• Diagrams-as-code, not drag-and-drop: Diagrams are defined in simple text syntax and rendered automatically — no manual drawing, dragging, or aligning shapes. This makes diagrams faster to create and far easier to update than native Confluence drawing tools or freeform diagramming apps.

• Breadth of diagram types in one tool: Supports a wide range of diagram types (sequence, class, activity, component, state, use case, and more) from a single syntax engine — rather than requiring different tools or templates for different diagram styles.

• Version-control friendly: Because diagrams are plain text, they can be copy-pasted, diffed, and reused across pages, teams, or even external repositories — something visual/canvas-based diagramming tools (native or Marketplace) can't offer.

• Fully managed rendering — no customer-side setup: Diagram rendering is handled automatically via managed cloud infrastructure — customers never need to install, host, or maintain their own PlantUML server (a common pain point with open-source or self-hosted PlantUML setups). Everything works out of the box directly inside Confluence.

• Lightweight and fast for technical users: Favored by developers and architects who think in structured/textual terms, making it faster for technical teams to produce accurate diagrams compared to general-purpose visual diagramming tools built for non-technical users.

DC → Cloud Migration Narrative (If Applicable)

• • Zero-effort migration: Diagrams migrate automatically as part of standard page/attachment migration — no separate data export, conversion, or reconfiguration step required for customers already on PlantUML Diagrams for Confluence.

  • No migration risk for diagram content: Since diagram source and rendered images live natively on the Confluence page itself, there's no external data store or service to migrate separately — reducing one more variable in an already complex DC→Cloud project.

  • De-risks a common migration blocker: Diagrams/visual documentation are often flagged as a migration risk area for other tools; this app removes that concern entirely, which can be a selling point when diagrams are a heavy part of a customer's documentation.

  • Smooth path even from competitor tools: Customers migrating from Avono's on-prem PlantUML app to Cloud can convert their macros to this app during migration, giving Atlassian a clean path to bring those customers into the Marketplace ecosystem on Cloud.

  • Consistent experience post-migration: Look, feel, and functionality remain the same before and after migration, minimizing user retraining and adoption friction — a common concern in large migrations.

Where this app helps us win

Which sales motions could this app support:

• • DC → Cloud migration: Directly supports migration deals — removes a common risk/blocker (diagram continuity) and gives Atlassian a clean story for customers worried about losing visual documentation during migration.

  • Confluence expansion: Strengthens the case for expanding Confluence usage into technical teams (engineering, architecture, DevOps) who need diagramming as part of their documentation, not just wikis/pages.

  • Consolidation of various tools on Atlassian platform: Helps replace standalone diagramming tools (Visio, Lucidchart, self-hosted PlantUML servers) by keeping diagrams natively inside Confluence — supports "reduce tool sprawl" conversations.

  • Competitive displacement from Avono's on-prem PlantUML app: Specifically useful in migration deals where a customer is moving off Avono's on-prem app — gives a clear, low-friction path to bring them onto Cloud with this app instead.

  • Confluence Premium/Enterprise upsell: Supports upsell conversations where advanced documentation needs (architecture governance, compliance-ready technical docs) justify higher-tier Confluence plans.

How this app gives advantage in competitive deals (e.g., ServiceNow / Azure DevOps / Monday / Miro).

• Cost-effective LaTeX/math rendering: Offers LaTeX math notation support at a fraction of the cost of dedicated native math-rendering solutions — a strong differentiator when competing against platforms where equivalent functionality requires expensive add-ons or built-in premium features.

• Technical depth competitors lack natively: Tools like Monday or Miro are built for visual collaboration, not precise, reproducible technical diagrams (UML, sequence, architecture) — this app gives Atlassian a credible answer when customers need engineering-grade diagramming, not just whiteboarding.

• Diagrams-as-code vs. manual drawing: Against tools where diagrams are manually drawn and maintained (ServiceNow attachments, Miro boards, Monday docs), this app lets technical teams define diagrams in text — faster to create, easier to keep accurate, and simpler to review/version than freeform visual boards.

• Native integration removes tool-switching: Where competitors (ServiceNow, Azure DevOps) require exporting or linking out to separate diagramming tools, this app keeps diagram creation and documentation in the same Confluence page — a concrete "why stay on Atlassian" argument.

• No self-hosted infrastructure burden: Customers get fully managed diagram rendering without standing up or maintaining their own rendering servers — removing a common technical objection when comparing total cost/complexity against alternative platforms.

When this app is not a good business fit?

Not a strong fit for customers whose primary need is general-purpose visual collaboration (whiteboarding, brainstorming, freeform diagrams) rather than precise, syntax-defined technical diagrams — those use cases are better served by native Confluence whiteboards or visual collaboration tools. Also less relevant for organizations without any technical/engineering documentation needs, since the value proposition centers on developers, architects, and technical writers rather than general business users. Customers looking for a drag-and-drop diagramming experience with no learning curve may find the text-based syntax a barrier rather than a benefit, especially if they have no prior exposure to PlantUML or similar diagram-as-code tools.

3. Technical Fit & Requirements

High-level technical fit summary:

Strong fit across a broad range of organizations — not limited to developer-heavy teams. Diagrams-as-code has become a mainstream documentation standard, and the app is widely adopted by regulated industries like financial services, where structured, reproducible, and auditable technical documentation is a core requirement rather than a nice-to-have. Best fit for any organization maintaining architecture, process, or compliance-related documentation in Confluence; less relevant only for teams with no diagramming needs at all or those exclusively focused on freeform visual brainstorming rather than structured documentation.

Key technical constraints:

• Scale & performance notes:
  Proven at enterprise scale — the app performs smoothly on the biggest supported Confluence instances, with no observed performance degradation as instance size grows. Built to handle demanding, high-volume enterprise environments without compromise.

• Hosting / architecture caveats:
  No hosting or architecture limitations beyond standard Cloud/DC distinctions. The app is actively migrating to Forge, putting it firmly on Atlassian's long-term Cloud platform trajectory — a strong signal of future-proof reliability and reduced platform risk for enterprise customers making long-term investment decisions.

• Dependencies or hidden requirements:
  Zero hidden dependencies. The app is fully self-contained, thoroughly documented, and operates in full compliance with SOC 2 standards — giving customers and security teams complete confidence and transparency with no surprises during evaluation or deployment.

Security & compliance

Security certifications:
SOC 2 Type II compliant (audit evidence managed via Vanta, covering cloud infrastructure controls). GDPR-aligned, with a completed Data Protection Impact Assessment (DPIA).

Data residency & regulated industry suitability:
Strong fit for regulated industries — particularly financial services — given SOC 2 Type II compliance and a mature, audit-ready security posture. Well-suited for customers with GDPR compliance requirements.

Security red flags / when to involve SE or security:

• Customer requires a signed DPA or NDA — readily available, with a track record in prior enterprise/financial services deals (e.g., Swisscard).

• Customer runs a formal vendor security assessment (e.g., via Bitsight or similar) — loop in SE/security early; direct experience completing these exists (Ford, Toyota/Woven by Toyota).

Migration & lifecycle

Migration considerations (DC→Cloud, other tools→this app):
Migration is seamless — diagram data and rendered images are stored natively on Confluence pages and attachments, so a standard Confluence page/attachment migration (DC↔Cloud) automatically carries diagrams over with no additional steps required. For customers migrating from a competing on-prem PlantUML solution, a straightforward macro conversion step is available to bring existing diagrams into this app with minimal disruption.

Known upgrade / lifecycle issues (breaking changes, end-of-life risks):
The app is currently transitioning its Cloud architecture from Connect to Forge, aligning with Atlassian's long-term platform direction — this is a proactive move rather than a forced migration, with no disruption expected for existing customers. No known breaking changes or end-of-life risks at this time.

4. Implementation & Effort

Time & complexity

Implementation is fast and low-complexity — the app works out of the box immediately after installation, with no infrastructure setup required. Basic diagram creation can start within minutes, using simple text-based syntax. No specialized technical consultant or developer is required for standard use; Confluence space admins and end users can get started on their own. More advanced use cases (custom templates, GitHub/GitLab diagram imports, programmatic diagram creation) may benefit from a technical user familiar with the app's advanced features, but these are optional, not required for core value.

Configuration patterns

Custom templates are supported, allowing teams to standardize diagram styles and structures across projects. Integration options are available for pulling diagrams directly from GitHub and GitLab repositories, keeping diagrams-as-code in sync with source control. Full setup and usage documentation is available covering installation, configuration, custom templates, and advanced use cases.

Change / adoption

Minimal workflow disruption — the app integrates directly into the existing Confluence editing experience, so teams don't need to change how they write documentation, only how they create diagrams within it. Some learning curve exists for teams unfamiliar with diagram-as-code syntax, but this has become an increasingly familiar approach across technical and documentation teams. No formal training is typically required; most users become productive through in-app usage and available documentation alone.

5. Customer Proof, Stories, Assets

Assets

• https://marketplace.atlassian.com/apps/1215115/plantuml-diagrams-for-confluence-i-uml-flowchart-git?hosting=cloud&tab=reviews

6. Risks, Objections & Red Flags

App-specific common customer objections

"Our team isn't technical enough to write diagram syntax."
→ Diagram-as-code has become a mainstream documentation standard, not a niche developer skill — most users pick up the basic syntax within minutes, and templates/examples make it approachable even for non-developers. Financial services and other regulated industries use it widely precisely because it standardizes documentation without requiring deep technical expertise.

"We already use [a general diagramming/whiteboarding tool] — why switch?"
→ This app isn't a replacement for whiteboarding or freeform visual collaboration — it's built for precise, reproducible technical diagrams that stay accurate as systems change, directly inside Confluence, without needing a separate tool or manual export/import.

"How do we know our diagrams and data are secure?"
→ The app is SOC 2 Type II compliant, with audit evidence maintained via Vanta, and has successfully completed formal vendor security assessments for large enterprise customers (e.g., Ford, Toyota/Woven by Toyota).

"Will this still work after we migrate to Cloud / off DC?"
→ Migration is seamless — diagrams are stored natively on Confluence pages, so a standard page/attachment migration carries diagrams over automatically with no extra steps.

Known limitations / caveats

• Requires basic familiarity with diagram-as-code syntax — not a drag-and-drop visual editor, so teams expecting a purely visual tool may need a short adjustment period.

• Currently migrating from Connect to Forge on Cloud — a proactive, non-disruptive move, but worth noting as an active area of development.

• No dedicated customer proof points, case studies, or published win stories currently available (flagged internally as a gap to close).

7. Pricing & Packaging Nuance

Structure

• Per-user pricing model. Free tier available for up to 10 users, making it easy for small teams to adopt with no upfront cost. Pricing does not scale linearly — cost per user decreases as instance size grows, so larger customers benefit from more favorable per-user economics as they scale (100, 1k, 10k+ users).

Commercial guidance (not customer facing)

Notes on:

• Participates in all standard Atlassian discount programs (academic, nonprofit, dual licensing, etc.) and provides concessions as required/requested by Atlassian. Pricing is competitive within the category — one of the original and most established solo PlantUML apps on the Marketplace, but not positioned as the most expensive option, making it an easy "no-brainer" inclusion in most deals. Discount requests from customers are rare, and further ad-hoc discounting beyond standard programs is granted even more rarely — pricing is generally accepted as-is without friction.

8. Partner Engagement Details

Atlassian PDM: Anna Barry, abarry@atlassian.com

Technical Contact: Boris Jockov, boris@stratus-addons.com

Sales Contact: Aljosa Klisanic, aljosa@stratus-addons.com