GoSeedly Pond & Water Features Kit
A seasonal route board for pond and water feature companies. The opening, midseason clean and closing windows are worked as route lanes by route day, each stop saying in words whether its visit is done, scheduled or late, and new koi ponds, water gardens, waterfalls and fountains move through eight build stages in the same Spillway workspace. Off season the board leads with next season’s agreements, booked openings and builds.
YOUR SPILLWAY WORKSPACE
01 — ROUTE BOARD
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 / Route boardThe season rail shows the opening, clean and closing windows with today marked and each window’s visits recorded. Visits past their scheduled date, estimates past follow-up and builds past their target finish lead the board, then the current window’s stops by route day in route order, then the build strip.
02 / Season gridOne row per service account with its route day, stop and plan, the opening, midseason clean and closing visit states in words, a count of monthly care visits and the agreement status. A window reads as closed only after its last day.
03 / BuildsAccepted builds with target and recorded start and finish dates beside eight stages, from design set and dig through liner, rock, plumbing, fill and plants to startup.
04 / EstimatesOne card per build with its status, sent and decision dates, follow-up date and a quote line per water feature. Only money is totalled; square feet and gallons stay on their own lines.
05 / Water featuresEvery koi pond, water garden, pondless waterfall, stream, fountain and bubbler rock with its surface square feet, gallons, fish count and pump label, each in its own column and never totalled together.
06 / AgreementsService agreements with the plan, season price, route day and stop, offered date and status. Off season this is the renewal desk for next year’s route.
07 / InsightsVisits by kind and state, water features by kind, agreements by status with season prices and build estimates by status with quote lines, each in its own ledger, plus the records behind them with the same alert flags.
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 14 fictional pond records: 8 service accounts on three route days and 6 build projects with 19 water features. The sample season follows today’s date. 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 record is a service account or a build for one season. It holds the property, technician or crew label and site notes; service accounts add the plan, season price, route day and stop, the agreement and visit rows with scheduled and done dates; builds add the estimate, target and recorded dates and the build stage. Both carry water features with square feet, gallons, fish count and pump label, and an editable checklist.
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, default pipeline name and season calendar. 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 account creation, edits and resource setup. They preserve native account permissions, unrelated custom fields and row history, refuse access codes, logins and identifiers, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
Everything shown is what the office recorded. The kit gives no water chemistry, water quality, fish or plant health advice, does not measure water or size pumps and liners, plan routes, dispatch technicians, order parts, bill, take deposits or payments, or send messages. Gate, lockbox and alarm codes, pump and Wi-Fi logins, card numbers and Social Security numbers are refused in notes and forms.
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.
Spillway keeps its dark lily-pad top bar and ripple band across the kit views and the 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.