Skip to content
View packages

CRM KitsSolar installers

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.

Project rail in the GoSeedly Solar Installer Kit with fictional sample records

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.

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

What’s in the kit

Screens

  • 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 pipelines

  • Residential solar · 8 stages
  • Commercial solar · 7 stages
  • Battery storage retrofit · 7 stages
  • Service and warranty follow-up · 7 stages

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

nine workflow drafts

  • 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

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

Sample workspace

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

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.

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.

Four optional pipeline templates and nine inactive workflow drafts. Ten fictional in-memory solar projects with recorded site visits.

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 Solar Installer 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?

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.

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.