The architecture of a product is what gives it SOUL.
Its hierarchy is what gives it structure. But too often, we build without a map. Without asking: What holds this together? What is this really made of?
Not just “what features should we build”— But deeper questions like:
- Are we building one product or many?
- What is at the core of this thing?
- What doesn’t belong here?
- What gives this system motion and meaning?
After building for years — products, platforms, ecosystems — I began to notice a recurring internal structure. A pattern that helped me move faster, decide better, and stay true to the essence of what I was building.
I call it the CAPE Framework. It’s not theory. It’s muscle memory. A compass for product architecture and product decisions.
CAPE = Core → Abstraction → Peripheral → Elegance
🔵 Core (the primitive) Every product must have one clear, singular core. The primitive. The thing everything else rotates around.
A task. A file. A block. A post. A payment.
This is not a concept. It’s a foundation. If you have multiple cores, you don’t have a product — you have confusion. A strong product starts with one honest, indivisible primitive.
🟡 Abstractions Once the core is defined, abstractions layer on top. These help organize and extend the core.
folders, collections, views, tags.
Too many abstractions and you create a maze. Just enough — and you give users structure without friction.
The best abstractions simplify, not obscure. They reveal the core.
🟢 Peripherals These are your tools, actions, workflows — everything orbiting the system.
APIs, automations, triggers, integrations.
They move the system forward, but they are not the system itself. They exist to interact with abstractions and drive progress.
⚪ Elegance And finally, the layer that matters most to the human mind — elegance.
layouts, transitions, typography, defaults.
It’s how the core is felt. How abstractions are understood. How peripherals are discovered, not dumped. Elegance isn’t decoration. It’s expression.
Over time, I’ve realized: Great products aren’t just functional. They’re architected.
One strong core. Minimal, meaningful abstractions. Peripherals with purpose. And elegance woven through it all.
That’s what CAPE brings me. It’s how I think. It’s how I build.