Start with your Seedly project.
Have your own Seedly CRM 5.8.4 installation, backend, and authentication configured. Keep a private checkpoint of your source and existing customizations.
GOSEEDLY ROOFING KIT / INSTALLATION
A clear path
to your workspace.
Use a compatible Seedly installation, then choose how much of the starter kit to bring into it.
Run guided setup.
Extract the kit outside your Seedly source. From the kit folder, run node setup.mjs. The checker inspects the integration files before offering to install.
Build and connect.
Follow QUICKSTART.md to build and run your web app. For optional starter content, follow STARTER_CONTENT.md to enable its helper on the intended backend.
Choose the content
that fits your team.
Open Starter setup from the roofing sidebar. Choose among four pipeline templates and nine workflow drafts, or install neither. Sample jobs are a separate in-memory view; they do not create sample customers in your database.
Use your own pipeline.
Drafts can target an existing pipeline with the matching stage named on the workflow card. Existing stages are preserved.
Review before publishing.
The included workflows use internal tasks, optional notes, and timed waits, and stay in draft until you choose to publish them. Adjust their stages, task details, timing, and assignments to your process. A timed wait is not a completion check.
Keep what you change.
Use Manage starter content to review unused additions for removal. Edited workflows and pipelines that have jobs are kept.
WORKING WITH AN AI AGENT?
Give it the context.
Keep your custom work.
The kit includes a complete guide for installations that are already customized.
Start with INSTALL_WITH_AI.md for the copy-and-paste prompt.
AGENT_INSTALL.md maps the integration files, permissions, routes, and backend contracts.
STARTER_CONTENT.md explains optional content, its deployment, and cleanup rules.
Changed files get a reviewed merge; checks are never bypassed with a force install.
Validate the build, account access, existing custom modules, and the new workflow before publishing.
Your brand.
Your ongoing changes.
Edit the installed config.ts to set company details and crew labels. The current theme applies to the whole web installation. Keep configuration edits privately so they can be carried into future updates.
Removal and updates
Preserve local edits, preview removal with node setup.mjs remove /path/to/seedly --dry-run, then use the documented removal/install process. Removing source files does not remove CRM records. Use Starter setup first if you want to remove unused kit-created content. A manual merge uses its private change ledger for rollback instead of an automatic installer receipt.
See the interface and everything included.
Back to the Roofing Kit