Weekly update · Samplereal example with client details removed

See a real weekly update before you sign anything.

Every Monday, our clients get a short written update: what went live last week, what is next, decisions we need from you by Wednesday, risks, and a handful of numbers that matter. The example below is a real one with client details removed.

From: [email protected]Monday · 09:30 MYT

Week 34 update · Checkout v2 pilot and reconciliation cleanup

Hi team,

A short one this week: three things went live, two decisions need to come back from you by Wednesday, and a heads-up on one partner-side limit we are working around.

What went live last week

01 / 5
  • Checkout v2: payment retries are now more reliable on Android. Our test data shows a 14% improvement in successful retries.
  • Merchant portal: the reconciliation export now runs in the background. Report page load time dropped from around 9 seconds to just over 1 second.
  • Internal audit log: access controls now apply to every change. Security review passed for the next release.

What we are working on this week

02 / 5
  • Launching Checkout v2 to 2 pilot merchants (controlled rollout).
  • Moving the reporting tool from the old database to the new one.
  • Closing the open paperwork item for the analytics vendor.

Decisions we need from you by Wednesday

03 / 5
  • Do we release the new payment fallback screen this week, or hold it for next week?
  • Are you comfortable keeping raw payment logs for 72 hours, or would you like us to extend it?

Risks and things blocking us

04 / 5
  • The partner's system has a known limit during peak hours. We have set up automatic retries, but we have also flagged it to their team.
  • One stakeholder is out this week. Their deputy is standing in to approve decisions.

Numbers that matter, kept short

05 / 5
  • Releases last week: 3 out of 3 planned went live (100%).
  • Incidents: none last week. One the week before, resolved in 42 minutes.
  • Test coverage on the main app: up from 76% to 78%.

Why we send the update on Monday instead of Friday

Sending on Friday pushes the update into your weekend. Sending on Monday morning puts it at the start of your working week, when decisions and replies are easier to coordinate. For the same reason, we also avoid releasing things late on a Friday so problems do not land on your weekend.

  • Readable without translation

    Every line is written for non-engineers. We avoid technical jargon unless it is needed.

  • Decisions first

    Decisions we need from you have their own section, with a clear deadline. If we need a yes or no, we say so.

  • Numbers kept short

    We include only the numbers that matter this week. No oversized dashboards.