Design Partners · inbound only

The deeper path into Calx.

A design partnership is for teams that want to ship the first real version of behavioral enforcement with us. You bring the correction workload. We bring the compiler. The roadmap gets shaped together.

Apply for design partnership →Start with an audit instead

01 · Entry

Correction Audit

Two weeks. One workflow. A behavioral control report with an enforcement plan.

02 · Pilot

Scoped Tether pilot

Ship the architectural rules from the audit. Measure recurrence reduction against baseline.

03 · now

Design Partnership

Deeper engagement. Shape the roadmap. Founder access. Bench + Tether for your team.

What a design partnership is

You ship the first real version with us.

This is not early access. Design partners shape what Calx becomes. Spencer works with you directly. The feedback loop is tight.

You get

Bench + Tether deployed for your team

The full product, provisioned for your operators and workflows. Correction capture, recurrence detection, rule promotion, runtime enforcement, and the weekly behavioral report.

You get

Direct founder engagement

Weekly pairing with Spencer. New features shipped in response to your workflow. Every correction you capture shapes the next version of the compiler.

You get

Input on the roadmap

Tether primitive ordering. Bench surface decisions. Serve schema and report format. Design partners read the roadmap before everyone else, and write half of it.

You get

Procurement-ready evidence

Monthly behavioral control reports your CIO can read. Prevented-violation logs with latency metrics. The proof pack for when it’s time to scale across the org.

You give

One workflow. One buyer. Real corrections.

We need a workflow where humans correct agents regularly, a single person owning the rollout, and read access to the correction stream. We never see prompts, completions, or source.

You give

Honest friction + 30 minutes a week

When something does not work, tell us. When a primitive is wrong, tell us. A 30-minute weekly sync, every correction flagged, every pattern mapped. That is the partnership.

Who we work with

Correction density qualifies. Job title does not.

We select design partners on two axes: correction density (you produce enough recurring corrections to make the compiler light up) and strategic fit (your use of Calx teaches us something the next 100 partners will need).

We currently work with a 9-agent engineering firm, a recruiting agency running multi-computer shared state, and two others. Every one is inbound. We are not running an outbound motion yet.

If your team is experiencing the problem but does not qualify for design partnership, book a Correction Audit. The audit is the lower-friction way in.

Fit criteria

3 to 30 heavy agent users
At least one supervised workflow
One buyer who can commit
Willing to capture correction data
Honest about what does not work
Recurrence density above threshold

Apply for design partnership.

Tell us which workflow you want to bring, who owns the rollout, and what you are trying to govern. We come back within 48 hours with either a scoping call or a pointer to the audit.

Why no pricesDesign partnership engagements are scoped per partner because the workload shape matters more than the seat count. We quote after a scoping call. That quote covers capture, compilation, runtime enforcement, and the weekly report for the pilot window. Standard tiers follow later, once the product surface is stable enough to price without context.