CRM KitsOptometry practices and optical shops
Every patient recalled. Every pair tracked.
A two-rail front desk: a five-rung recall ladder above an optical order tracker where every pair fills from ordered to dispensed. Lens keeps the relationship in one connected workspace and leaves clinical records in the practice's own system.
Both rails in one view.
The recall ladder sorts recorded recalls into five rungs by how far past their due month they sit. Below it, every open optical order is a capsule filling left to right through ordered, at lab, received, inspected and dispensed.
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 both rails
- Patients operating view
- Recalls operating view
- Optical orders operating view
- Pickups operating view
- Contact lenses operating view
- Insights operating view
- Server-enforced prescription guard on every text field
- Recorded reorder window with its own 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
- Optical orders · 7 stages
- Contact lens supply · 7 stages
- Recall campaigns · 8 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- New patient welcome
- Annual recall due
- Recall second attempt
- Order placed note
- Lab turnaround check
- Ready for pickup
- Pickup reminder
- Contact lens reorder reminder
- Remake follow-up
Inactive until you review and publish them. None send customer messages.
Forms and documents
- New patient registration
- Appointment request
- Eyewear pickup feedback
- Recall call sheet
- Optical order tracking slip
- Dispensing checklist
Editable native forms and document templates. Forms collect information for staff review.
Sample workspace
Explore 14 fictional patients with 22 recalls across all five rungs, 11 optical orders across all five stations and 6 contact lens supplies. 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
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.
How setup works
Full installation guideCheck your Seedly
Extract the kit and run the guided setup. It checks your installation and flags customized files before it changes anything.
Connect the helper
Deploy the included helper from your backend source, then build your web app and choose any starter pipelines and drafts.
Make it yours
Set practice 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 recorded reorder window and resource setup. They preserve native account permissions, unrelated custom fields and row history, check revisions before saving, and run the prescription 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, the preferred contact window, recalls as category labels with their due month and contact attempts, optical orders with frame, lens type, coatings and lab labels, contact lens supply rows and an editable front desk checklist.
This is a front desk and optical relationship record, not a medical record. It is not a HIPAA compliance tool, it is not an EHR or a 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 prescriptions, refraction values, sphere, cylinder, axis, add, pupillary distance, visual acuity, diagnoses, medical history, insurance member IDs or clinical notes, and the shared model refuses text that looks like a prescription value in every field, on the server as well as in the browser. Treat that as a guard against accidental entry rather than a guarantee. Clinical and prescription records stay in the practice's own system, and the kit gives no vision or medical advice. The practice is responsible for its own compliance and for whatever it chooses to record in its CRM. There is no EHR or practice management integration, no insurance or vision plan processing, no lab ordering integration, no scheduling engine, no automated recalls or patient messaging, and no payments.
Four optional pipeline templates and nine inactive workflow drafts. 14 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 Optometry Kit
Checking access…
DevLaunch All Access
Every kit and every template.
- All 220 CRM kits for Seedly CRM
- All 270 website templates for Seedly Sites
- Every class, course, and product we release, added as it ships
- Private calls with Aaron
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?
Lens retains its application frame 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.
More health, beauty & wellness kits
Browse all 220 kits
