Skip to content
QuxPulse
Join the waitlist

Delivery visibility for startup leadership

Know whether delivery is on track, and what every change cost.

QuxPulse turns stand-ups, leadership asks, pivots and requirement changes into a few honest numbers, beside the sprint and delivery data already in Linear and GitHub. One view each for leadership, product and engineering, and a report you can print.

Join the waitlistBook a walkthrough

Self-serve trial. Your data stays in your workspace.

Say/do82%+6 pts on last sprint
Cost of change14%of capacity, 7.0 eng-days
Time blocked6.5workdays, 3 blockers
Sprint 24 · day 7 of 10scope +5 −2
  • PivotOnboarding redesigned after the board meeting+4.0d
  • ChangePAY-212: two approval steps, not three+1.5d
  • RequestInvestor demo export, deferred to sprint 250.0d
Illustrative data

The problem

Engineering time goes on change nobody counts.

A pivot in Monday’s meeting. A requirement rewritten halfway through the sprint. A quick ask in a DM that quietly takes three days. Each one is reasonable on its own, and none of them is written down anywhere leadership can see.

So the roadmap slips, and the only explanation in the room is that engineering is slow. QuxPulse keeps the record: what was asked, what it displaced, and what it cost.

01 / 04The plan

Every sprint starts with a clean line.

Tickets are estimated, the team commits, and the burn-down points neatly at the end date. On day one, everyone agrees what on track means.

02 / 04The asks

Then the asks start arriving.

A customer escalation, a pivot from the board meeting, a requirement rewritten after review. Each lands as a sentence in a meeting or a DM, and none of them moves the end date.

03 / 04The cost

QuxPulse counts what they cost.

Engineer-days added, finished work thrown away, days spent blocked, tickets pulled into the sprint after it started. Logged the day they happen, as a share of the capacity you actually had.

04 / 04The view

And shows it to everyone, the same way.

Leadership sees whether delivery is on track and why; product sees its churn; engineering sees its day. One set of numbers, and a report that prints.

D1D2D3D4D5D6D7D8D9D10ENDPLANPIVOTREQUESTCHANGE+4.0d+2.0d+1.5d · 2.0d lost9.5 ENG-DAYS · 19% OF CAPACITYLEADERSHIPPRODUCTENGINEERING

One company, three views

Each role sees its own pulse.

Every view reads the same numbers, so leadership, product and engineering argue about decisions, not about whose spreadsheet is right.

01Leadership

Where delivery stands, and what change cost.

The founder’s view: say/do across the team, the cost of every pivot and request as a share of capacity, and who the work is waiting on. The board report prints from the same page.

  • Say/do ratio, week by week
  • Cost of change, by source
  • Time blocked, by who it waits on
  • A printable report for the board

Cost of change, by source

  • Leadership6.5d
  • Customer4.0d
  • Product3.0d
  • Compliance1.0d

Say/do, by week

84% this week

Waiting onProduct 2Design 1Vendor 1Print report
Illustrative data

02Product

Scope, churn, and what is waiting on product.

Every requirement change with its before and after, how far along the work was when it changed, and every ticket that joined or left a sprint after it began.

  • Requirement changes and their lateness
  • Sprint scope added and removed
  • Requests to triage: accept, defer, decline
  • Blockers waiting on product
  • PAY-212Two approval steps, not threeIn review+1.5d
  • ONB-88Invite by link as well as emailIn progress+2.0d
  • RPT-31Weekly, not daily, digestNot started+0.5d

Sprint scope after day one

added removed

Illustrative data

03Engineering

Today’s commitments, blockers and the shape of the day.

The engineering lead runs stand-up in it: what each person commits to, whether yesterday’s landed and why not, and what they are blocked on. One engineer’s entries are visible to them and to workspace admins, nobody else.

  • Stand-up in two minutes a person
  • Carried-over commitments, tracked
  • Blockers, aged in workdays
  • Cycle time and time to merge

Yesterday

  • Ship the invite-link endpoint
  • Migrate billing webhooks blocked

Today

  • Migrate billing webhooks carried over
  • Review PAY-212 change with product
BlockedWebhook spec waiting on product2 workdays
Estimated working day

8.4 h average, sustainable

Illustrative data

How the numbers are defined

Numbers you can check by hand.

Each figure is one sentence long and counted the same way in every view and every report. Stand-up input is per engineer; the views and reports are team-level and never name an engineer.

Tickets completed and cycle time come from Linear; pull requests merged and time to merge from GitHub, bots excluded.

  1. 01

    Say/do ratio

    completed ÷ resolved commitments

    Of the stand-up commitments since resolved, the share completed, counted by the day the commitment was planned for. A missed commitment that is carried over becomes a new commitment for the next day.

  2. 02

    Cost of change

    (days added + days invalidated) ÷ capacity

    Engineer-days added plus engineer-days of finished work invalidated, from the estimates on requests and requirement changes. Once a request has requirement changes filed under it, the changes are counted and the request’s own estimate is not. Shown as a share of capacity: active engineers times elapsed workdays.

  3. 03

    Time blocked

    Σ workdays, raised → resolved

    Workdays from the day a blocker is raised up to the day it is resolved, summed over blockers.

  4. 04

    Sprint scope

    joined or left after day one, before the end

    A ticket counts as added when it joins a sprint after the sprint’s first day and before it ends; removed when it leaves in that same window. First-day planning and end-of-sprint rollover are not counted. Read from Linear’s issue history.

Desktop companion

What only your Mac can reach, sent up on your terms.

The QuxPulse desktop app collects what lives on the engineering lead’s own machine: Outlook stand-up notes and department updates matched by rules you set, Teams transcripts and Granola notes, and the decision log of pull request reviews. Only what matches a rule ever leaves the Mac. Meetings are summarised on our servers, and Linear and GitHub sync there too.

Download for Mac

macOS. Signs in through your browser; its token stays in the keychain.

  • Outlook3 rules · stand-up notes, 2 department updates3 matched
  • MeetingsTeams transcript, Granola note2 sent
  • PR reviewsApprovals wait for your decision2 waiting
Illustrative data

Security and privacy

Your delivery data stays yours.

Stand-ups and estimates are sensitive. QuxPulse is built so that a mistake in our code still cannot show one company’s data to another.

Your data, used only for you

What your team puts in stays yours. We use it to run your workspace and for nothing else. We never sell it.

Isolated per workspace

Every table sits under forced row-level security in Postgres. A query that forgets its workspace returns nothing, not someone else’s stand-ups.

Credentials sealed

Linear and GitHub keys are encrypted with AES-256-GCM before they are stored and never shown again. The desktop keeps its token in the macOS keychain.

No third-party telemetry

No analytics scripts, no trackers, no advertising cookies, and framework telemetry switched off. One cookie, to keep you signed in.

The detail is in the Privacy Policy and the Terms.

Start here

See your first pulse this week.

Create a workspace, connect Linear and GitHub, add the team, and run tomorrow’s stand-up in QuxPulse. Or let us walk you through it first, on your own questions.

Join the waitlistBook a walkthrough

A walkthrough is 30 minutes with the team that builds QuxPulse.

QuxPulse: delivery visibility for startup leadership