Greyfinch
Implementation PlaybookDSO · Group Practice

Greyfinch

Step-by-step implementation guide — pre-implementation checklist, onboarding, staff training, go-live runbook, and ROI tracking.

Greyfinch — Implementation Playbook (DSO)

Executive Summary

Greyfinch is a cloud-based practice management platform designed to unify clinical workflows, patient data, and financial operations across multi-location dental organizations. It provides centralized scheduling, treatment planning, patient communication, and analytics—eliminating data silos common in acquired or merged practices.

DSOs benefit uniquely from Greyfinch because they inherit fragmented systems when acquiring independent practices. Greyfinch consolidates these into a single source of truth, enabling standardized clinical protocols, real-time visibility into network performance, and automated compliance reporting across locations. This accelerates integration timelines from 12-18 months to 4-6 months and unlocks immediate operational synergies.

Expected Timeline: Full deployment across a 5-10 location DSO: 16 weeks (pilot + scaled rollout). Practices begin capturing ROI within 30 days; full financial impact (staffing optimization, patient acquisition leverage) visible by week 12.


Pre-Implementation Checklist (Weeks 1-2)

Technical Requirements

  • Infrastructure audit: Document all legacy systems at each location (Dentrix, Eaglesoft, Open Dental, spreadsheets). Identify data export capabilities and API compatibility.
  • Network readiness: Confirm bandwidth ≥10 Mbps at all locations; test Greyfinch's cloud infrastructure compatibility. Deploy WiFi 6 in clinical areas if signal is unstable.
  • Hardware refresh: Minimum 4GB RAM workstations; tablets for treatment planning (iPad 6th gen or later). Budget $2,500–$4,000 per location.
  • SSO integration: Confirm Active Directory or Azure AD availability for centralized user management. This prevents duplicate logins and reduces IT friction.
  • Data migration staging: Allocate secure SFTP server or AWS S3 bucket for exporting patient records, treatment histories, and financial data.

Stakeholder Alignment

  • Clinical leadership buy-in: Hold 1:1 calls with clinical directors at each pilot location. Address specific fears (workflow disruption, patient data security). Share 2-3 peer case studies from similar DSOs.
  • Front desk + admin alignment: Schedule group calls with office managers and scheduling coordinators. Emphasize: Greyfinch reduces manual double-entry, speeds new patient onboarding, and surfaces appointment gaps they previously missed.
  • Finance/compliance: Ensure CFO, practice managers, and compliance officers understand audit trails, fee schedules synchronization, and insurance claim tracking. Highlight HIPAA alignment and automated compliance reporting.
  • Executive steering committee: Establish bi-weekly 30-min check-ins with DSO CEO/COO, CIO, and pilot location leaders. Set clear decision-making authority (who approves deviations, workarounds, go/no-go decisions).

Baseline Metrics to Capture

Document these before Greyfinch goes live; you'll compare against them at 30/60/90 days:

Metric How to Measure Why It Matters
New Patient Acquisition Cost (Marketing spend) / (new patients acquired) Greyfinch's centralized marketing automation typically reduces CAC by 15–25%
Scheduling Efficiency Average chair idle time; operatory utilization % Greyfinch's rule-based scheduling fills gaps automatically
Treatment Plan Acceptance # treatment plans presented / # accepted Digital treatment planning + patient portals increase acceptance 10–20%
Days Sales Outstanding (DSO) (Accounts receivable) / (daily revenue) Unified billing + patient communication reduces DSO by 5–8 days
Staff Administrative Burden Hours/week spent in manual data entry, inter-practice calls Expected 8–12 hour/week reduction per location
Insurance Claim Denial Rate # denied claims / # submitted Automated pre-authorization & claim validation drops denials 3–5%

Pilot Wave (Weeks 3-6)

Location Selection Criteria

  • Primary criteria: Choose 1–2 practices (ideally, 2 different DSO acquisition "generations"—one older, one newer). Avoid your flagship location.
  • Team readiness: Select sites with engaged office managers (2+ years tenure) and clinical leaders open to change. Avoid high-turnover locations.
  • Data cleanliness: Prioritize practices with <10% unmigrated/legacy patient records. Practices with 40%+ spreadsheet-based schedules will require 2x manual data remediation.
  • Size: Aim for 8–15 operatory locations. Large enough to see operational ROI; small enough to troubleshoot edge cases.
  • Diversity: If possible, choose locations with different specialties (general + ortho, or general + perio) to stress-test multi-specialty workflows.

Configuration and Setup

  1. Pre-go-live configuration (Week 3):

    • Map fee schedules, insurance panels, and referral networks from legacy system into Greyfinch. Validate PPO tier discounts match across all carriers.
    • Configure clinical templates: standard treatment plans, clinical protocols, and requisition routing.
    • Set user roles and permissions: ensure dental assistants cannot modify billing; hygienists cannot override clinical notes.
    • Build custom reports: monthly revenue by provider, treatment plan conversion by tooth #, DSO-wide abandonment analysis.
  2. Data migration (Week 3–4):

    • Export patient demographics, clinical history (last 24 months), and active treatment plans from legacy system.
    • Validate data integrity: patient counts pre/post, insurance verification completeness, clinical notes parsing.
    • Load into Greyfinch staging environment. Run parallel data validation queries.
    • Establish cutoff date: e.g., "Everything through March 31st" in legacy system; Greyfinch goes live April 1st with clean slate for new activity.
  3. System go-live (Week 4):

    • Execute cutover on a Tuesday or Wednesday—avoids weekend handoff, allows quick escalation response.
    • Run 24-hour "shadow mode": staff work in both systems simultaneously, identifying discrepancies.
    • Disable legacy system write access by end of Day 1.

Training Approach

  • Role-based cohorts (not all-hands):

    • Doctors + Hygienists (4h): Clinical workflows, treatment planning, patient engagement features. Hands-on practice with 3 dummy patients.
    • Front desk (6h): New patient intake, scheduling rules, insurance verification workflow, patient communication (SMS/email).
    • Office manager (8h): Dashboard configuration, staff performance reports, financial reconciliation, compliance audits.
    • Specialists (6h, if applicable): Referral intake, case acceptance workflows, periapical imaging integration.
  • Delivery format:

    • Live instructor-led sessions (Week 3): Greyfinch success manager + DSO practice manager co-teach at pilot location.
    • Recorded modules (asynchronous): Available for staff who miss live sessions; also used for onboarding new hires.
    • Job aids & checklists: Laminated "First 5 Scheduling Steps" cards at front desk; clinical flowcharts in operatories.
    • Shadow shifts: Super-users (identified during training) remain on-site for first 3 days post-go-live to answer ad-hoc questions.

Scaled Rollout (Weeks 7-16)

Wave Planning

  • Wave 2 (Weeks 7–10): 2–3 mid-size locations. Apply learnings from pilot. Reduce go-live duration from 3 days to 1 day.
  • Wave 3 (Weeks 11–14): 3–4 locations. Parallel deployment: migrate data while Wave 2 stabilizes. Reduce training from 4–8h to 2–4h (staff watch recorded modules + 2h live Q&A).
  • Wave 4 (Weeks 15–16): Remaining locations. Fully templated. Training is mostly self-service with 1h office manager sync.

Change Management

  • Resistance flags: Watch for staff reverting to legacy system shortcuts (handwritten notes, scheduling via spreadsheet). Address immediately in 1:1 conversations.
  • Quick wins communication: Share tangible wins weekly

AI-generated implementation guide based on public vendor information. Verify specifics directly with Greyfinch.