01 / WeekSee 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.
GoSeedly Pet Sitter Kit
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.
Checking access…See the interface
One-time purchase · USD · Your Seedly backend · Editable kit sourceYOUR PET SITTING WORKSPACE
01 — WEEKActual interface captures with fictional sample data. Open a screenshot for a closer look.
TAKE A CLOSER LOOK
From the first visit to the next trip.
One connected workspace, with views built around the decisions your team makes each day.
01 / Week
02 / Booking sheetKeep care notes beside the visit.
Select a visit to open its booking sheet beside the schedule. Review the owner, away dates, physical key record, pets, staff notes and dated visits in context.
03 / BookingsRead the whole booking.
Browse booking windows, recorded pets and visits, sitter labels and key states. Open a record to update it or change its native CRM stage.
04 / PetsBring the pet’s notes into view.
Read names, species, breed labels, feeding instructions and staff-entered care notes grouped under their booking.
05 / KeysFollow up on physical keys.
Review keys recorded as needing collection and bookings with no planned visits left whose key is still in hand.
06 / RebookKeep the next trip on record.
Review completed away windows with a recorded next trip date and bookings with no reminder recorded as sent. A booking can appear in both groups; the reminder flag records staff activity.
07 / InsightsRead the recorded activity.
Compare visit outcomes, key states and pet species across the loaded bookings. Recorded booking totals stay separated by currency.
YOUR PROCESS, YOUR STARTING POINT
Useful structure.
Only what you choose.
4 pipelines and 9 workflow drafts. Add the parts that match your work, with a separate sample view for exploring the interface.
Choose your starting structure.
Use a ready-made stage sequence or connect drafts to a suitable existing pipeline.
- New client meet and greets · 7 stages
- Vacation bookings · 8 stages
- Recurring dog walks · 7 stages
- Overnight and house sitting · 7 stages
Give the next step a shape.
- 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
Native trigger, task, wait, and note nodes provide editable examples. Every draft stays inactive until you review and publish it.
Explore before adding records.
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 inserted into your CRM.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
THE KIT, UNPACKED
Your workspace.
Your starting point.
Your code to edit.
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.
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 optional pipeline templates and nine inactive workflow drafts
Fictional in-memory bookings, pets and visits
Guided setup, compatibility report, and private rollback receipt
AI-agent documentation for customized installations
Original editable source, configuration, and tests
Read the installation guide FROM KIT TO CONNECTED WORKSPACE
Check. Connect.
Make it yours.
Check your Seedly project.
Run the guided setup from the extracted kit. Supported integrations can be installed directly; customized integration files get a reviewed merge.
Connect the required helper.
Deploy the included helper from your authoritative backend source before connected edits. Build your web app, then choose any optional pipelines and drafts you need.
Set up your own team.
Edit company name, descriptor, promise line and default pipeline name. Sign in with your account and verify the workflows and permissions your team uses.
Compatibility and operational details
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.
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.
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.
DEVLAUNCH ALL ACCESS
Every kit.
And everything else.
DevLaunch All Access includes every GoSeedly CRM kit, all 195 available today, along with every class, course, and product we release, and private calls with Aaron.
All 195 CRM kits
Every published kit as original editable source, with optional pipelines, workflow drafts, and guided installers. Browse the kits
Every class, course, and product
The full DevLaunch library and software collection, plus each eligible release during your access year, added to your portal as it ships.
Private calls with Aaron
Bring the idea, the offer, or the bottleneck, and leave with a plan you can follow.
DevLaunch All Access
Want more than one kit? All Access covers the whole CRM kit library and the rest of what we make. See everything it includes on the All Access page.
See DevLaunch All AccessAlready a member? Open your downloads.
For your own compatible Seedly CRM. Seedly software, hosting and installation services are separate. Each full-interface kit uses its own web installation.
BEFORE YOU MAKE IT YOURS
Good questions.
Clear answers.
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.
Find a workspace that fits the way you work.
Explore all CRM kits