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 build is a native contact-linked opportunity with namespaced lot, community, plan and elevation labels, a contract reference, superintendent and selections coordinator labels, a recorded phase, one recorded date per phase, a closing target date, allowance rows and change order rows. The lot register lives in its own account settings key beside the starter receipt. Recorded references are never written into native opportunity value.

A recorded allowance is a number somebody typed. The kit does no estimating, takeoff, bid levelling, vendor pricing, job costing, draw scheduling or accounting. The over or under reference must equal the recorded selection minus the recorded allowance, and the server refuses a row where it does not; rows missing either reference are excluded from the net and counted, so a partial ledger is never reported as complete. Phase dates are records somebody entered: nothing schedules, reschedules, dispatches a trade partner, orders material, files a permit or requests an inspection. The recorded closing target date is a date, not a closing, and nothing in the kit contacts a buyer, a trade partner or a lender. Change order statuses are notes, not signatures, addenda or invoices. The recorded phase is separate from the native pipeline stage: saving a build never moves a card. Totals are grouped by currency and never summed across currencies.

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.