How a 7-person team stopped Slack-screenshotting their agent output

Coding agents generate HTML and markdown faster than ever. The bottleneck moved. It is no longer making the work. It is getting that work in front of teammates to review, comment on and revise.

TL;DR
Indigo Engineering's 7-person team was sharing AI-generated HTML by pasting screenshots into Slack, with no versioning and comments tangled across threads. They moved the workflow to display.dev, where agent output renders as a real page, comments live on the work and versions track automatically. The full story is in our [Indigo Engineering case study](/customers/indigo-engineering).

Coding agents generate HTML and markdown faster than ever. The bottleneck moved. It is no longer making the work. It is getting that work in front of teammates to review, comment on and revise.

Indigo Engineering, a fully remote team building data tools for progressive organizers, hit that wall hard.

The before: screenshots in Slack

Before display.dev, the team shared artifact files in Slack and commented in the thread. For HTML artifacts that meant pasting screenshots, which were, in their CEO Max Wood's words, "messy and often confusing." Several conversations got mushed into one thread. Versioning was a nightmare. Tracking down a change or a past discussion was painful.

The obvious alternative was worse. Moving artifacts into git would still be annoying to render, would need a pull request for every revision and would bury discussion in threads that were hard to follow.

The after: a shared home for agent output

Indigo now publishes its markdown and HTML to display.dev and collaborates there. The artifacts render as real pages. Comments live on the artifact. Versions track themselves. All seven people on the team use it.

Three wins showed up, two of them unexpected:

  • Faster iteration on new features and a major redesign the team had been mired in.
  • A quiet exit from Google Docs, since so many of their docs are now markdown-native and converting them by hand had become a chore.
  • A deferred enterprise upgrade. In Max's words, it "helped us delay a switch to Anthropic enterprise plans, which we probably would've been forced into so we could collaborate on Claude Design output."

That last point is the pattern worth noticing. When agents produce the work, teams need a neutral, shared surface to review and collaborate on the output. A shared workspace for that removes the pressure to buy everyone a seat on whichever tool generated it.

Read the full story in the Indigo Engineering case study, or start free and give your own agents a home.

FAQ

How do teams collaborate on AI-generated HTML and markdown?+

Instead of sharing screenshots in Slack or opening a pull request for every revision, teams publish AI-generated HTML and markdown to display.dev, where the artifact renders as a real page, comments live on the work and versions track automatically.

Can a whole team collaborate on Claude output without buying enterprise seats?+

Yes. Indigo Engineering used display.dev to collaborate on Claude output across their 7-person team for one flat price, deferring a forced upgrade to Anthropic enterprise plans.

Does it work with agents other than Claude?+

Yes. Anything that writes an HTML or Markdown file to disk works – Claude Code, Codex, Cursor or a shell script. The publish step doesn't care what generated the file.

Publish your first artifact in 15 seconds.

Free tier. No credit card. One-time password auth for viewers on free, Google + Microsoft SSO on Pro (€49/month flat).

Get started free →See pricing