Skip to content
Emmanuel NanadoumRésumé(PDF, opens in a new tab)
Document details
Prepared forHiring teams in AI, SaaS and automation
Prepared byEmmanuel Nanadoum · rev. September 2026
Based inPhoenix, Arizona · Remote / Hybrid
RolesSolutions Engineer · Sales Engineer · AI Consultant

EmmanuelNanadoum

AI Consultant / Solutions EngineerSales Engineer · AI, CRM & Automation

Not: I make websites. Instead: I find where revenue and process break, and design the connected systems that fix them. 

Customer discovery → solution architecture → working demo → implementation.

1Summary of qualifications

Customer-facing technical and sales professional with 8+ years of consultative selling and 4+ years designing CRM, automation, web, and AI-enabled solutions. I lead discovery, translate business pain into technical requirements, build the demonstration, explain integrations and tradeoffs, and guide customers from evaluation through implementation.

Roles I am pursuing
Solutions Engineer · Sales Engineer · AI Consultant · Solutions Consultant · Technical Presales · Implementation Consultant
Where I add value
The space between the customer, the sales team and the build: discovery, demos, architecture and handoff.

2Method of engagement

Every exhibit in this document moved through the same seven phases. The order matters: nothing gets built before the problem is written down, and nothing is called done until someone else can run it.

  1. 2.1Discovery

    Find the real problem behind the request.

    Consultative questioning with owners and operators: where leads come from, where they stall, what the team already uses, what a win looks like.

  2. 2.2Requirements

    Turn pain into something buildable.

    Business goals mapped to functional requirements, integration needs, data ownership, and constraints, written down so everyone agrees on scope.

  3. 2.3Solution architecture

    Design the connected system, not a feature.

    Workflow diagrams and integration maps across CRM, voice, SMS, web, APIs and webhooks, with the tradeoffs named before anything is built.

  4. 2.4Demo / POC

    Show it working on the customer's own business.

    A live proof of concept built around the prospect's name, services and journey, so the conversation is about their system, not a slide.

  5. 2.5Technical validation

    Prove it holds up.

    Test calls, test forms, simulated pipeline runs, provider health checks and honest labels on anything that is sample data or not yet activated.

  6. 2.6Implementation

    Carry the design into production.

    Configuration, testing, launch, troubleshooting and post-launch tuning, coordinating technical and non-technical stakeholders.

  7. 2.7Enablement

    Hand it over so it keeps working.

    Training, documentation and clear ownership, so the practice or team runs the system without depending on the person who built it.

3Exhibits

Four engagements, each attached as a working build you can open. Status is stamped plainly: live, demo data, or not activated.

AVYBE

A ride that knows where it's going, who's in it, and what the car is in the mood for.

VYBE connects people × music × food × places × experiences around one shared ride context. The live site and VYBE Voice run on real APIs: ElevenLabs transcription and speech, Supabase for rides and saved VYBEs, and server-side functions that keep every provider key off the client.

  • Site + VYBE Voice live
  • Route generation not activated
VYBE Variation 5 home page: night-driving city skyline with the headline More Than a Ride. It's a VYBE.
  1. 01MicrophoneBrowser MediaRecorder captures the request
  2. 02/api/voice-sttElevenLabs Scribe transcription (Web Speech API fallback)
  3. 03/api/voice-liveTranscript + ride context + recent turns
  4. 04Product actionFood, music, stops, mood, group activity
  5. 05/api/voice-ttsElevenLabs speaks the response
Figure A.1 — VYBE Voice live path, as deployed. Provider keys stay server-side in Vercel Functions.

BCactus Chiropractic

From the first ring to a booked visit, on the practice's own brand.

A two-layer demo: a patient website in Cactus's own identity, and a revenue-system page where the owner can talk to a live AI receptionist, submit a test patient form, and walk every stage of a connected patient journey.

  • AI receptionist live
  • Website live
  • Dashboards use sample data
Cactus revenue system: One connected patient journey across 13 steps.
blair-demo-cactus.vercel.app/revenue-system

CPalmer & Herman Chiropractic

Reuse the system logic. Never reuse the client.

The same patient-acquisition logic as Cactus, rebuilt around a two-doctor practice in Connecticut: its own pipeline stages, tags, message copy and phone number, and its own rollout plan for what goes live now and what waits.

Cactus Chiropractic site, Peoria AZ.
Cactus · Peoria, AZ
Palmer & Herman Chiropractic site, Naugatuck CT.
Palmer & Herman · Naugatuck, CT

Same skeleton on purpose — both practices sell unhurried care. Everything a patient touches is the practice's own.

