Skip to content
View packages
CRM Kits Solar installers

GoSeedly Solar Installer Kit

Every roof.
Every phase.

A solar project waits on seven gates it does not control. Array puts all seven on one rail, one row per project, so the office can see at a glance which job is waiting on the survey, the design, the permit, the utility, the install day, the inspection or permission to operate.

Checking access…See the interface
One-time purchase · USD · Your Seedly backend · Editable kit source

YOUR ARRAY PROJECT RAIL

01 — PROJECT RAIL
Array solar project rail with one row per project, each carrying seven recorded phase cells for survey, design, permit, interconnection, install day, inspection and permission to operate, using fictional sample data

Actual interface captures with fictional sample data. Open a screenshot for a closer look.

TAKE A CLOSER LOOK

From the first roof visit to permission to operate.

One connected workspace, with views built around the decisions your team makes each day.

Project rail in the GoSeedly Solar Installer Kit with fictional sample records01 / Project rail

Seven gates, one row per project.

Each row carries a horizontal rail of seven recorded phase cells: filled for complete, ringed for the current phase, dashed for not started and struck for blocked. Recorded system size, panel count and crew label sit beside it, and the gold marker picks out the install day.

Project record in the GoSeedly Solar Installer Kit with fictional sample records02 / Project record

The whole record, under the rail.

Selecting a row opens the detail pane: the site survey, the permit and AHJ record, the interconnection and utility record, the install day and crew, the inspection result and every recorded site visit. One control records the current phase as complete.

Site surveys in the GoSeedly Solar Installer Kit with fictional sample records03 / Site surveys

Start at the roof.

Every project’s recorded survey, with the ones whose survey phase is not complete, or that still have an open recorded survey visit, listed first. Roof type, survey notes and visit outcomes stay with the project.

Permits and AHJ in the GoSeedly Solar Installer Kit with fictional sample records04 / Permits and AHJ

Paper before panels.

A ledger of recorded AHJ labels, permit number references, submitted and approved dates, and the permit phase status. These are office entries. The kit files nothing and reads no AHJ portal.

Interconnection in the GoSeedly Solar Installer Kit with fictional sample records05 / Interconnection

The utility side, recorded.

Utility label, recorded application status, the interconnection phase status and the recorded permission-to-operate date, in one ledger. No utility portal is contacted and no application is submitted from the kit.

Install days in the GoSeedly Solar Installer Kit with fictional sample records06 / Install days

Install day, in order.

Recorded install visits grouped by the week they were entered for, with crew label, panel count and recorded system size. Nothing here books a calendar, reserves a crew or orders equipment.

Portfolio insights in the GoSeedly Solar Installer Kit with fictional sample records07 / Portfolio insights

Read where the work is waiting.

Counts of projects by current recorded phase, recorded site visit outcomes, recorded inspection results and the recorded panel total for the selected pipeline. Every number comes from an entered record.

YOUR PROCESS, YOUR STARTING POINT

Useful structure.
Only what you choose.

4 pipelines and 9 workflow drafts. Add the parts that match your work, with a separate sample view for exploring the interface.

01 / FOUR PIPELINES

Choose your starting structure.

Use a ready-made stage sequence or connect drafts to a suitable existing pipeline.

  1. Residential solar · 8 stages
  2. Commercial solar · 7 stages
  3. Battery storage retrofit · 7 stages
  4. Service and warranty follow-up · 7 stages
02 / NINE WORKFLOW DRAFTS

Give the next step a shape.

  • Survey scheduling task
  • Design review task
  • Permit submission checklist
  • Permit follow-up task
  • Interconnection application task
  • Install day prep checklist
  • Inspection scheduling task
  • PTO follow-up task
  • Warranty check-in note

Native trigger, task, wait, and note nodes provide editable examples. Every draft stays inactive until you review and publish it.

03 / SAMPLE WORKSPACE

Explore before adding records.

Explore ten fictional solar projects sitting at different phases, with recorded site visits, permit and interconnection records, install days and inspection results. Example edits stay in the current page’s memory and reset on navigation or reload; sample projects are never inserted into your CRM.

No sample customers are inserted into your CRM.

Starter setup checks selected kit additions before removal and preserves edited records and live work.

THE KIT, UNPACKED

Your workspace.
Your starting point.
Your code to edit.

One project is a native contact-linked opportunity with recorded system size in kilowatts, panel count, inverter and roof type labels, AHJ and permit references, permit dates, utility label, interconnection status, crew label, inspection result, survey notes, a contract reference and the seven recorded phases. Site visits are stable-ID child records. Unrelated custom fields are preserved and stale record versions are rejected.

Project rail table with a seven-cell recorded phase rail on every row
Project detail pane covering survey, permit and AHJ, interconnection, install day and inspection
Site survey, permit, interconnection and install-day ledgers
Portfolio insights drawn from recorded workspace data
White, lavender and indigo Array application frame with full CRM tools
Four optional pipeline templates and nine inactive workflow drafts
Ten fictional in-memory solar projects with recorded site visits
Guided setup, compatibility report, and private rollback receipt
AI-agent documentation for customized installations
Original editable source, configuration, and tests
Read the installation guide

FROM KIT TO CONNECTED WORKSPACE

Check. Connect.
Make it yours.

01

Check your Seedly project.

Run the guided setup from the extracted kit. Supported integrations can be installed directly; customized integration files get a reviewed merge.

02

Connect the required helper.

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.

03

Set up your own team.

Edit company name, descriptor, and default pipeline name. Sign in with your account and verify the workflows and permissions your team uses.

Compatibility and operational details

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 solar helper is required for connected creation, editing and starter setup. It preserves native account permissions and unrelated custom fields, keeps the seven recorded phase keys and stable site visit IDs, and checks the current record state before saving. Deploy it from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional.

Phases and site visits are staff-entered records; nothing advances on its own. The kit does no solar design, shading analysis or production modelling. It files no permits and reads no AHJ portal. It contacts no utility and submits no interconnection application. It books no calendar, reserves no crew and orders no equipment. It schedules no inspection and makes no code compliance judgement. It reads no inverter or monitoring data. The contract reference is a recorded number, separate from opportunity value, invoicing and payments.

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.

Checking access…

DEVLAUNCH ALL ACCESS

Every kit.
And everything else.

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.

  • All 195 CRM kits

    Every published kit as original editable source, with optional pipelines, workflow drafts, and guided installers. Browse the kits

  • Every class, course, and product

    The full DevLaunch library and software collection, plus each eligible release during your access year, added to your portal as it ships.

  • Private calls with Aaron

    Bring the idea, the offer, or the bottleneck, and leave with a plan you can follow.

DevLaunch All Access

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 Access

Already 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

Good questions.
Clear answers.

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?+

Array keeps its project navigation across the original solar views and native CRM modules. Full CRM tools remain available within the same signed-in account and application theme. 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.

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.