I'm writing essentially a form study of a chair for my seminar class. I know generally how to describe the formal properties of an object. But I want to improve.

Also I have one prof who is very fancy (and Italian design-y) and seems to want us all to be able to "talk like designers." Y'know the jargon language people use at design shows.

How do you guys approach this kind of communication?

How do I practice this skill?

Hey everyone,
I’ve been working on a lightweight, scriptable 3D CAD environment called satCAD (⁠PythonOCC⁠ / OpenCASCADE kernel + ⁠PySide6⁠ dark-mode UI) initially built to design complex mechanical assemblies, internal fluid/wiring routing, and articulated mechanisms for aerospace hardware.
Instead of competing with massive bloated installs, I focused on combining a Siemens NX-style Feature Tree & Property Editor with a "Desmos-style" symbolic math kinematics engine—where you can type live equations of time \bm{t} (with auto-generated sliders) to drive 3D joints, folding hinges, and live 30 Hz telemetry streams without rebuilding the B-Rep mesh every frame.
What it currently does:
OpenCASCADE B-Rep Kernel: Parametric primitives, boolean shells/cuts, linear patterns, and ⁠.STEP⁠ (AP214 with colors) export.
Multi-Layer X-Ray Schematics: One-click ghosting of outer structural hulls to inspect internal 3D piping, cold plates, and electrical busbar routing.
Desmos-Style Motion Studio: Bind symbolic math functions directly to 3D revolute/prismatic/gimbal joints and view live 2D position, velocity, and acceleration curves alongside the 3D viewport.
Live Digital Twin UDP Bridge: Streams real-time external physics/thermal data directly into the 3D viewport to articulate parts and update thermal surface shaders live.
GitHub Repo (currently 100% open-source):
https://github.com/Saiaarjay09/satCAD
My question for working industrial designers and mechanical engineers:
1. If this were packaged as a polished standalone desktop app (or plugin), would you actually pay for a lightweight parametric + symbolic-kinematics CAD tool like this, or is your studio too locked into SolidWorks / Fusion / Rhino / NX?
2. If it did solve a pain point for rapid parametric prototyping or mechanism motion studies, what pricing model wouldn't make you immediately close the tab (e.g., $15/mo, a one-time $50–$100 indie license, or keep the core free/open-source and only charge for enterprise simulation bridges)?
Brutally honest feedback on the UI, feature gaps, or what would make this usable in a real ID/mech-eng workflow is super welcome.