What happens when one website has to talk to two different people?
A client of ours teaches two audiences at once: expecting mothers who want a calm pregnancy, and women who want to become doulas. One brand, one site, two very different reasons to visit.
The usual fix is a hero that speaks to "everyone" and lands with no one. We designed it as a fork in the road instead:
1. Two doors in the hero. "I'm pregnant" and "I'm training to be a doula", side by side, equal weight. The visitor picks a path in one click, and the headline above them stays about the shared value.
2. One voice, two tones. The mothers' path is softer: fewer words, more room, gentle photos. The doula path is more structured: modules, certification, dates. Same fonts, same colors, different rhythm.
One proof section, split in two. Testimonials from mothers on the left, from doulas on the right. Each visitor sees people like them before the price.
Writing for everyone is writing for no one. Give each reader a door.
Have you ever designed a page for two audiences at once? How did you split it?
Denty — From Consultation to Signed Consent. Built with Base44.
For this #Base44Challenge, I wanted to showcase something beyond a landing page or a beautiful prototype.
A real product. Solving a real problem.
Meet Denty, an AI-powered dental platform designed to simplify clinical documentation and patient consent workflows.
Here's what makes it different.
Instead of manually preparing everything after a consultation, a dentist can upload a transcript and let AI extract the relevant patient information.
The clinician remains in control, reviewing and editing the extracted details before preparing documents.
From there, Denty supports treatment planning, consent form generation, clinical document management, secure signature requests, and downloadable signed PDFs.
It also supports multi-clinic operations, team management, and activity tracking.
Why Base44?
I wanted to move quickly without compromising the product experience.
Base44 helped with application development, data integration, and AI features. But building a usable product required much more than prompts: thoughtful UX, careful design, testing, debugging, and repeated improvements.
Why a 6-minute video instead of 30 seconds?
Because I wanted to demonstrate the product rather than simply show it.
30 seconds can introduce an idea. It cannot meaningfully demonstrate every step of a workflow like this.
In the full recording, you'll see Denty create structured information from a consultation, generate documents, send a signature request, and demonstrate the patient signing process.
This is a functional product, developed for a real-world use case, shared with my client's approval.