GoSeedly Business Coaching Kit / INSTALLATION
Bring the kit into your compatible Seedly installation, preserve existing work, and choose the starter content that fits your team.
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.
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.
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.
Frontend installation and optional account content are separate. The included original coaching helper is required for connected creation, editing and starter setup. It checks the active account, native permissions, the captured record timestamp and a server-owned namespace revision, enforces every cross-field rule on both create and save, preserves unrelated custom fields and unknown session extensions, and invokes the native Seedly mutations inside one transaction. It exposes no stage mutation, so moving a card stays the host’s own. Deploy it from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional. Follow QUICKSTART.md and STARTER_CONTENT.md for the exact integration. The frontend installer does not deploy your backend.
Starter setup offers Discovery to enrollment, Cohort program, One-to-one coaching, Alumni and referrals. Select individual pipelines and drafts, or use a suitable existing pipeline with the exact stage needed by the chosen draft.
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 three fictional cohorts holding fourteen fictional cohort members, five fictional one-to-one clients and four fictional prospects, with their recorded session journal entries. Example edits stay in the current page’s memory and reset on navigation or reload; sample engagements 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?
Existing records and unrelated custom source do not require starting over. Modified integration files need a deliberate merge.
Edit apps/web/components/devlaunch-business-coaching/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.
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 client engagement is a native contact-linked opportunity with namespaced coaching details: engagement type, program or cohort label, coach label, session cadence, start and next session dates, recorded scheduled session count, up to eight business goal labels, discovery call date and outcome label, a package reference in integer minor units, and session rows with stable IDs. The same person coached twice, once in a cohort and once privately, is two engagements.
A session row is a record of a conversation that already happened. There is no video call, meeting link, recording or transcript, and no scheduling engine, booking page, availability, calendar sync, reminder or rescheduling: a recorded next session date is a date somebody typed. A recorded package reference is a number somebody wrote down, never an invoice, charge, subscription or recognized revenue, and it is never written into native opportunity value. Business goal labels are business outcomes only, never health, medical, therapeutic, psychological, financial-advice or legal categories, and the kit performs no assessment, scoring or profiling. Recorded attendance is attendance somebody wrote down; it predicts no outcome and guarantees nothing. Session records are archived, never deleted.
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.
See the interface and everything included.
Back to GoSeedly Business Coaching KitWe use essential storage to keep the site working. With your permission, we also use analytics and the Whop Pixel to understand visits and advertising results. Optional analytics stay off until you choose.
Read our Cookie Policy and Privacy Policy.