Aaron's framing from the April 29 call: "Mesh is the platform that allows for AI speed against compliance and regulated systems."
Mesh is the substrate. Black Flag is the AI Application Studio that ships apps on top of it. The rest of this folder (One Pager, SOW, Security) descends from this page.
The two sides of this partnership are aimed at different margins by design. Trabian is exceptionally well-placed: twenty years of custom builds for FIs, then Mesh on top to abstract the connectivity, then a roadmap moving toward workflow management. The platform is where the leverage compounds. Managing AI agents inside production apps for client after client is a different business with different economics. Trabian doesn't need to enter that lane to win from it.
Mesh is, in Aaron's own framing, "the platform that allows for AI speed against compliance and regulated systems". All the logging, all the connections to cores, payments, and partners, baked in. Jack Henry, Q2, Fiserv, Alkami. Licensing deals to get fintechs into Q2 and Alkami, not just talk to them. That ecosystem is on lock. As Mesh becomes the place agents are enabled — sandbox, governance, audit, action surfaces — the stability is what makes any of this credible to a banker.
Black Flag is the services layer that operates against that platform. We work directly with Trabian's partners, the banks and the fintechs, as boots-on-the-ground for whatever comes up. The bank doesn't always know what it wants yet. We sit with them, pick the workflow, ship the alpha, run the launch, and stay there after launch — that's where most "AI projects" die, and it's where a real partner is worth the most. Then we land the workflow back on Mesh as a clean integration. Trabian gets the platform attach; we get the services revenue; the client walks away with the full tech stack glued together by the partnership.
We've done this shape over and over — pick any of the case studies in the appendix. Take the product all the way: 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.
The Connecticut bank-analysis startup that surfaced on the April 29 call is exactly the shape of client this is built for. Real product to build, real banks already on the hook, regulators paying attention, and a team that doesn't have the application or AI muscle to ship the front half. Mesh gets them connected to cores and CRMs. Black Flag handles the product, the launch, and everything that comes after.
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.
Trabian owns the stable financial-services infrastructure. Black Flag owns the AI application and adoption layer on top. The two halves combine into one complete delivery motion for any bank, credit union, or fintech client. without either side having to step into a business model that isn't theirs.
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
Bank["PARTNER BANK / CU / FINTECH
the buyer
already runs cores (JH · Fiserv · CSI),
digital banking (Q2 · Alkami),
payment rails, and fintech partners"]
Trabian["TRABIAN / MESH
middleware that connects
the bank's existing stack"]
BFD["BLACK FLAG
application studio
that builds AI apps on top"]
Bank ==>|"pays for Mesh"| Trabian
Bank ==>|"pays for services"| BFD
BFD -.->|"apps ride Mesh"| Trabian
classDef bfd fill:#1E5BB8,stroke:#4985d8,stroke-width:2px,color:#FAFAFA;
classDef mesh fill:#1A1A1A,stroke:#4985d8,stroke-width:2px,color:#FAFAFA;
classDef bank fill:#252525,stroke:#FFC800,stroke-width:2px,color:#FAFAFA;
class BFD bfd;
class Trabian mesh;
class Bank bank;
The bank is the buyer in both directions. Solid arrows: money. The bank holds the contract with Trabian for Mesh, and a separate contract with BFD for services. Dashed arrow: BFD's apps ride Mesh as the surface the bank's people actually open. The bank's cores, digital-banking platforms, payment rails, and fintech partners aren't separate actors here — they're the bank's existing stack, which Mesh exists to govern and connect on the bank's behalf.
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 can plug in.
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 serving customers, already connecting cores. The remaining gap. the one a banker or a fintech CEO actually feels. is the application layer on top: the screens, the agents, the workflows, the human-in-the-loop copilots that make Mesh tangibly valuable to a buyer. Trabian doesn't want to staff a 30-person app-build org to fill that gap; it wants a partner that can. That's where Black Flag sits.
Frame the partnership as a shared services lane Trabian can sell, staff, and showcase. Black Flag operates as the embedded AI-application studio for Mesh, taking client ideas through a repeatable motion that respects Trabian's governance posture at every step.
Vague client idea becomes a defined workflow, agent policy, and risk register.
BFD prototypes the experience. Mesh defines available infra, data, and actions.
BFD builds. Mesh governs integration, security, platform fit. Synthetic data first.
Client tests usage. Successful patterns become repeatable Mesh-backed modules.
Each successful build becomes a candidate repeatable module. sold across the 200+ relationships Trabian already has, demoed to prospects evaluating Mesh, and used as evidence the platform actually ships application-layer outcomes.
Three made-up stories. Three different shapes of client. The same partnership shape every time: Trabian / Mesh on the substrate, Black Flag on the application layer, the client's people on the win condition. Each scenario leans into BFD's two unfair advantages: nothing to alpha faster than anybody else, and a team that manages agents writing the software, which is how a five-person studio ships work other firms need thirty to ship.
The shape of the client. A regional bank with a strong commercial book whose RMs lose days every deal because borrower context lives in three systems (CRM, core, LOS) and never in one place. Mesh is already in their stack to connect those systems; what they're missing is the surface a banker actually opens.
What Black Flag would build. A banker workspace on Mesh that pulls context out of CRM + core + LOS, summarizes the borrower in plain English, drafts the next RM action, and stages docs for compliance review. Read-only against production for the first 60 days. Synthetic data for the alpha. Every drafted action gated by a human click. Mesh handles the connectivity; BFD ships the UI, the agent policy, the workflow contract, and the adoption playbook.
What "good" looks like at 90 days. Time from first conversation to wired funds drops, the banker on screen says "this is faster than the spreadsheet," and the build is reusable as a Mesh-backed module across other commercial-lending FIs.
The shape of the client. A mid-size CU with an underperforming premium-checking product, a roadmap full of "we should ship this next quarter" features, and no internal capacity to actually run a launch. They want adoption, not slides.
What Black Flag would build. A productized "feature launch studio" engagement: 2-week facilitated discovery sprint, clickable prototype, AI-personalized member-facing experience, and an in-product adoption loop. Eli runs the room; agents do most of the build; the CU walks out with a launched feature and analytics that defend the budget for the next one. Mesh provides the digital-banking and member-data substrate the experience runs on.
What "good" looks like at 90 days. Premium-product adoption visibly moves in the first month, the next two CUs sign on the strength of that case study, and the studio motion becomes a Mesh-attached module Trabian can sell repeatedly.
The shape of the client. A fintech that's sold one bank a niche analysis product the regulator now wants every bank in the state to report against. They have a product, a single happy customer, and a regulator-shaped tailwind. They don't have the team to scale the product or the integrations to land it inside another twenty banks fast enough.
What Black Flag would build. The application layer end-to-end and stays past launch: web app, mobile companion, the backend that ingests cohort data through Mesh from each bank's CRM + core, the AI models and pipelines that turn cohort data into the insights regulators want, the human-in-the-loop review surface for bank staff, the launch, and the iteration cycles after. Mesh handles the connectivity into every bank's stack — the piece the fintech couldn't have built in time on its own. Black Flag is the team the bank still has on a Slack channel six months in.
What "good" looks like at 90 days. The fintech ships an alpha that one more bank runs for one real cohort report, the joint case study gives Trabian a referenceable engagement, and BFD has a wedge into every other bank in that state that's about to be required to file the same report.
The shape across all three: Trabian holds the platform attach and the agent-enablement story. Black Flag is on the ground with the client from the first conversation through launch and into the long tail of iteration. Each engagement lands back on Mesh as a clean integration the next ten clients can buy off a shelf, and the FI ends up with the full tech stack glued together by the partnership.
They didn't just build software, they built current and future leverage into our system.
Trust gets built one stage at a time, and the timeline below in section 08 traces what that looks like for a single 90-day engagement. Across all three engagements in section 05, the same pattern applies: crawl in synthetic data, walk on a real alpha with a design partner, run as a productized Mesh-backed module. Each step earns the next.
Workshop, workflow map, agent policy card, prototype, risk register. No real customer data ever touched. Output: a demo Aaron and the team can show internally.
One FI or fintech from Trabian's 200+ relationships agrees to be the design partner. Custom AI app alpha → user testing → human-in-loop beta. Real users, governed scope.
Successful pattern 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.
Everyone who's reading this. Aaron, Matt, Trey, Eli, Keith. already knows the thesis. The remaining question is whether there's a small real thing the five of us could build together in the next 30 days that would tell all five whether this works. The Connecticut bank-analysis referral is one obvious shape; an internal Mesh demo app is another. We're flexible on the wedge; we're firm on doing one.
One concrete next step: a 45-minute working session with the five names on this document. Goal. pick the wedge, shape the 30-day boundary, agree the rough commercial frame. We bring a one-page scoping template; you bring the candidate client (or the internal target). We leave with something 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 →