GoSeedly Landscape Lighting Kit
A fixture plan board for landscape lighting companies: every project in install drawn as its recorded wiring tree of transformers, zones and fixture counts, with the install stage and what the crew is still waiting on, then a tune-up roster for every system after handover. Nightplan keeps night demos, proposals, the fixture schedule, installs, tune-ups and outage tickets in one connected workspace.
YOUR NIGHTPLAN WORKSPACE
01 — FIXTURE PLANS
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 / Fixture plansEvery accepted project shows an eight-step stage track, a night panel with each transformer label as recorded, the zones wired to it and one dot per fixture by type and status, then the install date and three checks: fixtures in hand, transformers in hand and the utility locate. Records with fixtures or the locate not ready for install, an overdue tune-up or an outage past its promise lead, and the tune-up roster follows.
02 / Night demosOpen proposals with the night demo status and date, days open, the plan as drafted and the recorded amount, then every project accepted in the last 60 days with its stage and install date.
03 / Fixture scheduleZone, transformer, type, count, fixture label, lamp label and status for every line on projects in install, then what each install still waits on. Nightplan never adds up watts.
04 / InstallsInstalls grouped by date with crew, wire label, the utility locate requested and marked dates as recorded, the night aim date and the before-install checks, then recent handovers.
05 / Tune-upsNext tune-up due comes from the last recorded visit or plan start plus the interval in calendar months, with the plan price per year in its own column and a visit log underneath.
06 / OutagesOpen tickets past their promised date come first, with the area as the customer described it and warranty as the office recorded it.
07 / InsightsProjects by check not ready, fixtures by type on the plans and in hand, projects by stage, tune-up plans by status and outages by issue. Fixtures, zones, transformers, days and dollars are never added 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 12 fictional records: five projects in install, three open proposals, three handed-over projects and one service-only property, with 28 zones, 13 transformers, 146 fixtures, 6 tune-up visits and 4 outage tickets. 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 project holds the night demo, the proposal and install stage, the install date, crew and wire label, the utility locate as recorded, the tune-up plan, transformers, zones, fixture lines, tune-up visits, outage tickets 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 project creation, edits and resource setup. They preserve native account permissions, unrelated custom fields and row history, refuse access codes, logins, card numbers and Social Security numbers, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
Nightplan records what the office was told and saw. It does not size transformers, calculate load, voltage drop or wire gauge, check electrical code, request or verify utility locates, recommend fixtures or lamps, order from suppliers, route crews, connect to a transformer, timer or app, register warranties, bill or send messages. Gate, lockbox and alarm codes, controller, Wi-Fi and app logins, payment card numbers and Social Security numbers are refused in recorded text and in the native form drafts.
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.
Nightplan keeps its night-blue side rail across the kit views and 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.