Milestone 1.3
Design partners & early customers
Honest proof policy
We will not publish customer logos, testimonials, or metrics without written approval. Suite pages today use illustrative evaluation scenarios aligned with roadmap personas—they are not endorsements.
How we run a pilot
Internal workflow we follow with early teams—scoped, time-boxed, and tied to shipped templates.
- 1
Qualify
Persona fit (solo DevOps, platform lead, Web3 operator) and bundle interest—Platform core, Web3 ops, or Full platform.
- 2
Pilot scope
Time-boxed engagement with explicit deliverables: starter templates, runbooks, or ops support—not open-ended roadmap promises.
- 3
Checkout path
Exercise the crypto-only upgrade stub when SKUs exist; until production billing ships, pilots may use documented manual invoicing.
- 4
Retro
Patterns from the engagement feed Milestone 1.2 templates and Phase 2 modules—what worked ships in-product.
Evidence we collect (with permission)
What may appear on the marketing site after a successful pilot.
| Type | Use on site | Requirement |
|---|---|---|
| Design partner quote | Service page or home | Written approval |
| Logo | Footer or suite pages | Trademark permission |
| Metric | Pricing or case study | Verifiable, dated, scoped |
| Architecture diagram | Case study | Customer-owned or anonymized |
Published case studies
This list populates only when we have approved stories. Until then, use suite previews and starter templates to evaluate fit.
No published case studies yet
Milestone 1.3 adds real quotes, metrics, and logos only after written approval—we do not fabricate social proof. Illustrative evaluation scenarios remain on suite pages until then.
View illustrative scenariosEvaluate EHX today
Pick a persona path, browse starter packs in-product, and exercise the crypto checkout stub—production billing and auth ship in later milestones.