A clinic's development team, ready for the unplanned.

sprints against a shared backlog
tickets in a typical two-week sprint, give or take
of each sprint held for urgent requests
to publish a press page when the paper ran a story
The problem
Spectrum serves LGBTQ+ patients, people living with HIV, and the surrounding community. Their clinical side moves fast. They needed the website to keep up: new service lines, timely announcements, and patient-facing pages that clinicians had signed off on.
They didn't need a one-off project. They needed a development team that was already there when something came up.
What we did
We joined as their ongoing development team in late 2025 and shipped a full site refresh. Navigation was rebuilt around how patients actually search, service-line pages go through clinician review, and forms route leads into the marketing team's system.
We built a library of reusable page blocks. Every new service page since has been assembled from them, so new pages ship faster and stay consistent.
When a Phoenix newspaper ran a story, Spectrum had a landing page live the same day. When an unrelated platform incident touched patient information, we escalated it to the practice manager and compliance lead and walked through it with them in person afterward.
Every sprint or two, we run a working session on something the staff want to handle themselves.
Inside a two-week sprint.
Planned work
The roadmap: new service pages built from the block library, navigation and content updates, landing pages, and podcast episodes. Prioritized together in the shared backlog, about 40 tickets in a typical sprint.
Held back for the urgent
A fifth of every sprint stays open for whatever lands mid-sprint: a press story that needs a page today, or an incident that needs a careful response. The roadmap doesn't stall when it happens.
Need a team that's already there?
The first call is free and takes about 30 minutes. We reply to every message within one business day.