Skip to content
View packages

CRM KitsPet sitting and dog walking services

Every visit in view. Every key accounted for.

Keep the week’s visits, the pets in your care and the next key handover together. Latchkey brings booking date bands, a seven-day visit schedule and an owner’s booking sheet into one pet sitting workspace.

Week in the GoSeedly Pet Sitter Kit with fictional sample records

See the visits across the week.

Booking bands show recorded away windows above seven day columns. Visit cards carry pet names, the time window, visit type, sitter label, outcome and key state.

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

What’s in the kit

Screens

  • Seven-day visit schedule with booking date bands
  • Booking sheet with pet notes and dated visits
  • Bookings, Pets, Keys, Rebook and Insights views
  • Recorded key collection and return follow-ups
  • Archive-only pet and visit rows with stable IDs
  • Slate application bar with permission-filtered native CRM tools

four pipelines

  • New client meet and greets · 7 stages
  • Vacation bookings · 8 stages
  • Recurring dog walks · 7 stages
  • Overnight and house sitting · 7 stages

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

nine workflow drafts

  • Meet and greet task
  • Key collection task
  • Booking confirmation note
  • First visit reminder
  • Daily visit check task
  • Key return task
  • Post-trip follow-up
  • Rebook reminder
  • Recurring walk review note

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

Sample workspace

Explore fictional bookings, pets, visits and sitter labels in a sample week. Changes stay in the current page’s memory, reset on navigation or reload and create no records in your CRM.

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 company name, descriptor, promise line 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 booking helper is required for connected creation, editing and starter setup. It preserves native account permissions and unrelated custom fields, checks dates and key state, and refuses stale timestamp or revision values. Deploy from the authoritative backend source before connected edits. Optional pipelines and workflow drafts remain separate from source installation.

Each booking is a native contact-linked opportunity with owner and sitter labels, away dates, an address label, key state and location label, next trip date, a recorded reminder flag, an optional booking total and pet and visit rows. Child records keep stable IDs and are archived instead of removed. Other custom fields and unknown extensions are preserved.

Visits record dates, time windows and outcomes; they do not create calendar appointments, check availability or track GPS arrival. Care and medication notes are staff context, not veterinary records or advice. A completed visit requires the key recorded in hand, while a missed visit may be recorded without it. Key flags do not connect to smart locks. Sitter labels reserve nobody. Booking totals preserve cents as reference amounts, separate from payment processing and native opportunity value. Reminder flags send no messages. Native CRM stage changes remain independent of visit outcomes.

Four optional pipeline templates and nine inactive workflow drafts. Fictional in-memory bookings, pets and visits.

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 Pet Sitter 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?

Latchkey keeps the week schedule and native CRM modules in one application theme, signed-in account and permission model. 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.