The manuscript begins
We don't build catalogs.
We grow them.
Heartwood — a living catalog engine, built by MK Labs, proven first inside Evermark.
Begin with the HeartwoodTable of contents
Click a zone to enter its chapter
Chapter I — Why We Exist
A catalog that has to be maintained by hand is already dying the day it's published.
Every digital catalog platform on the market today — dCatalog, Flipsnack, Paperturn — sells the same thing: a nicer PDF viewer, billed by the page. Add a SKU, and someone has to open an editor, redesign a page, re-place a hotspot, republish. Discontinue a product, and the catalog lies until someone remembers to fix it.
And every customer who flips through it — every hotspot they click, every page they linger on, every search that comes up empty — that signal disappears the moment they close the tab. Nothing downstream ever learns from it.
That's not a catalog. That's a document pretending to be software.
Chapter II — The Heartwood
A tree's strength doesn't come from its bark. It comes from the dense, living core everything else grows around.
Heartwood starts with a living data core — a product database, illustrated here with Evermark's Product Hub — instead of a folder of static pages. The catalog isn't authored. It's grown around something that's already alive and already changing.
Old way
Catalog content lives in the catalog.
The page is the source of truth. Every change is a design task.
Heartwood way
Catalog content lives in the product data; the catalog is just where it becomes visible.
The Product Hub is the source of truth. The catalog is a rendering of it.
We don't build catalogs. We grow them.
Chapter III — The Grain
Grain is what a tree remembers about how it grew. Ours is what your catalog remembers about your products.
AI watches the product data source continuously. When a SKU is added, a finish is updated, a product is discontinued, or a spec changes, the relevant catalog pages and hotspots regenerate automatically — no editor, no re-upload, no design queue.
Old Way / Heartwood Way
| Old Way | Heartwood Way | |
|---|---|---|
| Add a new SKU | Re-design a page, re-upload, wait days | Appears in the next sync, automatically |
| Discontinue a product | Catalog quietly goes stale | Page updates or retires itself |
| Cost to grow | Priced by the page — growth costs more | Flat. Growth is architecture, not labor |
| Who maintains it | A person, manually | The data, continuously |
What changed this cycle — Evermark stair parts
Evermark Product Hub · synced 04:12
- addedMicroPlow 7500-OAKTreads / p.14
New white-oak profile, 3 finishes
- updatedProTread XLTreads / p.17
Slip rating revised to R11
- retiredMicroPlow 4100-PINETreads / p.12
Discontinued — page auto-retired
No editor opened. No re-upload. No design queue.
Chapter IV — The Rings
Every ring is a record of a season. Ours is a record of who looked, what they clicked, and where they hesitated.
Every hotspot click, page dwell, and search becomes a ring of data, mapped onto a customer adoption journey: Discover → Understand → Believe → Try → Adopt → Advocate. Instead of "page 6 got 40 views," Heartwood surfaces something like "Branch 12's reps are stuck at Understand on ProTread — nobody's opened the stability comparison in three weeks" — which can trigger a rep follow-up automatically or flag on a leadership dashboard.
Engagement rings — mocked reading of Evermark's catalog
Discover
89%
Understand
81%
Believe
73%
Try
31%
Adopt
23%
Advocate
15%
Signal, not pageviews
MicroPlow searches at Branch 04 returned zero results 11 times. There's demand for a profile you don't list.
Chapter V — The Branches
Branches are where a tree reaches toward people. Ours reach toward the moment someone's about to say no.
When a rep or dealer clicks a hotspot, an AI panel surfaces objection-handling content tailored to that exact product — "Engineered isn't real hardwood" gets a stability comparison, live, not a static spec sheet buried in SharePoint. From the same panel, a rep can generate an instant branded comparison PDF between two products, on demand.
Rep view — hotspot clicked
ProTread XL — engineered stair tread
“Engineered isn't real hardwood.”
ProTread XL is a 4mm sawn white-oak wear layer over a cross-laminated core. It moves 62% less than solid oak across a 20–80% humidity swing — the same reason we spec it for open-riser installs in unconditioned builds.
- Dimensional stability: ±0.4mm vs ±1.1mm solid
- Static load: 400 lb
- Refinishable: 2 cycles
Chapter VI — The Canopy
A canopy doesn't stop growing at the edge of one tree. It reaches toward the next.
Heartwood isn't a closed feature — it's a connection layer. It reaches outward to a product data hub, a sales-sheet and deck generator, a product configurator, and a leadership analytics dashboard. Every new integration is a new branch reaching further, not a new silo.
Product Data Hub
The living core — SKUs, finishes, specs, lifecycle
Sales Sheet & Deck Generator
Branded collateral assembled from the same grain
Product Configurator
Buildable combinations validated against real inventory
Leadership Analytics
Adoption rings rolled up by branch, region, product line
We don't build catalogs. We grow them.
Chapter VII — Two Ways to Grow
One way is carved. The other grows.
Static flipbook platforms / Heartwood
| Static flipbook | Heartwood | |
|---|---|---|
| Cost model | Per page, per year. Every product you add raises the bill. | Flat platform cost. Catalog depth is free to grow. |
| Update cycle | Manual, batched, measured in weeks. | Continuous. Data changes, pages follow within the sync. |
| Analytics depth | Pageviews, time on page, a heat overlay. | Adoption-stage signal per product, per branch, per rep. |
| Sales enablement | Download a PDF and hope the rep found the right one. | Objection handling and comparison docs generated in the moment. |
| Extensibility | A closed viewer. What you see is the whole product. | A connection layer — hub, configurator, decks, dashboards. |
Epilogue — The Grain Remembers
Cut a tree down and count the rings — every season it lived is still there. Nothing a customer ever did inside this catalog should disappear either.
Every launch, every engagement pattern, every objection a rep overcame becomes part of what the system knows next time. The catalog stops being a document you publish and forget. It becomes organizational memory that keeps growing whether or not anyone remembers to maintain it.
We don't build catalogs. We grow them.