01 / Project overviewSee 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.
GoSeedly Remodeling Kit
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.
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 / Project overviewChoose 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.
02 / Material selectionsRecord room, material option, allowance, and needed-by date. Internal review and recorded client decisions have separate controls, so checking a selection internally does not mark it accepted by the client.
03 / Contract & changesSee the original contract plus recorded approved changes, with cents preserved. Pending and declined requests stay outside the current total. Record scope and proposed schedule effects alongside each change.
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 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.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
THE KIT, UNPACKED
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.
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 company identity, locale, currency, project-team labels, and default pipeline stages. 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 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.
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.
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.
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.
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.