Demo listing. This page uses illustrative seed metadata to demonstrate the Atlas. Claims shown here are not verified product facts.
Midpole
Marketing & Growth
A brand experience portfolio that scores mid-market “hourglass” trap risk and reallocates spend and experience bets toward premium-purpose or platform-utility poles before commoditisation erodes the middle.
Last verified 15 Sept 2026 · Updated 23 Sept 2026 · Metadata v4
Problem
Mid-market consumer brands (retail, CPG, brewing/hospitality, financial products) whose engagement quality and quantity are stuck between Amazon-scale platforms and craft/purpose specialists, with $2M–$25M annual brand/experience budgets.
Outcome
A design-complete foundation in the active pipeline — engineering scaffold planned to complete this month.
Who uses it
- Operations Analyst
- Solution Architect
Key capabilities
Capabilities are defined during customer configuration.
Typical workflow
Primary operating flow
Trigger: An operator starts the primary use case
Task
Stage 1: Capture inputs
Operator
AI-assisted
Stage 2: Assist with draft
System
Human checkpoint
Stage 3: Human approval
Approver
Task Automated AI-assisted Human checkpoint Decision
About this foundation
Brand experience portfolio OS grounded in Fjord Trends 2017. Trend decks stop at “don’t get stuck in the middle”; Midpole operationalises the hourglass—plus ephemeral storydoing, Me/Myself/AI chatbots, Shiny API People rewiring, and unintended social-experience risk—into scored positions, reallocation decisions, and auditable experience bets.
Related applications
- • Addresses the same problem: Manual Workflow, Fragmented Systems
- • Shared capabilities: Workflow Automation, Document Intelligence
- • Addresses the same problem: Manual Workflow, Fragmented Systems
- • Shared capabilities: Workflow Automation, Document Intelligence
- • Addresses the same problem: Manual Workflow, Fragmented Systems
- • Shared capabilities: Workflow Automation, Document Intelligence
- • Addresses the same problem: Manual Workflow, Fragmented Systems
- • Shared capabilities: Workflow Automation, Document Intelligence
- • Addresses the same problem: Manual Workflow, Fragmented Systems
- • Shared capabilities: Workflow Automation, Document Intelligence
- • Addresses the same problem: Manual Workflow, Fragmented Systems
- • Shared capabilities: Workflow Automation, Document Intelligence
Primary operating flow
Trigger: An operator starts the primary use case
Task
Stage 1: Capture inputs
Operator
AI-assisted
Stage 2: Assist with draft
System
Human checkpoint
Stage 3: Human approval
Approver
Actors
Operator, Approver
Outputs
- Completed work item
Evidence generated
- Audit trail
Exceptions
- Incomplete inputs returned to operator
Task Automated AI-assisted Human checkpoint Decision
Included ships in the foundation · Configurable is switched or tuned per customer · Extension is customer-specific build scope · Planned is on the roadmap and not available today.
Core workflow
AI-assistedPlannedPrimary operating workflow for this foundation.
Document intelligence
AI-assistedPlannedExtract and ground decisions from operating documents.
- Architecture class
- Domain-driven design, OpenAPI-first
- Bounded contexts
- 3
- API-first
- Yes — OpenAPI contracts are authoritative
- Identity
- Enterprise OIDC / SAML via the fazeZERO identity blueprint; tenant-aware role-based access.
- Multi-tenancy
- Tenant-aware
- Service boundaries
- Bounded contexts behind one API server.
- Integration approach
- Ports-and-adapters: every external system sits behind an adapter; OpenAPI contracts for inbound APIs.
- Eventing
- Integration events via transactional outbox.
- Storage abstraction
- Repository interfaces; DynamoDB or relational adapters.
- Deployment pattern
- Containerized API + web application; infrastructure as code per cloud profile.
- Architecture version
- 1.0
Approved domain names
- identity
- catalog
- workflows
- Web Application
- API Server
- Application Services
- Domain / Generated Core
- Adapters
- Customer Systems
Generator source, templates and factory orchestration are proprietary and are not part of this listing.
Reference Adapter: shipped and tested · Previously Integrated: delivered before · Standard API Pattern: integrates via a documented pattern · Customer-Specific: built in your implementation.
APIs
| Integration | Status | Direction | Method |
|---|---|---|---|
| Customer systems of record | Standard API Pattern | bidirectional | REST API |
Deployment
- Deployment models
- Customer Cloud, Private Cloud
- Cloud profiles
- Azure Profile, Cloud-Neutral
- Containerized
- Yes
- Regions
- GLOBAL
Cloud profiles describe approved deployment patterns. They are not formal marketplace certifications.
Data handling
- Stores customer data
- Configurable
- Data leaves customer environment
- Configurable
- Uses external AI provider
- Configurable
- Sends logs externally
- No
- PII expected
- Determined during customer configuration
- Data-residency support
- Yes
- Subprocessors required
- Determined during customer configuration
Identity & access
- Authentication
- OIDC, Entra ID, SAML
- Authorization
- Role-Based, Tenant-Aware
- Source availability
- Proprietary
Support
- Implementation
- Delivered by fazeZERO or a certified partner during the Solution Definition and AI Production Sprints.
- Production support
- Production support available under a separate support agreement.
- Contact
- support@fazezero.com
Badges
fazeZERO Verified
Listing metadata and published technical claims have been reviewed by fazeZERO.
Issued 23 Sept 2026
Evidence shows that this listing represents real engineering. Internal metrics are only published when fazeZERO has approved them for publication.
Build
Automated tests
Deployment validation
- Last verification
- 15 Sept 2026
- Release
- 1.0.0
- Architecture version
- 1.0
- Listing metadata version
- 4
- Last published
- 23 Sept 2026