Your cutting list and saw optimisation, straight from the BIM model

Most timber frame (HSB) teams rebuild the cutting list by hand for every project: counting elements, retyping lengths, running saw optimisation separately in Excel. Miss one line and a truck gets loaded short, or a batch on the shop floor comes up incomplete.

Request a demo Try it free

The cutting list is where errors hide

The cutting list decides what gets cut, in what order, and how much stock it uses. Build it by hand and the result depends on who is at their desk that day. A missed element does not surface in the office. It surfaces on site or on the shop floor: a back order, a crew waiting, a truck sent back, a batch that has to be reopened. One incident easily runs €2,000 to €5,000. Failure costs like this run 5 to 15% of revenue in construction, against margins of 2 to 3%. The math does not forgive a forgotten line.

Every element has to be counted and typed into the list by hand, project after project.
Saw optimisation happens separately, in a different tool or a different sheet, so lengths and stock don't always match what was actually counted.
Grouping cuts per production batch is manual too, so batches drift out of sync with what is actually planned on the floor.

Configure once, then it runs automatically on every project.

Configure the rules once

Set the cutting rules, stock lengths and batch logic for your production once, reading from native Vertex BD models or IFC from Revit and other BIM tools.

The list builds itself

Every new model version runs through the same pipeline. The cutting list comes out complete: every stud, beam and board accounted for, grouped the way your factory works.

Mathematical optimisation packs the cuts

An optimisation engine works out the cutting pattern across your stock lengths, reducing offcuts instead of leaving that to a manual estimate.

Grouped and exported per batch

Lists come out grouped per production batch, as Excel/CSV in your own column format or through the Odoo integration, ready to hand to the shop floor.

Watch: from model to a least-waste cutting plan

How saw optimisation works as data

The cutting pattern is calculated mathematically instead of estimated. An optimisation engine combines the required lengths across your stock profiles, so the result rests on calculation, not a rule of thumb.

Less offcut waste because lengths are combined mathematically

No counting errors, because the quantities come straight from the model

The cutting list and the cutting plan are data that your own machine or CAM software reads in

See it on your own model

Koto runs live at construction companies today. In a demo we take your own model, run it through a pipeline and you watch your own cutting list and optimisation come out. Real output, not slides.

Request a demo Part lists per production batch from the same model

Works with what you already have

Koto reads the model you already build. No new CAD, no new ERP, no lock-in.

Output in your own column formats. Your data stays yours: switch CAD or ERP, and your Koto pipelines keep working.

Questions about cutting lists and saw optimisation

Yes. The optimisation engine calculates cutting patterns across your available stock lengths mathematically, instead of leaving it to a manual estimate or rule of thumb. That means fewer offcuts and less material ordered as a safety margin.

You re-run the pipeline. The cutting list and the optimisation update automatically from the new model version, so a revision does not mean starting the list over by hand.

The cutting rules, stock lengths and batch logic are configured once, together, at the start. After that it runs automatically on every project, with no re-setup per job.

No. Koto delivers the cutting list and optimisation as data. Machine control stays in your own machine or CAM software.

The cutting pattern is calculated mathematically instead of estimated, so you get less offcut waste and no counting errors. The exact saving depends on your profiles and stock lengths.