Every engineering team knows coordination eats time. Meetings, status chasing, missed handoffs, rework from lack of context. But "coordination tool" isn't a category people search for. Marzo AI needed a site that could name the pain before offering the fix, and make an abstract problem feel concrete enough to justify a pilot.

I handled the full project end to end. Design in Figma, development and interactions in Framer.

"Coding isn't the bottleneck anymore. Coordination is." That's the entire pitch in two sentences. Below it, a product UI mock shows a Slack-integrated alert ("Frontend blocked by auth API change"), a meeting card with attendees, and a follower notification. The visitor sees the product living inside tools they already use before scrolling a single pixel.

The trust bar follows with logos from companies like Microverse, Pachama, and COR, establishing credibility early.

Three animated stat blocks quantify the coordination tax: 11 hours in meetings per week, 8 hours context-chasing, 50% rework from lack of context. These aren't vague claims. They're specific enough to make an engineering manager nod and keep scrolling.

The "What Marzo AI does" section breaks into three numbered blocks: route changes to affected people, spot cross-team risk early, and keep commitments from slipping. Each block has a headline, a short explanation, and 3 bullet points that describe the behavior in plain language. No feature jargon. Just "unblock people before they know they're blocked."

For a tool that reads Slack conversations and meeting notes, trust is everything. The security section addresses this head-on with three cards: Your Infrastructure (managed cloud or self-hosted VPC), Your Permissions (inherits Slack access controls, "Off the Record" mode, no employee monitoring), and Your AI Choice (bring your own LLM keys). The design gives this section real visual weight instead of burying it in a footer link.

Dark backgrounds with soft gradient glows, clean card layouts, and a color palette that reads as technical but not cold. The UI mocks embedded throughout use real Slack-style components (message bubbles, avatar stacks, alert badges) so the product feels familiar before anyone installs it. Interactions are subtle: scroll-triggered reveals, animated stat counters, and smooth transitions that keep the pace without distracting from the content.

"Start Pilot" is the primary CTA throughout, with "Book a Demo" as the secondary. The pilot section at the bottom spells out exactly what's included: forward-deployed engineer, self-hosted or managed cloud, weekly tuning, and a final readout with measured outcomes. No ambiguity about what happens after you click.

A site that turns an invisible problem (coordination overhead) into something an engineering leader can point at and say "that's exactly what's slowing us down." Then gives them a clear, low-risk way to fix it.