Skip to content
View packages

GoSeedly Kitchen & Bath Kit / INSTALLATION

A clear path
to your workspace.

Bring the kit into your compatible Seedly installation, preserve existing work, and choose the starter content that fits your team.

01

Start with your Seedly project.

Use your separately obtained Seedly CRM 5.8.4 installation with extension API 1, a configured backend, and working authentication. Keep a private source checkpoint, including existing customizations. Use Node.js 20 or newer.

02

Run guided setup.

Extract the kit outside the Seedly source folder. From the kit directory, run node setup.mjs. The check identifies supported integration files, changed files, and destination conflicts before installation.

03

Build and connect.

Deploy the included required helper from your authoritative backend source before connected edits. Follow QUICKSTART.md with your project’s existing package manager. Build the web app, sign in, and open your existing /location/YOUR_LOCATION_ID address. Verify access, navigation, and your important CRM flows.

Install the interface.
Choose the starting content.

Frontend installation and optional account content are separate. The included original kitchen and bath helper is required for connected creation, editing and starter setup. It checks the active account, native permissions and the current record state, re-derives the current phase, preserves unrelated custom fields and unknown values, and invokes the native Seedly mutations inside one transaction. Deploy it from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional, and no schema migration is required. Follow QUICKSTART.md and STARTER_CONTENT.md for the exact integration. The frontend installer does not deploy your backend.

Pick your starting structure.

Starter setup offers Kitchen remodels, Bath remodels, Design and selections consults, Builder and multifamily packages. Select individual pipelines and drafts, or use a suitable existing pipeline with the exact stage needed by the chosen draft.

Adapt each workflow.

All nine workflows remain inactive drafts. Review their native triggers, internal tasks, notes, timing, and assignments before publishing in Seedly. Timed waits do not check whether a task is complete or the stage has changed. These examples do not send customer messages.

Explore sample mode.

Explore nine fictional projects in the separate sample view: kitchens, baths and one whole-floor job, with one project sitting in each of the eight trade phases and one finished project whose whole strip is complete. Sixty-one selections, fourteen of them still open, and two change notes on two of the nine projects, so every chevron state and both pill states appear. Example edits stay in the current page’s memory and reset on navigation or reload; no sample project is ever written to your CRM. Add ?example=1 to the home or custom-view URL. Leave sample mode to return to your real account.

INSTALLING WITH AN AI AGENT?

Give it the context.
Keep your custom work.

Existing records and unrelated custom source do not require starting over. Modified integration files need a deliberate merge.

Start with the copy-and-paste prompt in INSTALL_WITH_AI.md.
Read AGENT_INSTALL.md for routes, permissions, provider wiring, backend contracts, and compatibility requirements.
Run node setup.mjs check "/path/to/seedly" before modifying files.
Preserve existing extensions, providers, account controls, custom pages, and unrelated data.
Use a reviewed merge for changed integration files; never replace them with clean copies or bypass the installer’s fingerprints.
Deploy the required write helper from the authoritative backend source before connected edits; preserve existing functions and authorization.
Build and verify account access, original CRM modules, new screens, saving, and reload behavior before publishing.

Make the workspace
feel like your team.

Edit apps/web/components/devlaunch-kitchen-bath/config.ts to set company name, descriptor, and default pipeline name, then rebuild. The design applies to the entire web installation. Use separate web installations to evaluate different full-interface kits, rather than stacking their installers.

Starter removal, updates, and rollback

Review unused starter additions for removal in Starter setup before removing the frontend. Server checks preserve edited or published workflows and pipelines with jobs or references. The process targets recorded kit additions rather than sweeping account records.

Preserve your local configuration and source edits. Preview frontend removal with node setup.mjs remove "/path/to/seedly" --dry-run. The automatic uninstaller uses a private restoration receipt and refuses to overwrite later edits. Keep that receipt private and out of public hosting or source exports. Removing frontend files does not remove account data or undeploy backend functions.

For an update, follow the documented removal/install process and reapply your preserved changes. A manually merged installation needs its own private change ledger and reviewed source rollback.

What the workspace records

One project is a native contact-linked opportunity with a namespaced project name, room type, address label, designer and lead labels, target start and finish, a derived current phase, notes, an optional contract reference, and three sets of child records with stable IDs: selections, trade schedule rows and change notes. Two projects at the same address stay independent opportunities, and other custom fields are preserved.

The current phase is the one value the kit computes: the first of the eight trades, in sequence order, that nobody recorded as done, and punch once all eight are. The server re-checks it against the project’s own trade rows, so the chevron strip can never disagree with the schedule table. Everything else is typed in. A planned window and a trade label reserve nobody, create no native Calendar appointment and resolve no conflict, which is why phase windows are allowed to overlap. Ordered and delivered are flags a person set: there is no vendor integration, purchase order, lead time feed or delivery tracking. The contract reference and change note amounts are recorded numbers, kept separate from native opportunity value, with no estimating, allowance engine or price book. A change note amount may be negative, because a change can be a credit. There is no design tool, room planner or rendering, no permit or inspection tracking, no invoicing or signatures, and no client portal or selection approval link. Selections, trade rows and change notes are archived in place, never deleted. Empty values read as words, never a dash.

The kit’s original operational screens share the frame with full CRM modules from your own Seedly source. Existing account permissions, feature gates, and configured providers still determine access to those modules.

See the interface and everything included.

Back to GoSeedly Kitchen & Bath Kit