Manufacturing · Building materials
Panel specs from CAD drawings in seconds, not hours
Reads DWG/DXF layouts and builds the Excel spec: 10–30 seconds instead of 2–15 hours by hand. All 784 panels of one real project matched the manual spec line by line.
- Status
- MVP in operation
- Timeline
- 6 weeks
- Stack
- Python
- ezdxf
- ODA File Converter
- openpyxl
- customtkinter
- PyInstaller
The task
A sandwich panel manufacturer lays out each project in CAD, then counts hundreds of panels by hand and types the spec into Excel. On real projects this took 2–15 hours, and 1 to 15 days passed between a finished drawing and a spec sent to the customer. Drawings were marked up inconsistently — text tags on some, dimensions only on others — so a simple parser would not do.
What we built
- We built a drawing-to-spec pipeline: the app reads DWG/DXF, finds the panels, groups them and writes an Excel file in the client's own template.
- Three recognition strategies cover the different markup styles: text tags, dimension chains and block attributes. The app suggests a mode; a new project is a config change, not code.
- Engineers kept their usual CAD workflow: the app works with the existing drawing markup, and the designer confirms detected panels in a table before export.
- Shipped to workstations as a standalone Windows app with one-click install and on-demand updates. Output was verified against hand-made specs line by line and by totals.
- The next stage — from spec to quotes, orders, production and inventory — is designed and captured as a roadmap, not yet built.
Outcome
- 784/784 and 189/189
- panels on one project and wall panels on another matched the manual specs line by line, size groups included; area within 0.001 m²
- 2–15 h → 10–30 s
- to produce a project spec: manual work vs app processing, measured on real projects
- 40–200 h/month
- potential engineering time saved at 20–30 projects a month, per the project's economics model
- 1–3 months
- estimated payback, per the project's economics model
More cases
Real estate · PropTech marketplace
MVP in operationLand-plot marketplace with a next-step plan: MVP in 2 months
From a mock-up to a working platform: plot → works → contractor → request. Rule-based next-step engine, three dashboards, personal-data compliance. MVP in 2 months.
- 2 months
- from approved spec to pre-release MVP on an HTTPS stand — week 9 against the plan's own 10–13 week estimate
- 7 days
- from spec to the first full-implementation commit: 168 files, 21.5k lines, then two months of hardening to pre-release
EdTech · HR-tech
MVP in operation (demo stand)From business canvas to a student-work marketplace demo in about six weeks
The client had a business model and no product. We built a student-task marketplace MVP where the server enforces legal and platform rules, and put a demo stand live.
- ~6 weeks
- from first commit to a deployed demo with all workspaces; 7 working days in commit history
- 3 checks
- run by the server before a contractor is assigned: data consent, self-employed status, mentor — each with a plain refusal
Music tech · SaaS
MVP in operation (closed launch)Music releases without missed deadlines
Release ops for independent labels: 9-stage lifecycle, pitching deadlines for 12 stores, AI drafts with human approval. Zero to production-grade in 7 weeks.
- 7 weeks
- from first commit to a production-grade stack with Vault, encrypted backups, SLOs and a move to a Russian data centre (265 commits)
- 16 days
- from project start to an investor presentation with a live product demo
Estimate the impact on your own figures
AVA is a process-economics calculator. In a couple of minutes it shows whether a similar task pays off in your case — before any call and with no commitment.
Estimate the impact with AVAHave a similar task?
Describe the process and the data you have. We will tell you what can be measured in money and what cannot — before any work starts.
or email us directly: hello@xteam.pro