We keep doing this manually
Revit API Tool Development
Custom Revit add-ins for model checking, alignment, sheet workflows, schedules, exports, and automation.
Focus Stack
I work close to real CAD/BIM production problems: repeated clicks, slow exports, missing references, and standards that are easy to break under deadline pressure.
I build practical tools for Revit, AutoCAD, and AEC workflows so teams can reduce repetitive work and deliver with more consistency.
Most useful automation starts as ordinary production friction: the step someone repeats every week, the check that depends on memory, or the old script the team still needs but no longer wants to maintain.
The work may become a Revit add-in, an AutoCAD command, a WPF desktop tool, an APS workflow, or a better-documented internal process. The starting point is the production friction.
We keep doing this manually
Custom Revit add-ins for model checking, alignment, sheet workflows, schedules, exports, and automation.
Focus Stack
We need tools our team can actually use
AutoCAD .NET, AutoLISP, tool palettes, batch processing, standards checking, drawing cleanup, and productivity tools.
Focus Stack
We need cloud or APS automation
Autodesk Platform Services workflows for model derivative, ACC/Docs integration, PDF/DWG extraction, cloud processing, and data pipelines.
Focus Stack
We need better CAD/BIM standards
Tools that connect models, drawings, spreadsheets, and project data into cleaner workflows.
Focus Stack
Our old tools are hard to maintain
Converting older AutoLISP scripts into maintainable C#/.NET applications.
Focus Stack
We need documentation so tools get adopted
User guides, onboarding decks, workflow documentation, and support materials for internal tool rollout.
Focus Stack
A few examples from the places where production teams lose time: Revit geometry, CAD-to-BIM placement, internal tool access, Autodesk cloud extraction, and repeatable technical delivery work.
Technologies
Case Study
A geometry-driven Revit workflow for site teams who needed faster terrain alignment without repeatedly editing surfaces by hand.
Problem
Topography alignment in Revit was too manual for repeated landscape workflows.
Approach
Designed projection logic to align one Revit surface against another.
Outcome
Reduced manual terrain adjustment and improved repeatability for site modeling tasks.
Technologies
Case Study
A CAD-to-Revit placement utility for the Cracknell team that turns CAD block positions into properly placed Revit families in one step.
Problem
Placing Revit families manually based on CAD drawings was slow and error-prone, especially on large landscape projects with many repeated elements.
Approach
Developed a tool that reads CAD geometry or block references and uses their positions to automatically place the matching Revit family instances in the model.
Outcome
Significantly reduced family placement time and improved positional accuracy when working from CAD source drawings.
Technologies
Case Study
A ribbon UI that acts as the home base for all Cracknell internal Revit tools, making them discoverable and easy to access for the whole production team.
Problem
As more internal tools were built, the team had no central place to find and launch them — tools were scattered and inconsistently accessible.
Approach
Created a custom Revit ribbon tab with organized panels for each tool category, giving the team a clean, branded entry point for all internal automation.
Outcome
Unified tool access under one interface, improved team adoption, and made onboarding new tools easier going forward.
These are the languages and platforms I use to turn CAD/BIM production logic into tools people can maintain, explain, and roll out.






















DevCAD sits between AEC production and software development. The work is not only about code. It is about understanding how drawings are issued, how Revit models get messy, how CAD standards drift, and how internal tools need to fit into real delivery habits.
AEC Context
Built with drafting, BIM, and delivery realities in mind.
Usable Tools
Focused dialogs, clear buttons, useful defaults, and fewer confusing choices.
Rollout Support
Setup notes, edge cases, and handoff material so tools keep being used.
Production Tooling
1observe(workflow.beforeCode);
2buildTool(repeatedPain);
3document({ setup, edgeCases, rollout });
C#
Used for practical internal tools
JavaScript
Used for practical internal tools
AutoLISP
Used for practical internal tools
VBA
Used for practical internal tools
Workflow Logic
Clean Structure
Tooling Mindset
Send the software involved, the manual steps, where the process breaks, and what a better handoff would look like. I'll help you figure out whether it needs a small script, a Revit add-in, an AutoCAD tool, an APS workflow, or better documentation.