Your practice, your configuration
Cairn is shaped to how your clinic actually runs. Your forms, your workflows, your fee schedule, your roles. It's all configuration data, not custom code, so it survives every upgrade.
What gets shaped to your clinic
- Exam and intake forms: your fields, your order
- Note templates per visit type (wellness, dental, surgery…)
- Vaccine protocols and reminder sequences
- Fee schedules and invoice line behavior
- Roles and permissions that match your actual staff
- Workflows: who signs, who is notified, what routes where
- Your branding on client-facing documents
How it works
1. You describe your practice. A structured onboarding questionnaire: species mix, visit types, protocols, staff roles.
2. We build your configuration. Forms, templates, protocols, and roles are generated as configuration data and checked by validation rules.
3. You approve it. We review it with you, adjust, and load it.
4. It keeps evolving after you start. Describe a change and we configure it, validate it, and you approve it. Same loop, any time.
Included free at onboarding on every plan.
Why configuration
Cairn's core is one codebase for everyone. Everything clinic-specific lives in validated configuration data layered on top. That structure is what keeps customization safe and cheap.
- Upgrades never break your setup. Your config rides along. There is no "your version" to maintain.
- Changes are fast and cheap. A new form or workflow is a config change with validation, not a development project with a quote.
- Everything is reviewable. Config is human-readable data with an audit trail. You can see exactly what your clinic runs on.
Ongoing changes beyond onboarding are fixed-price config packs. See pricing.
Tell us how your practice runs.
Bring your intake form and your weirdest workflow to the demo. That's the fun part.
Request a demo