THE BRIEF
FRAMER · CMS · CUSTOM CODE
VISUAL SYSTEM & OUTPUT
The brief wasn't "build a reports page." It was "make this report actually work for us." That meant solving two separate problems in the same build. The sticky nav was about retention — keep the reader engaged through 12 expert opinions without losing their place. The PDF gate was about conversion — the team had no visibility into who was reading their research. Both components are custom code inside Framer. No external tools, no maintenance overhead.
THE PROBLEM
CMS COLLECTION · PDF DOWNLOAD · LEAD CAPTURE
Peec.ai published a 12-expert roundup on AI search strategy. The content was strong — the page wasn't built to do anything with the traffic. Readers came, read, and left. No way to capture who they were. No way to know how far they got. And no system to publish the next report without rebuilding the page from scratch.
THE SOLUTION
Long expert roundups lose readers halfway through. Built a custom component that sticks to the left of the page as the user scrolls — tracking reading position and highlighting the active section in real time. Readers stay oriented in a 12-section article. Completion rates go up. No scroll-jacking, no library dependencies, pure custom code.
Email-Gated PDF Download
The report was free to read but generating zero leads. Built a custom component that gates the PDF behind an email submission — the reader fills in their address, the lead goes into Peec.ai's email system, then the file downloads automatically. One interaction. Every download is now a captured contact. No Zapier, no third-party form tool.
WHY IT MATTERS
Every PDF download now captures an email address. The sticky navigator gives readers a clear path through long-form content. The CMS means the next report ships without a developer. Peec.ai went from a single research page with no feedback loop to a publishing channel that generates contacts on autopilot.