CAD & BIM Software Developer

Hey, I'm Justine.

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.

Revit APIAutoCAD .NETAutoLISPWPF ToolsAPS / Cloud
Where The Work Usually Starts

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.

  • Repeated sheet exports
  • Manual Revit family placement
  • CAD cleanup before issue
  • Title block consistency
  • Missing links and references
  • Legacy AutoLISP tools
  • APS extraction handoff
Ways I Can Help

Start with the sentence your team keeps repeating.

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

Revit API Tool Development

Custom Revit add-ins for model checking, alignment, sheet workflows, schedules, exports, and automation.

We need tools our team can actually use

AutoCAD Automation

AutoCAD .NET, AutoLISP, tool palettes, batch processing, standards checking, drawing cleanup, and productivity tools.

We need cloud or APS automation

APS / Autodesk Cloud Automation

Autodesk Platform Services workflows for model derivative, ACC/Docs integration, PDF/DWG extraction, cloud processing, and data pipelines.

We need better CAD/BIM standards

BIM/CAD Workflow Automation

Tools that connect models, drawings, spreadsheets, and project data into cleaner workflows.

Our old tools are hard to maintain

Legacy Tool Modernization

Converting older AutoLISP scripts into maintainable C#/.NET applications.

We need documentation so tools get adopted

Technical Documentation & Training

User guides, onboarding decks, workflow documentation, and support materials for internal tool rollout.

Tooling Context

The stack is only useful when it fits the workflow.

These are the languages and platforms I use to turn CAD/BIM production logic into tools people can maintain, explain, and roll out.

Programming Languages

  • AutoLISP
  • C#
  • JavaScript
  • Visual Basic
  • VBA
  • Google Apps Script
  • PML

Engineering and Architecture Software

  • Advance Steel
  • AutoCAD
  • AVEVA Everything
  • CubiCost
  • Mathcad
  • Navisworks
  • PDMS
  • Revit
  • SketchUp

Documentation, Estimating, and Handoff Tools

  • Access
  • Canva
  • Excel
  • PowerPoint
  • Photoshop
  • Word
Why Work With Me

Software built close to drawings, models, standards, and deadlines.

DevCAD sits between AEC production and software development: understanding how drawings are issued, how Revit models get messy, and how internal tools need to fit into real delivery habits.

Read My Background
  • 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.

Tell me the workflow that keeps wasting your team's time.

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.