The Performance Stack

Code ↔ Schema ↔ Model — the foundational architecture behind Hillspeed coaching.

Performance Is Three Layers. You Can't Fix the Top by Working the Bottom.

Every founder coaching relationship eventually arrives at the same moment. The work seems to be going well. The strategy is clear. The team is aligned. But something isn't moving the way it should — and the reason isn't obvious from where the founder is standing.

In most coaching approaches, the response is more of the same. More strategy. More accountability. More structure. The intervention stays at the level where the symptom is showing up.

The Performance Stack starts somewhere different.

Performance happens inside a matrix of elements, and those elements have structure we can talk to. The more you understand the construct of the matrix you're playing inside, the more you can control performance in your chosen game. The Performance Stack is that matrix — the architecture that connects the three layers every athlete operates within, whether they can see them or not.

Three interconnected layers: Code ↔ Schema ↔ Model.

Layer One: Code

We start with the athlete.

Before we look at any game they want to play, we need to understand the code that drives them. An athlete's code is complex — built on a complicated, interconnected codebase. The more we write lines of code into our life, the more we either clean or dirty the potential of what we're capable of.

The code layer has three structures.

Front end code — the driver of growth. Where the athlete has their code pointed. The dimensions of life they are applying themselves toward. What they believe is important, at a conscious level. These dimensions fall into one of four essential life buckets: Health, Wealth, Partnerships, and Playing Fields. Playing fields are the arenas where we choose to compete — each one a model with its own structure and rules. The front end code is the conscious experience of life that drives us.

Back end code — the enabler. There is a subconscious experience of life that enables the front end. This is the complete history of all code written to date — the entire story connecting into the front end codebase. The back end is a metaphor for both the past and the deep architecture that determines much of the front end's capability, stability, memory, and accumulated constraints. Without intentional curation of the back end, it controls the athlete. The subconscious runs the system, whether the athlete is paying attention or not.

Front end code potential is limited by back end code upkeep. This is not a theory. It is the observable reality in every athlete who hits a ceiling and can't explain why — because the constraint isn't visible at the front end level where they're looking.

Foundational language — the foundation. The third structure of the athlete's code is their foundational language. Who they believe they are. Not who they are — who they believe they are. This distinction is everything, because a belief is refactorable. At any point, the code can be rewritten.

A person cannot outlive their own personal identification. That which we believe we are, we become more of. The foundational language is the limiter that determines how far the front end can travel and what the back end will accept as change.

Layer Two: Model

At this point we want to understand the sport the athlete is playing.

For founders, the sport is subjective and undefined. There is no league table, no season structure, no rulebook handed to them on day one. So Hillspeed uses a Company Model to bring structure and rules to the game.

The model layer answers the question: what game is this athlete actually playing, and what does winning look like?

A growth model has three pillars. In sport: Health, Fitness, Skill. In a company: Leadership, Market, Business. Within each pillar sit three leverage points — nine in total. These are not descriptions of what the company contains. They are the places where force travels — the levers that produce movement when pulled.

The model is built in three steps:

First, the market. One customer. A series of frames that reveal where the materially important start, middle, and activation markers of the customer relationship sit. This produces the growth markers: GM1 (Engaged), GM2 (Monetised), GM3 (Activated). Company-specific — each founder defines what these look like in their model.

Then, the business. The structures, systems, and rules that drive any one of those frames. An objective reading of what the business actually is to the market — how it's built and how it works. A business is a reflection of past decisions, readable through those three levers.

Then, leadership. Not leadership as a person or a title. Leadership as a thinking and acting entity — the mechanism that brings market and business into alignment. Strategy, Standards, Execution. This is where the model becomes a game the athlete can compete in deliberately.

Six biomarkers sit across the Market and Business sides — the Scoreboard. They reveal where the company actually is, at a point in time, against the field of play the founder has chosen.

The Field of Play has three ascending levels: Good, Great, Exceptional. The founder chooses their field. The biomarkers tell the truth about whether they're actually playing there.

Layer Three: Schema

Now that we have a partial understanding of what defines the athlete, and what sport they are playing, we move to the schema layer to pull the two into alignment.

The schema is the connective layer of the performance stack. It is the decision engine that defines the athlete's state inside the performance environment. Without the schema, the code is potential and the model is theory. With it, both become a game being played by a real person, in real time, with the consequences of every decision visible.

The schema is not something we build from scratch. It is already embedded — partially expressed in the model and partially expressed in the code. The athlete already has a schema operating in their game. Their coding language is already shaping what leadership looks like. The schema is already running. Coaching makes it visible, then tunes it.

The schema has three structures: Persona, Policies, and Principles.

From the model side, the schema asks: what does this game demand? What persona does the sport call for, what policies does it enforce, what principles does it reward?

From the code side, the schema pulls: what does this athlete bring? What persona do they hold, what policies do they operate by, what principles run underneath?

These are two separate forces meeting at the schema layer. What the athlete brings and what the game demands. When they are in alignment, the athlete is playing with full-stack coherence — beliefs, behaviour, and environment pulling in the same direction. When they are out of alignment, something is fighting. The schema makes visible where that fight is happening.

Where Founders Break — and Why

Each layer is a potential constraint.

When code is the constraint, the founder has clarity on the game and a functional business — but something underneath keeps pulling in a different direction. The energy isn't there. The decisions that should be easy feel hard. The appetite for the work has shifted. This is back end code that hasn't been accounted for, or foundational language that's out of alignment with the game being played.

When the model is the constraint, the founder is capable and motivated — but operating inside a game that isn't structured for them to win. The market isn't defined. The business has no coherent rules. Leadership is working off instinct rather than a framework. The energy is real but it's not being channelled through a system that can hold it.

When the schema is the constraint, both the athlete and the model are present — but they're not in alignment. The founder can articulate who they are and what game they're playing. But the decisions they make in the game don't reflect either. The schema is running an old programme. The gap between intention and execution is the schema gap.

The mistake most coaching approaches make is to address the symptom at whatever layer it's most visible. If revenue is the problem, fix the market strategy. If the team is misaligned, fix the communication. These are model-layer interventions applied to symptoms that are often schema-layer or code-layer problems.

You cannot fix the top layer by working the top layer if the constraint is underneath it.

Full-Stack Alignment

The goal of coaching inside the Performance Stack is full-stack alignment — the state where the code, schema, and model are pulling in the same direction at the same time.

This is not a destination. It is a dynamic. A founder in full-stack alignment isn't finished — they're competing at their current level with coherence, and can feel the next level from where they are.

What full-stack alignment produces:

• Decisions that feel clear rather than contested
• A team that can hold alignment without constant reinput from the founder
• Market behaviour that matches strategic intent
• The capacity to see what needs to change before it becomes a crisis

The performance stack is bidirectional. Each layer has leverage over the others. Code shapes how the model is built. The model rewrites the code when it produces undeniable evidence. The schema is the live connection point where both forces meet and the athlete learns to navigate between them.

This is why Hillspeed starts with the athlete, not the company. The stack runs through a person. Align the person and the model follows. Miss the person and the model is just a framework.

Diagnosing Your Stack

Three questions. One for each layer.

Code: What dimensions of your life are you actually directing your code toward right now — and is that a conscious choice, or is something running it for you?

Model: Can you describe the game you're competing in with enough specificity to know whether you're winning it? Not aspirationally — objectively.

Schema: Between what you believe you are and how you actually show up in your game — what's the gap? What decisions are you making that don't match either the person you know you are or the model you've built?

The layer with the most friction is the constraint.

Frequently Asked Questions