Skip to content
View packages

GoSeedly Financial Advisor Kit / INSTALLATION

A clear path
to your workspace.

Bring the kit into your compatible Seedly installation, preserve existing work, and choose the starter content that fits your team.

01

Start with your Seedly project.

Use your separately obtained Seedly CRM 5.8.4 installation with extension API 1, a configured backend, and working authentication. Keep a private source checkpoint, including existing customizations. Use Node.js 20 or newer.

02

Run guided setup.

Extract the kit outside the Seedly source folder. From the kit directory, run node setup.mjs. The check identifies supported integration files, changed files, and destination conflicts before installation.

03

Build and connect.

Deploy the included required helper from your authoritative backend source before connected edits. Follow QUICKSTART.md with your project’s existing package manager. Build the web app, sign in, and open your existing /location/YOUR_LOCATION_ID address. Verify access, navigation, and your important CRM flows.

Install the interface.
Choose the starting content.

Frontend installation and optional account content are separate. The included original household helper is required for connected creation, editing and starter setup. It checks the active account and native permissions, compares the current record timestamp and the server-managed revision, preserves unrelated custom fields and unknown child-row extensions, and invokes the native Seedly mutations inside one transaction. Deploy it from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional and no schema migration is required. Follow QUICKSTART.md and STARTER_CONTENT.md for the exact integration. The frontend installer does not deploy your backend.

Pick your starting structure.

Starter setup offers Prospect to client, Annual review cycle, Service requests, Referral partners. Select individual pipelines and drafts, or use a suitable existing pipeline with the exact stage needed by the chosen draft.

Adapt each workflow.

All nine workflows remain inactive drafts. Review their native triggers, internal tasks, notes, timing, and assignments before publishing in Seedly. Timed waits do not check whether a task is complete or the stage has changed. These examples do not send customer messages.

Explore sample mode.

Explore sixteen fictional records in the separate sample view: twelve client households placed one on each of the twelve months of the review calendar, plus four prospects, with recorded meetings and recorded service tasks. Two households are a year behind on purpose, so the overdue tray is not empty. Example edits stay in the current page’s memory and reset on navigation or reload; sample households are never inserted into your CRM. Add ?example=1 to the home or custom-view URL. Leave sample mode to return to your real account.

INSTALLING WITH AN AI AGENT?

Give it the context.
Keep your custom work.

Existing records and unrelated custom source do not require starting over. Modified integration files need a deliberate merge.

Start with the copy-and-paste prompt in INSTALL_WITH_AI.md.
Read AGENT_INSTALL.md for routes, permissions, provider wiring, backend contracts, and compatibility requirements.
Run node setup.mjs check "/path/to/seedly" before modifying files.
Preserve existing extensions, providers, account controls, custom pages, and unrelated data.
Use a reviewed merge for changed integration files; never replace them with clean copies or bypass the installer’s fingerprints.
Deploy the required write helper from the authoritative backend source before connected edits; preserve existing functions and authorization.
Build and verify account access, original CRM modules, new screens, saving, and reload behavior before publishing.

Make the workspace
feel like your team.

Edit apps/web/components/devlaunch-financial-advisor/config.ts to set practice name, descriptor, and default pipeline name, then rebuild. The design applies to the entire web installation. Use separate web installations to evaluate different full-interface kits, rather than stacking their installers.

Starter removal, updates, and rollback

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.

What the workspace records

One household relationship is a native contact-linked opportunity. Its namespace holds the household label, member labels, recorded relationship, review cadence, last and next review dates, advisor and service model labels, prospect stage, source label, custodian label, an optional annual fee reference, recorded notes, and recorded meetings and service tasks as child records with stable IDs. A client household requires a recorded next review date, a next review date can never precede a last review date, and only a prospect carries a prospect stage.

Horizon is a relationship and review-cadence workspace. It stores no account balances, holdings, positions, transactions or performance data, aggregates no accounts, and reads nothing from any custodian. The custodian entry is a label typed by staff. Review dates and cadence are recorded intent: nothing reviews, schedules, reminds, renews or advances on its own, and no calendar appointment is created. Recorded meetings describe conversations that already happened and recorded tasks are the practice’s own work. The annual fee reference is the fee your practice records for its own planning, never a balance, never assets under management, and never billed or collected. The cadence-disagreement flag is advisory and changes no date. Nothing in the kit is investment advice, a recommendation, a proposal, a suitability or fiduciary determination, an e-signature, a document vault or a compliance record.

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.