2Box
Method
Every build gets scoped using our proprietary 2Box method, before a line of code exists. One box holds everything the business runs on. The other holds what the customer experiences. The lines between them are where everything else lives.
What engineers call entity modeling, three-tier architecture, and middleware — arrived at from scratch.
The method in six moves
One big box.
Most people see a problem as one big box in the way, and they push it harder.
Step back.
We get ten thousand feet above the box and watch the person pushing it. From up there the whole shape is visible.
Cut it in half.
One half is how the work runs today. The other half is how it should feel when it works.
Push the halves apart.
The space between them is where the problem gets solved.
Work the gap.
Fill it with the inner workings: the lines, the options, the questions. One sign-in, a phone that works, sheets or forms. One idea leads to the next, and everyone in the room can see it.
Hand it to the tools.
Pictures, notes and a voice memo go into a prompt for AI builders like Replit, v0 or Claude. What comes back is already close to the right-hand box. Then we refine.
Paddock20 Build Framework: full method taught inside the course
Everything the business runs on, in one place: data points, business logic, services, APIs — organized so nothing gets asked for twice.
Workflows. Nuance. IP. Flow. Nice-to-haves. The connection path between raw material and finished experience — plus every step in between, infinitely.
What the customer sees, feels, and walks through. Deliberately sparse. Specified so precisely there is nothing left to guess at build time.
Learn the framework.
Ship the software.
“The operation is now being built into the software. The two boxes came first. The architecture theory came after.”
Gavin Brooks · Paddock20