Decision API Product Suite Research
Validation run date: February 17, 2026.
This paper answered one product question: where should Krafthaus win if decidefyi remains the deterministic runtime layer?
The call was clear: Krafthaus should own the operator-facing decision pack workflow, while decidefyi stays as deterministic runtime and policy infrastructure.
1. Current decidefyi surface (verified)
The runtime validation pass showed a narrow but useful surface:
POST /api/decidereturns a deterministic yes / no style payload with a request ID.GET /api/runtime-configexposes runtime and commercial readiness flags.GET /api/metricsis partially exposed, but full metrics stay token-gated.GET /api/proof-metricsandGET /api/pilot-exportare unauthorized without an access token.
Implication: decidefyi is strongest as deterministic runtime and policy infrastructure, not as the full operator-facing product.
2. Category benchmark map
We mapped the adjacent categories to see where a real wedge existed.
| Category | Representative tools | Strength | Gap for our thesis |
|---|---|---|---|
| Policy engines | OPA, Cedar, DMN stacks | Rule execution and policy authoring | No sentiment-to-decision packaging workflow |
| Experimentation | LaunchDarkly, Statsig | Variant testing and exposure analytics | Not structured for one-owner deterministic decision packets |
| Survey / research | Qualtrics, SurveyMonkey | Feedback collection at scale | Weak runtime handoff and deterministic execution |
| Support automation | Intercom AI, Zendesk AI | Ticket automation | Narrow to support, not general product decision operations |
| Risk decisioning | Taktile, Alloy-like stacks | Risk orchestration and automation | Heavier integration burden, less low-friction operator loop |
The gap to own was the same across all of them: none of them were built around constrained brief → ranked evidence → confidence gate → deterministic runtime call → outcome calibration.
3. Product candidate matrix
We scored 15 candidate products across value impact, moat potential, adoption friction, and revenue speed.
| Candidate | Home | Value | Moat | Friction | Revenue | Total |
|---|---|---|---|---|---|---|
| Pricing Anchor Pack | Krafthaus | 5 | 4 | 4 | 5 | 18 |
| Offer Mix Pack | Krafthaus | 5 | 4 | 4 | 5 | 18 |
| Packaging / Plan Limits Pack | Krafthaus | 5 | 4 | 3 | 4 | 16 |
| Feature Priority Pack | Krafthaus | 4 | 4 | 4 | 4 | 16 |
| Onboarding Path Pack | Krafthaus | 4 | 3 | 4 | 4 | 15 |
| Churn Rescue Pack | Krafthaus | 5 | 3 | 3 | 4 | 15 |
| Release Go / No-Go Pack | Krafthaus | 4 | 3 | 4 | 3 | 14 |
| Sales Discount Exception Pack | Krafthaus | 4 | 3 | 3 | 4 | 14 |
| Support Exception Decision Pack | decidefyi-native | 5 | 4 | 4 | 5 | 18 |
| Dispute Evidence Bridge | decidefyi-native | 5 | 4 | 3 | 5 | 17 |
| Policy Drift Radar | decidefyi-native | 4 | 5 | 3 | 4 | 16 |
| Decision QA Cloud | decidefyi-native | 4 | 5 | 2 | 4 | 15 |
| Audit Snapshot Export Hub | decidefyi-native | 4 | 3 | 5 | 4 | 16 |
| MCP Tool Selection Orchestrator | decidefyi-native | 3 | 4 | 2 | 3 | 12 |
| Decision Benchmark Network | Shared later | 5 | 5 | 2 | 4 | 16 |
4. Shortlist and wedge
- Pricing Anchor Pack for product and growth teams.
- Offer Mix Pack for packaging and monetization choices.
- Feature Priority Pack for product-level tradeoff calls.
Primary wedge for the next 90 days: Krafthaus Decision Pack Suite for product and growth teams, powered by decidefyi Decision API runtime.
5. Why this can become proprietary
- Outcome-calibrated decision dataset: not just opinions, but verdict, execution, reversal, and KPI outcome.
- Operational lock-in via packet contract: teams standardize on one decision packet format and calibration loop.
- Audit-grade traceability: every call can be traced from evidence to runtime verdict.
- Benchmark layer later: anonymized cross-customer distributions can become a moat once the workflow exists.
6. Build / defer / skip
Build now
- Decision Pack Suite: Pricing, Offer Mix, and Feature Priority.
- Packet validator and contract enforcement in Krafthaus.
- Outcome scoring and threshold calibration loop.
Defer
- Benchmark network.
- Full QA cloud.
- Broad MCP selection orchestration.
Skip for now
- Generic survey tool positioning.
- Generic experimentation platform clone.
- New policy DSL or platform beyond decidefyi runtime scope.
7. 30 / 60 / 90 execution plan
First 30 days
- Lock the packet schema and validation gates.
- Ship the operator-facing pack creation and export flow.
- Run 2-3 design-partner pilots.
By 60 days
- Add low-friction ingestion via CSV, API endpoint, and forms.
- Add outcome closure and reversal tagging.
- Add weekly calibration reporting.
By 90 days
- Publish case studies with real scope and measured deltas.
- Productize pricing and readiness checks.
- Start benchmark collection.
8. Positioning lock
- Krafthaus: decision pack workflow and operator UX.
- decidefyi: deterministic yes / no runtime and policy infrastructure.
- Message: Decision Pack by Krafthaus, powered by decidefyi Decision API.