Skip to content
Emmanuel NanadoumRésumé(PDF, opens in a new tab)

Blair Digital Studios

Not “I make websites.” I find where revenue leaks and design the system that closes it.

Built for
Blair Digital Studios (Emmanuel's consulting practice)
Engagement
Revenue systems for small practices
My role
Principal consultant, discovery through implementation
Source
blair-demo-canham.vercel.app
Canham Chiropractic owner experience: Your digital front door is only the beginning.
blair-demo-canham.vercel.app

Status at time of writing

Stamped from the live build, not from the plan.

Status of each component
ComponentStatus
Canham owner presentation + auditLive

Guided presentation built on public information only.

Missed-call recovery simulationDemo data

Animated demonstration. No message is sent.

Six live prospect demos and reference buildsLive

Built for five prospective chiropractic clients, plus a med spa template.

1Business problem

Small practices lose opportunities between systems: a search that finds thin information, a call nobody answers, a form nobody follows up, a happy patient never asked for a review.

Most vendors sell one piece (a website, a phone tool, a CRM) and leave the owner to connect them.

2Discovery

  1. 2.1A Digital Revenue Leak Audit built only from publicly observable information, stating that private systems were not accessed.
  2. 2.2Every finding is labeled as verified publicly, an opportunity to investigate, or a proposed solution. For example, missed calls are an operational opportunity that requires client confirmation, not an accusation.

3Requirements

Requirements
R-01An owned, fast, mobile-first website with clear calls to action.
R-02Lead capture from every channel into one CRM pipeline.
R-03AI voice or receptionist coverage, missed-call recovery and qualification.
R-04Booking, confirmations and reminders that protect the calendar.
R-05Approved SMS / email nurture, review requests and reactivation.
R-06Reporting the owner can read without a consultant in the room.

4Solution architecture

Eleven stages from search to reactivation. Each one explains what happens, why it matters and what Blair implements.

Connected growth system

  1. 01Local search
  2. 02Premium website
  3. 03Call / request
  4. 04Lead capture
  5. 05CRM
  6. 06Follow-up
  7. 07Appointment
  8. 08Reminders
  9. 09Visit
  10. 10Reputation
  11. 11Reactivation
Figure 4.1 — Connected growth system

5Demo / POC

The owner sees their own practice audited honestly, then watches a missed call become a recovered opportunity.

Canham Digital Revenue Leak Audit: Limited owned digital presence, labeled as an opportunity to investigate.
Figure 5.1 — Findings are labeled: verified, to investigate, or proposed.
Canham connected system: one journey from search to reactivation, stage by stage.
Figure 5.2 — What happens, why it matters, what Blair implements.
Canham missed-call recovery simulation with a phone mockup and a recovery sequence.
Figure 5.3 — Simulated end to end; no message is actually sent.

6Technologies

  • GoHighLevel
  • Twilio voice / SMS
  • AI voice workflows
  • REST APIs
  • Webhooks
  • Supabase
  • HubSpot / Salesforce familiarity
  • Modern web stack

7Integration points

Integration points
FromTo
Website + phoneCRM pipelineEvery channel feeds one system
Missed callApproved text-backStaff notified on reply
CalendarRemindersProtects the schedule
Completed visitReview requestTimed, never gated

8Tradeoffs

Design decisions and tradeoffs
Public-information auditInstead of: Guessing at internal problemsCredibility comes from not overstating. The owner confirms what the audit can't see.
Connected systemInstead of: Best-of-breed point toolsLeaks happen in the hand-offs, so one pipeline owns every hand-off.
Non-clinical AI scopeInstead of: An assistant that answers everythingThe concierge handles hours, location, FAQs and requests; clinical questions go to people.

9Implementation & handoff

  • Scope, message approval, configuration, testing, launch, staff training and post-launch tuning are owned end to end.
  • Documentation and a plain-language walkthrough so the practice runs the system without depending on its builder.

10What this demonstrates

  1. 1.Consultative discovery that finds the business problem before proposing technology.
  2. 2.Solution architecture across web, voice, CRM, SMS, APIs and webhooks.
  3. 3.Honest selling: labeling assumptions is part of the pitch, not a disclaimer.