Krafthaus
Start intake
Live intake activity this cycle. We keep a focused queue so every accepted brief keeps the 7-day delivery target. All systems operational
For PM + Product Ops owners with one critical call to make

Make the right KPI call in 7 days with a board-ready decision brief.

One critical decision. 2-6 locked options. Structured analysis and one clear recommendation your team can execute.

Start intake See reference decision packet

Delivery guarantee: clear recommendation package for agreed scope or full refund.

Built for PM + Product Ops owners One owner, one locked option set Clear go/no-go checkpoint Leadership-ready audit trail
Same-sprint action 61% decisions executed without rerun loops
Decision cycle 8 days from accepted brief to final recommendation
Execution engine decide.fyi policy-checked yes/no handoff

Baseline metrics shown. Live pilot metrics replace these after kickoff.

Verified pilot intakes --

Live count appears when pilot storage is connected.

Intake response SLA 1 business day

If accepted, kickoff + payment link are sent before execution starts.

How one KPI loop runs

One scoped brief in, one policy-checked call out, one KPI readout for the next sprint.

Step 1 Evidence inputs

Operator input + market evidence

Step 2 Runtime gate

decide.fyi policy engine returns one clear yes/no call.

Step 3 KPI outcome

Result is logged and reused in the next decision brief.

Evidence inputs Operator input + market evidence
Runtime decide.fyi policy engine
Output KPI-linked execution call

Evidence Quality Score (SQS) rates input trustworthiness from four checks: reliability, freshness, noise, and consistency. Method details.

What keeps the loop consistent

Three guardrails keep each KPI brief clear, fast, and executable.

Pillar 01

Scoped intake

Each brief starts with one KPI owner, one decision question, and 2-6 locked options.

Pillar 02

Evidence ladder

Inputs are normalized and quality-scored before ranking so options are compared on one frame.

Pillar 03

Deterministic handoff

Decision Packet plus audit trace move into decide.fyi for a policy-checked execution call.

Instead of reopening debate every sprint, teams run one operating loop and learn from outcomes.

Pricing Anchor Pack (launch)

Scope one pricing KPI question, lock options, and get one execution packet your team can run.

Launch wedge Live now

Resolve one pricing anchor in 7 days

One active brief at a time. Batch queue available for 5- and 10-brief plans.

  • Input: one pricing question, 2-6 locked options
  • Evidence: normalized lane inputs with quality weighting
  • Quality: reliability, freshness, and noise scoring
  • Gate: explicit yes/no readiness before dispatch
  • Output: execution packet JSON + audit trace (optional executive PDF)

If your team only has one draft direction, intake can request option-shaping support before packet assembly.

Start intake
Delivery contract

What ships in each packet

Inputs KPI brief, locked options, evidence inputs, and policy checks
Validation /api/decision-packet-validate
Decision call Clear yes/no recommendation via decide.fyi policy engine 
{
  "pack_type": "pricing_anchor",
  "evidence_inputs": ["operator_input", "market_evidence"],
  "evidence_weights": { "operator_input": 0.64, "market_evidence": 0.36 },
  "evidence_quality": {
    "label": "Evidence Quality Score",
    "components": ["reliability", "freshness", "noise", "consistency"]
  },
  "candidate_option_id": "opt_a",
  "lead_margin_pp": 24.2,
  "gate_passed": true,
  "runtime_provider": "decidefyi"
}

Primary output is machine-readable execution packet + audit trace. PDF summary is optional.

Coming next

Offer Mix Pack

After pricing anchor pilots establish a stable decision baseline.

Coming next

Feature Priority Pack

After pricing loop quality and team adoption are stable.

6-Step PM Workload-Reduction Loop

Run one weekly decision loop that compounds into quarterly KPI movement: scoped question in, clear go/no-go call out, outcome fed forward.

Step 1 of 6: Define KPI Question

Role lens

Use one loop across functions. Switch lens to see exactly how the same flow is scoped for each owner.

PM lens: frame one KPI movement call, lock options, and route one execution-ready decision packet.

01

Define KPI question

Frame one binary decision tied to one KPI and lock 2-6 options so scope stays clear.

