The per-person amount is the actual question

Almost everyone organizing one of these will tell you the hard part is the chase. They are wrong. The hard part is the ask, and the chase is just what happens after a vague ask hits a busy team. The biggest decision you make is the number you name in your first message: a specific per-person amount, not a range, not a 'whatever feels right', not a sliding scale, not 'whatever you can swing'. One number, written clearly, sent once.

The defaults I have landed on after running maybe two dozen of these badly:

  • Ten bucks. A coworker's birthday cake, a thank-you for the office manager. Buys a gift card and a printed card and nobody thinks about it twice.
  • Twenty dollars per person for the default workplace ask, which is most of what you will ever run: a leaving gift for a colleague, a milestone birthday for a team member who has been around a while, a baby shower for a coworker. From a team of ten this is two hundred dollars, which is a real gift without anyone feeling shaken down. Twenty is also the amount that produces the cleanest participation rate, in my experience, because it is small enough that nobody opts out on principle and large enough that nobody feels like the ask was pointless.
  • Thirty to fifty for a real milestone: a retirement after twenty years, a wedding for someone close to the team, a leaving gift after a decade of service. The ask is bigger and the participation rate is lower, but the people who do pay are the ones who actually wanted to contribute, which is its own filter.
  • A hundred or more per person only for genuinely close groups (a wedding gift from six college friends, a baby gift from four siblings, the bachelor-party fund where everyone is already friends with everyone). Past that threshold the whole thing stops being a collection and turns into a coordinated joint gift, which has different mechanics entirely. You will probably end up on a shared spreadsheet and that is fine, because the group is small enough to actually maintain one. The collection model breaks somewhere around the point where you stop knowing everyone's last name.

Above all, do not write 'whatever feels right'. That phrase converts a clean per-person ask into a sliding scale where the high payers feel mildly resentful, the low payers feel mildly guilty, and the organizer ends up forty percent under target. The openness in the ask is read as the absence of an expectation, and the absence of an expectation is read as 'I do not actually need much from you'. I have watched this happen four separate times. The Jules pool from my opening was the fourth. I will admit, in the interest of honesty, that I have also broken my own rule: when the team is one I know well and the implicit twenty is obvious, I have skipped naming the amount and it has been fine. The rule holds for teams where the social baseline is unclear, which is most teams in most workplaces.

The other thing that breaks the ask, and which I have done at least as often as I have left the amount vague, is forgetting to say what the gift is. 'We are pooling for the rolling kitchen cart she pinned on Pinterest in October' is a picture; people can see the cart, see the recipient using it, and decide whether to chip in for that specific thing. 'We are pooling for a gift' is not a picture. It is a category, and categories produce the minimum. Gift cards and charity donations are the obvious exception to this, since the dollar amount itself is what people are picturing; for almost anything else, you need to name the object.

Pick the channel before you send the first request

This is the section where I am going to be slightly annoyed, because I have written it in my head about thirty times and every team I have ever been on still gets this wrong. Venmo, Zelle, Cash App, Splitwise, Apple Pay, PayPal, the cash envelope on the corner of someone's desk. Most teams use at least two of these in regular life. Most workplace gift collections accidentally invite all of them at once. The organizer sends Venmo requests to the people they know, says 'or Zelle me if you don't have Venmo' to the others, accepts a five-dollar bill from the one person who refuses to do digital payments, and three days later has a pool spread across four apps with no single total visible anywhere.

That is the failure. Not because any single channel is bad. Because the organizer becomes the bookkeeper, mentally adding it up, remembering who paid through which app, chasing missing payments across whichever app the missing person uses. The collection turns into part-time accounting for a job nobody asked for. By the time the gift moment arrives, the organizer is annoyed at the team, the team is mildly annoyed at the organizer, and the recipient gets a gift nobody is in the mood to actually present warmly.

Pick one channel. Match it to where the team already moves money. If most of the team is on Venmo, the ask is a Venmo request and the holdouts get one alternative. If the team is remote and crosses borders, neither Venmo nor Zelle works at all, and you need a pool that does (a group gift card on Reco handles this case because the gift is bundled into the card flow, not tied to a US payment app). If the team is older and uses checks or cash, do not run the collection on an app at all; pass an envelope in person and skip the digital tracking entirely. One channel, not three. I do not have more to say about this. Pick the channel and move on.

When collecting money is the wrong move

This is the section nobody writes, and I think it is the most important one in the piece, so I am going to slow down for it.

There are real situations where running a money pool is worse than not running one. The team is small (three or four people). At that size the ask becomes individual social pressure on each person, and saying no is awkward in a way it is not when the ask goes to twelve. Three coworkers who actually want to pool for a gift will just text each other. They do not need an organized collection, and trying to formalize one only adds weight.

The recipient would be uncomfortable knowing money was collected. Some people, especially in a leaving-the-company moment or a milestone they did not particularly want to mark, would rather have a thoughtful card than a pooled gift card. If you are not sure, the safer move is a card that does not mention money and a small token gift from the organizer alone. The asymmetry to remember is that a card-and-no-money never reads as cheap; a poorly executed money pool can read as obligatory in a way that subtracts from the gesture.

