The 7-layer model I use for any product I build
Most product visions are flat. Mine is stacked. Each layer compounds the one below.
The premise
When I started Struvo I drew a flat product map: features down the left, customers across the top. Useful. Wrong shape.
The right shape is layered. Each layer below is the substrate for the layer above. Cut the bottom layer and the top falls. Add a top layer and the whole stack compounds.
Here's the 7-layer model I now use for any product I build.
Layer 1: Capture
The cheapest, most boring layer. Voice memo, photo, handwritten note, web form, email reply. Whatever the user already does.
The whole thing fails if Layer 1 is too friction-heavy to use daily. I've watched two products die because Layer 1 required a behavior change. Don't.
Layer 2: Normalize
Take the messy capture and make it queryable. Transcription, OCR, parsing. The data leaves Layer 2 typed.
This is where most products stop. They sell normalized data and call it a day.
Layer 3: Extract
Pull entities out. Names, dates, dollars, decisions, tasks. The data leaves Layer 3 with structure.
Layer 3 is where the product starts feeling intelligent. Up to here it's just plumbing.
Layer 4: Connect
Link entities across captures. "This task was created in last week's meeting; this dollar amount belongs to that vendor; this photo shows the same wall as the inspection on Tuesday."
Layer 4 is where the product becomes a system instead of an inbox.
Layer 5: Synthesize
Generate something new from the connections. A weekly digest. A predicted blocker. A flagged anomaly. A draft proposal.
Most products THINK they're at Layer 5 when they're actually still in Layer 3. The test: did the synthesis surface something the user didn't already know?
Layer 6: Recommend
Tell the user what to do next. With confidence, with evidence, with the alternatives ranked.
Layer 6 requires a real model of the user's goals. Most products skip Layer 6 because they don't have that model.
Layer 7: Act
Do the thing. Send the email. Schedule the visit. Pay the invoice. With approval gates the user controls.
Layer 7 is where the product starts replacing labor. It's also where you face the highest legal and trust bars. Don't skip Layers 5 and 6 to get here.
The compounding rule
Each layer makes the layer below more valuable. Better Layer 4 (connect) makes Layer 5 (synthesize) much smarter. Better Layer 6 (recommend) makes Layer 7 (act) safe to ship.
Skip a layer and you're shipping a magic trick instead of a product. Magic tricks fail when the user trusts them.
What you can steal
Drawing your product as 7 stacked layers — even if your product only ships 3 of them — does two things:
- It tells you which layer is broken when users churn.
- It tells you which layer is the next investment that compounds.
For Struvo, we're shipping Layers 1-4 in V1. Layer 5 is where the product becomes hard to displace. Layer 6 is the upsell. Layer 7 is the acquisition story.
If you can't draw your product as a stack, you're shipping a feature, not a product.