The delivery workspace, evidence-aware

See the rocks
before you hit them.

Lighthouse is the delivery workspace for projects, programs and portfolios — plans, risks, decisions, capacity, updates and steering, in one place. Lighty reads the evidence behind the work, cites every recommendation, and refuses to guess when the evidence runs out.

Start your delivery workspace See how Lighty helps

14-day Lighty MAX Preview · no credit card

Steering pack · reported

Tue 09:30

Project Phoenix — on track

“Sprint 12 closed clean. Team firing on all cylinders. No blockers. Confidence: green.”

Lighty scan

Watchtower · evidence

5 signals

Capacity at 140%
Lead architect shared across 3 initiatives
Stale status evidence
Last Jira update 11 days ago on the gateway epic
Vendor dependency slipping
Payments API delivery moved twice in 14 days
Budget burn above forecast
$420K spent · $310K forecast through Sprint 12
Missing decision record
Scope cut on 22 Apr never logged in the decision register

LLighty recommendation

Move 1 engineer from Atlas → Orion.

Confidence

45% → 72%

Atlas

–1 FTE

Orion

+1 FTE

Evidence:JiraBudget sheetSteering deck

Built for the room, not just the role

One platform. The whole delivery team.

Pick the seat you sit in.

Running a solo project can be lonely — status reports, capacity drama and false positives kill half the week.

Drop your business case or plan. Lighty drafts the initiative overview from your own data, runs Watchtower against your status, and produces a board-safe weekly update. You get to be the PM, not the kindergarten teacher.

Weekly update · Apollo

T2 · Sprint 12

Green → Amber

Capacity contradiction

Lead architect at 140%. Apollo confidence drops 90% → 35%.

Suggested move

Move 1 engineer from Atlas. Confidence 35% → 72%.

Ready to sendExport weekly update

Lighty · in project manager mode

“Apollo reads green. Lead architect at 140%, burn 1.3× forecast. Real confidence is 35%, not 90%. One move lifts it to 72%.”

Not another tool to feed

Works with the tools your teams already use.

Lighthouse sits across Jira, Excel, steering packs, RAID logs and status updates, then turns the mess into one delivery workspace. Teams keep using the tools they know. Delivery leaders get the connected view they've been missing.

Backlog & engineering tools

Jira · Azure DevOps · GitHub

Teams keep managing stories, sprints, tickets, and epic dates where they are. Lighthouse pulls delivery signals into plans, capacity, reporting, and Suggested from Jira dependency prompts without asking engineers to update a second system.

Spreadsheets & trackers

Excel · Google Sheets · Smartsheet

Budgets, RAID logs, resource plans and PMO trackers stay where they live. Lighthouse reads them, shows what changed, and flags the gaps reported status would normally hide.

Steering decks & status reports

PowerPoint · Google Slides · Word

The decks and status reports the steering room already runs on become evidence, not theatre. Lighthouse reconciles what was reported against what the delivery data actually says.

Docs & wikis

Confluence · SharePoint · Notion

Drop documents and exports into Lighthouse intake today — business cases, RAIDs, programme plans. Live workspace sync is on the roadmap.

Live sync — roadmap

Task & work management

Asana · Monday · ClickUp

Great for task-level workflow. Lighthouse connects those tasks to delivery confidence, evidence and portfolio decisions.

Enterprise PPM platforms

Planview · Jira Align · Clarity

Built for multi-year enterprise PPM transformation programs. Lighthouse stands up in days for mixed-methodology teams that need delivery truth without a six-month rollout.

Lighthouse doesn't ask teams to stop using Jira, Excel or steering packs. It gives delivery leaders one workspace to understand the dates, blockers, risks and decisions those tools are really showing.

The delivery week, in Lighthouse

Plan the work. Run the week. See what changed.

Start the week in the initiative workspace — update plans, review risks, unblock decisions, model the trade-off, send the steering update. Lighty reads across the work and flags what no longer adds up.

Step 1 · Evidence / Intake

Lighty reads the material and drafts the context.

Plans, decks, Jira exports, RAID logs, budgets — or just describe it in a paragraph.

Works above Jira, Excel, decks, and RAID logs
Per-field source attribution back to the evidence chunk
Auto-extracted: scope, sponsor, dates, budget, named people, risks

Inputs · what Lighty reads

Business case PDF
Jira board
Budget sheet
Resource plan
Status deck
A paragraph

Every claim links back to its source

Step 2 · Watchtower

Reconciles reported status against delivery evidence.

When the steering deck says green and the data says red, Watchtower shows the gap.

Watermelon detection: PM-declared green, evidence says amber
Severity ranked — red only when something is actually broken
Lighty narrates the contradiction; Watchtower does the reconciliation

PM declaredGreen

Project Apollo

T2 · Deliver · S. Adams

Confidence (self-reported)90%

Watchtower reconciles

WatchtowerAmber

Project Apollo

Reconciled · 3 contradictions surfaced

Reconciled confidence35%

Capacity22%Lead arch at 140%

Data40%Sprint data 9 days stale

Financial45%Burn 1.3× forecast

Step 3 · Scenario

Models the move before you make it.

Branch live data. Watch the cascade. Promote when the numbers land.

Confidence delta + capacity cascade + dollar impact
Live data stays untouched until you promote — atomic, or not at all
Lighty explains the cascade — it doesn't decide the move for you

Scenario · branchlive data untouched

Move 1 engineer from Atlas → Orion. Lighty narrates the cascade:

Confidence

45% → 72%

Atlas

–1 FTE

Orion

+1 FTE

Dollar impact

Apollo go-live moves left 2 weeks · $100K/mo financial relief on Atlas overrun

Promoteone-click · atomic · or not at all

Step 4 · Steering

Produces a board-safe decision pack.

Every claim cited. Decision register tracks what Lighty recommended, what was decided, and what actually happened.

Cited, sourced, audit-ready — no invented facts
Decision register: recommendation vs. outcome, append-only
When evidence runs out, Lighty says so
Export to PDF, DOCX, or paste into Confluence

Trust by construction

Source citation
Every claim links back to the evidence it came from.
Refusal to guess
When the evidence runs out, Lighty stops talking
Decision register
Recommendation vs. actual outcome — append-only
Workspace isolation
RBAC + RLS. Your data never trains a model.

See how the evidence layer works →·Security details →