Skip to content
View packages

CRM KitsPond and water feature companies

Open, clean and close every pond, then build the next one.

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.

Route board in the GoSeedly Pond & Water Features Kit with fictional sample records

Start with the stop that slipped.

The 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.

Actual interface captures with fictional sample data. Open a screenshot to see it full size.

What’s in the kit

Screens

  • Season-aware route board with a needs-attention strip
  • Route lanes by route day for the opening, clean and closing windows
  • Build strip and builds ledger across eight stages
  • Build estimates that total money only
  • Water features with square feet, gallons and fish counts in separate columns
  • Service agreements and an off-season renewal board
  • Editable account checklists
  • Three native form drafts and three editable document templates

four pipelines

  • Pond service agreements · 7 stages
  • Pond and water feature builds · 8 stages
  • Build stages · 7 stages
  • Commercial and HOA fountains · 7 stages

Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.

nine workflow drafts

  • Agreement follow-up
  • Opening preparation
  • Closing preparation
  • Inquiry review
  • Site visit preparation
  • Estimate follow-up
  • Materials check
  • Startup preparation
  • Proposal review

Inactive until you review and publish them. None send customer messages.

Forms and documents

  • Pond service request
  • Water feature build inquiry
  • Pond access and closing notes
  • Season service plan
  • Build estimate summary
  • Opening and closing visit sheet

Editable native forms and document templates. Forms collect information for staff review.

Sample workspace

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.

No sample customers are added to your CRM.

Setup and source

  • Guided setup and compatibility report
  • Private rollback receipt
  • AI-agent guide for customized installations
  • Original editable source, configuration, and tests
Read the installation guide
  1. Check your Seedly

    Extract the kit and run the guided setup. It checks your installation and flags customized files before it changes anything.

  2. Connect the helper

    Deploy the included helper from your backend source, then build your web app and choose any starter pipelines and drafts.

  3. Make it yours

    Set business name, descriptor, default pipeline name and season calendar. Then sign in and check the workflows and permissions your team uses.

Technical details and compatibility

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.

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.

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.

Four optional pipeline templates and nine inactive workflow drafts. 14 fictional in-memory pond records.

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.

Get the Pond & Water Features Kit

Checking access…

DevLaunch All Access

Every kit and every template.

See DevLaunch All Access

Already a member? Open your downloads.

Questions

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?

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.

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.

Browse all 220 kits

Customer experiences / Trustpilot

What customers say
about DevLaunch.

Read all reviews on Trustpilot ↗

Selected excerpts from reviews of DevLaunch training, software, and services. Individual customer experiences across DevLaunch.