AIM Works started from a problem I kept running into as a mechanical engineer: the engineering wasn't the hard part — the workflow was fragmented across calculation tools, spreadsheets, standards, equipment selections, and documentation. AIM Works is being built to connect those steps while keeping the engineer in control of the design.
The industry has good calculation engines. What's missing is the process around them: loads in one program, ventilation in a spreadsheet, selections in a third place, and the reasoning behind each number in someone's head. Every handoff is a chance for the numbers to drift apart, and a reviewer has to rebuild the chain to check them.
AIM Works keeps that chain in one project, from setup through deliverables, so the reasoning travels with the design.
The AI drafts scope, zones, and changes. The engineer reviews every change, applies judgment, and signs. Results are advisory, and the result itself says so.
Every calculation names its method and code edition and carries a Validated, Advisory, or Reference label. We would rather mark something Reference than let it be issued on trust it hasn't earned.
A module earns Validated only by matching a reference value, and those checks re-run in an automated test suite on every change. Everything else ships as Advisory until it earns the label.
The methodology is public, the limitations are listed, and the free calculators carry their own equations. If something doesn't hold up, we want to hear about it.
Demos, support, and the calculation engines all run through the engineer who built them.
Mechanical engineer based in Cincinnati. Wrote the calculation engines and checks them against published references and an automated test suite that re-runs on every change.
AIM Works launches October 15, 2026. Demos are open now. Bring a project and tell us what would make it useful in your work.
Book a Demo