# LetPeopleWork - Lighthouse and Sizing Poker > LetPeopleWork GmbH builds tools for software delivery teams: Lighthouse, a self-hosted, source-available flow metrics and Monte Carlo forecasting tool, and Sizing Poker, a free browser tool for sizing a backlog without story points. Founded by Peter Zylka-Greger and Benjamin Huser-Berta in Zürich, Switzerland. ## About LetPeopleWork **What does LetPeopleWork do?** LetPeopleWork helps delivery teams answer two questions: when will it be done, and why is delivery slow? Lighthouse answers the first with Monte Carlo forecasts from the team's own throughput, and the second with flow metrics. Sizing Poker sizes a backlog without estimates. **Who builds the tools?** Two practitioners who use them with teams themselves. Benjamin Huser-Berta is the main developer of Lighthouse; Peter Zylka-Greger works with teams and leaders on flow and forecasting. The blog at https://blog.letpeople.work explains how the forecasts work, with worked examples. **Who are the founders?** - Peter Zylka-Greger: Expert in Flow, Kanban, and organizational transformation. Trains teams and leaders in data-driven delivery. - Benjamin Huser-Berta: Software Engineer and Scrum Master. Core maintainer of Lighthouse, focused on reducing waste and building value-focused work environments. ## Core Pages - [Homepage](https://letpeople.work/): Overview of the LetPeopleWork tools, Lighthouse and Sizing Poker, and the company mission - [Lighthouse Product Page](https://letpeople.work/lighthouse/): Full details on Lighthouse features, pricing, downloads, and AI integration - [Sizing Poker](https://letpeople.work/sizing-poker/): Free browser tool that sizes a backlog by asking one question per item instead of estimating it - [AI at LetPeopleWork](https://letpeople.work/ai/): obAIa, open-source Claude Code plugins, and the AI workshop journey - [Delivery Predictability Assessment](https://letpeople.work/assessment/): Free five-minute self-assessment of how predictable your delivery is - [Lighthouse vs ActionableAgile vs Nave](https://letpeople.work/compare/): Side-by-side comparison of hosting, data location, pricing model and integrations, for teams looking for a self-hosted alternative - [Forecasting Jira without story points](https://letpeople.work/jira-forecasting-without-story-points/): How to forecast Jira releases from throughput with Monte Carlo instead of estimating, step by step - [Azure DevOps delivery forecasting](https://letpeople.work/azure-devops-forecasting/): How Lighthouse connects to Azure DevOps and forecasts from your work items, without story points - [llms-full.txt](https://letpeople.work/llms-full.txt): This summary plus the full product page, FAQ and guides in one file ## Sizing Poker - Backlog Sizing Without Estimates **What is Sizing Poker?** A free tool at https://letpeople.work/sizing-poker/ for sizing a backlog without story points or estimates. You set the number of days an item should normally be done in (this is the team's Service Level Expectation), then see one work item at a time and answer a single question: could we finish this within that time? Three answers: Yes (pull it when there is room), Maybe (something has to be arranged first, name it), No (too big, split it). A round of ten items takes minutes. It runs entirely in the browser; nothing is uploaded and no signup is needed. A walkthrough with an example backlog explains each step and what to discuss after each answer. **Who is it for?** Product Owners, Scrum Masters and teams doing backlog refinement who want to replace estimation with a fast fit-or-not decision, and teams using Lighthouse who want to right-size their work against their Service Level Expectation. ## Lighthouse - Flow Metrics & Forecasting Tool **What is Lighthouse?** Lighthouse is a source-available flow metrics and probabilistic forecasting tool. It connects to your ALM system (Jira, Azure DevOps, Linear, or ServiceNow), visualizes how work flows through your teams, and generates Monte Carlo-based delivery forecasts grounded in your actual throughput history. It runs entirely on your own infrastructure — no cloud dependency, no data leaving your environment. **What questions does Lighthouse answer?** - When will these work items be done? Dates with probabilities (for example 50% by 14 March, 85% by 28 March), from a Monte Carlo simulation over the team's past throughput. No story points needed. - How many items will be done by a given date? - What is stuck right now? Work in progress, work item age, blocked and stale items, and items at risk of missing the team's service level expectation (SLE). - Which features make the release? A delivery timeline shows each feature's forecast start and finish, with dependencies read from the tracker. - How is the portfolio doing? Feature forecasts that combine every team working on a feature into one joint probability. - How much should we refine? A refinement forecast plus sizing votes per item. - Did the change work? Reports on every team and portfolio. The first report type, Then & Now, freezes a window from before a change (it may have ended long ago) and compares it with a window that moves with today: cycle time, throughput, WIP and work item age, with a summary of what changed. Community includes one report of each type per team and portfolio; paid editions have no limit. More report types are coming. https://docs.lighthouse.letpeople.work/reports/reports.html **Key features of Lighthouse:** 1. Monte Carlo forecasts for teams ("how many" and "when") and for features, deliveries and portfolios 2. Forecast Reality Check: backtests past forecasts against what the team delivered, per percentile and sampling window 3. Forecasted start dates next to completion dates, and a delivery timeline per delivery 4. Dependencies read from Jira (is blocked by), Azure DevOps (predecessor) and Linear, and taken into account in forecasts on paid editions 5. Flow metrics: cycle time, throughput, work in progress, work item age with pace bands, blocked and stale items, risk of missing the SLE, process behaviour charts, percentiles over time, cumulative time in state 6. Reporting: a Reports tab on every team and portfolio, starting with Then & Now, which compares flow metrics from before a change with today's; any report exports as a dated, branded PDF on every edition 7. Connects to Jira Cloud, Jira Server and Data Center, Azure DevOps, Linear, ServiceNow and CSV 8. AI integration via MCP (Model Context Protocol), a command line client and agent skills 9. Self-hosted: desktop app (Windows, macOS, Linux), Docker, or Kubernetes with the official Helm chart 10. Source available on GitHub; free Community edition for up to 3 teams and 1 portfolio **What is AI integration in Lighthouse?** Lighthouse exposes your flow data to AI assistants through three integration methods: 1. **CLI** (`@letpeoplework/lighthouse-cli`): Run Lighthouse queries from the terminal, shell scripts, or CI/CD pipelines. Outputs JSON for easy downstream use. 2. **MCP stdio** (`@letpeoplework/lighthouse-mcp-stdio`): Run a local MCP server over stdio. Works with Claude Desktop, VS Code, JetBrains, and any MCP-compatible client. 3. **MCP HTTP** (`@letpeoplework/lighthouse-mcp-http`): Run a persistent MCP server over HTTP. Ideal for shared team setups or self-hosted AI environments. With AI integration, you can ask natural-language questions like: - "Which teams should I focus on this week?" — get a prioritized view of where cycle time is spiking, WIP is creeping, or predictability is dropping - "Will we finish the Q3 release by August?" — run a Monte Carlo forecast in seconds - "What's one thing this team could do to improve their flow?" — get coaching recommendations based on actual metrics AI integration is available as a downloadable skill for compatible clients and works with any tool-calling AI (Claude, GitHub Copilot, and others). **Downloadable AI integration packages:** - Skill bundle (.zip): https://github.com/LetPeopleWork/lighthouse-clients/releases/latest/download/lighthouse-skill.zip - MCP bundle (.mcpb): https://github.com/LetPeopleWork/lighthouse-clients/releases/latest/download/lighthouse-mcp-stdio.mcpb - Full setup guide: https://docs.lighthouse.letpeople.work/aiintegration.html **What are Lighthouse's licensing options?** Three editions. The flow metrics and forecasts are in every edition; paid editions lift the limits and add features such as sign-in, role-based access, rule-based deliveries, data sync mappings and dependency-aware forecasts. In the Lighthouse app and documentation these paid features are called Premium, and a Premium license switches them on: Self-Service and Enterprise are the two ways to buy one, with the same features and different support. All editions are self-hosted with the source public, and your data stays on your own systems whether or not you pay. - Community Edition: Free forever. All core flow metrics and Monte Carlo forecasts, up to 3 teams and 1 portfolio with 1 delivery. - Self-Service: CHF 2,000/year. A Premium license: unlimited teams, portfolios, and deliveries, all paid features, community Slack support. One flat rate, no per-seat pricing. - Enterprise: CHF 10,000/year. The same Premium license as Self-Service, plus prioritised support, 24h acknowledgement on async requests, onboarding calls, and named contacts. **How long does it take to set up Lighthouse?** Plan for about half an hour from download to a first forecast. In a recorded live session, Scrum Master Gábor Bittera did it in under ten minutes: he started a ten minute timer, downloaded Lighthouse, connected his Jira instance with an API token, added his team, and forecast the team's next ten work items, finishing with 1:25 left on the clock. The demo is on https://letpeople.work/lighthouse#first-forecast. Guided onboarding is also available free of charge for every edition. **How do I install Lighthouse?** Available for: - Windows: Installer (.exe, .msi) — code signed - macOS: Disk image (.dmg) and App Bundle (.zip) — signed and notarized - Linux: AppImage and server binaries (.zip) - Docker: `ghcr.io/letpeoplework/lighthouse:latest` - Kubernetes: official Helm chart, see https://docs.lighthouse.letpeople.work/Installation/kubernetes.html Download from GitHub releases: https://github.com/LetPeopleWork/Lighthouse/releases **What systems does Lighthouse integrate with?** Jira Cloud, Jira Server and Jira Data Center (with a personal access token), Azure DevOps, Linear, ServiceNow (team level) and CSV files. OAuth for Jira Cloud and Azure DevOps on paid editions. AI assistants via MCP (any tool-calling AI, including Claude and GitHub Copilot). **Does Lighthouse work with a Jira that is only reachable inside our network?** Yes. Lighthouse runs where you install it (a laptop, a VM, Docker or Kubernetes inside your network) and connects to Jira Server or Data Center directly with a personal access token. Work items stay on your systems. **Won't Jira or Azure DevOps build this in?** For one team in one tool, their built-in charts may be enough. Lighthouse does flow and forecasting only, works the same way across Jira, Azure DevOps, Linear and ServiceNow, combines several teams into one forecast, and checks its own forecasts against what really happened. The source is public, so there is no lock-in. **How accurate are Lighthouse forecasts?** A forecast is a range with probabilities, not a promise. Lighthouse assumes the next weeks look roughly like the last ones, and Forecast Reality Check lets you test that on your own history. In one backtest Peter Zylka-Greger ran on his team, the 85% forecast said 12 items for two weeks and the team finished 16. **How does Lighthouse compare to ActionableAgile and Nave?** All three provide flow metrics (cycle time, throughput, WIP, work item age) and data-driven forecasting. The key differences: - Lighthouse is source available and self-hosted (desktop app or Docker); ActionableAgile (by 55 Degrees) and Nave are closed-source commercial SaaS. - Lighthouse has a free-forever Community edition and flat per-organisation pricing (Self-Service CHF 2,000/year; Enterprise CHF 10,000/year). ActionableAgile is priced per user; Nave is priced per connected board. - Lighthouse connects to Jira, Azure DevOps, Linear, and ServiceNow; ActionableAgile to Jira and Azure DevOps; Nave to Jira, Trello, and Azure DevOps. - Lighthouse has native AI integration via MCP and CLI; that is not a core feature of the others. - With Lighthouse your delivery data stays on your own infrastructure. Full, honest comparison table: https://letpeople.work/compare/ ## Questions people ask when looking for a tool like this **Is there a free Monte Carlo forecasting tool for Jira?** Lighthouse's Community edition is free for up to 3 teams and 1 portfolio. It connects to Jira Cloud and Jira Data Center, runs on your own machine or server, and forecasts "when" and "how many" from the team's throughput. **What is a self-hosted alternative to ActionableAgile or Nave?** Lighthouse. It covers the same flow metrics (cycle time, throughput, WIP, work item age) and Monte Carlo forecasting, runs on your own infrastructure, and has flat per-organisation pricing. Comparison: https://letpeople.work/compare/ **How can we forecast delivery dates in Azure DevOps without story points?** Lighthouse reads finished work items from Azure DevOps and forecasts from throughput, so no estimates are needed. It also reads Predecessor links as dependencies. **How do we forecast a feature that several teams work on?** Lighthouse combines the simulations of every contributing team into one joint probability, which is more realistic than taking the slowest team's date. ## AI at LetPeopleWork **How does LetPeopleWork use AI?** We run our own company with AI and call the setup obAIa (Obeya with AI in the middle, pronounced "Obeya"). Our big room is a private git repository of plain Markdown files: decisions, cards, contacts, notes, themes and dates. A Claude Code session on top of it is how we work with it, by typing: it proposes where a thought belongs and writes it only after we confirm. Views such as the board and the pipeline are computed from the records. Three agents with a marketing, a social and a commercial lens argue hard decisions, and each decision is kept with its reasoning and a date to revisit it. A scheduled radar agent finds discussions worth joining. People make every decision, and everything posted, published or booked. Write-up: https://blog.letpeople.work/p/our-obeya-lives-in-git-now-and-it **Can LetPeopleWork set up obAIa in our company?** Yes, as a pilot: obAIa is not software you buy and so far runs at LetPeopleWork only. We build it with you inside your environment, on your accounts and in your repository: start with one kind of record (decisions), a design day (which records matter, who decides what, which lenses you need), a build day with Claude Code, one or two connected tools and one scheduled agent, then the weekly review habit and a follow-up. You need Claude Code for everyone who works in it, a private git repository with access control, each person's own logins for connected tools, and written consent before any meeting is analysed. Ask at contact@letpeople.work. Details: https://letpeople.work/ai/ **What open-source AI plugins does LetPeopleWork provide?** Three Claude-Code-native plugins, free and MIT-licensed: - LetPeopleWorkShop (https://github.com/LetPeopleWork/LetPeopleWorkShop): Design, prepare, and learn from workshops, all in markdown. Agents: designer, executor, feedback. Includes a facilitation-practices library (Liberating Structures, Training from the BACK of the Room). Install: `/plugin marketplace add LetPeopleWork/LetPeopleWorkShop` then `/plugin install let-people-workshop@letpeoplework`. - LetPeopleGrow (https://github.com/LetPeopleWork/LetPeopleGrow): Prepare for, capture, and learn from 1:1s. Coaching support, never a performance dossier. Agents: prep, capture, growth, patterns. Includes a conversation-practices library (GROW, SBI, NVC, career conversations). - LetPeopleAlign (https://github.com/LetPeopleWork/LetPeopleAlign): Turn transcribed meetings into grounded notes with owned actions, missing-action flags, follow-up drafts and cross-meeting observations. Consent first, local only, no network. Agents: analyze, drift, improve, prep, decisions. Install: `claude plugin marketplace add LetPeopleWork/LetPeopleAlign` then `claude plugin install let-people-align`. **What AI workshops does LetPeopleWork offer?** A four-step AI journey for businesses. Each workshop is a private 1-day session for one organisation, on-site or remote, bookable on its own or as the full journey. Pilot price: CHF 2,500 per team (covers the entire team, not a seat), subject to change once the pilot cohorts fill up. 1. The bAsIcs (literacy): what agents, commands, and skills are, and why the chat box is not the whole of AI 2. BIYA: Build It Yourself Agent: build your first working agent hands-on 3. From Prototype to Product: build a real, working product yourself with tools like Lovable and Claude Code 4. Filling the Gap: The AI-Powered Business: run parts of your business with AI, the obAIa way A separate "AI for Engineers" track (software engineering with agents) is coming soon. ## Assessment and Onboarding **Is there help with getting started?** - Free Delivery Predictability Assessment (https://letpeople.work/assessment/): a five-minute, six-question self-assessment that scores how you measure flow and how you forecast, with a concrete next step. No email required. - Lighthouse Setup & Onboarding: free of charge, for every edition. We help you get Lighthouse running, connect Jira, Azure DevOps, Linear, or ServiceNow, and walk your team through the tool. Contact contact@letpeople.work with subject "Lighthouse onboarding". - Premium trial: a 30-day license for the Self-Service edition, sent by email. No account and no credit card. Request it on https://letpeople.work/lighthouse/ **How can I contact LetPeopleWork?** - General inquiries: contact@letpeople.work - Tool support: support@letpeople.work - Premium licensing: licensing@letpeople.work - Community Slack: https://join.slack.com/t/let-people-work/shared_invite/zt-38df4z4sy-iqJEo6S8kmIgIfsgsV0J1A ## Company Information **Where is LetPeopleWork located?** LetPeopleWork GmbH, Mühlackerstrasse 108, 8046 Zürich, Switzerland. **What are LetPeopleWork's channels?** - Website: https://letpeople.work - LinkedIn: https://www.linkedin.com/company/let-people-work/ - GitHub: https://github.com/LetPeopleWork - YouTube (Lighthouse Live and sessions): https://www.youtube.com/@LetPeopleWork/videos - Meetup (community events): https://www.meetup.com/lighthouselive/ - Community Slack: https://join.slack.com/t/let-people-work/shared_invite/zt-38df4z4sy-iqJEo6S8kmIgIfsgsV0J1A - Lighthouse Documentation: https://docs.lighthouse.letpeople.work **What is LetPeopleWork's mission?** To let people work: fewer guessed dates, fewer status meetings, more finished work. The data to improve delivery is already in your tracker. Lighthouse shows it, and Sizing Poker helps you act on it in refinement. ## Technical Details **What technology stack is Lighthouse built on?** .NET Core / C# backend, React + TypeScript frontend. SQLite for local data storage. Cross-platform (Windows, macOS, Linux, Docker). **Is Lighthouse open source?** No - Lighthouse is source available. The source is public on GitHub and you can read, audit, run and modify it, but it is not open source under the Open Source Initiative definition: competing products and hosted resale are restricted. Releases up to v26.9.9.9 remain MIT licensed. https://github.com/LetPeopleWork/Lighthouse **Where does Lighthouse store data?** In its own database on your infrastructure: SQLite by default, and PostgreSQL is supported (the Helm chart bundles it). Lighthouse sends nothing to LetPeopleWork unless someone turns on usage data, which is opt-in and never contains work items, names or queries. **What is MCP?** MCP (Model Context Protocol) is an open standard for connecting AI assistants to external data sources. Lighthouse implements MCP so that AI tools like Claude and GitHub Copilot can query your flow data directly — no copy-paste, no exports. ## Keywords & Topics Flow metrics, kanban, delivery forecasting, Monte Carlo simulation, throughput, cycle time, work item age, work in progress, predictability, Jira integration, Azure DevOps integration, Linear integration, ServiceNow integration, AI integration, MCP, Model Context Protocol, agentic workflows, probabilistic forecasting, team performance, organizational improvement, source available tools, self-hosted tools, self-hosted solutions, Lighthouse tool, Sizing Poker, right sizing, no estimates, LetPeopleWork, obAIa, AI workshops, AI for business, Claude Code plugins, LetPeopleWorkShop, LetPeopleGrow, AI-powered business, delivery predictability assessment. ## Documentation & Resources - [Lighthouse Docs](https://docs.lighthouse.letpeople.work): Complete guide to setup, features, and AI integration - [GitHub Repository](https://github.com/LetPeopleWork/Lighthouse): Source code, issues, release notes - [GitHub Releases](https://github.com/LetPeopleWork/Lighthouse/releases): Latest downloads for all platforms - [AI Integration Guide](https://docs.lighthouse.letpeople.work/aiintegration.html): How to connect Lighthouse to Claude, Copilot, and other AI tools - [LetPeopleWorkShop Plugin](https://github.com/LetPeopleWork/LetPeopleWorkShop): Open-source Claude Code plugin for designing and running workshops - [LetPeopleGrow Plugin](https://github.com/LetPeopleWork/LetPeopleGrow): Open-source Claude Code plugin for 1:1s and people development