Services

Services

Every engagement starts with one repeating job and ends with a system your own designers can run and change.

The four offerings

  1. One repeating task, examined end to end. Process map, rules inventory, feasibility, ROI estimate and a fixed quote for what comes next.

    fixed fee 1–2 weeks

  2. One generator for one job: parameters in, models, drawings, cut files and BOM out — tested against your own past orders.

    fixed scope 3–8 weeks

  3. Configuration, drawings, BOM and ERP data connected into one verified flow, with a rule library your team owns.

    milestones 2–5 months

  4. Support & Improvement

    Rules change; the regression suite stays green. A monthly allocation of hours.

    retainer ongoing

Responsibility

Who decides what

Support & Improvement

After handover

Rules change. CAD versions change. New variants appear and people move on. A monthly allocation of hours keeps the regression suite green, absorbs the changes, and answers the question that comes up on a Tuesday afternoon. Next-business-day response; no twenty-four-hour promise, because that would be a promise this practice cannot keep.

Twelve-month terms, unused hours partially carried over, and an annual rules review so the system still matches the shop.

Handover

What every engagement hands over

The point of the work is that it does not need its author permanently attached to it. These are not optional extras.

Handed over with every engagement
Deliverable What it contains
Source code The generator, add-in or application, with build instructions. Yours to keep and change.
Regression suite Your own past jobs as acceptance cases, so a rule change that breaks an old part is caught before it ships.
Rules documentation Every rule the system applies: where it came from, who owns it, what it assumes.
User guide and handover session Written for the designer who will run it, not for a programmer.
Acceptance report What was tested, against what, with the results — the record that goes in your file.
Release record Version, date, what changed, and how to reproduce the build.

Not sure which of these fits?

Send one example of the job you keep redoing. The first reply says which rung makes sense — and if the honest answer is that it is not worth automating, you get that answer too.