Advise a client choosing between polished concrete and terrazzo
domain: ntma.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Compare substrate dependency: polished concrete uses the existing structural slab as the finished wear surface, while terrazzo is an applied topping/matrix system independent of the underlying slab's aesthetic quality.
Weigh consistency risk: polished concrete finish quality depends heavily on the original slab's mix design, aggregate, and placement quality, which is harder to control on existing/older slabs, whereas terrazzo's aggregate and matrix are specified and installed fresh for a more consistent, designed appearance.
Compare design flexibility: terrazzo supports custom color/aggregate blends, logos, and precise divider-strip pattern work more readily than polished concrete's inherent-aggregate look.
Evaluate cost and schedule: polished concrete is generally lower material cost and faster where an existing slab is suitable, while terrazzo (especially cement/sand-cushion systems) carries higher material/labor cost and longer install time but offers a long service life and a well-established re-polishing/restoration path.
Consider long-term restoration: both systems support mechanical regrinding/repolishing over decades, but a poor-quality or heavily patched slab caps what polished concrete can achieve, while terrazzo's applied topping isn't limited by the underlying slab's cosmetic condition.
Known gotchas
Polished concrete quality is capped by the original slab — a poor-quality or heavily patched existing slab won't polish to a high-end architectural finish regardless of grinding process, so don't spec it without first evaluating the slab's aggregate exposure and surface quality.
Don't treat these as interchangeable 'similar-cost' options — they have materially different cost, schedule, and design-flexibility profiles that should be modeled for the specific project rather than assumed equivalent.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?