Playlister

Summary
Playlister is a cloud‑based presentation and digital signage platform built for church teams and volunteers. I designed and developed the marketing site from the ground up, focusing on clarity, speed, and ease of use. The goal was to communicate Playlister’s value quickly, reduce friction for first‑time visitors, and support ongoing updates as the product evolved.
Company
Playlister
Year
2020
Challenge

The project was constrained by a tight two‑week timeline to design and launch the entire site. With limited time for research and prototyping, decisions needed to be made quickly and confidently. At the same time, Playlister did not have an in‑house designer, which meant I was responsible not only for the initial build, but also for setting up a structure that could withstand future edits by multiple stakeholders without degrading the system.

Solution

I designed and built the site from scratch within the two‑week window, prioritizing the core pages and messaging needed for launch. The structure was intentionally simple, allowing Playlister to iterate on content over time without disrupting the foundation. After launch, I continued working closely with the team to refine pages, support new needs, and maintain visual and structural consistency as the site evolved.


Rapid design and development

Given the compressed timeline, I focused on establishing a strong foundation rather than over‑optimizing early details. The initial build centered on the primary sitemap and messaging, with landing pages and secondary content added incrementally after launch. This approach ensured the site shipped on time while remaining flexible for future growth.

Ongoing collaboration and ownership

Because Playlister does not have a dedicated design team, I remain closely involved in most website updates. I work directly with stakeholders via Slack, review proposed changes, and provide staging links for approval. Feedback cycles are typically short, allowing updates to ship quickly and with confidence.

Managing shared ownership in Webflow

Occasionally, changes made directly in Webflow outside of CMS structures introduced inconsistencies or unnecessary classes. To address this, I coordinated closely with the team to stay informed of updates and periodically clean up the site as needed. These maintenance passes helped preserve the integrity of the original system and ensured the site continued to reflect a high standard of quality.

Long‑term relationship and impact

Over time, this collaboration evolved into a strong working relationship built on trust and shared standards. The success of the Playlister site led to additional referrals and opportunities, reinforcing the value of thoughtful execution, clear communication, and ongoing stewardship beyond the initial launch.


More work

2025

Grail

Read case study
2025

Webflow

Read case study
2023-2025

Webflow Conf

Read case study
2025

Tight

Read case study
2024

Contrast

Read case study
2024

Webflow Shop

Read case study
2022

Wicomico

Read case study
2022

Evryone

Read case study
2022

IBG Social

Read case study
2020

Mono Solutions

Read case study

Let's connect

© #### — Mike Birkey