Outcome-driven agile, in one tool

Stop managing tasks.
Start betting on outcomes.

Pengwiz replaces feature factories with outcome-driven bets. Shape work, set appetites, track through The Path, and close the Learn loop. Built for teams that ship, not teams that shuffle tickets.

Free forever for teams of five. No credit card.

Designed to fix what's broken in
JiraConfluenceLinearNotionMonday
Features

Everything you need to ship with confidence

One tool. No plugins. No marketplace tax.

casino

Outcome Bets

Every piece of work is a bet with a target outcome, appetite, and kill criteria. No more zombie tickets.

route

The Path

Visual progress from Shaped to Live. Replaces hill charts with clear stages your whole team understands.

timelapse

Fixed Cycles

Time-boxed betting rounds with cooldowns. No endless backlogs. What doesn't get bet on gets shaped or killed.

local_fire_department

Appetite Burn

Every bet shows day N of its appetite — automatically, no time tracking needed. Scope creep gets caught mid-cycle, not at the review.

cell_tower

Signals

Real-time team awareness. Blocked? Risk spotted? Scope cut? The team knows instantly without standups.

school

Learn Loop

Grade every shipped bet. Proven, supported, or failed? Close the causal loop. Track your hit rate over time.

menu_book

Wiki

Built-in documentation with stale detection, page verification, and public sharing. No Confluence needed.

dashboard_customize

Custom Dashboard

Drag, drop, resize. Your dashboard, your layout. No fixed columns or deprecated gadgets.

sensors

Live Board

Every board and bet page updates in seconds, for everyone. A card moved in one office — or by an agent — lands on every screen. No refresh, no “any updates?”

smart_toy

Agent Teammates

Point Claude Code at the CLI or install the Pengwiz plugin: agents find their assigned tasks on their own, work the loop, and signal honestly — badged as agents, never disguised.

public

Public Progress

Share strategy progress with stakeholders. Accept intake requests. No licenses needed for viewers.

support_agent

Support Desk

Give every product a public support page. Customers file tickets with file attachments and follow the thread by link — no account required.

event_available

Meeting Scheduling

Publish your weekly availability and let people outside the team book a slot. Double bookings are rejected at the database, not by a cron job.

bolt

Automations

Turn a support ticket straight into a bet. Route repeat requests without copying them between tools.

How it works

Six steps. One continuous loop.

No ceremonies, no story points, no status meetings.

1

Shape the bet

Every piece of work gets a target outcome and a fixed appetite. No open-ended features.

2

Do the work

Teams — and their agents — pick up bets and move through The Path, from shaped to solving to shipping.

3

Signal, don't meet

Blocked? Risk spotted? Scope cut? Post a signal and the team knows, without a standup.

4

Work in cycles

Fixed time boxes with a protected cooldown. Unfinished bets don't carry over — they get re-evaluated.

5

Show progress

Stakeholders follow real-time progress on public pages. No status update meetings required.

6

Grade the outcome

Did the bet hit its target? Track your hit rate and feed it back into the next cycle's shaping.

Want the full method behind this? Read the docs.

CLI

Built for terminal agents

Every action in Pengwiz, one command away. Point Claude Code, Cursor, or any terminal agent at pengwiz — place bets, log time, post signals, submit timesheets — with --json output made for machines.

pengwiz — zsh
$ pengwiz tableCycle 13 [planning]  Aug 3 → Aug 31  capacity: 40 daysOn the table:BET-012  Checkout revamp        bet       10 daysBET-014  Self-serve onboarding  longshot  15 days$ pengwiz bets place BET-012Placed BET-012 — Checkout revamp (now active, started)$ pengwiz time log 90 --bet BET-012Logged 1h 30m on BET-012 (2026-08-04)$
curl -fsSL https://products.pengwiz.com/cli/install.sh | sh
Live

Add an agent to the team. Watch the board move.

Agents claim tasks, move cards and post signals through the CLI — and every teammate's board follows in about two seconds. Nobody asks for a status update, because the status is already on their screen.

  • ~2s from any action to every screen
  • Agent work is badged, never disguised
  • Nothing to set up — it's just on
Why switch

What Pengwiz fixes

$ git diff how-we-work.md
@@ your team's week @@- Endless backlogs nobody reads+ Shaped bets with kill criteria- Story points that mean nothing+ Fixed appetites in days- 100s of browser tabs in Jira+ Internal tabs, split view, zero clutter- Sprint retros that change nothing+ Learn loop grades every bet- Confluence pages nobody trusts+ Wiki with stale detection + verification- Status update meetings+ Public progress pages for stakeholders- Features shipped, outcomes unknown+ Outcome hit rate tracked over time- Overruns discovered at the retro+ Appetite burn on every bet, live8 rituals replaced, 0 kept
Pricing

Simple, transparent pricing

One tool instead of four. No marketplace plugins, no add-on tax.

Free

$0/forever

For individuals and small teams getting started.

  • check Up to 5 team members
  • check Unlimited bets
  • check The Path + Signals
  • check Wiki (5 pages)
  • check Public progress pages
Start Free

What Pro replaces

  • Jira Standard$7.91/user
  • Confluence Standard$5.42/user
  • Calendly Standard$10/seat
  • Zendesk Suite Team$55/agent

Project tracking, wiki, scheduling and a support desk in one place, for less than the tools it replaces. List prices as of July 2026.

Need SSO, audit logs, or self-hosting? Get in touch.

Ready to stop shuffling tickets?

Start betting on outcomes today. Free forever for small teams.

Get Started Free arrow_forward