Decision memos for startup operators

One KPI. One owner. One written call.

Stop turning operator calls into Slack debates.

Krafthaus takes one pricing, onboarding, packaging, or growth question, compares 2-6 real options, and writes the memo that names the winner, the tradeoffs, and the rollback plan.

Best for Pricing, onboarding, packaging, retention
Ships in Hours, not next sprint
Comes back as Memo, audit trace, next checkpoint
Use it when The team is choosing between real paths this week.

Not for brainstorms, category strategy, or open-ended “what should we do?” research.

2-6 options compared Winner named Losing paths preserved Rollback attached

Credit restored if a submitted decision brief cannot be delivered.

Not for strategy offsites. For the call somebody needs to own this week.

Krafthaus is strongest when the question is scoped, the options are real, and the team needs a written answer they can forward without another meeting.

Use Krafthaus when
  • There is one KPI and one decision owner.
  • The team is choosing between 2-6 actual options.
  • The call needs to turn into a launch, policy, or test.
Do not use it for
  • Open-ended research with no real option set.
  • Long-range company strategy or vision work.
  • Decisions with no KPI, no owner, or no shipping path.
What the memo settles
Call What to ship now
Tradeoffs Why the others lose
Risk Guardrails before rollout
Reversal When to revisit the decision

The startup decisions that get expensive when nobody names the winner.

These are operator calls, not brand strategy decks: price points, usage caps, onboarding moves, retention policies, and roadmap tradeoffs.

Most common brief

Choose the starter price anchor

Should we keep $15, move to $20, or split monthly versus annual?

The goal is not more analysis. It is a memo the team can actually ship against this week.

Packaging

Decide the usage billing policy

Burst packs, capped overage, or a hybrid path for high-volume accounts?

Onboarding

Pick the activation flow

Short checklist, guided setup, or a sales-assisted version for larger customers?

Retention

Set the renewal offer policy

Discount, service credit, or tier change for at-risk accounts this cycle?

Roadmap

Choose the next release to ship

Monetization lever, onboarding fix, or reliability work as the next decisive move?

Qualification

Choose the sales handoff rule

Volume, fit, or intent as the default threshold for moving leads to the AE queue?

What Krafthaus replaces

The old workflow is debate, deck, meeting, drift.

Most startup operator calls do not fail because the team lacks ideas. They fail because nobody produces the artifact that says what to ship, what to watch, and who owns the next checkpoint.

Before Slack thread fills up, but the winner never gets named.
Then A strategy deck appears and the tradeoffs get softer.
Then Another meeting happens because execution still feels risky.
Instead Krafthaus writes the call, the guardrails, and the rollback in one memo.
Without Krafthaus
Decision lives across four places

Slack, Notion, the meeting, and whoever remembers the tradeoffs.

No clear reversal rule

The team moves forward, but nobody writes what would make the call wrong.

Ownership gets fuzzy

There is urgency, but not one operator who clearly owns the next checkpoint.

With Krafthaus
One artifact carries the call

Winner, losing alternatives, expected impact, and audit trace stay together.

Guardrails are written before rollout

The memo says what must stay true and when to stop, review, or reverse.

Forwardable by design

The output is made for founders, PMs, finance, or growth leads to pass around fast.

From scoped question to written call.

Not a consulting engagement. Not a brainstorm. One operator-sized workflow from packet to memo.

01

Frame the question

Lock the KPI, owner, guardrails, and real options before the run starts.

02

Review the packet

Confirm the evidence, constraints, and framing before you spend the credit.

03

Share the memo

Get the winner, why alternatives lose, and the rollback checkpoint in one artifact.

What the team gets back in one artifact.

The memo is built to survive handoff: one winner, why it won, what would reverse it, and what happens next.

Best-fit packet

  • One decision question
  • 2-6 options with real tradeoffs
  • One KPI + one accountable owner
  • Constraints written before the run
  • Memo + audit trace delivered together

Best when the team is deciding, not brainstorming.

Page 1 + audit

What stays attached to the call

Winning option One clear call
Why alternatives lose Losing paths stay visible
Expected impact Directional KPI forecast
Guardrails Constraints checked before delivery
Rollback + checkpoint What would reverse the call and when to review it
Why it gets forwarded

It reads like an answer, not analysis theater.

Teams forward Krafthaus because it gives them the thing they were missing: a written call that still carries the tradeoffs, the guardrails, and the next review point.

Winner Named on page 1
Rollback Attached before launch
Owner Visible in the artifact

The answer is named

No burying the call in a strategy deck, Slack thread, or pile of meeting notes.

The tradeoffs stay attached

Why the winner wins and why the other options lose travel with the memo.

The next move is already there

Owner, checkpoint, and rollback frame are written before execution starts.

Buy credits when you have a real call to make.

Credits live in the workspace. Build the packet, confirm the run, and get the memo and audit trace back in hours.

Commercial model One credit = one live decision brief
No retainer Buy only when there is a real decision to make
Output Memo + audit trace, not a software seat
Popular bundle

5 decision credits

$450 total

$90 per decision · Best for a monthly decision cadence

Save $50 vs single credits

  • Run 5 decision briefs
  • Redeem anytime
Buy 5 credits
Scale bundle

10 decision credits

$850 total

$85 per decision · Best for teams running briefs every week

Save $150 vs single credits

  • Run 10 decision briefs
  • Best for teams running frequent decisions
Buy 10 credits
After purchase 1. Credits land in workspace
2. Build decision packet
3. Confirm packet + run
4. Brief arrives with audit trace

Your decision history

Track credits, decision status, and brief history in one workspace.

Checking account...

Credits remaining Locked
Decisions this month 2 sample entries
Latest status Sample status: brief delivered

Your decisions

Illustrative workspace preview shown before sign-in.

Sign in to unlock your workspace history, credit balance, and brief access.

What unlocks after sign-in

Run decisionsStart a new analysis from your workspace
Credit balanceSee remaining credits before each run
Brief historyOpen past decision briefs and outcomes
Latest statusTrack live state from submission to brief delivery

FAQ before you run

Short answers to the key questions before you run a decision.

What if we don't have clean options yet?

Submit a draft direction. Krafthaus will help shape a usable option set before analysis runs.

What is in the brief?

One clear recommendation, expected impact, guardrails, rollback triggers, and audit trace.

How fast does a decision run?

Most decisions complete within a few hours. Complex cases may take up to 24 hours.

Is there a credit guarantee?

If a decision brief cannot be delivered for the submitted brief, the credit is restored.

What if we disagree with the recommendation?

The brief 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 decision text.

Run a decision brief

Submit one scoped decision. Review the packet. Confirm the run.

Credits remaining: --

Decision request form

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

Real example: decide.fyi extra-usage billing decision

KPI metric: Expansion MRR from paid API accounts near monthly usage limits

Baseline: $8,700 (last 30 days; 42 accounts above 90% capacity) Target: >= $12,000 within 45 days

Decision question: Should decide use automatic overage billing or burst packs for extra API usage?

Options: A) Burst packs only, B) Automatic overage billing, C) Hybrid with optional capped overage

Constraint: No surprise billing, explicit spend caps + usage alerts, churn must stay <= 2.0%, support SLA must stay >= 95%

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 stay clear.

State one clear decision question your owner must resolve now.

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.

Add current churn, baseline MRR, usage, or SLA values to unlock Tier 1 company-data evidence.

What you receive

Decision brief output

  • Decision recommendation
  • KPI forecast
  • Risk checks
  • Brief + audit trace

Includes recommendation, KPI forecast, guardrails, and audit trace in one output package.

See sample brief