CareCru

CareCru Website

Our buyers were dental groups, but the site spoke to single clinics. A darker, leaner website for DSOs, designed and built in Webflow without a developer.

Design and Webflow buildLaunched Mar 2024Live

The new CareCru website on desktop and mobile: dark purple, with the headline The Growth Platform for DSOs
OverviewThe new site on desktop and mobile.

The problem

A site for single clinics, sold to dental groups

CareCru's ideal customer is the DSO, a company that runs many dental clinics. The old website did not show that. It looked like every competitor: light, soft and made for one practice manager.

It was also hard to keep alive. An outside agency built it on WordPress and Elementor. It was slow, with a mobile PageSpeed score of 26, and every change needed a developer.

The real problem. Make the site speak to DSOs, and make it something our small team could own and change.

Two homepages side by side. Left: the old light site, The Last Practice Growth Platform You Will Ever Need. Right: the new dark site, The Premier Platform driving DSO Growth
Before and afterThe old light site for single practices, and the new dark site for DSOs.

The strategy

Dark on purpose

Our new Enterprise Management tool already had a dark mode. The sales deck, slides and brand book followed it. The website was the last piece.

Big competitors use soft, white branding to appeal to single practices. A dark look set us apart and signaled an enterprise product.

Fewer pages, one goal. With leadership, we cut the site down to what sells. Three clear offers: Scheduling, Intelligence and Pro, with a feature matrix on Pricing. Three steps to start: Connect, Analyze, Automate. Every page leads to Get Demo. Company, Contact and Resources came off until they had real content.

Constraints

No developer, and a site the team must own

No developer. I had to design and build it myself.

Easy to edit. Any designer or staff member should update content without code.

HubSpot. Demo forms had to feed the CRM and the sales team's alerts.

SEO. Marketing needed settings for each page.

Speed. The site had to load much faster, above all on phones.

Process

Sitemap first, then wireframes

I mapped every page in Lucid first, so we could agree on what to keep and what to cut. Then I drew wireframes in Figma, page by page, using the refreshed brand colors as the base.

Hero animation

From sketch to illustrative UI

The homepage had a few seconds to explain what CareCru does. A screenshot of the real product was too dense for that, so the hero tells a story instead.

It started as rough sketches: scan the schedule for opportunities, show them, fill the gaps with online booking, automate the patient journey, hit the monthly goal, then repeat the next day.

Each product then got its own storyboard: Scheduling, Pro and Intelligence. Same layout, a different story. The side tabs show which product is playing.

Before building anything in UI, I drew a rough animatic frame by frame in Sketchbook, to test the timing. Then I turned the sketches into simplified, illustrative UI, based on the real product but with only the parts that tell the story, and animated it as one loop for the homepage.

Colored storyboard in four frames for Scheduling: the schedule tab is selected, a booking request arrives, it is dragged into an open slot, and the patient leaves hearts
SchedulingA booking request fills an open slot.
Colored storyboard in four frames for Pro: the automation tab is selected, the patient journey steps light up one by one with a chat, and a five star review comes in
ProThe patient journey runs on its own and ends in a review.
Colored storyboard in four frames for Intelligence: the analytics tab is selected, the schedule is scanned, a green progress bar fills, and the header says Crushing it
IntelligenceThe scan fills the goal bar.
AnimaticDrawn frame by frame to test timing. Sped up 6×.
Final animationThe loop that shipped on the homepage.

Build

Why Webflow, learned on the job

I compared Framer and Webflow. I chose Webflow for its CMS, its HubSpot integration, per-page SEO and the plugin that brings Figma designs into Webflow.

I had never used Webflow before this project. I learned it while building, and built about 90% of the site myself, plus all the video animation.

Webflow covered each constraint: a visual editor instead of a developer, a CMS for the team, native forms connected to HubSpot, SEO fields on every page, and built-in image compression and code minification.

The launched CareCru homepage with the headline Meet DonnaAI, The Copilot for Dental Practice Growth, and Get a Demo and Watch Video buttons
LaunchThe homepage on launch day, March 2024.

Outcome

Faster, and more leads

Speed. Google PageSpeed on mobile, a month before and a month after launch. Performance went from 26 to 57. Accessibility from 79 to 93. Best practices from 78 to 100. SEO stayed high, from 100 to 97.

Leads. Every form sent from the site posts an alert in the sales team's Slack channel. In the 12 months after launch, the channel got about 13.8 leads a month. In the months before, about 9.4. That is around 40% more.

What this does not prove. The count does not control for sales activity, ads or the time of year. A few entries look like duplicates. The site was one part of a larger push, and a team result.

Two Google PageSpeed Insights mobile reports. March 3, 2024, old site: Performance 26, Accessibility 79, Best Practices 78, SEO 100. April 6, 2024, new site: Performance 57, Accessibility 93, Best Practices 100, SEO 97
PageSpeedMobile reports for the old site (Mar 3, 2024) and the new site (Apr 6, 2024).
Leads per monthForm alerts in the sales Slack channel, May 2023 to Feb 2025. The form was broken for about two weeks in Jan 2025.

What I learned

A brand choice is a product choice

The dark look was not decoration. It told DSOs who the product was for, before they read a word.

Owning the build mattered as much as the design. The team could change the site the same day, without waiting for an agency.

What I would do differently. Set up proper analytics before launch, so the result would not depend on counting Slack alerts.