Skip to content
View packages

CRM KitsGutter cleaning, repair and guard installers

Two passes a year. Every foot on record.

A two-pass service board that puts both passes of the plan year for the same property side by side, with the linear feet somebody measured on site, the crew day, and the install and repair work sold by the foot. Downspout keeps the round and the quotes in one connected workspace.

Two-pass board in the GoSeedly Gutter Service Kit with fictional sample records

Both passes, one screen.

Each property on a plan appears under both passes of the plan year on the board, labelled the way the office records its own two season windows, with its linear feet, storeys, pass state, downspouts and guards. Open work leads and a completed pass sorts last. A narrow column beside them stacks the install and repair jobs, material on order first.

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

What’s in the kit

Screens

  • Two-pass board operating view
  • Properties operating view
  • Quotes operating view
  • Schedule operating view
  • Installs and repairs operating view
  • Recurring plans operating view
  • Insights operating view
  • A revision-guarded office settings record for the season windows and follow-up days
  • Three native form drafts and three editable document templates
  • Editable per-property checklists and preserved row history

four pipelines

  • Recurring gutter plans · 8 stages
  • Gutter quotes · 7 stages
  • Gutter installs · 7 stages
  • Guard and repair work · 7 stages

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

nine workflow drafts

  • New quote request task
  • Quote follow-up after a wait
  • Plan started note
  • Spring pass scheduling task
  • Autumn pass scheduling task
  • Skipped pass follow-up task
  • Material arrival check task
  • Plan renewal task
  • Review request task

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

Forms and documents

  • Gutter quote request
  • Recurring plan sign-up request
  • Job feedback
  • Linear-foot quote
  • Pass completion note
  • Plan renewal letter

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

Sample workspace

Explore twenty fictional properties working through the current plan year, sixteen of them on a recurring plan: fourteen first passes done and two skipped, five second passes done, six booked and five with nothing booked, seven install and repair rows, six open quotes and four plans renewing inside sixty days. The sample dates itself from the day you open it. Sample 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 and default pipeline name. 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 property creation, edits, the office settings record and resource setup. They preserve native account permissions, unrelated custom fields and row history, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.

One contact-linked property holds the customer, the linear feet measured on site, the storeys label, the downspout count, a guards flag, the recurring plan with its passes a year, renewal month and price per pass, each season pass with its state, crew day, completed date, skip reason and photographs flag, the install and repair rows with their material and colour labels, the quote state with its sent date and follow-up attempts, access directions, a ladder or lift note and an editable checklist.

The season windows and the follow-up days are your office policy, recorded in a small revision-guarded settings record rather than decided by the kit. Nothing is measured from aerial imagery, no roof or structure is inspected, no route is optimized, no GPS or weather feed is read, a crew day is a date somebody typed, and no message, payment or invoice is sent or taken. The kit records no gate, keypad, lockbox or alarm code and refuses the obvious accidental entries in every free-text field, which is a guard against accidental entry rather than a guarantee.

Four optional pipeline templates and nine inactive workflow drafts. 20 fictional in-memory examples.

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 Gutter Service 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?

Downspout keeps one mid-slate bar across the top of the workspace, with 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.