GoSeedly Window Cleaning Kit
A window cleaning company does not lose money on the clean. It loses money on the rebook nobody made. Pane puts every recurring account on one white year: twelve month columns, a service dot in each month, and the current month tinted, so the accounts that fell off their season are visible without opening a record.
YOUR PANE REBOOK GRID
01 — REBOOK GRID
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 / Rebook gridOne row per recurring account and twelve month columns. A filled dot means a clean is recorded in that month, a ring means the derived next due date falls there, and a red ring means that month has already passed. The current month column is tinted, and rows sort by next due date so the accounts that have fallen off their season come first.
02 / Account sheetSelecting a row opens the account sheet: the address, type, recorded frequency, pane count reference, crew and price per clean, then the clean log with its date, crew, surfaces and note, then the rebook block with the last recorded clean, the derived next due date and the reminder somebody recorded. A storefront on a monthly season fills a dot in every month a clean is recorded and rings the month it next comes due.
03 / The bookThe whole book as one ruled table with type, frequency, pane count, crew, price per clean, last clean and next due. Filter by frequency. An account with nothing recorded reads "No clean recorded yet" rather than showing an invented date, and an overdue account is marked where it actually is.
04 / Due and overdueOverdue accounts first, then the accounts due this month, each with the last recorded clean, the derived next due date, how far away that is in days, whether a rebook reminder was recorded, and the access notes somebody typed. Overdue means the next due date is earlier than the first day of this month, and nothing else.
05 / Recorded cleansRecorded cleans grouped by the date and crew label somebody typed, most recent day first, with the surfaces recorded on each row. Two cleans on one day stay two rows, because a building can record an interior visit and an exterior visit with different crews. Nothing here computes an order, a drive time or a distance.
06 / Season insightsThe frequency mix and the account type mix as ruled bars, interior and exterior coverage over recorded clean rows, rebook reminder coverage against the accounts that have a due date, and price and pane references grouped by currency with the number of accounts that recorded one.
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 fourteen fictional accounts in the separate sample view: nine residential and five commercial across all four frequencies, with a year of recorded cleans, two crew labels, five accounts due this month, two overdue and one with no clean recorded yet. Example edits stay in the current page’s memory and reset on navigation or reload; sample accounts are never inserted into your CRM.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
THE KIT, UNPACKED
One account is a native contact-linked opportunity with a namespaced account name, service address label, account type, recorded frequency, pane count reference, access notes label, default crew label, an optional price per clean, the clean log with its stable row IDs, and the rebook reminder flag with its recorded date. Two accounts at the same address stay independent, and other custom fields are preserved.
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 company 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 window cleaning helper is required for connected creation, editing and starter setup. It checks the active account, native permissions and the current record state, preserves unrelated custom fields and unknown values, and invokes the native Seedly mutations inside one transaction. Deploy it from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional, and no schema migration is required.
The next due date is derived once and shared by the editor, every view and the server: the last recorded clean advanced by the recorded frequency in calendar months, landing on the same day of month and clamping down in a shorter month. An account with no recorded clean has no due date and is never overdue, and there is no grace period. The frequency tag is the season somebody recorded, not an interval measured from the clean log. The rebook reminder flag is a staff record that a reminder went out; the kit sends no email, text or postcard. A crew label reserves nobody and creates no native Calendar appointment, and recorded cleans are grouped by date and crew with no route optimization, drive time or GPS anywhere. Pane count and price per clean are two separate recorded references that are never multiplied into a quote, and a recorded price is never written into native opportunity value. There is no invoicing, payment, weather integration, building or equipment master record. Empty values read as words, never a dash.
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.
Pane keeps its rebook-grid navigation across the original window cleaning views and the native CRM modules. Full CRM tools remain available within the same signed-in account and application theme. 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.