GoSeedly Gutter Service Kit
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.
YOUR DOWNSPOUT OFFICE
01 — TWO-PASS 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 / Two-pass boardEach 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.
02 / PropertiesLinear feet on record, downspouts and guards, the plan and the passes done this year against it, the quote state and the derived state the office should act on.
03 / QuotesOnly the quotes recorded as sent, with the feet quoted, the date it went out, its age in days and the follow-up attempts. A quote older than the days your office recorded carries the reserved red.
04 / ScheduleEvery recorded crew day with its stops, the storeys the crew has to reach and the ladder or lift note exactly as somebody typed it. Scheduled passes and scheduled jobs both appear.
05 / Installs and repairsJob rows grouped by state, with the material and colour labels as your office types them, the linear feet, the crew day and the amount recorded against each one.
06 / Recurring plansThe plan label, the passes a year recorded, both season pass states, the renewal month and the price per pass, ordered by the nearest renewal.
07 / InsightsRecorded counts and recorded linear feet with a filter behind each number. Feet and money are never drawn on one scale and never totalled together.
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 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.
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 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.
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 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 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.
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.
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.
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.
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.