02

Collect evidence inputs

Capture targeted operator input and market evidence without opening broad research loops.

03

Score quality and weight evidence

Score input quality and set adaptive weights so teams argue less about data trust.

04

Assemble execution packet

Package ranked options, recommended option, rationale, confidence spread, and guardrails in one shareable artifact.

05

Run policy gate

Send the execution packet to decide.fyi for policy checks and return a final go/no-go call your team can execute.

06

Measure KPI outcome

Track KPI impact and feed the result into the next brief to reduce repeat decision work.

Evidence inputs Operator input + market evidence

Targeted operator input plus source-scored market evidence

Normalize Quality scoring + weighting

Adaptive blend based on reliability, freshness, and volatility.

Policy check Execution packet -> decide.fyi policy endpoint

Policy-checked go/no-go call with decision rationale

Outcome KPI result feedback

Outcome snapshot reused in the next sprint decision cycle

Exact example run

PM example: starter pricing anchor

One sprint call tied to self-serve conversion, with a single owner and clear launch guardrails.

KPI brief Self-serve conversion: choose the Q2 starter price anchor.
Option set Option A: $15 anchor, Option B: $20 anchor, Option C: $15 with annual default.
Gate output Recommended call: Option A, policy-safe, launch-capacity confirmed.
Delivered artifact Packet JSON + audit trace + operator summary for weekly review.

Outcome feedback: first-sprint uplift and reversal checks are logged into the next brief.

Start this 7-day sprint

Is this for your decision?

Best when you already have 2-6 real options and need one clear call in a fixed 7-day window.

Use this when a PM owner needs execution speed and a Head/VP Product needs clear rationale in the same loop.

Best fit

Best fit

  • B2B SaaS PM deciding between pricing tier options
  • Growth PM choosing onboarding experiment variants
  • Product Ops owner prioritizing scoped feature options
  • Marketing owner selecting campaign variants tied to one KPI
Not fit

Not fit

  • Strategic pivots with unclear scope and no locked options
  • Engineering architecture decisions outside PM/ops/go-to-market ownership
  • Open-ended exploratory research without a decision deadline
  • Teams without a clear KPI owner accountable for execution

Case Proof

Baseline metrics shown below. Live pilot metrics replace these values automatically after kickoff.

Pilot intakes logged --
Most recent intake --

Live intake activity appears here when pilot storage is connected.

Decision engine telemetry (60m)

Awaiting traffic
Started --
OK --
Degraded --
Failed --
Latency p95 --
Circuit --
Intake endpoint --

p95 --

PDF endpoint --

p95 --

Evaluations are counted from server-side decision engine events.

Sample baseline Decision cycle
8 days

Time from brief open to final decision dispatch.

Sample baseline First directional lead
19 hours

Hours until one option establishes a stable lead.

Sample baseline Separation at gate
42%

Spread between yes/no gate before handoff.

Sample baseline Same-sprint action
61%

Packets acted on in the same sprint window.

Decision cycle 8 days
First directional lead 19 hours
Confidence at gate 42%
Same-sprint action 61%

Baseline metrics shown. Live pilot data replaces this after kickoff.

Latest proof packet format

Baseline dataset • 2026-02-16
Indicator Reference baseline Current Delta
Decision cycle time 12 days 8 days -33%
Time to first evidence 72 hours 19 hours -74%
Confidence separation 9% 42% +33 pts
Same-sprint action rate 22% 61% +39 pts
Anonymized pilot sample

Anonymized pricing-anchor pilot snapshot

De-identified case showing exactly how one KPI brief moved from scoped question to final verdict and KPI outcome.

Decision question Should we anchor self-serve Starter at $15 or $20 this sprint?
Options compared A) $15 monthly, B) $20 monthly, C) $15 + annual default
Recommended call Ship $15 monthly anchor (policy-safe).
KPI outcome +2.1pp self-serve conversion within one sprint window.

Case values load from /api/site-case. Keep this de-identified for customer-safe proof sharing.

Votes124
Lead margin+31%
Runtime verdictYES
Decision dateExample
Anonymized pilot sample