Table C.1 — What is reused, what is customized
Reused (system logic)Customized (the practice)
Capture → conversation → schedule → remind → reviewStage names and tags, e.g. ph-website-lead
Reminder cadence: 24 h and 2 hMessage copy in the practice's voice and number
Follow-up stop conditionsWhich modules are active at launch
Review rules: no incentives, no gatingReactivation run manually by staff
Pipeline patternAI voice receptionist held for later
  • Website and system live
  • Simulator uses demo contacts
  • AI voice not yet activated

DBlair Digital Studios

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

Blair Digital Studios is Emmanuel's consulting practice. Each engagement starts with an honest audit of how a practice is found, contacted and followed up with, then connects website, AI voice, CRM, booking, follow-up and reputation into one system.

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

What a Blair system connects

AI receptionist and voice · lead capture and qualification · CRM automation and pipeline design · appointment booking · missed-call recovery · SMS / email nurture · review automation · reporting · websites wired to revenue workflows through APIs and webhooks.

4Client solution lab

Six live demos built for prospective Blair Digital Studios clients from public information. Each has its own page a practice owner can open directly.

Open the client lab
Client builds
Cactus ChiropracticPeoria, ArizonaEvery new-patient call and form is answered, tracked and followed up, from first ring to a booked visit.
  • Website live
  • AI receptionist live (browser)
  • Dashboards use sample data
Revenue system Website Client page
Palmer & Herman ChiropracticNaugatuck, ConnecticutWebsite requests, missed calls and unbooked leads flow into one 12-stage pipeline with respectful, automatic follow-up.
  • Website live
  • Simulator uses demo contacts
  • AI voice not yet activated
Revenue system Website Client page
Canham ChiropracticPhoenix, ArizonaAn honest look at how patients find, contact and return to the practice, and one connected system from search to reactivation.
  • Website live
  • Owner presentation live
  • Missed-call demo is simulated
Revenue system Website Client page
Nelson ChiropracticTempe, ArizonaA clear, calm website that turns local searches into appointment requests and phone calls.
  • Website live
Open site Client page
Coyote Chiropractic & Wellness CenterTempe, ArizonaA considered, unhurried website for chiropractic, injury care, massage and wellness, with a clear path to book.
  • Website live
Open site Client page
Blair MedSpaReference buildAn editorial med spa experience designed to move visitors from treatment interest to a booked consultation.
  • Reference template live
  • Contact details are template placeholders
Open site Client page

5Schedule of capabilities

Pre-sales & discovery

  • Consultative discovery
  • Needs analysis
  • Solution mapping
  • Technical demos
  • POCs
  • Objection handling
  • Value articulation
  • Proposal support

Solution design

  • Workflow architecture
  • Integration maps
  • Implementation planning
  • Technical documentation
  • Stakeholder communication
  • Presentations

Technical foundations

  • REST APIs
  • Webhooks
  • SQL
  • Python
  • HTML / CSS / JavaScript
  • Supabase
  • AWS fundamentals
  • Troubleshooting

Platforms

  • GoHighLevel
  • HubSpot
  • Salesforce
  • Twilio voice / SMS
  • ElevenLabs
  • Vercel
  • Jira
  • Git / GitHub

Integration register

Only connections that exist in the live builds.

Integrations by build
BuildConnected to
VYBE VoiceElevenLabs Scribe · ElevenLabs TTS · Supabase · Vercel Functions
Cactus revenue systemAI voice receptionist (browser) · Test patient form · CRM pipeline · SMS + email
Palmer & Herman systemWeb form → CRM · Missed-call text-back · 12-stage pipeline · Review requests
Canham growth systemLocal search · Lead capture · Follow-up · Reputation workflow
  1. Principal Consultant — CRM, AI Automation & Technical Solutions

    Blair Digital Studios · Remote

    2020 – Present

    Lead customer discovery and requirements conversations, identify operational pain points, and map business goals to practical CRM, automation, web and AI-enabled solutions.

  2. Sales Representative

    A Better Way Wholesale Autos · Naugatuck, CT

    Sep 2017 – 2025

    Managed a high-volume, high-ticket pipeline from discovery through close, matching customer needs to vehicle and financing options.

  3. Customer Success Specialist

    Family First Life · Manchester, CT (Remote)

    Jan 2023 – Jan 2024

    Onboarded and educated 15–20 new customers a month, translating complex product options into clear, needs-based recommendations.

7Sign-off

If your team needs someone who can run discovery, build the demo and carry it into implementation, the next step is a conversation.

Emmanuel Nanadoum

Prepared by · Phoenix, Arizona

Accepted by · your team