Blink Security Automation — Confidential

Fortress-SubTenant — Customer Success Report

Generated 2026-09-10 | fortress-subtenant-value-report.md
2026-09-10Report Date
11Total Playbooks
1Unique Workflows (12m)
3Actions Automated (12m)
$1Money Saved (12m)
Last 12 MonthsData Period
CSM — Please review before sharing. AI-generated content may contain errors. Verify key metrics before sending to the customer.

01Business KPIs — Last 12 Months

11
Total playbooks built
all non-deleted workflows
1
Active playbooks
currently enabled
1
Unique workflows executed (12m)
distinct workflows that ran
3
Actions automated (12m)
completed action steps
0.0h
Hours saved (12m)
@ 20s per action
$1
Money saved (12m)
@ $100K avg salary
0
New active workflows (last 30d)
recently created & enabled
0
Total cases managed
0 opened in last 12m
N/A
MTTR — mean time to resolve
closed cases, last 12m
In the last 12 months, Blink automated: - No automation activity recorded in this tenant for the reporting period.

02Use Cases & Playbook Distribution

Cumulative Playbooks Built — Last 90 Days

New Active Workflows Added — Last 30 Days

Use Case Summary
Use CaseKey Business KPIsShare of ActivityPlaybooks
Onboarding / Hello World0 executions
0.0%
1
0 active
Total0 executions100%
1
0 active

Use Case Growth Over Time

1 unique playbooks  |  1 operational use cases  |  0 total executions (12m)  |  2026-04
Toggle:
Toggle:

03Integration Ecosystem

No integration data found — ensure the CSV contains an actions column.

04Key Observations

✓  Strengths

Strengths

  • The tenant workspace is provisioned and accessible, with Blink infrastructure in place.

###

△  Gaps & Growth Opportunities

Gaps

  • No production workflows exist. The only workflow present is the default "Hello World" onboarding sample, which has never been executed.
  • Zero automation coverage across all security domains: SOC, Cloud Security, Vulnerability Mgmt, GRC, IAM, and Other.
  • No integrations are connected — no external tools, SIEMs, ticketing systems, or identity providers are wired in.

Recommendations

  • Engage the Fortress-SubTenant team to understand their primary security pain points and identify a first use case to automate (e.g., alert triage, employee onboarding, or vulnerability enrichment).
  • Review whether this sub-tenant is actively managed or inherited from a parent Fortress account — production workflows may exist in a parent workspace.
  • Consider a guided onboarding session to move beyond the starter template and deploy at least one outcome-driving playbook.
Appendices
A Case Management

Case Management

No case management data found for this customer.

B AI Agents

AI Agents

No agent data found for this customer.

C Self-Service & Webforms 0 app runs | 0 form submissions

Self-Service Applications

Apps
1
self-service applications
Runs (12 months)
0
total executions
Runs (30 days)
0
recent executions
Top 5 Apps by Runs (Last 12 Months)
#AppRuns (12m)Runs (30d)
1 Assessment Process 00

Webforms

No webform usage data found for this customer.

D Full Use Case Analysis 1 use cases | 0 executions (12m)

Business KPIs

Metric Count Playbook
— — No executed playbooks in period
In the last 12 months, Blink automated: - No automation activity recorded in this tenant for the reporting period.

Use Case Summary

Use Case Category Subcategory Playbook Count Executions
Onboarding / Hello World Other IT helpdesk & ticket routing 1 0

Total: 1 playbook · 0 executions

Use Cases

1. Onboarding / Hello World

Description: A starter workflow provided out-of-the-box to help new users learn the Blink platform. It demonstrates core automation primitives (print, Bash, Python) but has no production business logic.

Business Problem Solved: Introduces the platform to new users; not yet solving a production security or IT problem.

Integrations: None (internal Blink actions only — internal.print, core.bash, core.pythonV2)

Trigger: On-demand

Playbooks

Playbook Executions (12 mo) Category Subcategory
Getting Started - Hello World 0 Other IT helpdesk & ticket routing

Key Observations

Strengths

  • The tenant workspace is provisioned and accessible, with Blink infrastructure in place.

Gaps

  • No production workflows exist. The only workflow present is the default "Hello World" onboarding sample, which has never been executed.
  • Zero automation coverage across all security domains: SOC, Cloud Security, Vulnerability Mgmt, GRC, IAM, and Other.
  • No integrations are connected — no external tools, SIEMs, ticketing systems, or identity providers are wired in.

Recommendations

  • Engage the Fortress-SubTenant team to understand their primary security pain points and identify a first use case to automate (e.g., alert triage, employee onboarding, or vulnerability enrichment).
  • Review whether this sub-tenant is actively managed or inherited from a parent Fortress account — production workflows may exist in a parent workspace.
  • Consider a guided onboarding session to move beyond the starter template and deploy at least one outcome-driving playbook.
E New Integrations (detail) 0 added in last 30d

New Integrations Added - Last 30 Days

No new integrations found, or DB query was skipped.