ENCY CAM · product page refresh

Concept brief — A / B / C

ENCY CAM product page — 3 concept directions

Synthesized from: current page state (01), ENCY 2.0 features (02), competitor landing analysis (competitors/cam-landing-pages-research.md), community pains (03).

Brand non-negotiables (from vault + past feedback)

Concept A — "The Honest CAM" (pain-led)

Premise: Every competitor is hated for the same five things — crashes, broken posts, maintenance extortion, lathe afterthought, cloud lock-in. Lead with calm, confident "we don't do that." Most aggressive of the three.

Hero - H1: "CAM that doesn't crash. Posts that work day one. Pricing that doesn't trap you." - Sub: "ENCY CAM is built for shops that are done losing toolpaths, waiting six months for a working post, or paying to fix bugs they already bought." - Primary CTA: Download 30-day trial (visible, hero-level — not buried) - Secondary CTA: Book a 20-minute demo with a CAM engineer

Above-fold proof - One named customer + measured outcome: "[Customer X] — programming time for [class of part] cut from 4 hours to 35 minutes. Single post. Zero revisions." - Three trust strips: "Stable mid-job" • "Post validated for your machine, in-house" • "Flat, published pricing — no maintenance paywall"

Section flow 1. Hero (anti-pain headline + UI screenshot, not workshop photo) 2. Anti-pain pillars (4 cards, each addresses a documented community pain): - Stable mid-job — toolpath calc that survives geometry edits, background collision detection during calc (not just sim) - Posts that work — two in-house postprocessor systems (SPPX generator + open .NET), pre-validated for common machine + control combos - Mill, lathe, multi-axis & EDM in one seat — no per-axis upgrades, no lathe afterthought - Transparent pricing — published model, no "maintenance to unlock fixes" 3. The 12 strategies grid (kept from current page — it's working) 4. "See the AI propose a toolpath" — concrete AI demo with actual part + actual G-code, not abstract "AI-driven" claim 5. ENCY X ecosystem (MachineMaker, ENCY Robot, ENCY Clouds) — compact cross-sell strip, links out; not the CAM hero promise 6. Pricing block — show the model even if not exact numbers (per-seat, perpetual + maintenance vs annual subscription) 7. Free trial + Get a quote (final CTA pair) 8. Customer story + named contact for sales engineer

Tone: confident, factual, slightly pointed. Anti-marketing posture is the marketing.

Risk: positioning against competitors' weaknesses can read as petty. Mitigation: don't name competitors, just state what we do — and what shops are tired of (in shops' words, via testimonials).

Best when: ENCY is willing to commit publicly to a stability + pricing + post-quality SLA. If the product team can't back the claims, this concept hurts more than it helps.

Concept B — "Go Beyond CAD/CAM" (modern-CAM-led)

Scope note (per @a.kh, 2026-05-25): ENCY CAM is a CNC-only product. Robots / MachineMaker / Multi-channel are separate products under the ENCY X umbrella. They appear only in an "ENCY X ecosystem" cross-sell strip near the bottom — never in hero / USP.

Premise: "Go Beyond CAD/CAM" reframed for CNC: ENCY CAM is more than a toolpath generator. It is a modern CAM with built-in AI, machine-aware planning, true-solid simulation, and additive + subtractive in one seat — strategies and a technology stack legacy CAMs don't carry as defaults. Vault tagline preserved; meaning sharpened to a CNC story.

Hero - H1: "Go Beyond CAD/CAM." - Sub: "A modern CAM platform — AI-assisted programming, machine-aware toolpaths, true-solid simulation, mill, turn, multi-axis, EDM and additive in one seat." - Primary CTA: Start for free (30-day trial) - Secondary CTA: Talk to a CAM engineer

Above-fold proof - Hero visual: a single ENCY UI screenshot of a complex multi-axis part with toolpaths + sim viewport — no stock workshop photography - Outcome strip: "[Customer X] — programming time for [class of part] cut from 4 hours to 35 minutes. Single post. Zero revisions."

Section flow 1. Hero (UI screenshot, mono labels, no editorial) 2. What "beyond" means here — four pillars (each a card with one concrete proof, doc link, demo gif): - AI built into CAM — In-CAM AI assistant (ChatGPT-based, G-code + macros + Python) and AI auto-generation that proposes operations from your part model - Machine-aware, not just simulation — background collision detection during toolpath calculation, machine-space link planning, true-solid sim with axis & material-removal graphs - Every strategy in one seat — mill, turn, mill-turn, HSM/adaptive, Swiss/MTM, 5-6D multi-axis, EDM, additive (Cladding 3D/5D, non-planar slicing) - Two in-house postprocessor systems — SPPX generator and an open .NET system you can extend in VS Code; posts validated against the same kinematics CAM uses 3. 12 strategies grid (preserve from current page — high-utility section) 4. See the AI do the work — single concrete demo: prompt → proposed operations → resulting toolpath, on a real part (screen recording or image sequence) 5. Technological independence — proprietary stack, no third-party licensing, your G-code stays on your machine 6. ENCY X ecosystem (compact cross-sell strip): MachineMaker (digital-twin builder), ENCY Robot (separate product for industrial robot programming), ENCY Clouds (collaboration). Single line each, links out — not part of the hero promise 7. Pricing + trial + dealer locator 8. Customer story / case (named, with outcome)

Tone: confident, technical, "the platform is the differentiator." Less anti-competitor than A, more "look at the stack a 2026 CAM should have."

Risk: "modern CAM" is a soft frame on its own. Mitigation: every pillar leads with a concrete documented capability + a doc link + a demo — the page sells by stacking specific proof, not adjectives.

Best when: ENCY wants to consolidate brand around the actual ENCY-2 feature stack (AI + machine-aware + multi-tech + additive) without leaning on robots, and attract programmers shopping a modern Fusion/Mastercam alternative.

Concept C — "Programmed on a digital twin. Cut on the machine." (machine-aware/twin-led)

Premise: ENCY's machine-awareness story is its deepest tech differentiator — every operation is generated and verified against a real digital twin of the actual machine, not a generic kinematic. This single insight addresses the post-processor pain, the collision pain, and the "I lost a day because the sim missed something" pain at once.

Hero - H1: "Program on a digital twin. Cut on the machine." - Sub: "ENCY CAM checks every toolpath against your actual machine kinematics — collisions, axis limits, post — before a single line of G-code leaves the software." - Primary CTA: Download trial — see your machine in the twin - Secondary CTA: Find a dealer / Get a quote

Above-fold proof - Hero visual: split — the CAM UI with toolpath + a 3D twin of an actual machine running the same toolpath, with collision highlights - Outcome strip: "[Customer X] — first program ran the first part. No edits, no recovery, no scrap."

Section flow 1. Hero (UI + twin split, not stock workshop) 2. What machine-awareness means — three blocks: - Background collision detection during toolpath calc (not just simulation — catches issues while you're still in the operation, not after) - Posts validated against the twin (the .NET / SPPX postprocessor knows the same kinematics — no "20 revisions" story) - True-solid simulation (not voxel-only) with axis graphs and material-removal analytics 3. Build the twin once, run everything on it — MachineMaker (no programming required) + free Robot Components library 4. ENCY X ecosystem (compact cross-sell strip — MachineMaker / ENCY Robot / ENCY Clouds; one line each, links out; not part of the CAM promise) 5. 12 strategies grid (preserve) 6. AI that explains itself — in-CAM AI assistant + auto-generation, with a real example 7. Technological independence — your stack, your G-code, no third-party gates 8. Pricing / trial / dealer 9. Customer story with named outcome

Tone: technical-credible, confident, "show your work" — every claim is backed by a doc link, a video, or a numbered outcome.

Risk: "digital twin" is becoming buzzword territory (ESPRIT, NX, Siemens). Mitigation: show the actual twin with the actual machine name in the hero visual — specificity beats label.

Best when: ENCY's primary buyer is a senior programmer / production engineer who cares about cycle-time, scrap rate, and confidence-on-first-run. Slightly higher-end positioning than A.

Comparison

Dimension A — Honest B — Beyond CAD/CAM C — Digital Twin
Primary hook Pain-relief Unique platform Machine-awareness
Risk profile Highest (anti-competitor lean) Medium (robot may dilute CAM-only buyer) Lowest (positive + technical)
Marketing energy required High (must back claims) Medium (already vault-aligned) Medium-high (must show twin specifically)
Buyer this attracts most SMB shop owners frustrated with current vendor OEM / integrator / multi-tech shop Senior programmer / production engineer
Vault alignment Partial — implicit Direct (tagline match) High — pillar match
Differentiation strength Strong if backed Strongest (unique) Strong (table-stakes for premium tier)
Build complexity (wireframe) Medium Medium-high (split visuals) Medium-high (twin visuals)

Mix recommendation (one possible blend)

A pure pick is fine; a blend is also possible. Recommended blend: B as primary ("Go Beyond CAD/CAM" — modern CNC CAM with AI + machine-awareness + multi-tech, vault-aligned tagline), C's machine-awareness + digital-twin pillar as the strongest features section, A's transparent pricing + stability promise as a trust strip and pricing-section anchor.

This blend keeps the brand voice, leads with the actual CNC-product story, addresses the documented community pains as proof rather than primary message, and lets the page operate without naming competitors or mixing in the Robot product.

Open questions for @a.kh before wireframe

  1. Concept pick — A, B, C, or blend? (one or two wireframes?)
  2. Pricing transparency — do we have a published model we can put on the page? (per-seat / perpetual + maintenance / annual / per-axis?) If yes, this is a category-disruption move. If not, we still call out "no maintenance paywall for bug fixes" as a trust strip.
  3. Named customer + outcome — do we have one that's clearable for landing-page use? (Even one named SMB with a measured cycle-time win is enough.)
  4. AI demo asset — is there a screen recording or screenshot of the AI assistant in-action we can use, or do we render a static "here's the prompt → here's the proposed toolpath"?
  5. Trial CTA — should it remain "Start for free" (30-day Trial) or shift to something more concrete ("Download trial — works offline")?