Dermsquared

Dermsquared runs conferences and education for dermatology professionals. We moved it off a conference app it rented every year and onto an app and platform it owns, which members use all year.

Client
Dermsquared
Sector
Medical education
Work
App, platform, data and AI
Timeline
Ongoing partnership
The Dermsquared app's agenda on two phones, the Dermsquared wordmark, and the app in use at the Fall Clinical conference

Where Dermsquared started

Dermsquared's meetings ran on an app it rented for each conference. Attendees downloaded it and used it during the meeting, and when the conference ended, so did the app. The next meeting started over, and members had nowhere to go in between.

Behind the app sat an aging content system and an older technology stack, with the work spread across several teams. Keeping members connected all year meant moving the app and the platform under it forward together.

80%
fewer support tickets.
3 months
from concept to production.
2,400+
engaged attendees per conference.

What we built

The meeting app came first, because it had a date. Everything after it runs on the same code, and all of it belongs to Dermsquared.

  • The meeting in one app. Agenda, faculty, maps, the next session and notifications, with polls, speaker ratings, posters and networking.
  • Credit where they learn. Attendees sign in once, evaluate sessions and claim CME credit inside the app.
  • Learning between meetings. Courses and sessions on the web and in the app, so members come back between meetings.
  • A platform that can change. A new API behind the web and the app, so the content can move without the app standing still.
Claiming CME credit in the app: a session evaluation question with five answers
A session in the app, with its time, room, assessment, sponsor note and speakers

How we worked

Our team worked inside Dermsquared's, with design a step ahead of engineering and a demo every week. The first release went to real attendees at the August meeting, with the old vendor app kept as a fallback, and a fuller one followed for Fall Clinical in October.

We still meet Dermsquared's leadership every week to plan what to build next.

Behind the screen

The app was the visible part. The same team moved Dermsquared's content system from Strapi to Storyblok, rebuilding the paths that mattered and letting expiring content age out, so the move never hung on one risky switch. The work reached into infrastructure, analytics and security too.

122
live activities on the new CMS by the August 2026 review.
6
database upgrades, none with an outage.
550+
registered test cases.
They didn’t just build what we asked for. They understood what we were trying to accomplish and helped us get there.
Andrew DouglasCDTO, Dermsquared
Dermsquared's learning site on a laptop and a phone, with a video session and the lessons beside it

More from this partnership

The app is one piece of the work. Each of these has its own short write-up:

We'd love to chat.

Bring what's slow, rented or stuck. You'll leave with what we'd build first and how long it takes.

Book a call