Coastaldetox/blueprint

Coastal Detox — Operational Intelligence Blueprint Coastal Detox — Operational Intelligence Blueprint Confidential · Youtiva Blueprint 1 Business Overview 2 Pain Points Workflow 3 Current Workflow 4 Optimized Workflow Build 5 System Architecture 6 Execution Proof 7 Live Demo Investment 8 Investment Business Overview Coastal Detox — Operational Intelligence Command Center A 12-bed inpatient detox and residential treatment facility in Southern California. Cash-pay and out-of-network insurance. The business generates revenue across CallRail leads, Cipher Billing collections, and a growing repeat patient base — all tracked in separate, disconnected platforms. The data exists. The intelligence layer to connect it does not yet. Key Metrics 12 Licensed inpatient beds — detox and residential treatment ~75% Insurance-based patient mix — out-of-network policies ~33% Repeat patients — arriving outside CallRail entirely Business Profile Business Name Coastal Detox Business Type 12-bed inpatient detox / residential treatment facility Location Southern California Revenue Model Cash Pay Out-of-Network Insurance Patient Mix ~75% insurance-based · ~33% repeat patients (arrive via partner's direct line, outside CallRail) Core Systems CallRail Kipu EMR Cipher Billing Power BI QuickBooks Billing Partner Cipher Billing — takes 7% of collections. Manages claims, AR, payer negotiations, and denials. Reports back via a Power BI partner dashboard. Lead Coordinator Dedicated web lead coordinator (significant salary, recruited from American Addiction Centers). Performance currently untracked in any unified view. Current Reporting Cipher's Power BI partner dashboard (billing) + manually built static command center (no longer updates) Main Problem Data exists across all platforms but is completely disconnected. Every answer requires logging into multiple systems separately. Stage Diagnosis Operating and generating revenue — but zero unified visibility. Leadership clicks through 4–5 separate platforms to understand the state of the business. The North Star In Adrian's Own Words "I don't want to click through CallRail, QuickBooks, the bank, and the billing company. I want one dashboard where I can see everything." And: "If we could just copy their CRM and make it better — tag the calls that came in, the clients that admitted, connect them to the Cipher record. This client paid X amount." One phase. Both sources. One connected line from call to payment. Phase 1 — Cipher + CallRail + Connected Extract Cipher billing data via Power BI API and CallRail data via its public API. Normalize both. Connect them into one patient record per admitted patient. Surface everything in one owned admin portal with an AI assistant. Adrian stops logging into five separate platforms. He opens one portal instead. The Long Game — Business Asset Every data point collected increases analytical depth, predictive capability, and business valuation. Insurance companies use this exact intelligence to control what they pay and when. This system flips that advantage to Coastal Detox. When the time comes to scale or exit, this intelligence layer is what buyers acquire — not just the beds. Coastal Detox · Operational Intelligence Blueprint · Youtiva Pain Points → Pain Points The Data Exists. Nothing Is Connected. Coastal Detox has CallRail, Cipher Billing, Kipu, QuickBooks, and a static command center — all working, all separate. Every answer about the business requires logging into a different platform. The bottleneck is not operations. It is visibility. Core Bottlenecks Category The Problem Business Impact Disconnected Platforms Cipher Billing, CallRail, QuickBooks, and the bank all operate separately with no shared data layer between them. Every answer requires logging into multiple platforms manually. No single picture of the business exists. No Billing Ownership Cipher's Power BI dashboard is Cipher's product. Adrian has viewer access only — he can see the numbers but cannot extract, cross-reference, or own the raw data outside their interface. Cannot connect billing outcomes to lead sources, payer behavior, or admissions history without manual effort every time. No Connected Patient Record A call in CallRail and a billing record in Cipher are two completely separate entries with no system connecting them. Leadership cannot see the true value of each lead source, payer, or admitted patient. The full revenue journey does not exist as a single view. Lost Qualified Leads Qualified callers disappear after the first call, insurance verification, or follow-up. Partner tracks all prospects via personal phone and physical notebook. After 30–45 days, qualified prospects are forgotten — even those who may admit months later. Admissions are lost silently. Manual Follow-Up Partner manages all lead follow-up off her personal phone and a physical notebook. No system surfaces who needs a call, when, or why. One-third of patients are repeats — but new qualified leads that go cold are simply lost with no accountability layer. No Payer Intelligence Cigna, Anthem, Blue Shield — all pay different amounts at different speeds. Some take 120–360 days. Some may net a loss after billing costs. Coastal may accept policies that create cash flow problems or cost more to collect than they produce. The data to know this exists but is not actionable. Static Command Center A friend built a dashboard manually — the right idea, but requires manual data feeding and stopped being useful the moment the data went stale. No operational value. The system Adrian already knows he needs — it just needs to be live, automatic, and owned. No Lead Source Visibility Web lead coordinator performance tracked only by clicking through CallRail manually — not visible in any unified view. Cannot confirm ROI on a significant salary investment without manually building the picture from scratch each time. The Core Problem Two Sources, Zero Connection CallRail knows who called and what tag they got. Cipher knows who got billed and how much was collected. Neither knows about the other. Phase 1 is about extracting both, owning both, and connecting them into one patient record. That single connected line is the intelligence Adrian has been describing since the first call. The Payer Intelligence Opportunity Insurance companies use sophisticated data intelligence to control what they pay and when. Coastal currently lacks the visibility to push back. Once billing data is centralized and payer performance is ranked, Adrian can make intake decisions based on data — not guesswork. Some payers accepted today may be net-negative after collection time and billing fees. ← Overview Current Workflow → Current Workflow Five Platforms. Zero Connection. Coastal Detox runs an 8-step operational flow from inbound lead to revenue collection. Treatment delivery works. The bottleneck is everything around it — visibility into leads, admissions, billing, and payer performance requires manual navigation across disconnected systems every time. How the Business Runs Today — And Where It Breaks # Step How It Happens Today The Friction 01 Lead Comes In Calls and form submissions tracked in CallRail. Lead source, timestamp, and call recording captured automatically. Visible in CallRail — not connected to billing, admissions, or revenue outcomes anywhere. 02 Lead Qualified Partner reviews calls and applies tags — thumbs up (qualified), admitted, referred out. Some leads have notes. Many do not. Managed off partner's personal phone and notebook. No system tracks what happens after a tag is applied. 03 Insurance Reviewed Policy sent to Cipher for verification. Good or bad determination made. Team decides whether to pursue admission. Happens outside any unified pipeline. No record of which leads were verified, accepted, or turned away. 04 Follow-Up Managed Partner tracks warm leads — people who went quiet, need re-contact, or said "not yet." Managed by memory and physical notes. After 30–45 days, qualified leads are forgotten. People who may admit in 4–5 months fall through permanently. 05 Patient Admits Once admitted, patient enters Kipu EMR — full personal, medical, and insurance information recorded. Kipu contains sensitive PHI — deferred. Not a Phase 1 dependency. 06 Billing Submitted Cipher submits claims. Tracks payments, denials, AR aging, allowed amounts inside their Power BI partner dashboard. Cipher owns the dashboard and the data. Adrian has viewer access only — cannot connect this data to CallRail. 07 Revenue Reviewed Adrian logs into Cipher's Power BI portal to check paid, pending, denied, and processing amounts by month and by payer. Useful view — but entirely separate from CallRail. Cannot connect a billing record to the original call or lead source. 08 Business Health Checked Adrian manually logs into Cipher, CallRail, bank, and QuickBooks separately to form a picture of how the business is performing. No unified view. Every health check is a manual multi-platform exercise with no single source of truth. The repeat patient problem compounds the lead picture. Roughly one-third of patients are repeats — arriving directly through the partner's personal phone, entirely outside CallRail. Any lead-to-revenue analysis will be structurally incomplete without a manual entry path for direct and repeat admits — this is scoped into Phase 1. Current Tech Stack Tool Role Current Limitation CallRail Calls, form submissions, tags, lead source tracking, call recordings Not connected to billing or revenue. Tag hygiene depends entirely on partner consistency. Kipu EMR Patient records, admissions, clinical data, sensitive PHI Contains sensitive PHI — deferred to a future phase. Not a Phase 1 dependency. Cipher Billing Claims submission, collections, payer data, AR aging, denials Dashboard is Cipher's product on Power BI. Adrian has viewer access only — cannot extract raw data independently. Power BI Cipher's billing dashboard layer — Adrian logs in via credentials Cipher provided Viewer access confirmed. Export API is the Phase 1 extraction path. Dataset Build access is the upgrade path. QuickBooks Financial records, P&L, cash flow Deprioritized per Adrian's direction. Available for future phases. ← Pain Points Optimized Workflow → Optimized Workflow Every Platform Stays. One Connected Line From Call to Payment. No existing tools are replaced. No workflows are disrupted. What changes is the layer above them — a privately owned intelligence system that extracts Cipher billing data and CallRail lead data, connects them into one patient record, and surfaces everything in one portal with an AI assistant. All in Phase 1. The Connected Patient Record — Phase 1 Goal One Line Per Patient — Call to Payment Today, a CallRail lead and a Cipher billing record are two completely separate entries. Phase 1 connects them. Every admitted patient becomes one record: where the call came from, how they were tagged, whether they admitted, what was billed, what was paid, which payer, how long it took. "Connect them to the Cipher record. This client paid X amount." — That is exactly what Phase 1 delivers. CallRail Call → Qualified Tag → Insurance Reviewed → Admitted → Cipher Billing Record → Billed → Paid → Payer Performance How Every Layer Changes Layer What Changes Outcome Billing Visibility Cipher's data extracted automatically via Power BI API on a defined schedule. Stored in Coastal's own database. No more logging into Cipher's portal to check numbers. Billing data is owned, live, and cross-referenceable. Adrian opens his portal instead of Cipher's. Lead Pipeline CallRail data pulled via API. Lead tags, call notes, timestamps, and form submissions visible in one pipeline view. No manual clicking through CallRail. Full lead pipeline in one place. Partner has a working tool. Lead source performance tracked automatically. Connected Record CallRail lead matched to Cipher billing record per patient. One connected record: call source → tag → admission → billing → payment outcome. True value of every lead source, payer, and admitted patient visible in one view for the first time. Payer Intelligence Payer data — billed, paid, pending, denied, AR aging, average allowed, average paid, payment speed — centralized and ranked. Connected back to which lead sources and call types each payer comes from. Adrian knows which insurers pay the most, fastest. Intake decisions become data-driven, not instinct-based. Follow-Up Gaps System flags qualified leads with no activity for 30+ days. Surfaces who needs a call, when, and why. Includes a manual entry path for repeat and direct admits that bypass CallRail. No more forgotten qualified leads. People who may admit months later stay in the pipeline consistently. Lead Coordinator ROI Web coordinator performance tracked automatically — leads generated, qualification rate, admission rate, and revenue tied back to web-sourced patients via the connected record. Adrian can confirm or challenge coordinator ROI with actual connected data, not impression. AI Assistant Natural language assistant trained on the full connected dataset — billing + leads + matched patient records. Answers questions across both data sources simultaneously. "Which payer paid most this quarter?" "Which leads haven't been followed up?" "Which lead source generates the most revenue?" — answered instantly. ← Current Workflow System Architecture → System Architecture One Intelligence Layer — Two Sources. One Record. One Portal. A single admin portal built on a dual-source data pipeline. Cipher Billing via Power BI. CallRail via its public API. A patient matching engine connecting both into one record. An AI assistant on top that answers questions across the full connected dataset. All of this — Phase 1. Admin Portal — Phase 1 Views One Owned Interface — Everything in One Place Adrian and his partner open one portal. Billing intelligence, lead pipeline, follow-up tasks, payer performance, and the connected patient record — all in one view that Coastal owns and controls. No vendor can limit it, restrict it, or take a percentage of it. Billing Intelligence Cipher / Power BI Monthly billed, paid, pending, denied AR aging view by payer Payer performance ranking — collection rate, average paid, payment speed Month-over-month comparison Lead & Admissions Intelligence CallRail API Full lead pipeline — calls, forms, tags, status Admissions tracker — qualified, admitted, referred out, ghosted Follow-up task board — leads needing action by priority Lead source performance — web coordinator attribution Manual entry for repeat and direct admits Connected Intelligence Matched Records Connected patient record — call to payment in one line Lead-to-revenue view — true value per lead source Payer profitability connected to call origin AI assistant across full connected dataset Data Pipeline Architecture Source 1 — Cipher Billing via Power BI Export API Adrian has login credentials to Cipher's Power BI partner dashboard. The Power BI REST API Export endpoint allows programmatic extraction of exactly what Adrian already sees — using his credentials, on a defined schedule, with zero dependency on Cipher's cooperation. Data is parsed, normalized, and stored in Coastal's own database. Upgrade path: if Cipher grants dataset-level Build access, raw DAX queries unlock more granular extraction — worth requesting, but not a Phase 1 gate. Source 2 — CallRail Public API CallRail has a confirmed public API. Endpoints cover calls, form submissions, tags, lead source attribution, call recordings, timestamps, and notes. Adrian's account gives direct access — no third-party dependency, no negotiation required. Data normalizes into the same database as Cipher, ready to be matched. Matching Engine — One Record Per Patient Match CallRail leads to Cipher billing records using shared identifiers — phone number, name, and admission date. Confidence-scored matching: high / medium / low certainty. Manual reconciliation queue for ambiguous records. Important: CallRail callers are often a family member, not the patient — match rates are directional, not exact. Source-level revenue attribution is a powerful business signal, not a pixel-perfect science. The reconciliation queue keeps data quality honest. AI Assistant — Trained on the Full Connected Dataset The AI assistant reads from Coastal's owned, normalized, connected data layer — not from Cipher's dashboard or CallRail directly. Phase 1: billing intelligence + lead intelligence + connected patient records. Natural language questions answered in real time. Every data point added makes it more intelligent. Every question asked teaches it what Adrian needs to know. ← Optimized Workflow Execution → Execution Phase 1 in 3–3.5 Months — Cipher. CallRail. Connected. Live. Phase 1 is sequenced across 7 stages — each building on the last, no stage starts until the previous one is confirmed. The goal is not speed at the cost of accuracy. It is a trusted, validated system that Adrian opens every day instead of logging into five separate platforms. The Build Principle Data Trust Before Data Volume Phase 1 succeeds when Adrian opens the portal and trusts what he sees. That means every billing figure validated against Cipher, every lead count validated against CallRail, and every matched patient record spot-checked against known admits. Trust is the deliverable — not just the interface. Build Timeline Stage 1 1–2 Weeks Discovery + Data Access + Matching Logic Confirm Power BI Export API access using Adrian's credentials. Confirm CallRail API access and available endpoints. Test extraction from both sources. Map all data points available from Cipher — billed, paid, pending, denied, AR, payer details, average allowed, average paid. Map all data points from CallRail — calls, tags, forms, lead sources, recordings, timestamps, notes. Define shared identifiers for patient matching — phone number, name, admission date. Design confidence-scoring logic and manual reconciliation queue. Define all KPIs and dashboard views. Set refresh schedule for both pipelines. Output: confirmed dual-source extraction path, matching logic defined, full dashboard specification — no ambiguity before Stage 2 begins. Stage 2 2–3 Weeks Cipher Data Pipeline — Extract, Normalize, Store Automated Power BI data extraction built on the confirmed path from Stage 1. Data parsing and normalization — billing records structured into clean, queryable format. Stored in Coastal's own database. Refresh logic running on defined schedule. Initial validation: extracted figures compared against Cipher's dashboard. At the end of Stage 2: Coastal owns a live, auto-refreshing billing data pipeline. The data Cipher has been holding is now also Coastal's. Stage 3 2–3 Weeks CallRail Data Pipeline — Extract, Normalize, Store Automated CallRail API data extraction on schedule. Data parsing and normalization — calls, tags, forms, lead sources structured into clean format. Stored in the same database as Cipher data, structured to be matched. Lead status logic applied: qualified, admitted, referred out, ghosted, pending follow-up. At the end of Stage 3: Coastal owns a live CallRail lead pipeline. Both data sources are now in one database, ready to be connected. Stage 4 2–3 Weeks Admin Portal — Billing + Lead Dashboards Billing dashboard: monthly billed, paid, pending, denied. AR aging view by payer. Payer performance ranking. Lead pipeline view: all inbound leads with tags, status, and timestamps. Admissions tracker. Follow-up task board: qualified leads with no recent activity surfaced automatically. Manual entry path for repeat and direct admits. At the end of Stage 4: Adrian can see billing intelligence and lead intelligence in one owned portal without logging into Cipher or CallRail. Stage 5 2–3 Weeks Patient Matching Engine — One Connected Record Matching engine connecting CallRail leads to Cipher billing records using phone number, name, and admission date as shared identifiers. Confidence scoring: high / medium / low match certainty per record. Manual reconciliation queue for ambiguous records surfaced in the admin portal. Connected patient record view: full journey from call to payment in one line. Lead-to-revenue view: which lead sources and call types produce the most revenue per admitted patient. At the end of Stage 5: the friend's command center becomes real — one connected record per patient, call to payment. Stage 6 1–2 Weeks AI Assistant — Full Connected Dataset AI assistant built on top of the full connected database — billing + lead + matched patient records. Connected to the live, auto-refreshing data layer — answers are always current. Natural language question-answering across both data sources simultaneously: payer performance, AR status, lead follow-up gaps, lead source revenue attribution, monthly collections. At the end of Stage 6: Adrian asks questions in plain English and gets answers from data he owns. Stage 7 1 Week Validation, Training + Launch Full validation of all billing figures against Cipher's dashboard. Full validation of all lead data against CallRail. Patient match accuracy spot-checked against known admitted patients. Adrian and partner trained on the portal. System goes live. Future phase priorities identified based on real usage — Kipu integration, automated follow-up reminders, QuickBooks connection, cash flow forecasting. Phase 1 Total 3 Months What Exists at the End of Phase 1 Delivered Cipher billing pipeline Live, auto-refreshing — Coastal owns the billing data CallRail lead pipeline Live, auto-refreshing — Coastal owns the lead data Connected patient record Call to payment in one line per admitted patient Billing dashboard Billed, paid, pending, denied, AR aging, payer ranking Lead pipeline + follow-up board Qualified leads surfaced, follow-up gaps flagged automatically Payer performance view Ranked by collection rate, average paid, and payment speed Admin portal One owned interface — no vendor dependency AI assistant Natural language questions across billing + lead + connected data Validated numbers Every figure confirmed against source systems before launch What the System Replaces Logging into Cipher's dashboard Replaced — Adrian's own portal Clicking through CallRail Replaced — unified lead pipeline view Static command center Replaced — live, auto-refreshing system Partner's phone and notebook Replaced — follow-up task board Payer guesswork Replaced — ranked payer performance data Multi-platform health checks Replaced — one portal, one view Two disconnected data sources Replaced — one connected patient record Billing data owned by vendor Replaced — Coastal owns its own data What Comes Next Future phases are scoped after Phase 1 based on real usage and business priorities. Every future phase plugs into the same foundation — no rebuilding, no starting over. Kipu Integration Clinical admission data connected to the revenue journey. Kipu records matched to the existing CallRail-Cipher connected record — adding the clinical layer to the full patient picture. Automated Follow-Up System triggers outreach reminders to warm leads automatically. Denial intelligence — patterns in denied claims surface and route to the team. Staff accountability reports on follow-up performance. Cash Flow Intelligence Payer profitability scoring, cash flow forecasting from AR aging and payer payment patterns, QuickBooks integration for full P&L visibility. The complete financial intelligence layer built on Phase 1 data. The Foundation Principle First, own the data. Then, see everything. Then, act on it. The friend's command center was the right idea. Phase 1 is what it actually becomes — live, owned, connected, and compounding in value with every data point collected. ← System Architecture Live Demo → Live Demo The Command Center — Live & Interactive. Walk through a working version of the Coastal Detox Command Center. Built in Coastal's brand. Billing intelligence, lead pipeline, payer performance, follow-up board, connected records, AI assistant, and alerts — fully interactive. Access the Demo Coastal Detox Command Center Live interactive demo of the full Phase 1 system. Built in Coastal's brand. Every tab, every chart, every AI conversation — fully clickable. Open Live Demo → client-demo.youtiva.com/demo/Coastaldetox/admin/demo How to experience the demo Open the demo in a new tab. Start at the Command Center — that's the executive overview. Then walk through Billing Intelligence (Cipher data), Payer Performance (which insurance is worth it), Lead Pipeline (CallRail data), Follow-Up Board (qualified leads needing contact), Connected Records (the call-to-payment journey), and the AI Assistant. Try asking the AI a question — it's connected to the same data shown on every other tab. What's in the Demo Billing Intelligence Live KPIs from Cipher — collected, pending AR, denied, payer breakdowns. AR aging by payer with escalation indicators. Payer Performance Ranked table of every insurer by collection rate, average paid, and payment speed. Verdict per payer — Top Payer to Avoid. Lead Pipeline & Follow-Ups CallRail leads in one view. Follow-up board surfaces qualified leads with no contact in 30+ days — replacing the notebook. Connected Records CallRail lead matched to Cipher billing record. One connected line per patient — call source to final payment. AI Assistant Ask any question in plain English. Connected to billing + lead data. Try suggested questions or type your own. Alerts Critical, Monitor, and Good News alerts auto-generated from billing and lead data. The system tells Adrian what needs attention. ← Execution Investment → Investment Two Ways To Own the Intelligence Both paths build the same system — privately owned, fully documented, built to grow. Phase 1 delivers Cipher + CallRail + connected patient records in one owned portal with an AI assistant. Nothing is pre-fixed beyond Phase 1. How We Work Together The Same for Both Investment Structures Phase 1 is scoped, built across 7 sequential stages, and delivered in 3–3.5 months. Future phases are defined together based on what the business needs next. Nothing is pre-fixed beyond Phase 1. The system grows with Coastal Detox — not ahead of it. All infrastructure, data, and workflows are owned exclusively by Coastal Detox from day one. Phase 1 Delivery 3–3.5 Months Cipher + CallRail + connected record + AI assistant — built in 7 sequential stages with a validated, trusted system at the end. Data Sources 2 Connected Cipher Billing via Power BI and CallRail via public API — extracted, normalized, and matched into one patient record. Ownership 100% Yours All infrastructure, pipelines, matched records, and the portal belong exclusively to Coastal Detox from day one. Choose Your Path Lease to Own $2,000 / month Fixed monthly investment — own the system as you build it Fixed monthly — predictable investment throughout the build Ownership transfers as each stage is completed and delivered Long-term partnership — continues as the platform expands into future phases Option to convert to full buyout at any point Buy Outright $18,000 / phase Full phase investment — owned outright on delivery One-time payment per phase — no ongoing fees for completed work Phase 1 fully owned on delivery — Cipher, CallRail, connected record, AI assistant Continue into future phases as the business scales Full ownership from day one — per phase delivered What Both Paths Include Same Build. Same Quality. Same Ownership. Long-Term Partnership. Regardless of which path is chosen, the infrastructure built is identical — privately owned, fully documented, built to the same standard. This is not a project with an end date. It is a long-term partnership that grows as Coastal Detox grows. The first time Adrian opens his own portal, sees Cipher billing data and CallRail lead data in one view, and asks the AI which payer paid the most last quarter — that is the moment Phase 1 proves its value. The goal is to get there in Month 3, then build from there. Infrastructure 100% Owned Privately built — not a SaaS subscription. Coastal Detox owns everything built, from day one. Data Ownership Full Control All billing data, lead data, matched patient records, and connected intelligence belong exclusively to Coastal Detox. Ongoing Support Included Refinements, updates, and support included throughout the engagement in both paths. ← Live Demo Coastal Detox · Operational Intelligence Blueprint · Youtiva · Confidential