For teams — A team license
ResourceADay is a five-minute editorial habit. When a team subscribes together, it becomes a quiet form of shared literacy — the same article read over morning coffee, the same line quoted in a Monday standup, the same reference passed to a new hire on day three.
We license the daily edition and the full archive to working teams of every size, from a six-person product squad to a 1,200-person engineering org. No perk-portal integrations, no L&D dashboards, no completion certificates — just the email, opened by people who choose to.
Three tiers — Pick the size that fits
The differences are plain: how many seats, how deep into the archive, and how much rollout support you'd like from our editors. There is no feature wall — every tier reads the same edition, every weekday at 6am ET.
For a working team of one to ten people.
$9per seat / month, billed annually
Best for: a product squad, a design team, a small engineering group.
For a function of twenty-five to two hundred people.
$7per seat / month, billed annually
Best for: a product org, a design department, an engineering function.
For organizations of two hundred people and up.
Custompriced per seat, with volume tiers
Best for: a company-wide learning program, a 500+ person org, multi-team deployments.
All tiers include the same daily edition, written and edited by our six-person editorial team in Brooklyn. Prices in USD; annual billing. We do not run quarterly discounts or end-of-year promotions — the price you see is the price you'll pay next year.
A short rollout — How one team uses the archive
What follows is one team's experience, told as a brief anecdote. Names of the team lead are with the editors and can be shared on request after a demo.
Linear's product team — twenty-eight people across product management, design, and engineering — licensed ResourceADay as a Department in early 2023. Their lead had a simple problem: the team was reading the same five Substacks in rotation, and the in-group Slack channel where they posted links had gone quiet. She wanted a single, reliable input — something read by everyone, not algorithmically sorted for each individual.
The rollout took an afternoon. The team added the daily edition to a shared internal mailing list, then added a single Slack integration that posts each day's link into a #reading channel at 6:15am ET. No badges, no completion tracking, no manager reports.
Two rituals emerged, both unplanned. New hires are now onboarded with a reading list of twenty past editions chosen by their manager from the archive — searchable by topic ("how we ship," "design critique," "engineering org design") — and asked to write a one-paragraph reaction to one of them in their first week. And on Friday afternoons, the team lead posts a "what stuck this week" thread to the same Slack channel, with two or three sentences from anyone who wants to weigh in.
"It is the lowest-cost team-learning program I have ever run," the lead wrote to us in a recent note. "It does not ask anything of anyone. It just shows up."
This is one team. Yours may use the archive differently — for a monthly writing prompt, for an all-hands book club, for an L&D curriculum. The archive is yours to read however your team reads.
Request a demo — Talk to one of our editors
Tell us a little about your team — the rough size, the function, and what you'd like a daily read to do inside your week — and one of our editors will write back within one business day. There is no sales deck on the other side of this form, just a short reply and, if it's useful, a 30-minute call.
Or write to us directly at [email protected]. We reply to every team inquiry within one business day, usually faster.
