Preview image. Unlock full-res
Light feature block with orbit illustration linking engineering and support tags and a 2x2 grid of cards for issues, Slack discussions, shared views, and integrations.
Summary
A collaborate-across-teams section with headline, orbital diagram of #engineering and #support teams meeting at Plain, and four feature cards covering issue tracking, Slack discussions, shared views, and integrations.
Visual description
Light gray background. Top row: left side has bold black Collaborate across teams headline and gray paragraph about discussing customer issues, escalations, and engineering work; right side shows abstract illustration of two overlapping circular orbits with purple #engineering and green #support tags, avatars along paths, and Plain logo at the intersection. Below, 2x2 white cards. Top-left: timeline UI showing issue I-673 linked four days ago and moved to Done with Close the Loop note, caption about engineering integrations. Top-right: Slack-style thread with Start Discussion button, Carla message about a bug, notification card, Open in Plain button. Bottom-left: Views sidebar listing Onboarding Product Team, Retention Product Team, Enterprise Queries with star icon. Bottom-right: integration diagram from Salesforce, HubSpot, Linear, Slack icons down to account, contact, and issue pills into Plain logo.
Key takeaway
The orbit diagram instantly communicates cross-team routing without a paragraph. Each card shows a different collaboration surface (tracker timeline, Slack thread, shared views list, integration map) so the section covers multiple buyer mental models. Color-coded team tags (#engineering purple, #support green) make roles scannable.
Reuse notes
Strong for B2B support platforms selling internal collaboration, not just ticket closure. Needs simplified but recognizable UI for each workflow. Light background and white cards; illustration should stay abstract enough to avoid dating quickly.
