<!-- Generated from the public HTML page by tools/generate-discovery.mjs. -->

Source: https://www.quantumsteeldesign.com/design-partners/

Charter design-partner program

# Help build steel automation around real work.

Quantum Steel Design is seeking its first charter fabricator and detailing partners to define, test, and measure one bounded workflow at a time.

[Apply for a pilot conversation](https://www.quantumsteeldesign.com/contact/?source=design-partners&projectType=Design%20Partner)
[Check program fit](https://www.quantumsteeldesign.com/design-partners/#program-fit)

Open and honest status

QSD is actively recruiting initial charter participants. This page does not imply an existing customer roster, completed production pilot, or proven project result.

A suitable pilot begins with a repetitive steel-detailing or information handoff, a qualified reviewer, defined acceptance criteria, and a result that can be measured.

Do not send confidential project files through the initial public inquiry. Scope and data-handling terms come first.

Who should apply

## A real workflow owner with a review path.

The strongest fit is a structural steel fabricator, detailing team, or closely related project participant with a recurring task that consumes time, produces avoidable review friction, or breaks at a document and data handoff.

A design partner must be able to explain the current process, identify who owns the decision, and provide qualified review of any pilot output. A software name alone is not a use case.

Fit 01

### Repeatable detailing work

Drawing preparation, checking, comparison, revision review, schedules, references, or another well-defined task that repeats across a package or project.

Fit 02

### Observable acceptance criteria

A reviewer can determine whether the result is correct, incomplete, uncertain, or unsafe to use—and can explain the controlling source.

Fit 03

### Willingness to measure

The team can compare a bounded baseline and pilot result without overstating savings, accuracy, or production readiness.

How a charter pilot starts

## Scope before software. Terms before files.

A conversation is not a commitment. Scope, schedule, price, confidentiality, data handling, ownership, support, and permission for any public reference must be agreed in writing before a pilot begins.

- Initial conversationDescribe the company, team, current workflow, recurring problem, and person responsible for reviewing the result. No confidential files are needed.

- Bounded workflow mapIdentify the source, revision, inputs, outputs, exceptions, current effort, and exact acceptance criteria for one narrow task.

- Written pilot termsAgree on permitted data, confidentiality, access, retention, deliverables, review responsibility, commercial terms, and stop conditions.

- Controlled test and reviewRun against representative information, log exceptions, compare the baseline, and keep output outside production control until it is accepted by the designated reviewer.

What QSD brings

### Direct access to the builder of the workflow.

- A documented map of the selected task and handoffs

- Explicit inputs, outputs, assumptions, and exceptions

- Human-review and release boundaries

- Direct feedback into jumpSteel priorities

- A measured pilot summary when the test supports one

What QSD needs

### Context, review, and candid feedback.

- An owner for the workflow and an accountable reviewer

- Representative information under agreed terms

- Known edge cases and expected failure conditions

- Timely correction when QSD misunderstands the work

- Permission for public use only if separately approved

### Public case-study permission is optional.

A participant does not have to permit its name, project, files, results, or comments to be published. Any public proof must be separately approved, accurately qualified, and limited to the evidence the pilot actually produced.

Good first-pilot questions

## Give the inquiry enough context to be useful.

In the initial message, include your company's role, the repetitive task, the software and file types involved, the person who reviews the work, how the task is handled today, and what a successful result would change.

Do not attach or paste confidential drawings, models, customer information, credentials, proprietary standards, or controlled project data into the first inquiry.

Before applying, review the [capability matrix](https://www.quantumsteeldesign.com/integrations/), [Trust Center](https://www.quantumsteeldesign.com/trust/), [Proof Center](https://www.quantumsteeldesign.com/proof/), and current [jumpSteel Pro boundaries](https://www.quantumsteeldesign.com/jumpsteel-pro/).

Seeking first charter participants

## Bring one repetitive steel workflow worth improving.

Start with a non-confidential description. Quantum Steel Design will determine whether the problem is specific enough for responsible discovery before requesting any project information.

[Apply for a pilot conversation](https://www.quantumsteeldesign.com/contact/?source=design-partners&projectType=Design%20Partner)
[Email the inquiry](mailto:d.carne1191@quantumsteeldesign.com?subject=Design%20partner%20pilot%20inquiry)
