Design Partner Program

Design Partners for Governed AI Coding Agents

SICKR is building the control plane for AI coding agents - live/replay visibility, workflow governance, human approvals, evidence, and audit for teams using tools like Claude Code, Codex, Gemini CLI, and local runners.

What we evaluate together

Live/replay visibility into local agent sessions
Governed workflow tickets
Human approval and intervention points
Evidence and audit history
Dependency-gated execution
Workflow metrics and cost visibility

Who this is for

This program is for engineering teams already experimenting with AI coding agents and asking questions like:

  • What did the agent actually do?
  • Who approved the work?
  • What evidence exists?
  • Which actions should require a human?
  • How do we govern agent work across tickets, PRs, and workflows?

What design partners get

  • Early access to SICKR Arc and Prime Workflow
  • Founder-led onboarding
  • Workflow-mapping support
  • Direct influence on roadmap priorities
  • Clear end-of-pilot rollout recommendations
  • Coordinated support during the pilot

Program commitment

Typical design partner commitment:

  • Focused pilot engagement
  • One primary pilot owner
  • One real or realistic AI-assisted engineering workflow
  • Kickoff, workflow-mapping, feedback, and final review sessions
  • Candid feedback on product fit, missing controls, and purchase readiness

Pilot structure

What to Expect During the Pilot

Design partners receive hands-on access to SICKR with founder-led onboarding and white-glove workflow integration support.

Over an 8-week evaluation period, we work closely with your team to understand how AI coding agents fit into your real engineering workflow, where governance is needed, and what SICKR must improve before broader rollout.

This is not a passive beta. It is a structured collaboration.

Weekly Collaboration

Early-week implementation session

We help your team configure SICKR, connect the right agent workflows, map your engineering process, and remove onboarding friction.

Late-week feedback session

We review what worked, what broke, what felt valuable, and what still needs improvement. We focus on your pain points, expectations, security concerns, and buying criteria.

What We Ask From You

  • One primary pilot owner
  • One real or realistic engineering workflow to evaluate
  • Two short working sessions per week during the pilot
  • Candid feedback on product fit, missing controls, and operational risk
  • Willingness to start with observation, simulation, or low-risk governed workflows

8-Week Pilot Flow

Week 1

Kickoff and workflow selection

Choose one real or realistic AI-assisted engineering workflow to evaluate.

Week 2

Arc setup and visibility

Capture and review local AI-agent sessions using replay/live visibility.

Week 3

Workflow mapping

Translate the selected workflow into tickets, states, approvals, dependencies, and evidence.

Week 4

Simulation or canary execution

Test the workflow safely before production use.

Week 5

Human approval and governance

Identify where humans must approve, intervene, or review evidence.

Week 6

Metrics and audit review

Review history, evidence, cost/usage signals, and operational gaps.

Week 7

Fit assessment

Evaluate what is required for broader rollout.

Week 8

Pilot review and next step

Decide whether to continue into a paid rollout, extend the pilot around a sharper use case, or close the engagement with documented learnings.

End of pilot

At the end of the pilot, both sides should have a clear answer: continue into a paid rollout, extend the pilot around a sharper use case, or close the engagement with documented learnings.

Built for staged adoption

SICKR helps teams adopt AI agents without giving up control.

Design partners typically begin with replay visibility, workflow mapping, simulation, approvals, and audit. From there, we work together to identify which workflows are ready for governed execution and which actions should remain human-gated.

The goal is not blind autonomy. The goal is trusted autonomy: agents doing real work inside clear workflows, with the right evidence, approvals, and human oversight.

As confidence grows, teams can expand the scope of agent authority through deliberate rollout, security review, and agreed operating boundaries.

Apply

Apply for the Design Partner Program

Public application only. Pricing, pilot agreements, security terms, signatures, and onboarding details are handled after qualification.

Which AI coding tools are you using?
Are AI coding agents officially used by your team today?
What problem are you trying to solve?
Would you be open to a paid design-partner pilot if there is fit?
Can your team commit to a structured 8-week design partner pilot with one implementation session and one feedback session per week?