GoSeedly Pool Service Kit
Skimmer puts the week on one page. Five weekday ledgers of stops, each row carrying a tick for whether a reading is recorded this week and a three-bar range strip drawn against the reference band, so the pools that need a conversation are the ones you can see.
YOUR SKIMMER SERVICE WEEK
01 — STOP LEDGER
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 / Stop ledgerMonday to Friday as five narrow ledgers. Each stop shows its pool label, its route, a tick for whether a reading is recorded inside this week, and three tiny range bars for pH, free chlorine and total alkalinity with the latest recorded value printed beside each one.
02 / Pool sheetSelect a stop and the sheet below fills in: pool type, address label, volume reference and monthly rate, the recorded equipment labels, the chemistry log with its reference bands and band check, and the equipment repairs with their part labels and status.
03 / RoutesEvery stop grouped by its recorded weekday and route label, with the latest reading repeated beside it. A route label is a label your team typed; nothing here computes an order, a distance or a drive time.
04 / PoolsThe whole list in one table: pool type, service address, volume reference in gallons, route label, service weekday, equipment labels and the recorded monthly rate. Filter by pool type and open any record to edit it.
05 / Chemistry logPools carrying a reading outside a band come first, then every recorded reading with its date, its three values and its band check. The three reference bands are printed as a legend above the log, and a value only turns red when it actually sits outside its own band.
06 / Equipment repairsRepairs that are not recorded as done, then the recorded complete ones, then the archived ones that stay on their pool record. Each row carries the pool, its weekday and route, the recorded part label, the status and the date.
07 / Service insightsCounts by pool type, recorded readings with the share outside a band and its denominator printed, where a reading is recorded this week, repair counts by status, and the recorded monthly rate grouped by currency code.
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.
Walk a fictional week first: twelve pools across the five weekdays and two route labels, 24 recorded readings with two outside a reference band, and five recorded repairs including one archived row. Sample edits stay in the current page memory and reset on navigation or reload; sample pools 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 serviced pool is a native contact-linked opportunity with namespaced pool type, address label, volume reference, route label, service weekday, equipment labels, monthly rate reference, service notes, chemistry readings and equipment repairs. pH and free chlorine are stored as integer tenths and total alkalinity in whole ppm, so a recorded 7.4 stays 7.4. Readings and repairs use stable IDs and are archived rather than deleted.
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 pool service helper is required for connected creation, editing and starter setup. It preserves native account permissions and unrelated custom fields, re-checks every reading and repair rule on the server, and compares the current record state before saving. Deploy it from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional.
The three reference bands are a display band recorded in the kit so a reading can be drawn against something. They are not dosing advice: nothing calculates a dose, names a chemical or multiplies the recorded pool volume. The done tick is derived from the chemistry log on every render, so it says a reading is recorded inside the displayed week and never that a visit happened. A route label and a service weekday reserve no technician, create no calendar appointment and compute no route. A recorded part label and an ordered status contact no supplier and reserve no stock. A recorded monthly rate is a reference, not an invoice, and is never written into native opportunity value.
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.
Skimmer keeps its pool service navigation across its original 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.