Make the next
design easier.

Company work planning: a work package alongside each company project, with customer/project references, assignment to an existing editor, a due date, input and deliverable checklists, and reported effort with correction history. Open the optional team-work view to find assigned, overdue or waiting work and the inputs needed next; the queue and work details stay collapsed until requested. The quick demo and design workflow need no work-package setup. Customer acceptance and engineering approval are recorded in their own steps.

Scope and fee agreements: optionally preview and issue versioned scope, deliverables, exclusions, fee terms and review rounds within company work planning. A company administrator who is also a project editor can issue an agreement to one named customer with an existing verified account. Both confirm their authority to act; the customer signs in to accept or decline that exact version. Later work changes preserve the original agreement and response. Payment, tax and engineering approval are handled separately.

• Keeps the project together. Briefs, saved versions and the original files people sent you live in the company workspace, and comments point at the version they were written about.
• Reuses your own way of working. A kit says which sizes are allowed, which checks run and which files come out.
• Review by named people. Invite colleagues to review one version, share only the documents you choose, and keep earlier comments when the design moves on.
• Your own model account. A practice with its own Anthropic account can have design planning run on its own key, stored encrypted. It is switched on per company on request.
• Your own channels and tools. Shared versions and workspace changes can post into your Slack or Teams channel, and your projects are reachable through API tokens. Each connection is enabled per company and either side can switch it off.

Available in company work packages. An audit brief connects selected company Standards audits, a named reviewer, scope, acceptance criteria and the customer’s CAD application and version. The customer can state their preferred application when responding to the scope agreement and on the delivery page, including a tool outside the suggested list. Choosing a tool records a preference.

The first exchange adapter prepares IFC material-grade, existing text-property and explicitly mapped numeric length or ratio changes and compares a returned IFC’s readable properties. Geometry equivalence, native editability and drawing updates are checked in the customer’s application.

Named Standards engineers can publish versioned customer engineering packs tied to a published component library, check naming and required properties, and record equipment envelopes, declared loads, mounts and service connections. Editors can compare readable model properties with explicit object-level BOM and drawing references; fixture trials compare counts, length totals and units. These records preserve their source basis.

Package electrical-duty checks compare supplied cable correction factors, protective-device ratings and short-circuit let-through. Serial fluid-duty checks calculate head loss and pump-head demand from supplied fluid properties and pipe data. Selectivity, earthing, arc flash, network balancing, cavitation and pipe stress are assessed separately. Evidence can be downloaded and included in the reviewed delivery files.

The same package record adds accepted-scope change entries, links to declared drawing, purchasing or fabrication commitments, recorded costs, invoice and collection references, model/library fixture trials and partner handoff checklists. Partner assignments use existing project permissions. Historical effort and fee ranges support the next quotation, which a person prices and sends.

A company administrator with editor access can issue selected ready files under an accepted customer scope after the selected audits have engineer acceptance. The named customer can review that delivery; only they can accept it or request changes. Scope agreement, engineering review and the customer’s delivery response are separate decisions.

The model proposes a change the kit allows. Our code builds the geometry and prepares the files. Your team looks at the result and decides whether to keep it.

Each run uses the kit version attached to that design, so improving a kit never rewrites work someone already did. The inputs, the decisions and the files that came out can be read together afterwards.

Writing a building system down as a kit, onboarding and training are days of somebody’s time, and they are quoted as such. Your administrators fill in a form with us, inside your workspace, one section at a time:

• Who makes the system and what it is called.
• The sizes you stand behind, each one with the document and page it came from.
• The parts, in the names your own drawings use.
• Your sheet sizes, scales, title block, layers and views.
• Your material-list columns, grouping, part-number format and rounding.
• Your connection rules and the tolerances your factory works to.
• The checks the kit runs and the country notes it runs with.
• One past project to replay, with a customer change made on it and how long that change took you.
• The responsible designer on your side, and the rights you grant us for the files.

Every save is a new version and older versions stay readable. The form works out what is still missing, exports as a document you can sign, and an agreed version becomes a draft kit that stays switched off until we switch it on deliberately and on the record.

Prices are proposed until the first invoice for that line, and are agreed with your practice before anything is scheduled. There is no checkout: a request reaches us with your company and the size of your team, and a person answers it.

Nobody is recorded as having set this price, and it has never been invoiced.

Company administrators can ask for any of these from the workspace, and a person answers.

Past that seam is your production system, your machine files and your site. Shop drawings and member sizing for manufacture are done there, by your team.

Your team can work against Nordform from a script, a build pipeline or an AI assistant. A token carries only the permissions you give it, expires on a date you choose and has its own run limit. The same token works for the API and for our MCP server, which is how assistants such as Claude Code connect.

An assistant can read a project’s versions and the inputs behind them, ask for a change the kit allows and start a check. It never draws anything.

What comes out is a concept. Complete building design, certified engineering and production drawings come from a professional scope, agreed with the people who sign it.