Anonymized onboarding-gate pilot snapshot

Reference case showing option shaping to one executable onboarding call with quality checks and reversal guardrails.

Decision question Should new users complete a required setup checklist or keep a fast optional setup path this sprint?
Options compared A) Required checklist, B) Optional checklist, C) Hybrid required for paid-plan trials
Recommended call Ship required checklist for paid-plan trials (policy-safe).
KPI outcome +1.7pp activation completion and -0.6pp early-support escalations.
Votes96
Lead margin+24%
Runtime verdictYES
Decision date2026-02-24
Example Decision Packet

Exactly what a paid KPI brief returns

Question Should we price Starter at $15 or $20 per month?
Recommendation $15/month starter anchor
Confidence 78%
Expected impact +2.1pp conversion
Risk checks All pass: margin floor, support load, launch capacity

Confidence represents expected execution reliability given evidence quality, option spread, and guardrail pass rate. It is not a certainty claim.

Why this option won

  • Highest projected KPI movement across the submitted option set.
  • Decision spread cleared separation threshold versus next-best candidate.
  • Margin, support-load, and launch-capacity gates all passed before dispatch.

Decision boundary: winning option led by +23 blended score points vs runner-up.

Sample PDF preview (first page)
View full sample packet JSON View sample report format Open sample PDF report View PDF API docs
Use this brief in pilot intake Open full packet example page
Built on decide.fyi decision infrastructure
Policy-checked packet handoff
Retention windows set per pilot scope
Machine-readable packet + audit trace export
Operator approval before dispatch
Security posture + controls summary on kickoff
Setup 90-minute kickoff
Scope Up to 10 queued (1 active at a time)
Cadence Weekly packet review

Start intake flow

Submit intake first (free), then pay only after scope confirmation for accepted briefs.

Step 1 Choose plan + submit intake

2 minutes. No payment yet.

Step 2 Scope confirmation

We confirm fit in one business day.

Step 3 Payment link

You pay only for accepted scope.

Step 4 Execution + delivery

Decision packet delivered on agreed timeline.

Primary offer

1 KPI brief (recommended start)

$100 total

  • One KPI owner, one decision question, 2-6 options
  • Recommended call plus implementation-ready reasoning
  • Execution packet JSON, audit trace, and optional PDF summary
  • Option-shaping assist available if your options are still draft quality
Submit intake (1 KPI) Prefill intake with this brief
Optional bundle

5 KPI briefs

$500 total

$100 per brief plus shared kickoff and weekly PM operating review.

  • Five scoped KPI decisions in one operating cycle
  • Shared kickoff and weekly operating review with your PM lead
  • Five packet + report outputs ready for leadership readout
  • Brief-by-brief option-shaping support where teams are not yet fully scoped
Submit intake (5 KPI) Prefill intake with this brief
Optional bundle

10 KPI briefs

$1,000 total

$100 per brief plus priority queue handling and bundle-level exports.

  • Multi-squad KPI queue with per-brief traceability
  • Common policy guardrails across all submitted briefs
  • Bundle export for operating review and archive
  • Option-shaping pass included for incoming briefs that need framing help
Submit intake (10 KPI) Prefill intake with this brief
What you get Decision call, execution packet JSON, audit request trail, and optional executive PDF summary.
What you provide One KPI owner plus 2-6 viable options for each KPI brief (or request option-shaping support during intake).
Response time Scope + kickoff plan within one business day. Packet turnaround depends on brief quality and execution constraints.
Delivery guarantee If we do not deliver a clear recommendation package for the agreed KPI brief scope, you get a full refund.

Scope is confirmed before work starts so both sides know exactly what is being delivered.

Payment workflow Clear 4-step flow with no payment before scope confirmation
  1. Submit intake in 2 minutes (free).
  2. Receive scope confirmation within 1 business day.
  3. Approve scope and complete payment for accepted briefs.
  4. Execution starts immediately after payment and delivers on the agreed timeline.

Ready to proceed? Continue to intake below on this page.

FAQ before you submit

Short answers to the practical questions PM, Marketing, and Finance owners ask before sending a KPI brief.

