Three options I’d be confident in building, scoped against the DNA Behavior process I went through firsthand and the architecture Hugh and Leon described on the call.
"There’s a meaningful opportunity to embed behavior as a foundational layer within any program."
Leon Morales · April 3, 2026Leon, your note framed the foundational-layer opportunity. Hugh, on the call you suggested handing me the deck on a couple of areas inside DNA Behavior to build against. This is my answer to both. Not bolted on top. Actually built in. That's the question I kept coming back to while I was putting this together.
Here's what I keep seeing: most software treats behavioral data like a feature you add when the core product is done. A widget. A report tab. And then you wonder why it doesn't move the needle on engagement and lifetime value, including coaching and advisory programs where the whole point is understanding how a person is actually wired. When behavior is a foundational layer, the product is different from day one. The data means something different. The client feels it from the first screen.
What follows is what I'd be confident building. Real DNA Behavior data, real constraints, real clients, including coaching. Not a proof-of-concept against a synthetic dataset that sits in a demo environment and never ships. I've ordered them from full scope to smallest scope. Pick whichever fits your appetite for the first move. The foundation extends from any of them.
First: what most platforms get wrong, and why the options below are the right place to prove the alternative.
Anyone building a behavior-first platform faces the same four paths. Three of them ship slowly, cost more than they should, or leave behavioral IP on the outside of the platform instead of underneath it. The fourth is what this proposal is about.
Hugh asked on the call for a couple of areas inside DNA Behavior where I'd build something. Leon, your follow-up named the foundational-layer opportunity. This is my answer to both. Logic-first, numbers where they matter. Later than I'd intended. One sentence on that, then onward: I wanted to bring a complete picture, not a rough one.
Anyone building a behavior-first platform has four paths. Three of them are already in the market. Here's what each one costs.
Reference ranges: Option A based on 2026 senior AI engineer fully loaded cost estimates. Option B: Salesforce Einstein and Microsoft Copilot for Microsoft 365 published rates per user per month. Option C: Deloitte and Accenture AI transformation engagement benchmarks across mid-market and enterprise scopes.
That's the frame. Sections 03 through 05 are the three builds.
Behavior-routed delivery is the natural extension of DNA's existing training programs into a fully digital experience. This changes that.
Take one of DNA Behavior's existing training or certification programs and turn it into an adaptive digital experience. The learner picks the program. The program adapts to them. Each lesson, exercise, and prompt routes through the learner's behavioral profile so two learners with different DNA profiles get different framing, even when the underlying content is the same.
Coaching, certification, and advisor onboarding all share this shape. Build it once for the right program and the same foundation carries forward. The behavioral layer isn't an add-on here. It's the reason the learner experience works differently for different people.
Leon identified the gap: a reliable person who could actually do a build. This is that build.
Pick one DNA Behavior client, or a composite built from patterns Leon and Hugh see repeatedly, and build the platform they'd want on top of the DNA Behavior API. White-labeled, fully functional: a financial advisor's client-facing tool, a leadership development cohort, an onboarding journey. Personalizing user experiences from the behavioral data up, not from a configuration panel down.
The same code, with a different client-facing skin, becomes a reusable asset for the next SDK client. One build, two purposes: proof of operator capability and a reference the next team can actually start from. The architecture works across programs, including coaching, onboarding, and advisory.
A proof of architecture, not a proof of product. Built to be the artifact every future SDK client starts from.
Leon described SDK clients running into trouble building their own experiences. The piece that's usually missing is the answer to "here's how you put behavior at the bottom of your stack." This build produces that answer as working code. Auth handoff, profile fetch, behavioral routing logic, a minimal UI layer that adapts to a user's DNA style, and documented architecture diagrams. The artifact DNA Behavior's next SDK client uses as a starting point instead of figuring it out from scratch.
An SDK client that stalls in build is a relationship that costs more in attention than it returns in revenue. This makes the next client succeed in week one. The reference build is the asset that pays for itself on the first client it saves.
Any of the three is a starting point, not a destination. The first build proves the model: behavior as a foundational layer, built in from the first screen, operator staying through launch. From there the arc is wider. Full deployment across an advisor base. Multi-program rollout where each new program inherits the same behavioral foundation instead of starting from scratch. An ongoing operator role coordinating the build pipeline. Partnership economics if the working relationship earns it.
Leon's framing of a "foundational layer" is the right one. When the foundation is right, every program built on top of it compounds in value. The first build is how we find out if the foundation is right.
Every build above is fixed-price, fully scoped, and ships a working system. Not a deck and a plan.