Indigo Engineering builds straightforward software and data products that help progressive organizers build power in their communities. The team of seven is scattered across the US and ships two products: Matchbook, a voter-contact CRM with machine-learning optimization, and Matter, a voter-file enrichment tool.

Like most teams shipping software in 2026, Indigo’s engineers and designers lean heavily on coding agents. Those agents produce a constant stream of HTML and markdown: design output, reports, specs, internal docs. The work gets generated quickly. Getting it in front of teammates to review, comment on and revise was where things broke down.

Before: Slack threads, HTML screenshots and a versioning nightmare

“Before display.dev, we were sharing artifact files with each other in Slack and putting our comments there. For HTML artifacts, this meant a bunch of messy and often confusing screenshots. It also meant several conversations were mushed into the same thread, versioning was a nightmare, and tracking down changes or discussions was very annoying.”

The team had seen where this leads and didn’t like the alternative either:

“We might have eventually started using git to track artifacts, but that would have still been annoying to render, we’d need constant PRs for revisions, and threads would be hard to follow.”

After: a shared home for agent output

Indigo now publishes its markdown and HTML artifacts to display.dev and collaborates on them there. The artifacts render as real pages. Comments live on the artifact. Versions are tracked automatically. The whole seven-person team uses it.

“We use it to share and collaborate on markdown and HTML artifacts, and it’s helped us work together more seamlessly in this weird new agentic coding era. Our whole 7-person team uses it.”

The wins

Once the workflow moved to display.dev, the payoff showed up in three places the team didn’t expect to feel it.

Faster iteration on new features and a major redesign. “display.dev has helped us iterate much more quickly on new features and a big redesign project we’ve been mired in.”

An unexpected exit from Google Docs.“It’s also unexpectedly been a great way to move on from Google Docs since so many of our docs are now native to markdown and getting them into a friendly Google Doc format for visibility and collaboration had become a real chore.”

A deferred forced upgrade to Anthropic enterprise plans. “It’s also 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.”

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.

On how display.dev could improve

No new product is perfect, and we asked Max what was still missing. His answer says as much about how we work as about the gaps:

“display.dev is sort of a perfect elegant solution for us. There have been issues that you’d reasonably expect from any new software product but we’ve been so grateful for the display.dev team’s responsiveness when we’ve shared feedback.”

The bottom line

When agents do the producing and humans do the steering, the work still needs a home. display.dev gives agent-generated HTML and markdown a place to render as real pages, hold a team’s comments and version every change, at one flat price for the whole org. Indigo runs their redesign, their internal docs and their Claude output through it, with all seven people collaborating in one surface. Any team shipping in the agentic era can do the same.