Skip to content
View packages

CRM KitsRemodeling & renovations

Thoughtful spaces. Clearer decisions.

Build the workspace around the project. Forma pairs an editorial project header and charcoal project rail with a broad milestone timeline, material decisions, recorded changes, and field notes.

Project overview in the GoSeedly Remodeling Kit with fictional sample records

See what the next phase depends on.

Choose a project and keep its context as you move between sections. A milestone timeline, dependency notes, illustrative plan, and latest field note give the work a shared point of reference.

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

What’s in the kit

Screens

  • Selected-project workspace with editorial headings and a milestone timeline
  • Trade schedule with recorded dependencies, statuses, and blockers
  • Material selection queue with separate internal review and client decision records
  • Contract/change summary that excludes pending requests from the current total
  • Field notes and a matching Forma frame for native CRM modules

four pipelines

  • Renovation delivery · 7 stages
  • Consultation to project · 7 stages
  • Preconstruction · 7 stages
  • Punch list & handover · 8 stages

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

nine workflow drafts

  • Inspection preparation
  • Finish readiness review
  • Project kickoff handoff
  • Discovery follow-up
  • Selection decision reminder
  • Pending change review
  • Scope review
  • Trade coordination review
  • Handover checklist

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

Sample workspace

Explore three fictional remodeling projects with milestones, material selections, change requests, and field notes. Example changes remain in memory and reset on reload; no sample CRM customers are created.

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 identity, locale, currency, project-team labels, and default pipeline stages. 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 helper is required for connected project creation and editing. It compares the current record timestamp and project revision, preserves other custom fields, and invokes native Seedly mutations with their existing permissions. Deploy it from your authoritative backend source before testing saves. Business-content presets remain optional; no schema migration is required.

Each project is a contact-linked opportunity with its own scope, lead label, dates, milestone dependencies, selections, contract cents, change requests, and field notes. Project edits preserve unrelated custom fields and reject stale record versions.

Milestone dates and trade labels are recorded plans; dependencies do not automatically reschedule work or reserve a calendar. Internal material review and recorded client decisions remain separate. Contract and change status are manual records, not signatures, invoices, payment collection, or a financial ledger. Notes use entered author labels rather than verified signatures. The floorplan and swatches are labeled illustrations, not measured plans or material specifications.

Four optional pipeline templates and nine inactive workflow drafts. Three fictional in-memory remodeling projects with decisions and field notes.

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

Forma keeps a selected-project rail inside the shared application frame. Its original project sections and native CRM pages use the same account, backend, and charcoal-and-plaster 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.