A clear path
to your workspace.

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.

One showroom visit is a native contact-linked opportunity with a namespaced visit name, recorded visit date, room labels, a whole square footage reference, a budget band, a salesperson label, visit notes, an immutable supported currency, a quote group of amount in minor units, quoted date, decision and decision date, an installer handoff group of partner label, handoff date and install target date, and archive-only sample rows with stable IDs carrying a product label, a category and its checked out, due back and returned dates. The recorded quote amount stays separate from native opportunity value. Other custom fields are preserved.

Eleven cross-field rules are validated by one shared implementation used by the editor, every view and the server, identically on create and on save: a board cannot be checked out before the recorded visit date, a due back or returned date cannot precede the checked out date, a recorded quote needs both an amount and a quoted date, an unquoted visit cannot hide a draft amount or date, a recorded decision needs a decision date while a quote still waiting must leave it blank, a decision date cannot precede the quoted date, a quoted date cannot precede the visit date, a handoff needs both a partner label and a handoff date, a handoff requires an accepted quote, and an install target date requires a recorded handoff it cannot precede. Four non-rules are deliberate: a returned date is never constrained against a due back date because a board that came back late is still back, two boards of one product may sit on one visit, an install target never waits for a board to come home, and a quote amount is never constrained against the square footage or the budget band. Nothing prices anything: there is no product catalog, price book, square-foot rate, markup, margin or pricing advice, and the recorded square footage is never multiplied by anything. A recorded due back date reminds nobody, because the kit sends no message, email or text of any kind and a workflow draft writes an internal task or note only. A recorded handoff reserves no installer, checks no availability, builds no install schedule and creates no calendar appointment. A sample row is a record of a board somebody took home, not a stock level: the kit holds no inventory, reads no supplier catalog and orders nothing. There is no point of sale, no invoicing and no payments. Day counts are calendar arithmetic at UTC noon, so they never shift across a daylight saving boundary. Totals are grouped by currency and never added across currencies. The pipeline stage stays your CRM’s own: the helper exposes no stage mutation at all, so recording a returned board never moves a card and moving a card never rewrites a recorded sample, quote or handoff.

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.