Skip to content
View packages

CRM KitsNail and lash studios

Every client. A clear next visit.

A client workspace for nail and lash studios. Fill keeps recorded services, visit history and requested fill dates together.

Fill cycles in the GoSeedly Nail & Lash Studio Kit with fictional sample records

A little time. A clear next visit.

Review the interval between each last recorded visit and requested next fill, with missing dates shown explicitly.

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

What’s in the kit

Screens

  • Fill cycles operating view
  • Clients operating view
  • Services operating view
  • Appointments operating view
  • Visit history operating view
  • Follow-up operating view
  • Insights operating view
  • Three native form drafts and three editable document templates
  • Editable studio checklists with preserved row history

four pipelines

  • Studio appointments · 7 stages
  • Fill follow-up · 7 stages
  • Service reviews · 7 stages
  • Client relationships · 8 stages

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

nine workflow drafts

  • Inquiry review
  • Appointment preparation
  • Service plan review
  • Visit record review
  • Fill-date review
  • Fill follow-up
  • Checklist review
  • Client check-in
  • Rebooking review

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

Forms and documents

  • Studio appointment request
  • Fill follow-up request
  • Appointment change request
  • Client appointment brief
  • Service record
  • Fill follow-up card

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

Sample workspace

Explore 12 fictional client records with 24 service lines, 24 visit records and 24 checklist steps. 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
  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 business 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 support connected record creation, edits and resource setup. They preserve account permissions, unrelated custom fields and row history, and reject stale revisions. Reconcile them with your authoritative backend. Pipelines and inactive workflow drafts are optional.

One contact-linked client episode holds an artist label, service family, last visit, requested next fill and appointment dates, recorded service lines, visit history and an editable studio checklist.

Fill records office-entered dates and service details. It does not reserve appointments, prescribe treatments or intervals, take payments or send reminders. Quotes are service references, not collected revenue. Keep health information, allergy or patch-test details, body measurements, payment details, government identifiers and access codes outside the workspace.

Four optional pipeline templates and nine inactive workflow drafts. 12 fictional in-memory studio clients.

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 Nail & Lash Studio Kit

Checking access…

DevLaunch All Access

Every kit and every template.

See DevLaunch All Access

Already a member? Open your downloads.

Questions

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?

Fill keeps its white studio navigation and fuchsia client fill-cycle cards connected to 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.