I build practical civil engineering software for teams that need results, not software gymnastics.
My platform has two parts that work as one system:
1) a CAD add-on for AutoCAD and AutoCAD LT, and
2) a standalone companion for focused workflows outside the drawing session.
My purpose is simple: remove the gap between what projects demand and what everyday CAD setups can actually deliver.
In many offices, the workflow still breaks at the worst moments: survey data arrives in one format, design happens in another, quantities are checked somewhere else, and handoffs between tools create delay, rework, and avoidable mistakes. Teams switch context too often, re-enter data, and lose confidence in version-to-version consistency.
I built this bundle to solve exactly that.
The CAD add-on gives civil and survey teams the capabilities they usually expect only from heavier, more expensive stacks – while staying in the DWG environment they already use. On AutoCAD LT in particular, this is a major shift: I bring real terrain and section workflows into an environment traditionally centered on 2D drafting.
What I offer in CAD:
- 3D terrain/TIN-style modeling from project data
- Volume calculations by elevation and between surfaces
- Section workflows, including longitudinal and chainage outputs
- LAZ point-cloud integration for survey and as-built coordination
- LandXML import/export for open interoperability across platforms
- A synced 3D viewer workflow for LT users who need true spatial review
This matters because the industry is moving toward open exchange and multi-platform collaboration. LandXML remains a critical bridge for civil data transfer, and LAZ has become a standard way to manage dense lidar data efficiently. I designed my tools around these realities so your team can exchange data with less friction and less vendor lock-in.
The standalone companion extends the same philosophy: fast, focused utilities for processing, validation, and delivery tasks that should not require bloating the CAD session. Together, the add-on and standalone components reduce tool switching, reduce manual translation work, and keep your delivery pipeline cleaner from field data to final output.
Who I serve:
- Survey and civil teams working under tight deadlines
- Offices balancing capability against software cost
- Firms that need LT seats to do more than “just drafting”
- Projects that require reliable interoperability, not isolated files
What makes my approach different is not just feature count – it is workflow continuity. I do not ask teams to abandon their environment. I make that environment more capable, more connected, and more production-ready.
I am not trying to replace AutoCAD. I am unlocking it for civil work at the level teams actually need: model, calculate, section, exchange, review, and deliver – with confidence.