The occasion does not warrant it. A coworker's seven-year work anniversary does not need a pooled gift. A coworker's retirement after thirty years does. A regular birthday for someone you barely know does not need one. A milestone birthday for someone the team genuinely loves does. Pooled money is not the universal upgrade over a signed card; it is the right move for specific moments and the wrong move for most.

The relationship is awkward. A pooled gift to a recently-fired colleague reads strange. A pooled gift to a boss who is still your boss can read like a bribe, even if it is not. A pooled gift for a coworker you privately do not like, and would rather just sign the card for, is a quiet kind of dishonesty that wears on the organizer. If the ask makes you uneasy as you draft the message, that is information. Trust it. I will also admit, since I am being honest in this section, that I have been the 'thumbs up but never paid' person at least once myself, on a baby-shower collection for someone I did not know well and the implicit twenty felt like a tax on being on the team. I am not proud of it. I think the implicit twenty did feel like a tax that week, though looking back it was probably just that I had been on three other collections in a month and the back-to-back ask wore me down.

The card is the part that does the actual work

A thing worth saying, since most advice on this skips past it: the money is not the gift. The money is just packaging. The thing that lands when the recipient opens the bundle is the card, signed by the actual people they work with, with actual lines about actual moments. The gift card or wrapped object is the punctuation mark at the end. A two-hundred-dollar Amazon gift card with no card around it reads as 'we owed you something and paid the minimum to get out of it'. The same gift card inside a card with fifteen specific notes reads as 'we love you, here is also enough to buy the cookbook you have been threatening to buy for two years'.

So the collection mechanics should not become the dominant story. If you spend three days chasing payments and one hour on the card, the card will read like an afterthought and the gift will feel transactional even when the money is real. Flip the time ratio: spend an hour on the card setup and a few minutes on the collection, by tying the collection to the card itself so the two are one thing. On Reco the group card with multiple signatures can carry a pooled gift target inside the same flow; people sign and chip in on the same page, the organizer sees the running total live, and the bundled card and gift land together at the scheduled moment. No separate Venmo thread, no spreadsheet, no Friday-morning panic about whether the pool will hit the target.

Step-by-step: the version that actually works

The order matters. Most people who run these as ad-hoc Venmo requests get the order wrong, and that is what produces the chase. The version that works:

First, decide the gift before you decide the amount. 'We are buying her the noise-cancelling headphones she has been hinting at since November' is a different ask than 'we are pooling money for whatever'. The specific gift sets the target, the target sets the per-person ask, and the per-person ask is the number you put in the invite. Working in the other order, target-first, produces the 'whatever feels right' situation.

Second, build the card. Pick the format. Sign it yourself first with a real message. The card has to exist before the collection starts, because the collection invite is the same message as the card invite. People are not signing up to pay money into a void; they are signing the card and contributing to the gift in the same flow. The piece on how to sign a group card covers the blank-box freeze that hits the moment you click the link, if you need a starting point for your own first message.

Third, name the amount and the deadline. 'I am collecting twenty dollars from each of us for a leaving gift for Jules. Deadline is Wednesday at noon. Card and gift deliver Friday morning. Sign the card and chip in here.' One sentence per piece of information. Anything more elaborate is padding.

Fourth, post the link in the chat the team already uses. Slack channel, WhatsApp thread, group iMessage. Not a fresh thread, not a new channel, not individual DMs to fourteen people. The collection has to live where the team already pays attention.

Fifth, send one individual reminder twenty-four hours before the deadline to each non-payer. Short, low-pressure. 'Hey, no pressure, but the gift for Jules closes tomorrow at noon if you want to add a note.' After that, stop. The participation rate you get is the participation rate. Do not chase further.

Sixth, close the books at the deadline. Round the total to a clean number, pick the gift that fits the amount you actually have (not the amount you hoped for), and deliver the card with the gift. The collection is over; the gift moment begins. For the gift-attach side specifically (amounts, currencies, the native bundling of card and money), how to send an ecard with a gift card covers the part where the money actually meets the message. For the card setup itself (PIN, surprise, schedule), how to make a group card everyone signs walks the setup end to end.

Turn the collection into a group card with a built-in gift pool

The version of this that works at scale is the group card with the gift collection baked in, not the spreadsheet plus Venmo thread plus separate card. You can create a card online in a few minutes; the longest part is writing your own first signed message, which is also the most important, because it tells every other signer what register the card is in.

One last thing, off-topic. The Jules thing ended with the bookstore gift card I mentioned in the opening, which I bought at the small independent bookstore she had been to once with the team, the kind that smells faintly of cedar and has a cat that sleeps on the new-releases table during the week. The card was eighty-four dollars in the end, plus a little of my own money to round it, and I taped it inside a printed card with the team's signatures collected in person over two days because the digital collection had already half-collapsed. Jules opened it on her last day in the office, said 'oh, this is so sweet, thank you', and put it in her bag. She left for a job in Denver and we lost touch the way people do when one person moves and nobody is the natural maintainer of the friendship. About six months later I ran into someone who had stayed in touch with her, and asked, half as a joke, whether she had ever used the gift card. He laughed and said he had no idea, and we changed the subject. I think about that bookstore sometimes when I walk past it. The cat is gone now; the owner died last summer. The store still has my card receipt on file somewhere, probably, in the same drawer as the receipts of everyone else who has ever bought a gift they were not sure about for someone they were not sure they were close enough to.