In early December, the Wikipedia apps will show each reader a recap of their year. The Wikimedia Tech News issue of 9 November says the Wikipedia Apps team is preparing to launch Year in Review in early December, giving app users "a personalized recap of how they read and engaged with Wikipedia throughout the year." It joins a December habit that most of your users already know from music and social apps.
Spotify's Wrapped is the best-known version: its 2025 edition had more than 300 million engaged users and more than 630 million shares on social media, according to Spotify's fourth-quarter 2025 earnings release.
Those recaps are made for the person who receives them. They are shared because they say something about the listener or reader. If you run a small software product whose users serve clients of their own, you can build a December recap with a second, more practical job. Each user gets their own year in numbers, and they also get a polished card or one-page report for each of their clients: "your 2026 with us". The user sends that card as a year-end thank-you. A small "made with" line at the bottom shows the client which product produced it.
This post sets out the play in full. There is no published case study of a small product running this exact loop, so the numbers below are a designed model. Every figure in the model is labelled illustrative. Replace them with your own data before you decide anything.
The idea and why it works
A growth loop is a cycle in which using the product creates the next round of new users. This one has three parts, and each does a separate job.
First, the product sends something useful on a schedule, without the user setting anything up. A year-end report arrives in the first week of December whether or not the user remembered your product existed. That brings lapsed users back with a reason to log in.
Second, the report draws on the history the user has built up in your product. A year of invoices, bookings or published posts is data the user cannot get anywhere else in one view. The longer someone has used your product, the better their recap, which gives them a reason to keep their work with you next year.
Third, part of the output is made to leave the product. The client card goes to people who have never heard of you, carried by someone they already trust. The "made with" line is attribution on that output, in the same way a form or a deck can carry a small credit. We covered that credit mechanism in how Gamma and Tally use a "Made with" badge. What changes here is the carrier. The card is a deliverable the user is proud to send to a paying client, so it travels by email to a business owner, at the time of year when people already send thank-you notes.
The user wins first. A freelancer or small agency gets a client report they would otherwise have to assemble by hand in a spreadsheet, and it lands in December, when a good year-end note helps keep a client for the next year. The product wins second, through return visits, a stronger reason to stay, and a stream of warm introductions to new prospects.
Who it's for
The play fits products where three things are true: your users have clients, your product holds a record of the work done for each client, and those clients look like future users.
Good fits include invoicing and bookkeeping tools (amounts invoiced, invoices paid on time, average days to pay), tools that agencies use to run client work (projects delivered, hours, turnaround times), scheduling tools for service businesses (sessions booked, attendance rate), website and social analytics tools that agencies report from (traffic growth, posts published, best month), and freelancer tools for writers, designers and developers.
The third condition decides how much growth you get. A bookkeeping tool whose users serve small businesses is sending cards to exactly the kind of person who might want bookkeeping software. A scheduling tool for personal trainers sends cards to individual gym clients, who will enjoy the card but are unlikely to sign up. The recap can still be worth building for retention in the second case, but expect little acquisition from it.
It does not fit products where the client data is sensitive: health, therapy, legal matters, finance for individuals, or anything involving children. A card that says "12 sessions with your therapist this year" should never exist. It also does not fit products with less than a few months of history per user, internal tools whose users have no outside clients, or enterprise products whose customers forbid vendor branding on anything sent to their clients.
What you need
Tools: the usage data you already store, a template that turns numbers into a card image and a one-page PDF (most teams use an HTML template rendered to image or PDF), the email system you already send product emails with, a private share page per card, and a referral parameter on the "made with" link so you can count signups. Time: an estimate of one to two weeks for a solo builder who knows their own data model, most of it spent on the data queries and checking the numbers are right. Cost: mostly your time, because rendering and email are usually things you already run.
Timing matters. If you want cards in inboxes in the first week of December, you have about two weeks from today. Start with the private recap and a single client card format, and leave the variations for next year.
Step by step
Pick three to five numbers per side. For the user's private recap, choose numbers that reflect their business: total invoiced, clients served, busiest month, and one figure about how your product helped (for example, hours saved by automatic reminders, if you can measure it honestly). For the client card, choose numbers that describe the relationship and flatter both sides: projects delivered, hours of work, average turnaround, years working together. Never show revenue, rates or margins on a client card. Never compare one client with another.
Set eligibility rules. Only build cards for clients with enough activity to say something, say at least three jobs or invoices in the year. Skip clients with disputes, overdue balances or refunds, because a cheerful card to a client who owes money is awkward. Let the user see who was left out and why.
Make privacy the default. Each card contains only the work between one user and one client, and only the fields you chose in step 1. That is the data minimisation principle in UK and EU law: personal data should be "adequate, relevant and limited to what is necessary", as the UK Information Commissioner's Office puts it, and the EU wording is the same in Article 5(1)(c) of the GDPR. Nothing goes to a client automatically. The user previews every card, can edit or hide any number, and sends it themselves, either from their own email or as a download. Share pages use unguessable links, show no other client's data, can be revoked by the user, and expire after 60 days. Do not add tracking pixels that identify individual recipients; count views and clicks in aggregate. Check that your terms of service cover using account data to build reports for the account holder, and say in plain words on the recap page what the card contains and who can see it.
Build the private recap first. Send each active user an email in the first week of December with their year in numbers and a button to their recap page. On that page, show the numbers, one or two suggestions for next year tied to their data (for example, "You sent 40 reminders by hand. Automatic reminders would have done that for you"), and a clear second section: "Thank-you cards for your clients".
Make sending a one-minute job. List eligible clients with a preview of each card, a short editable note from the user, and three actions: copy a ready-written email, download the card as an image or PDF, or send from the user's connected email. Let the user tick several clients and send them in one go.
Add the "made with" line, small and honest. One line at the foot of the card: "Made with [Product]", linked to a page made for recipients, with a referral parameter that identifies the sender. That page should explain what the product does for a business like the recipient's and offer a first useful task without a signup wall, an approach covered in letting visitors get a real result before they sign up.
Let paid users remove the line. On paid plans, give users a switch to remove your branding or replace it with their own logo. Removing branding is a familiar paid feature: Tally's Pro plan includes removing Tally branding from forms. Free users keep the line, which is a fair trade for a report they did not have to build. Expect some paid users to switch it off, and treat the ones who leave it on as a sign they are happy to be associated with you.
Check the numbers before anything goes out. Reconcile a sample of 20 recaps against the raw records. A recap with a wrong total sent to a client damages your user's credibility and yours. Exclude test accounts, deleted clients and duplicate records.
Template: card and email copy
The names below are fictional examples. Replace the bracketed fields with your own.
Client card (image or one-page PDF)
Your 2026 with Harbour Design Studio
Prepared for Kettle & Co
14 projects delivered
212 hours of design work
Average turnaround: 3 working days
Busiest month together: September
Working together since 2023
"Thank you for trusting us with your brand this year. The spring menu relaunch was our favourite job of 2026. Here's to 2027." Mia, Harbour Design Studio
Made with [Product]
Email from the product to the user (first week of December)
Subject: Your 2026 in [Product], and a thank-you card for each client
Hi [first name],
Your year is ready. In 2026 you invoiced [total] across [number] clients, and your busiest month was [month].
We have also made a short thank-you card for each of your [number] regular clients, showing the work you did together this year. You can preview and edit every card, and nothing is sent unless you send it.
[See your year]
The [Product] team
Email the user sends to their client (pre-written, editable)
Subject: Our year together, and thank you
Hi [client first name],
Before the year closes, I wanted to say thank you. I put together a short summary of what we worked on in 2026: [number] projects, and some of my favourite work of the year.
[Card attached or link]
I'm looking forward to next year. If there's anything you'd like to plan for early 2027, reply and we'll set a time.
[User's name]
The illustrative maths
Illustrative only, using assumed rates rather than measured ones. Suppose you have 2,000 active users. If 40% open their recap, that is 800 users. If 25% of those send at least one client card, you have 200 senders. If each sends to an average of 8 clients, 1,600 clients receive a card. If half of them open it, that is 800 card views. If 2% of viewers click the "made with" line and sign up, you get 16 new users.
Sixteen signups in this illustrative model sounds small. Three things make it worth the work. Each signup arrives with a recommendation from a supplier they already pay, so they are likely to be better prospects than a cold visitor. The same build brings back some of the users who drifted away during the year, and every one of the 800 users who opened a recap in the illustrative model has just seen why leaving would cost them their history. And the recipient fit changes the result sharply: illustrative again, if your users' clients are small businesses who need the same tool and 5% sign up, the same 800 views give 40 users. Run the sum with your own numbers before you build, and decide in advance what result would make you repeat it next year.
Metrics to watch
Recap open rate: users who opened the recap page divided by users emailed.
Send rate: users who sent at least one client card divided by users who opened the recap. This is the number that tells you whether the card is useful to them.
Cards per sender: how many clients each sender chose. A low figure with a high preview count suggests users like the card but distrust some numbers.
Card view rate and "made with" click rate, counted in aggregate.
Signups and activation from the referral parameter. Count only signups that complete a first real task, not account creation alone.
January retention of users who opened their recap compared with similar users who did not. If you can, hold back the recap from a small random group so the comparison is fair.
Branding removal rate on paid plans, and any support tickets about wrong numbers or privacy. One complaint about the wrong client's data is a stop signal.
Pitfalls
Wrong numbers are the biggest risk. A recap is a statement of fact sent in your user's name, so reconcile before you send and let users edit.
Some years were bad. A user who lost half their clients does not want a celebration. Lead with neutral numbers, never show year-on-year declines on client cards, and make it easy to skip the whole thing.
Heavy branding turns a thank-you into an advert and users will stop sending it. Keep your mark to one line in small type.
Late timing loses the moment. Cards that arrive after mid-December compete with holidays and closed offices. Aim for the first week.
Sending on the user's behalf without a clear preview breaks trust. The user presses send, every time.
Counting vanity numbers, such as shares of the private recap, tells you little. Judge the play on send rate, signups that activate, and retention.
Variations
A quarterly client review uses the same template four times a year, which turns a December event into a regular loop and gives you four chances to tune it. A client anniversary card goes out on the twelve-month mark with each client rather than in December. A year-end statement for bookkeeping tools can include the totals a client needs for their tax return, which makes the card useful enough to be kept. For agencies, a team version credits the staff who worked on each account. And for products where reviewers or approvers are already part of the workflow, the card can sit alongside the draft-review loop, so the people who reviewed work all year see the summary too.

