Skip to content

Software for the jobs CAD and ERP don't cover

Desktop tools and integrations, built by engineers who have spent years in CAD. Your CAD, ERP, and file server stay where they are. We connect to them.

What we build

Most projects are one of these, or a mix. We write them in C#, .NET, Python, and VBA.

Standalone tools

Desktop and web apps for jobs that don't fit in CAD or ERP, like estimating, nesting, or job tracking.

Parts and product data

One parts list that CAD, ERP, and the shop floor all read from, with rules and revisions set up once.

APIs and background jobs

Services that move data between your design tools and business systems, so nobody copies it by hand.

AI for narrow, boring jobs

Like pulling requirements out of a 40-page spec. Anything the model is not sure about goes to an engineer first.

More on AI tools

How a software project runs

Same team from the first site visit to support after launch.

  1. 01

    We visit before we quote

    We see how an order moves through your shop, and meet the people who will use the tool, before pricing the work.

  2. 02

    We plan around what you run

    Data and integrations are designed around your CAD version, your ERP, and your IT rules, on your own servers or AWS.

  3. 03

    You see it early

    We test screens with the engineers, estimators, and operators who will use the tool, then demo working software as it comes together.

  4. 04

    Tested, documented, handed over

    Every rule runs against past orders before release. You get documentation and training, and we stay on after launch.

Got a job that doesn't fit in CAD or ERP?

Send us a drawing or describe the process. An engineer will reply within a day.