DonzyBeta
Sign inStart free
Product awareness & recognition

Nothing you ship should stay invisible — or anonymous.

Donzy turns every product update into a dispatch the whole org can see — who built it, why it matters, and how people reacted. One email goes out on Monday. Nobody has to go looking.

Create your organization →See a sample dispatch
The problem

Shipping it was never the hard part. Telling people is.

And it breaks in the same three places every time.

Writing it

Nobody’s actual job, so it lands at 6pm on Friday — or not at all.

Posting it

The channel holds it for a day. Nobody scrolls back.

Crediting it

The commit has names on it. The announcement doesn’t.

How it works

Easy to publish. Impossible to miss.

Three steps, and only the first one costs you any time. Here is what each one looks like from the inside.

01

Write it

Describe it in a sentence. Publish something worth reading.

Fill in the form yourself, or type what changed in plain language and let Claude draft the title, summary, and why it matters. You edit before anything publishes — and product area, audience, and impact level are always your call, never guessed.

A draft you'd actually send beats a perfect one you never wrote.

02

Publish it

A permanent home, not a thread that scrolls away.

Every published change lands in the org feed with its impact level, product area, and date attached. Filter by this week, by product area, or by the department it was built for. Nothing gets buried under standup notes.

Chat is a river. This is a record.

03

Get credit

Credit lands on the people, not the ticket.

Contributors are attached the moment it publishes — main and supporting. Teammates react and comment in public, then send kudos as a private note in their own words. Every person keeps a private wall of the kudos they’ve been sent. No leaderboard, no score, nobody ranked.

Recognition that arrives a week late isn't recognition.

Sample dispatch

One card. The whole story behind it.

Open one and everything is there: the summary, why it matters, the screenshots, everyone who worked on it, and the conversation that followed.

In the feed

Impact level, product area, and the one line explaining why it matters — enough to know whether this one is yours to read.

One click deeper

Weekly digest

Nobody has to remember to check Donzy.

Monday morning, in your organization’s timezone, one email goes out to everyone who wants it. Three sections, no digest fatigue.

  • Company-wide — everything published last week.
  • For your department — the changes built with your team in mind.
  • Kudos you received — the private ones, quoted in full.

Opting out is one click, and it’s per person — not per organization.

Who it’s for

Built for whoever’s in the room.

Editors, teammates, and admins all read the same feed — each with exactly the controls they need, nothing more.

For editors

Turn a rough description into a polished dispatch in one shot. Save it as a draft, publish when it’s ready, edit it in place after.

For everyone else

React to what’s new, send private kudos to the people who built it, and keep your own wall of every kudo you’ve received. Filter the feed by product area or department — no extra app to check.

For admins

Invite the team, adjust roles and departments, and keep product areas and initiatives tidy — all from one settings page.

Straight answers

The questions we get before anyone signs up.

Mostly variations on “isn’t this just a Slack channel?” It is not.

We already post updates in Slack. Why add this?

Because a channel is a river, not a record. A dispatch here keeps its own page — impact level, product area, contributors, screenshots, and the reactions it got — and it’s still findable in six months. Filter by product area or by the department a change was built for. Nothing gets pushed off the screen by standup notes. Closer to a changelog than a Slack thread, but with the people who built it credited and the reactions it got attached — not a list of release notes nobody opens.

Who has to write these? We don’t have a comms person.

Admins and editors publish; everyone else reads, reacts, and gives kudos. If writing is the bottleneck, describe the change in one sentence and Claude drafts the title, summary, and why it matters. You edit before anything publishes.

Will the AI make things up about our product?

It only has the description you give it, and it never picks the taxonomy — product area, audience, and impact level are always chosen by a person. Read the draft, edit it, regenerate it, or ignore it and write your own. Nothing publishes until you say so.

Does everyone have to remember to check another app?

No. Monday morning, in your organization’s timezone, everyone gets one email: what shipped company-wide, what shipped for their department, and any kudos they received that week. Opting out is one click, and it’s per person — not per organization.

Are kudos public? We don’t want a leaderboard.

Kudos are a private note to one contributor, and a kudo can’t be blank — you have to say something, in up to 280 characters. Nobody else sees it. They collect on a wall only the recipient can open, and there’s no score or ranking anywhere in the product. Reactions and comments are public on the change itself; that part is meant to be seen.

What happens after something is published?

It stays editable. Editors and admins can fix a title or sharpen a summary in place, so a typo doesn’t become permanent. Comments run one reply deep, which keeps a change page readable instead of turning it into a thread.

What does this cost?

Free while we’re in beta. When we introduce pricing, it’ll depend on your organization’s size — with generous plans, not a per-seat toll. Beta users get advance notice before anything changes.

Ready when you are

Your next release deserves an audience — and its people deserve credit.

Create the organization, invite the team, publish the first change. Nothing new for anyone to learn.

Free while we’re in beta — pricing later will depend on organization size, with generous plans.

Create your organization →