Mesh is the substrate — what Aaron called "the platform that allows for AI speed against compliance and regulated systems." Black Flag is the AI Application Studio that ships fintech-shaped products fast on top of it. Together: one stack, two margins, no overlap.
The leverage point: BFD takes ideas 0→1. Somewhere between 0.25 (it's a financial product) and 0.75 (billing, cash management, assets), every startup we ship needs financial services underneath. Mesh is what lights up there. Banks become the channel that lands those fintechs into Q2 and Alkami — not a TAM the partnership chases.
Two real BFD clients sit at those marks today. The rest of the deck is what's built, where Mesh slots in, and the smallest real shape we ship in the next 30 days.
The two halves of this partnership are aimed at different margins by design. Trabian's twenty years of FI engineering, consolidated as Mesh, is the place the leverage compounds — connectivity to cores, payments, partners, plus the licensing deals into Q2 and Alkami that let a fintech ride inside a bank's digital surface, not just talk to it. Black Flag is the application studio that operates on top — taking a product from idea to alpha to year-three iteration. Same client, same stack, two margins, no overlap.
Mesh is, in Aaron's framing, "the platform that allows for AI speed against compliance and regulated systems". That ecosystem is the channel a BFD-built fintech rides into a bank's surface — exactly the shape of a credit-repayment company that wants a presence inside online banking, the example Aaron put on the table. A fintech like that needs an application studio to ship the experience and an integration platform to land it inside the bank's digital surface. BFD ships the experience. Mesh runs the integration. Banks aren't outside this — they're the channel where the leverage compounds.
The same shape shows up directly in BFD's portfolio. Angela (Totum AI) is the 0.25 case — a fintech that doesn't know it's a fintech yet, currently making architecture decisions Mesh should be in the room for. The enterprise care-coordination platform anonymized in section 05 is the 0.75 case — billing, cash management, and asset visibility are the next layer once the core care product is at scale. Both detailed below.
We've done this motion over and over — discovery, design, build, launch, adoption, the next quarter's iteration, the integration polish a year in. "Build the product" is short-selling it. We take it from the first conversation through to the version of it that's still being used in year three.
We are well positioned to be the banking infrastructure platform for you guys. We will find a way to make it economically viable for all of us to be playing in this thing.
The buyer in this framework is the fintech (or the startup that doesn't yet know it's one). BFD brings the relationship and ships the product. Mesh slots in at the 0.25 or 0.75 mark and becomes the financial-services substrate. Trabian's existing bank-distribution licensing — Q2, Alkami, the cores — turns the bank surface into a channel where the fintech ends up inside, not a TAM the partnership chases. Two sides, two specialties, one deal flow.
A firm that does what you do doesn't want to do what we do, and we can't do what you do because we're doing all of this.
flowchart TD
Fintech["FINTECH / STARTUP
BFD's client · taking it 0→1
doesn't know it's a fintech yet,
or knows the financial product
IS the product"]
BFD["BLACK FLAG
application studio
(0→1 builder, year-three operator)"]
Mesh["TRABIAN / MESH
financial-services substrate
+ Q2 · Alkami · cores licensing"]
Bank["BANK SURFACE
distribution channel for the fintech
(Q2 Helix · Alkami · online banking)"]
Fintech ==>|"pays for product"| BFD
Fintech ==>|"pays for FS at 0.25 or 0.75"| Mesh
BFD -.->|"pulls Mesh into the build"| Mesh
Mesh -.->|"lands the fintech inside the bank"| Bank
classDef bfd fill:#1E5BB8,stroke:#4985d8,stroke-width:2px,color:#FAFAFA;
classDef mesh fill:#1A1A1A,stroke:#4985d8,stroke-width:2px,color:#FAFAFA;
classDef fintech fill:#252525,stroke:#FFC800,stroke-width:2px,color:#FAFAFA;
classDef bank fill:#1c2536,stroke:#4985d8,stroke-width:2px,color:#FAFAFA;
class BFD bfd;
class Mesh mesh;
class Fintech fintech;
class Bank bank;
Fintech is the buyer in both directions. BFD ships the product; Mesh provides the financial-services substrate when the product hits 0.25 or 0.75. Trabian's existing licensing into Q2, Alkami, and core providers turns the bank surface into a distribution channel — exactly the credit-repayment-in-online-banking pattern Aaron volunteered on the April 30 note. Banks aren't a TAM here. They're the place a Mesh-backed fintech lands.
Four moves, in twelve months, walked Trabian from "custom dev shop" to "platform operator with a workflow-management roadmap." Each one widened the surface area where an application studio like Black Flag plugs in cleanly — and where a 0→1 fintech build can ride Mesh into a bank's surface without either side stepping out of its lane.
Per IBJ, the pre-Mesh shape was "everyone was bespoke, custom-built." Twenty years of trusted FI engineering, but every project was a snowflake.
Repurchased shares from MVB Bank. Free to define a platform-led future on its own terms. without a bank-side cap table dictating direction.
Bought from Core10. Inherited core connectivity (Jack Henry, Fiserv, CSI) and licensing deals into Q2 and Alkami. Months-not-years became a real claim.
Trabian's stated direction shifted: morph from integration platform → workflow management platform. Reliability + accountability + time-to-market for FIs and fintechs.
Mesh is already in production, already connecting cores, already running the compliance and audit substrate. The roadmap shifts from "integration platform" toward workflow-management platform for FIs and fintechs. That word — fintechs — is where this partnership lives. Every BFD-shipped fintech crosses the 0.25 or 0.75 mark and needs financial-services plumbing; Mesh is what's underneath when it does.
One client at a time, the partnership runs the same four-step motion. BFD owns the client relationship and the application work. Mesh slots in once the product hits 0.25 or 0.75 and stays as the financial-services substrate underneath. The bank surface is where the fintech ends up — a distribution outcome, not a buyer.
BFD's pipeline brings a fintech (or pre-fintech startup) into the room. Workflow defined, agent policy drafted, risk register sized.
Once the FS need is real — financial product (0.25) or billing / cash / assets (0.75) — Mesh is pulled into the build. Joint architecture conversation.
BFD builds the experience and ships the alpha. Mesh runs the FS plumbing, the audit trail, and the bank-distribution licensing. Synthetic data first.
The integration shape becomes a Mesh-native module Trabian sells across the existing 200+ FI relationships. Repeat with the next BFD-shaped fintech.
The repeatable module is what compounds. Each engagement teaches the platform a new "shape of fintech" — consumer-AI on a Helix-backed account, healthcare-spending account with vendor-direct disbursement, regulator-grade analysis riding cores — and each shape becomes resellable across Trabian's existing FI relationships without another full build cycle.
No fictional scenarios. Two real BFD engagements. The first block is the current state in numbers — what's running, what's built. The second block places each one on the 0.25 / 0.75 financial-services scale and shows the V2 product idea Mesh makes possible.
Block B · Mesh spotlight
TodayAI explains a quarterly statement after the user uploads it. No accounts, no billing data, no continuity quarter to quarter.
V2 with Mesh + Q2 HelixAngela becomes the experience layer on a real deposit account. The user opens checking or savings inside a Q2-powered partner bank; her persona — Bass, Drums, whatever the onboarding lands her on — selects the advisor voice attached to the account. Savings goals trigger contextual nudges from the matched advisor. An optional companion savings account compounds engagement the more she puts in. A male-advisor variant, a female-advisor variant, and a strict-coach variant can all coexist as different persona-account pairings on the same banking primitive.
Why pitchable to TrabianFintech-as-account inside Q2's deposit ecosystem is the exact pattern Mesh's licensing already covers. The integration ships in weeks. The repeatable module Trabian sells: persona-routed AI advisor on a Helix-backed account — sellable into every other consumer fintech BFD ships.
TodayThe platform organizes care journeys, recommends vendors, and surfaces asset visibility through a manual Limited Power of Attorney at Schwab. Vendor payments live outside the platform — invoiced, mailed, lost.
V2 with Mesh + Q2 HelixThe family opens a dedicated healthcare-spending account inside a Q2-powered partner bank. The advisor and the platform jointly manage cash position alongside the care journey. Every platform-recommended vendor — long-term care providers, geriatric care managers, home-care services, the platform itself — gets paid directly from the account via Mesh's payment rails. Tax-aware: HSA-shaped where eligible, brokerage-shaped where not. Cash-flow projections trigger advisor nudges around upcoming care events before they hit the family's checking.
Why pitchable to TrabianReplaces the LPOA workaround with API-grade custodial reads + a deposit primitive built for the use case. Productizes into a "healthcare-spending account" SaaS module Mesh sells across every RIA distributing the platform. Care + cash, one tool, two revenue lines.
One pattern is fintech-as-account. The other is vendor-direct disbursement. Both ship on the same Mesh + Q2 stack. Both turn a single BFD client engagement into a Mesh-native module Trabian sells across the rest of the 200-FI base.
Both client tracks in section 05 ride the same trust-building pattern. Crawl in synthetic data, walk on a real alpha with a design partner, run as a productized Mesh-backed module across the existing 200+ FI base. Each step earns the next. Section 08 traces what this looks like across a single 90-day engagement.
Workshop, workflow map, agent policy card, prototype, risk register. No real customer data ever touched. Output: an internal demo the joint team can show.
The design partner can come from either side — a fintech in BFD's pipeline, or a fintech / FI from Trabian's 200+ relationships. Custom AI app alpha → user testing → human-in-loop beta. Real users, governed scope.
Successful integration shape becomes a repeatable Mesh-backed module sold across the 200+ FI base. Demo library, governance framework, partner enablement kit, commercial packaging.
Every custom AI application ships with an agent policy card: business purpose, user role, data sources, permitted/prohibited behaviors, allowed actions, actions requiring human approval, logging, failure modes, escalation path, retention model, success metrics. Early work lives at Levels 0–3.
The chart below is the real shape of one of these engagements. applied to any of the three stories in section 05. Defined, low-risk, fixed-fee. Synthetic data through day 60. Clear go/no-go on day 90. design partner identified and beta scope agreed, or a clean exit. Crawl, walk, run mapped to the timeline rather than treated as an abstract ladder.
The work isn't just "the model". It's the full delivery: web app + mobile companion, backend, the workflows and data contracts between Mesh and the client, the stakeholder management that gets the FI's people on the same page, and the agent governance that keeps compliance teams calm. The differentiator across all of it: BFD's team manages agents that write the software. That's how a five-person shop runs at the velocity of a thirty-person one. without sacrificing the compliance posture banks need.
gantt
title AI APPLICATION DELIVERY · TRABIAN + BLACK FLAG (90-DAY ALPHA)
dateFormat X
axisFormat Day %s
section Crawl · BFD-led
NDA + Mesh orientation :crawl1, 0, 10
Use-case workshop + workflow map :crawl2, 5, 18
Agent policy card + risk register :crawl3, 10, 24
Clickable prototype + demo script :crawl4, 14, 30
section Walk · Joint
Backend + data contracts (Mesh ↔ client) :walk1, 22, 50
Web app + mobile companion build :walk2, 28, 60
Synthetic-data alpha :walk3, 35, 60
Internal user feedback + iteration :walk4, 45, 60
section Run · Design partner
Design partner identified (from 200+ FIs) :run1, 55, 68
Integration + compliance gating :run2, 60, 82
Production data, governed scope :run3, 70, 90
Adoption playbook + reusable module spec :run4, 75, 90
What the chart doesn't draw, but matters: every cell that has BFD building, has BFD agents building under BFD oversight. That's the speed multiplier that makes 90 days realistic on a custom AI app where most shops would quote nine months.
The framework's clear, and two real BFD clients sit on the .25 / .75 spectrum ready to come into the Mesh conversation tomorrow. The remaining question is the one Aaron put on the table directly: what's the smallest real thing the five of us could ship together in the next 30 days that would tell all five whether this works. Either of the V2 sketches in section 05 could be the wedge. So could the credit-repayment-in-online-banking pattern. We're flexible on the wedge; we're firm on shipping one.
Concrete next step: a 45-minute working session with the five names on this document. Goal: pick the wedge, name the first joint design partner, scope the 30-day boundary, agree the rough commercial frame. We bring a one-page scoping template; we leave with one Mesh-shaped client engagement on the calendar.
Print-ready partnership brief. Hero, stats, capabilities, 90-day path, CTA. Forward to Matt, Trey, or anyone who needs the shape in 90 seconds.
Open →Pilot SOW scaffold. Editable scope, fees, and cadence. we'd shape the real one around the first joint client we land.
Open →Architecture + data-handling answers, pre-filled. Send only if procurement asks. don't lead with it.
Open →