Skip to content
QuxPulse
Join the waitlist

Delivery visibility for startup leaders

Know if delivery is on track, and what change costs.

QuxPulse turns stand-ups, pivots and new asks into a few clear numbers, with one view each for leadership, product and engineering.

Join the waitlistBook a walkthrough

Connects to your ticket tracker and code host. Your data stays in your workspace.

Say/do82%+6 pts
Cost of change14%7.0 eng-days
Time blocked6.5workdays
Sprint 24 · day 7 of 10scope +5 −2
  • PivotOnboarding redesign after the board meeting+4.0d
  • ChangePAY-212: two approval steps, not three+1.5d
  • RequestInvestor demo, moved to sprint 250.0d
Illustrative data
Connects to
  • Linear
  • Jira
  • ServiceNow
  • monday.com
  • Perfex CRM
  • GitHub
  • QuxGit
  • GitLab
  • Bitbucket

The problem

Engineering time goes on change nobody counts.

A pivot on Monday. A requirement rewritten mid-sprint. A quick ask that takes three days. None of it is written down where leadership can see it.

So the roadmap slips, and engineering gets the blame. QuxPulse records what was asked, what it displaced and what it cost.

01 / 04The plan

Every sprint starts with a clean line.

The team commits, and the burn-down points straight at the end date.

02 / 04The asks

Then the asks start arriving.

An escalation, a pivot, a rewritten requirement. None of them moves the end date.

03 / 04The cost

QuxPulse counts what they cost.

Days added, finished work thrown away, time blocked and tickets added mid-sprint, as a share of real capacity.

04 / 04The view

And shows it to everyone, the same way.

The same figures in every view and every report, so nobody argues about whose numbers are right.

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.

01Leadership

Where delivery stands, and what change cost.

For founders: is the team doing what it said, and what pulled it off course?

  • Say/do ratio, week by week
  • Cost of change, by source
  • A 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 waits on product.

Every requirement change, how late it came, and what joined or left the sprint.

  • Requirement changes, before and after
  • Scope added and removed mid-sprint
  • Requests to accept, defer or decline
  • 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 lead runs stand-up here. One engineer’s entries are visible to them and to workspace admins, nobody else.

  • Stand-up in two minutes a person
  • 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.

Views and reports are team-level and never name an engineer.

Tickets and cycle time come from your tracker; pull requests and time to merge from your code host, bots excluded.

  1. 01

    Say/do ratio

    How much of what the team commits to at stand-up gets done.

    completed ÷ resolved commitments
    Exact definition

    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

    Work added or thrown away by changes, as a share of capacity.

    (days added + days invalidated) ÷ capacity
    Exact definition

    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

    How long work sits blocked, in workdays.

    Σ workdays, raised → resolved
    Exact definition

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

  4. 04

    Sprint scope

    Tickets added to or removed from a sprint after it starts.

    joined or left after day one, before the end
    Exact definition

    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 the tracker’s issue history.

Desktop companion

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

The desktop app sends stand-up mail, meeting notes and pull request decisions to your workspace. Only what matches your rules leaves the computer.

Get the desktop app

For Mac and Windows. Signs in through your browser.

  • OutlookStand-up notes, 2 department updates3 matched
  • MeetingsTeams, Granola2 sent
  • PR reviewsWaiting for your decision2 waiting
Illustrative data

Security and privacy

Your delivery data stays yours.

Built so that a bug in our code still cannot show one company’s data to another.

Your data, used only for you

We use it to run your workspace and nothing else. We never sell it.

Isolated per workspace

Postgres row-level security walls off every table, so a faulty query returns nothing.

Credentials sealed

Tracker and code host keys are encrypted (AES-256-GCM) and never shown again.

No third-party telemetry

No analytics, trackers or ad cookies. One cookie keeps you signed in.

The detail is in the Privacy Policy and the Terms.

Start here

See your first pulse this week.

Connect your tracker and code host, add the team, and run tomorrow’s stand-up in QuxPulse.

Join the waitlistBook a walkthrough

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