How it runs: Lift request, then Collision check, then Shareable plan.
The problem
Planning a crane lift means checking the crane’s rated capacity at a given reach, and making sure the boom and load clear everything on site. Done by hand with charts and drawings, it is slow and mistakes are expensive.
Crews also need the finished plan on site, often without a reliable connection.
What I built
Capacity charts built in
Crane capacity charts live in the software, so the rated capacity for a planned lift is checked there rather than looked up by hand.
Automatic collision checks
A geometry engine models the crane, the load and site obstacles, and flags clashes before anyone is on site.
Lift plans as PDFs
A finished plan exports as a clear PDF that can be shared with the crew and the client.
Works on site
The app installs to a phone or tablet and keeps working offline. Each company only sees its own cranes, jobs and plans.
How it runs
The core loop, from the moment something happens to the moment it is handled.
How it runs: Lift request, then Collision check, then Shareable plan.
What changed
- Crane Plan Pro is in production. Planners get a checked, shareable lift plan from one tool.
Abdur is a good problem solver, ready to work through complex coding needs.
Under the hood
- Next.js with server actions
- React
- PostgreSQL and Prisma
- A custom geometry and SVG collision engine
- PDF generation
- Installable, offline-capable web app
- Per-company data scoping
Want something like this?
SaaS products
AI-native products built to take paying customers from the first release.
Questions about Crane Plan Pro
Straight answers. If yours is not here, ask me.
Ask me directlyI read and answer every message.Why a web app instead of a desktop program?
Planners work in the office and crews work on site. An installable web app runs on any device, works offline when it needs to, and updates for everyone at once.