GoSeedly Locksmith Kit
An urgency queue over a hardware ledger. Tumbler puts lockouts waiting now beside the rekeys, installs and commercial master-key work that are measured in dates, locks and keys cut.
YOUR TUMBLER WORKSPACE
01 — QUEUE
Actual interface captures with fictional sample data. Open a screenshot for a closer look.
TAKE A CLOSER LOOK
One connected workspace, with views built around the decisions your team makes each day.
01 / QueueOpen jobs sit in the lockout now, today and scheduled bands. Every row carries the site, the job type, the technician label, the minutes since the call and a strip of locks serviced, keys cut and hardware still to source.
02 / JobsReview the full ledger with the site, job type, urgency band, technician label, the three counts and the derived job state.
03 / LockoutsCalls with no recorded arrival are ordered by minutes waiting. A second table lists arrivals with the recorded wait and the authorization method.
04 / Rekeys and installsScheduled rekeys, installs and safe work group under their recorded date with the lock and key totals for that day.
05 / HardwareEvery active hardware line still recorded as not sourced, earliest booked date first, with its site, quantity and job type.
06 / Commercial accountsCommercial work groups by account label with the recorded system labels, the last recorded service date and the account totals.
07 / InsightsJob-state counts filter the ledger, beside the lockouts past the threshold, the hardware lines not sourced and the keys cut on loaded jobs.
YOUR PROCESS, YOUR STARTING POINT
4 pipelines and 9 workflow drafts. Add the parts that match your work, with a separate sample view for exploring the interface.
Use a ready-made stage sequence or connect drafts to a suitable existing pipeline.
Native trigger, task, wait, and note nodes provide editable examples. Every draft stays inactive until you review and publish it.
Explore 13 fictional jobs: three lockouts with one past the recorded threshold, six scheduled rekeys and installs, and four commercial account visits. Sample edits stay in memory and reset on navigation or reload.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
MORE OF THE WORKING DAY
Editable native forms and document templates give your team a practical starting point.
Choose forms individually in Setup & resources, then customize and publish them in the native form builder.
Open each template in Documents and complete it for the actual job or visit.
Record progress and notes in the kit’s operating views. Keep earlier rows by archiving them, and retain the context for the next person.
Forms collect information for staff review. They do not automatically change the kit’s custom records. Repeating setup preserves existing resource edits.
THE KIT, UNPACKED
One contact-linked job holds the site record, the urgency band, the call and arrival times, the technician label, the locks serviced, the keys cut, the hardware lines and a visit log. Keyway and stamped labels are descriptors; key bitting, key codes, safe combinations, alarm codes and door codes are never stored.
FROM KIT TO CONNECTED WORKSPACE
Run the guided setup from the extracted kit. Supported integrations can be installed directly; customized integration files get a reviewed merge.
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.
Edit business name, descriptor and default pipeline name. Sign in with your account and verify the workflows and permissions your team uses.
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 job creation, edits and resource setup. They preserve native account permissions, unrelated custom fields and row history, check revisions before saving, and refuse a code-like value on the server as well as in the browser. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
A recorded wait turns red only when a lockout passes the 45-minute threshold. An arrival cannot be recorded before its call, and a lock recorded as opened needs a verified authorization with a method label. The authorization flag records that staff checked the customer's right to access; it is not an identity verification service. The kit does not dispatch, track location, hold key codes, source or order hardware, take payments or send messages.
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
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.
Every published kit as original editable source, with optional pipelines, workflow drafts, and guided installers. Browse the kits
The full DevLaunch library and software collection, plus each eligible release during your access year, added to your portal as it ships.
Bring the idea, the offer, or the bottleneck, and leave with a plan you can follow.
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
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.
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.
Tumbler 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.
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.
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.
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.
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 kitsCustomer experiences / Trustpilot
Selected excerpts from reviews of DevLaunch training, software, and services. Individual customer experiences across DevLaunch.
We use essential storage to keep the site working. With your permission, we also use analytics and the Whop Pixel to understand visits and advertising results. Optional analytics stay off until you choose.
Read our Cookie Policy and Privacy Policy.