Decision API Product Suite Research

This note locked the product thesis behind Krafthaus: Krafthaus should be the operator-facing decision workflow, powered by decidefyi as the deterministic runtime layer.

The goal was not to brainstorm endlessly. It was to verify the runtime surface, map the category, and decide which wedge was worth building first.

What we verified first

The runtime validation pass on February 17, 2026 showed a clear pattern:

• POST /api/decide already behaved like a deterministic yes / no decision endpoint.
• GET /api/runtime-config exposed operational and commercial readiness information.
• Several proof and metrics endpoints were token-gated, which reinforced the separation between public workflow and protected runtime internals.

The implication was straightforward: decidefyi was strongest as runtime and policy infrastructure, not as the full operator-facing product.

The gap worth owning

We compared adjacent categories: policy engines, experimentation tools, survey/research platforms, support automation, and risk decisioning stacks.

The gap across them was the same: none of them were built around constrained brief → ranked evidence → confidence gate → deterministic runtime call → outcome calibration.

The product bets that scored highest

1. Pricing Anchor Pack for product and growth teams.
2. Offer Mix Pack for packaging and monetization choices.
3. Feature Priority Pack for product-level tradeoff calls.

The primary wedge became: Krafthaus Decision Pack Suite for product and growth teams, powered by decidefyi Decision API runtime.

Why this could 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.

What the 30 / 60 / 90 plan looked like

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.

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.