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 booking is a native contact-linked opportunity with namespaced property address, property type, year built and floor area references, booking date, an HH:mm arrival window, inspector, referring agent and brokerage labels, client side, up to eight recorded add-on labels, a fee reference in integer minor units, the recorded report delivery step, report due and delivered dates, notes and follow-up rows with stable IDs. Other custom fields are preserved, and archived follow-up rows are kept rather than dropped.

This kit never contains the report. There is no report writing, no report template, no narrative library, no defect rating, no photo storage, no image annotation and no lab result; it records only that a report is drafted and delivered. There is no scheduling engine, availability model, double-booking prevention or travel-time calculation: booking dates and arrival windows are recorded plans that reserve nothing and create no Calendar appointment, and two cards may overlap on the same day without comment. Recording radon, a sewer scope, termite, pool and spa, mold sampling, well water, thermal imaging or crawlspace work orders nothing, schedules no subcontractor, prices nothing and records no result. There is no agent or client portal, no shared link and no messaging: the referrals ledger is an internal view of labels somebody typed, and nothing texts, calls or emails a client, an agent or an inspector. It makes no claim about any jurisdiction’s inspector licensing, standards of practice, report content requirements, retention rules or insurance. The recorded delivery step is a staff entry independent of the native pipeline stage, and saving booking details never moves a deal. A booking counts as due only when it has been inspected or drafted and records a due date, and the recorded on-time delivery rate excludes any delivered booking missing either date rather than counting it late. The fee reference is a recorded planning number, separate from opportunity value, estimates, invoices and payments.

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.