Skip to content
View packages

CRM KitsAudiology and hearing care

Every trial followed. Every follow-up kept.

A trial countdown board where each device trial is a thin bar cut into its recorded length in days, filled to today, ticked at every follow-up appointment and counted down to the day the patient decides. Tone keeps the front desk work in one connected workspace and leaves hearing test results in the practice’s own system.

Desk in the GoSeedly Audiology & Hearing Kit with fictional sample records

The countdown board, soonest deadline first.

One row per recorded trial. The bar is cut into the recorded trial length in days and filled to today, with a tick at every follow-up day: a filled square for kept, a hollow circle for booked, a filled diamond for missed. The days remaining sit beside it as a tabular number, and a narrow column lists the supply reorders due inside the recorded window.

Actual interface captures with fictional sample data. Open a screenshot to see it full size.

What’s in the kit

Screens

  • Desk operating view with the trial countdown board and the supply reorder column
  • Patients operating view
  • Trials operating view with contact attempts and decisions
  • Fitting follow-ups operating view
  • Annual check recall operating view grouped by month
  • Supplies and warranty operating view
  • Insights operating view
  • Server-enforced hearing and clinical guard on every text field
  • Recorded reorder window and coverage notice behind one revision guard
  • Three native form drafts and three editable document templates
  • Editable front desk checklists and preserved row history

four pipelines

  • Patient relationships · 7 stages
  • Device trials · 8 stages
  • Recall and follow-up calls · 7 stages
  • Supplies and coverage · 7 stages

Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.

nine workflow drafts

  • Consultation enquiry task
  • Fitting booked note
  • Trial started note
  • Trial follow-up due task
  • Missed follow-up call task
  • Trial ending in seven days task
  • Annual check recall due task
  • Supply reorder reminder task
  • Coverage ending task

Inactive until you review and publish them. None send customer messages.

Forms and documents

  • Consultation request
  • Supply reorder request
  • Visit feedback
  • Trial follow-up call sheet
  • Trial period summary slip
  • Annual check recall call sheet

Editable native forms and document templates. Forms collect information for staff review.

Sample workspace

Explore 18 fictional patients with 9 trials on the countdown board across all four decision states, 3 of them ending inside seven days and 2 carrying a missed follow-up, 8 follow-up appointments booked and due inside the next seven days, 14 annual check recall months with 3 past due, 7 supply reminders of which 4 fall inside the recorded 30-day reorder window, and 5 coverage rows of which 2 end inside the recorded 90-day notice. Sample edits stay in memory and reset on navigation or reload.

No sample customers are added to your CRM.

Setup and source

  • Guided setup and compatibility report
  • Private rollback receipt
  • AI-agent guide for customized installations
  • Original editable source, configuration, and tests
Read the installation guide

Please read

A front-desk workspace, not a medical record.

  • This kit is not a HIPAA compliance product and does not make a practice HIPAA compliant. It is not an EHR, EMR or practice management system.
  • It is built for relationship work: recalls, reminders due, follow-up, intake progress and front-desk tasks. Clinical notes, diagnoses, prescriptions, test results, insurance details and other protected health information belong in your clinical system, not here.
  • You install the kit on your own Seedly CRM. DevLaunch does not host, receive or process your patient data. Your practice decides what it records in its CRM and is responsible for its own privacy, security and regulatory obligations, including any agreements with its hosting and software providers.
  1. Check your Seedly

    Extract the kit and run the guided setup. It checks your installation and flags customized files before it changes anything.

  2. Connect the helper

    Deploy the included helper from your backend source, then build your web app and choose any starter pipelines and drafts.

  3. Make it yours

    Set office name, descriptor and default pipeline name. Then sign in and check the workflows and permissions your team uses.

Technical details and compatibility

Seedly CRM 5.8.4 · extension API 1. Node.js 20 or newer. The installer checks supported integration-file versions and does not deploy your web app or backend. The included original backend helpers are required for connected record creation, edits, the two recorded desk values and resource setup. They preserve native account permissions, unrelated custom fields and row history, check revisions before saving, and run the hearing and clinical guard before anything is written. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.

One contact-linked record is one patient relationship. It holds the patient label, an age band label, a companion or family contact label, the preferred contact window, the annual check recall type, month, state, attempts and last contact date, device trials with their product label, inventory identifier, start date, length in days, follow-up appointment days and states, decision and decision date, recorded reference amount and contact attempts, retail supply reminders, recorded warranty and loss and damage end dates, and an editable front desk checklist.

