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 service address label, request summary, handyman label, recorded request and planned visit dates, priority, job notes, an immutable supported currency, and three archive-only child collections with stable IDs: task rows with a quarter hour estimate and a done flag, material rows with a whole quantity and an on hand flag, and visit rows with a date, a handyman label, recorded actual hours, an outcome and a note. The recorded quoted reference stays separate from native opportunity value. Other custom fields are preserved.

Every hour figure, both a task estimate and a recorded actual, must be a quarter hour from 0.25 to 24. A value that is not a multiple of a quarter hour is refused rather than rounded, because rounding somebody’s estimate is editing it, and quarter hours are exactly representable so a card total never drifts. Nothing multiplies an hour by anything: there is no hourly rate, labor rate table, price book, markup, margin or pricing advice anywhere in the kit. A job that has not been itemized reports No tasks recorded rather than zero hours and draws no bar at all. Evidence-based rules are identical on create and on save and re-checked by the server: a recorded handyman requires a recorded visit date, a visit date may not precede the recorded request date, and a task can only be recorded done once the job records a visit, because a punch list cannot tick itself. Three non-rules are deliberate: a visit log date is not constrained against the planned date because work slips and work gets pulled forward, two visit rows may share a date, and recorded actual hours are never constrained against the estimate. A recorded visit date and handyman label reserve nobody and create no calendar appointment; there is no scheduling engine, availability check, capacity model or calendar sync. A material’s on hand flag is a note about the van, not a stock level, and the kit orders nothing from anybody. There is no route optimization, GPS or drive time estimate, no invoicing or payments, no customer messaging of any kind, and no timekeeping or payroll. 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 ticking a task never moves a card and moving a card never ticks a task.

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.