Sample summaries
Honest by design
Git data says what changed, not what it means. Gitmayo only uses outcome language when the activity earns it — and says so when a week is quiet or all under-the-hood. Here's how three very different weeks read.
Each one can be downloaded as a branded PDF or PowerPoint — try it below. (In the app, exports are a Pro feature.)
A shipping week
investor toneWeek of 14–18 Jul
investor tone
A solid week — the payment flow is live, and onboarding is nearly there.
Shipped
- Stripe checkout is live. Customers can now pay and subscribe end to end.
- Fixed a billing bug where annual plans showed the wrong total.
In progress
- New onboarding flow — most of the screens are built; wiring up the final step next week.
- Started work on team invites.
Heads-up
- The mobile layout for settings still needs a pass before we point users at it.
Why it reads this way — A real feature merged to the main branch, so “shipped the payment flow” is fair.
A quiet week
plain toneWeek of 7–11 Jul
plain tone
A quieter week — mostly small fixes and housekeeping.
Fixed
- Corrected a typo on the pricing page.
Heads-up
- Nothing major shipped this week; the work went into the onboarding rework that's still in progress.
Why it reads this way — Little happened, so it says so plainly. An honest thin week beats a fabricated busy one.
A behind-the-scenes week
cofounder toneWeek of 30 Jun–4 Jul
cofounder tone
A behind-the-scenes week — reworking internal code, nothing user-facing yet.
In progress
- Reworked how the app is organised internally to make future features easier to build. No change customers will see yet.
Why it reads this way — Lots of commits to a refactor branch → “reworked internal code”, never “improved performance”.
Get yours this Friday
Connect GitHub and Gitmayo writes your first plain-English summary automatically.