PrescriberPoint replaced manual demo invitations with a self-serve HubSpot page

The Customer

PrescriberPoint is a healthcare technology company that runs a prescriber information platform for pharmaceutical companies. Its sales team sells into physicians’ offices and runs product demos for the office staff.

The company ran its sales and marketing on HubSpot, with its main website designed in Figma.

The Challenge

Getting a physician’s office to sign up for and attend a demo was a manual process. A sales rep booked the meeting and handled everything after it by hand.

PrescriberPoint wanted the office contact to do that part themselves. After booking, the contact should be able to see who was invited, add or remove coworkers, and have the calendar invites and follow-up emails go out on their own. The whole thing needed to run inside the platform the company already paid for, and it needed to look like the rest of its website.

The Solution

We designed the process before we designed a page. Two discovery sessions and a working session produced a solution design, documented as a process flow, which the client reviewed and approved before any build started.

Then we tested the parts of the platform the design depended on. Booking a meeting from a calendar link and confirming the invite reached the contact. Keeping the platform’s tracking code off the scheduling page, so a sales rep can book on a prospect’s behalf from their own browser. Building email CTAs from token data that add an existing event to the recipient’s calendar, styled as buttons. And storing the attendee list in HubDB so emails and workflows could read from it.

With those answers in hand, we wireframed the dynamic landing page and took it through revision with the client’s team. Their feedback shaped the details, including the sales rep’s photo next to their name, how the scheduler is highlighted, the table header and the placement of the invite toggle. We then produced two design options and built the one they chose, with the toggle matched to their brand guide. Global styles, header and footer were built from the client’s Figma files so the page matches the main website.

The page itself is personalized to the booked meeting. The office contact lands on a branded page headed “Invite your coworkers to a demo of PrescriberPoint”, reviews the attendee list, edits it, and saves. A confirmation notice appears and the page redirects to a thank-you page the client provided. Saved changes update the HubDB record, and workflows send the confirmation and follow-up emails with calendar invites titled “Demo of PrescriberPoint”. Sales reps add attendees through the same front end.

After the handoff sessions in June 2023, we ran a second phase to expand the sales process around the page, with working sessions and additional workflow builds. In September we designed, developed and demoed custom-coded workflow actions for the parts of the process that standard workflow steps could not do, and moved them to production.

What They Got

PrescriberPoint’s sales team sends a booking link. From there, the office contact manages its own attendee list on a page that carries PrescriberPoint’s branding and the rep’s name and photo. Confirmations, follow-ups and calendar invites go out from workflows, and the attendee data lands in the CRM where the rep already works.

The team can change the page copy, the email content and the workflow logic in the platform’s own editors, and the custom-coded actions cover the steps those editors cannot. The company runs this inside its CRM.

Wrapping Up

Our standard on a build like this is to prove each piece of the platform can do the job before a page is designed, and to put the client’s team in control of the result. PrescriberPoint approved the process, shaped the page, and took it into production.

Lynton now builds AI-native websites on open infrastructure; see our current work at /case-studies.