Fourteen days, no card. The first summary arrives on the Friday after you start.See the plans

Subscription product
  • Home
  • Pricing
  • About
  • Contact
Start a trial

About

Four people, one product, no roadmap slide

Cadence is made by a company of four in a rented room above a bakery. We have one product and no plan to have a second one.

A line drawing of scattered notes being gathered into a single sheet

Why it exists

It started as a Thursday evening chore

Two of us ran delivery teams at a company where every Friday someone spent an hour reading chat backwards to write an update nobody was sure anyone read. We built the first version to get that hour back, for one team, on one laptop. It was three hundred lines long and it only read one chat channel. The part that surprised us was not the writing. It was that once the summary existed, arguments about what had happened stopped, because there was a page with links on it. That is the whole product: a shared record of the week that somebody is accountable for.

The four of us

How it got here

  1. Year one

    A script for one team, run by hand on a Thursday. Two chat channels, no editor, no archive.

  2. Year two

    Six teams at three companies paid for it. We added the Thursday draft and the sign-off, because the unedited version was wrong often enough to be dangerous.

  3. Year three

    Links to sources on every line. This is the change people mention most, and it is the one we resisted longest.

  4. Now

    Around two hundred teams. Four of us, no outside money, and the price has gone up once.

Who you are writing to

Support is not a department here

When you send a message through the contact page, one of these four answers it.

  • Portrait of a person with short hair against a plain background

    Mara Oduya

    Writes the code that reads your sources

    Spent eight years on data pipelines and is unreasonably strict about what counts as a source.

  • Portrait of a person wearing glasses, looking towards the camera

    Tomas Reijer

    Decides what the summary says

    Former delivery lead. Argues for fewer headings roughly once a quarter and loses.

  • Portrait of a person with long hair, three-quarter view

    Ines Carbo

    Design and the editor screen

    Responsible for the rule that a draft must be readable in under two minutes.

  • Portrait of a person in a dark jumper against a plain background

    Devan Holt

    Billing, contracts and the security questionnaires

    Answers the procurement forms so the rest of us do not have to, and answers support email first.

What we have decided not to do

Four promises that cost us money

  • No scores for people

    Cadence will never rank a person by how much they appeared in the week. We have been asked for this and we have said no each time.

  • No reading between the lines

    The summary reports what was written. It does not infer mood, risk or sentiment from how somebody typed.

  • No lock-in

    Everything exports as plain Markdown, one file per week, with the source links intact.

  • No acquisition-shaped features

    We are not building a suite. If a request would make Cadence into a second product, the answer is no.

That is the whole company

If you want to know how a particular thing works before you pay for it, ask. You will get an answer from one of the four.

Write to usSee the plans

Subscription product

One written summary of the week, sent every Friday at 09:00. 00 a month per team.

Product

  • What it does
  • Plans and prices
  • Questions before paying

Company

  • Who makes it
  • Contact

Legal

  • Legal notice
  • Privacy
Cadence is a fictional product. Prices, names and figures on this site are placeholders.