This is a front desk and trial record, not a medical record. It is not a HIPAA compliance product, it is not an EHR, EMR or practice management system, and installing it does not make a practice HIPAA compliant. Do not use it to store protected health information. It never stores hearing test results, audiograms, thresholds or decibel values, word recognition percentages, degree or type of hearing loss, ear side, tinnitus or other conditions, device programming settings, medications, medical history, insurance member or policy numbers, benefit amounts, government identifiers or dates of birth. Visit and recall types are category labels only, and a product label is the office’s own plain label rather than a device specification. The shared model refuses free text that reads like one of those in every field, on the server as well as in the browser, and names the rule it matched; ordinary front desk text such as "left a message", "right away", "Trial ends 10/31" and "As discussed, call Friday" is accepted. Treat that as a guard against accidental entry rather than a guarantee. Clinical records stay in the practice’s own system, and the kit gives no medical or hearing advice. The practice is responsible for its own compliance and for whatever it chooses to record in its CRM. There is no practice management integration, no manufacturer fitting-software integration, no clinical or device record, no insurance or benefits processing, no device ordering or repair tracking, no scheduling engine, no automated reminders or patient messaging, no patient portal, no payments or financing and no revenue forecast.

Four optional pipeline templates and nine inactive workflow drafts. 18 fictional in-memory patient relationships.

Calling, messaging, signing, payments, and external integrations depend on your Seedly installation, account permissions, plan, and configured providers. Screenshots use sample data and reference imagery. Hosting, installation, and ongoing maintenance are your responsibility.

Get the Audiology & Hearing Kit

Checking access…

DevLaunch All Access

Every kit and every template.

See DevLaunch All Access

Already a member? Open your downloads.

Questions

Is this kit HIPAA compliant?

No, and it does not claim to be. It is not a HIPAA compliance product, an EHR or a practice management system, and installing it does not make a practice compliant. It is a front-desk and relationship workspace for recalls, reminders, follow-up and intake progress. Keep clinical notes, diagnoses, prescriptions, test results, insurance details and other protected health information in your clinical system. The kit runs on your own Seedly CRM; DevLaunch does not host, receive or process your patient data, and your practice remains responsible for its own privacy, security and regulatory obligations.

How do I receive the kit?

Purchase securely through Whop. Your original source ZIP and installation documentation are delivered manually to the email used at checkout. This is a one-time purchase of this kit; Seedly software, hosting, and installation services are separate.

Does this include Seedly CRM?

You obtain and configure Seedly separately. The kit adds original frontend screens, a shared theme, starter definitions, and integration instructions. It does not include Seedly’s codebase, license, hosting, or a separate CRM database.

Is this one connected workspace?

Tone keeps its ink-teal masthead and pill tab strip across the kit views and native CRM tools in the same signed-in account. Contacts, Calendar, Estimates, Documents, and other full modules retain the functionality supplied by your own Seedly installation. Existing authored content and provider screens retain their own layouts.

Can I use it with existing customizations?

Yes, with a compatibility review. The installer checks the supported integration files. Changed integration files need a reviewed merge; the included AI-agent guide explains how to preserve custom extensions, permissions, providers, and routes.

Do I have to import all the starter content?

No. Choose individual pipelines and workflow drafts, use a compatible existing pipeline, or install none. Workflows remain inactive until reviewed and published. They use native triggers, internal tasks, optional notes, and timed waits. A wait does not verify task completion or recheck the current stage. The included drafts do not send customer messages.

Can I remove the examples and starter content?

Sample records stay in memory and never create customers in your CRM. Leave sample mode to return to your account. Starter setup lets you review removal of unused kit additions; server checks retain edited or published workflows and pipelines with live work or references. Removing the frontend does not delete account records.

Can different subaccounts use different kits?

The current design and branding apply to the whole web installation. Subaccounts still separate data and access. Use a separate web installation for another full-interface kit; running different kit designs by subaccount in one installation requires additional customization.

Browse all 220 kits

Customer experiences / Trustpilot

What customers say
about DevLaunch.

Read all reviews on Trustpilot ↗

Selected excerpts from reviews of DevLaunch training, software, and services. Individual customer experiences across DevLaunch.