What if we do not have 2-6 clean options yet?

Submit the brief anyway. We confirm and tighten the final option set during scope alignment.

Is this weekly work or quarterly planning?

Krafthaus handles weekly operating decisions tied to a quarterly KPI. The loop reduces day-to-day decision overhead while still serving quarterly targets.

What do we receive for each KPI brief?

One recommendation, packet JSON, audit trail, and optional PDF summary for leadership review.

How fast do we hear back after intake?

Scope and kickoff path are sent within one business day. Decision packet timing depends on brief quality and constraint checks.

Can multiple teams submit in the same cycle?

Yes. Use 5- or 10-brief plans for queue management. One brief runs active at a time with clear owner assignment.

What happens right after we submit?

You receive an intake ID immediately. Krafthaus confirms scope and kickoff steps, then returns the recommendation package on the agreed timeline.

How is this different from internal team polling?

Polling gives sentiment. Krafthaus returns one scoped recommendation package with quality-scored evidence, gate checks, and an execution-ready packet.

How is this different from hiring a consultant?

Krafthaus is a fixed-scope decision loop: one KPI brief, one recommendation package, and one execution-ready packet on a defined timeline.

What if we disagree with the recommendation?

The packet includes rationale, confidence spread, and constraint checks so teams can review quickly. Final execution remains your team's call.

Can we submit confidential decisions?

Yes for normal commercial decision context. Do not submit credentials, payment data, or regulated sensitive data in intake text.

Who actually assembles the packet?

Krafthaus assembles and validates the packet format, then runs policy checks through decide.fyi before delivery.

Can we request faster than the 7-day target?

Yes. Mention deadline constraints in intake. Feasibility depends on brief quality, option clarity, and policy/risk checks at kickoff.

Start your 7-day sprint intake

Submit your first KPI brief in about 2 minutes from the PM or Product Ops owner. We confirm fit, scope, and kickoff options within one business day. Use the real example below if you want a fast, high-quality starting point.

Pilot intake form

Loads a complete example you can edit instead of starting from blank fields.

Real example: decide.fyi price-point decision

KPI metric: Self-serve trial-to-paid conversion rate

Baseline: 12.0% (last 30 days) Target: 14.0% within 14 days post-launch

Decision question: Should decide.fyi price Starter at $15, $19, or $24 this sprint?

Options: A) $15 starter, B) $19 starter, C) $24 starter

Constraint: Gross margin floor >= 70% and support tickets per 100 accounts must not rise by more than 10%

Name the exact KPI this decision should move.

Use the latest measured value so expected movement is auditable.

State success target + window so execution and readout are scoped.

State one clear decision question your owner must resolve this sprint.

If options are rough, add draft directions here and mark readiness in step 2.

One guardrail is enough. We will use it as a hard execution check.

Pilot Includes

One complete operating loop with less PM overhead

Operator-ready workflow for 1, 5, or 10 KPI briefs with one packet per brief and one policy decision call per packet (1 active brief at a time), plus clear leadership review artifacts.

What happens after you submit
  1. Instant intake ID appears on-screen and by email.
  2. Scope confirmation plus payment link for accepted briefs within 1 business day.
  3. After payment: option lock, evidence scoring, and decision run.
  4. Final packet and report are delivered on the agreed timeline.
Need help scoping first? Get a quick scope check by email.

Delivery guarantee: if we cannot deliver a clear recommendation package for agreed scope, you get a full refund.

After submit: instant intake ID on-screen. Accepted intakes follow a 7-day target timeline from kickoff to packet delivery.

  1. Day 1 Scope and decision framing

    Confirm KPI owners, brief count, and locked option sets so everyone aligns quickly.

  2. Days 2-4 Evidence ladder and packet assembly

    Collect lane inputs, score quality, rank options, and assemble the execution packet.

  3. Days 5-7 Final decision and KPI readout

    Run the policy-checked decision call and record KPI outcome for the next operating cycle.

Setup 90 minutes
Scope Up to 10 queued (1 active at a time)
Cadence Weekly review
See reference decision packet Start intake