Meeting with Denis Schmitz¶

Source files: C:\Users\adeel\OneDrive\100_Knowledge\203_TextCAD\10_Pilots\01_Denis\Meeting minutes\Meeting_Minutes_2026-03-11.docx, C:\Users\adeel\OneDrive\100_Knowledge\203_TextCAD\10_Pilots\01_Denis\Meeting minutes\Meeting_Minutes_Denis_Schmitz_Follow-Up.docx Last synthesized: April 2026 Context: Expert feedback on RapidDraft positioning, DFM scope, demo priorities, and pilot presentation.

Overview¶

These two meetings sharpened how RapidDraft should be presented to manufacturing-facing teams. The strongest recurring message was that RapidDraft should not be framed as a fully finished expert system. It should be framed as a structured review layer where companies encode their own design guidelines, run repeatable checks, and get a clear result presentation that feels like an experienced design engineer is supervising routine work.

The notes also added one adjacent pilot signal from the same source bundle: H55 in Switzerland showed specific interest in injection-molding DFM review, which is a useful validation point for the molding wedge.

April 22, 2026 Follow-Up (Advisor Delta)¶

The April 22 advisor note reinforced the same direction but made priorities much more explicit:

The highest-value demo is the rule-editing loop: define rule, edit threshold or condition, rerun on the same part, and show before/after finding change.
The first-run user experience needs clear hierarchy: Required rules for gatekeeping and Recommended rules for optimization.
Injection molding remains the strongest near-term wedge when tied to measurable warpage proxies such as mass concentration, rib-crossing density, and section-thickness imbalance.
Go-to-market should stay vertically focused by manufacturing process, instead of pitching broad multi-process coverage in the first conversation.

Product Translation of the Follow-Up¶

Signal from follow-up	Product implication
"Rule Maker" must be visible and editable by supervisors	Keep policy-authoring as a first-class workflow, not hidden in advanced settings.
Required vs Recommended rule tiers	Add explicit rule-tier metadata in UI and report outputs.
Warpage and mass concentration are pain-first in molding	Keep injection route investment tied to measurable geometry evidence and clear physics language.
Discovery before generic demo	Lead pilots with company-specific pain mapping before running technical walkthroughs.

Durable Product Signals¶

Positioning¶

Present RapidDraft as a template and guideline framework, not a universal "master solution."
Emphasize that companies can feed their own design guidelines into the system and get validated, repeatable outputs back.
Use the language of codified expert knowledge or an experienced design engineer supervising routine work, rather than "fully autonomous engineering."
Do not present the product as fully finished or off-the-shelf during early pilots.

Result Presentation¶

Show standards-ingest and rule coverage during demos so the product feels grounded in real engineering knowledge.
Use a simple visual rating layer for findings. The meetings suggested an AMPLE-style traffic-light presentation so results can be scanned quickly.
Prepare a reusable visual template for how rules, evidence, and outcomes are presented in pilot conversations.

DFM Scope Priorities¶

The meetings highlighted a practical DFM demo surface that is concrete enough for pilots:

Focus area	Specific examples called out	Product implication
Injection molding	Draft angle, minimum radii, cold runner recommendation, strut dome case	Keep molding in the demo story even if machining and sheet metal remain the easier starting point.
Casting	Add aluminium casting support	Broaden process coverage carefully where expert feedback is concrete.
Visual evidence	Cross-sections on demand, thickness analysis with clipping	Make DFM findings inspectable, not just textual.
Geometry-risk checks	Rib intersection detection, unbalanced wall-thickness distribution, concentrated mass	Build a measurable-rule inventory behind each finding.
Physics-aware warnings	Warpage prediction, mismatching CTE	Treat as guidance or expert-warning layer unless backed by deterministic inputs.

Rule Authoring and Searchability¶

Build a table of measurable input variables for each DFM check so every rule has a clear data contract.
Separate a baseline checklist from an enhancing checklist to keep pilot deployments simpler.
Make DFM knowledge searchable through terms such as warpage, minimum wall thickness, minimum draft angle, concentrated mass, and avoid too many ribs crossing.

Drawing Generation Wedge¶

Repetitive, routine drawings are a stronger wedge than highly specialized one-off drawings.
RapidDraft should feel like a design supervisor for routine parts, where consistency and review speed matter more than heroic drafting intelligence.
Process-specific workflow still matters: injection molding can start from a single STEP file, while sheet metal and laser-cut workflows stay much more drawing-centric.

Go-to-Market Signals¶

Buyer Framing¶

Do not treat designers as the only audience.
The meetings explicitly widened the buyer map to include CEO, CTO, and CFO level stakeholders when the pitch is about review cost, consistency, and captured engineering knowledge.

Outreach and Ecosystem¶

Early channels suggested in the meetings included Designer Magazine and Konstruktionspraxis.
Public positioning should be checked against Simulia so RapidDraft is framed as complementary to an AI design-coach narrative rather than accidentally colliding with it.

Pilot Validation Signal¶

H55 was called out as specifically interested in injection-molding DFM review.
This is useful evidence that the molding wedge is not just theoretical, even if the broader product still leads with more deterministic review surfaces.

Concrete Next Actions From the Meetings¶

Define one consistent result-presentation template for demos and reports.
Prepare three example parts that show the intended review flow clearly.
Add measurable-variable definitions behind each DFM rule candidate.
Keep the demo language focused on customer-specific guidelines and repeatable review, not full automation.

Open Questions¶

Which subset of the suggested DFM checks can be made deterministic soon enough for pilot use?
Should the AMPLE-style rating system be a shared reporting pattern across RapidDraft, or only a demo-layer convention?
How closely should RapidDraft position itself next to Simulia's design-coach framing versus staying separate?

Sources¶

C:\Users\adeel\OneDrive\100_Knowledge\203_TextCAD\10_Pilots\01_Denis\Meeting minutes\Meeting_Minutes_2026-03-11.docx
C:\Users\adeel\OneDrive\100_Knowledge\203_TextCAD\10_Pilots\01_Denis\Meeting minutes\Meeting_Minutes_Denis_Schmitz_Follow-Up.docx
C:\Users\adeel\OneDrive\100_Knowledge\203_TextCAD\01_Product_Project_Management\TextCAD_Wiki\docs\01_RapidDraft\_sources\Denis_Feedback_22April2026.docx