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.

A job is a native contact-linked opportunity with a namespaced job type, site address label, crew label, recorded schedule window, prep notes, an immutable supported currency, rooms with their surface measurements and colors with their approval status. The recorded estimate total and the contract reference stay separate from native opportunity value. Other custom fields are preserved.

Every number is something somebody measured or typed, or arithmetic on it. A surface reference equals the recorded square footage times the coats times the per-square-foot reference, a room total equals the sum of its surfaces, and the estimate total equals the sum of the rooms that are not archived. The editor computes all three and the server re-checks them, so a sheet that does not add up cannot be stored. An archived room keeps its measurements and stops counting. The contract reference is deliberately allowed to differ from the estimate: a contract is a number two people agreed on. Nothing is invoiced, deposited, collected or signed. There is no paint brand catalog, fan deck, color matching or formula, no material ordering or gallon calculation, and no takeoff from plans. An approved color needs a recorded six-digit hex label, and a recorded crew label needs a recorded start date. Crew labels and schedule windows reserve nobody, check no availability and create no calendar entry. Nothing in the kit messages a client or asks anyone for an approval. Totals are grouped by currency and never added across currencies. The pipeline stage stays your CRM’s own: the kit adds no stage model and no stage mutation, and the recorded color approval status is a separate field.

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.