Paid Production Program
The AxonFlow Design Partner Program is a paid, bounded route for organizations that need to decide whether one AI workflow can run under production governance. It is not a free product evaluation or an open-ended consulting engagement.
The program combines:
- AxonFlow Enterprise access for one agreed workflow and deployment footprint
- a 60-day Core or 75-day Core + Fraud & Risk window
- founder-led rollout and architecture support
- measurable success criteria and a fixed sponsor decision date
- an indicative conversion price and procurement path agreed before the program starts
If your team can evaluate independently and mainly needs higher limits, approval gates, policy simulation, and evidence export, use the free Evaluation License instead.
Program Tracks And Pricing
| Track | Core, 60 days | Core + Fraud & Risk, 75 days | Publication activity |
|---|---|---|---|
| Public Design Partner | $2,000 | $3,000 | Collaborative deployment story, subject to mutual written approval |
| Confidential Paid Pilot | $4,000 | $6,000 | None |
Prices are in USD and are subject to eligibility and a signed agreement. The founding-cohort prices are reviewed after the first three completed programs.
The program fee is fully credited against the first quarterly invoice when a commercial licence is signed within 30 days of program end.
The public track costs less because the partner participates in drafting and fact-checking a deployment story. Participation in the agreed review process is required, but publication still requires mutual written approval. The partner may decline publication after participating. The confidential track has no case-study, logo, reference, or other marketing obligation.
Qualification Requirements
Every program requires all five conditions before signing:
- A dated forcing event. Examples include a security approval blocking launch, an audit, a regulator request, an incident, a board commitment, or a production deadline.
- Existing written requirements. The organization already has risk or control requirements; the program does not invent the buyer's governance policy from scratch.
- A named executive sponsor and technical owner. The sponsor can approve the eventual purchase and attends kickoff, midpoint, and the final decision review.
- A real workflow. LLM or MCP tool calls are already in production or are expected to enter production during the current quarter.
- An agreed program plan. Scope, success criteria, dependencies, commercial path, and decision mechanics are written down before the agreement is signed.
No Enterprise keys are issued without the sponsor, program plan, signed agreement, fee, and calendared sponsor sessions.
Program Plan
The plan is an annex to the agreement. It defines:
- the sponsor's decision question in one sentence
- one primary workflow, including users, integrations, data classes, environments, and deployment boundary
- baseline and measurable success criteria tied to the forcing event
- partner dependencies, owners, and dates
- explicit exclusions, including any bespoke build that is not promised
- the evidence shown at the final readout
- expected production footprint and indicative conversion price or pricing band
- procurement, security, and legal steps required to buy, with owners
The conversion economics are visible at signing. The later commercial review is final alignment, not the buyer's first exposure to pricing.
Scoped Production Use
The workflow and footprint in the signed plan may run in scoped production during the program. This lets the sponsor decide against real operating evidence rather than a staging-only demonstration.
Expansion beyond that workflow or footprint requires a commercial licence. Roadmap influence happens through the weekly working session, but AxonFlow makes no build commitment outside the signed plan.
Working Rhythm
| Point | What happens |
|---|---|
| Day 0 | Agreement and plan signed, fee paid, keys issued, and all sponsor sessions placed in both calendars |
| Weekly | One founder session plus bounded asynchronous support |
| Midpoint | Sponsor review against the success criteria and unresolved dependencies |
| Day 40 / 50 | Final commercial alignment with the sponsor present |
| Final day | Evidence readout and a convert, Community, or Stop decision |
| Following 14 days | Technical wind-down only; the existing scoped workflow is frozen and keys expire at the agreement's stated time |
For production-impacting issues, the support target is acknowledgment and triage by the next business day. Resolution timing depends on the issue.
Partner-caused delays and missed sponsor sessions do not automatically extend the program. AxonFlow may pause access or support for unmet partner dependencies without shifting the end date or creating a refund.
Decision Outcomes
The sponsor chooses one of three outcomes on the fixed decision date:
- Convert: sign the commercial licence, apply the program fee credit, and expand production under the licensed footprint.
- Community: Enterprise capabilities and support end at key expiry; eligible Community use continues independently within the Community licence boundary.
- Stop: the program, support, and Enterprise use end. No response by the decision date is treated as Stop.
The following 14 days are a technical wind-down, not a free extension. The existing workflow may continue without expansion, new workflows, configuration changes, or support until the key expires.
Which Path Fits?
| Your situation | Recommended path |
|---|---|
| Exploring product fit or integration locally | Community |
| Running a self-serve technical assessment with higher limits | Evaluation |
| Taking a sponsored workflow into scoped production against a dated requirement | Paid Production Program |
| Expanding a proven deployment across workflows or teams | Commercial Enterprise licence |
Review public fit, pricing, and the application
