GoSeedly Business Coaching Kit
A coaching practice runs three clocks at once. Cadence gives each one its own surface: a cohort board for group programs, a cadence list for private clients, and a discovery log for the people who have only had a first call. A session journal sits underneath all three.
YOUR CADENCE COACHING WORKSPACE
01 — COHORT BOARD
Actual interface captures with fictional sample data. Open a screenshot for a closer look.
TAKE A CLOSER LOOK
One connected workspace, with views built around the decisions your team makes each day.
01 / Cohort boardColumns are grouped from the program or cohort label your team typed, so a cohort appears as soon as somebody records one. Each column head carries its earliest recorded start date, its member count and its recorded session count, and each member card shows the coach label, an attendance meter and the recorded next session date.
02 / ClientsEvery engagement in the selected pipeline, whatever its recorded type, with the program or cohort label, coach label, recorded cadence, start date, next session date, attended of scheduled and the recorded package reference. Filter by recorded engagement type.
03 / One-to-onePrivate clients grouped by the cadence somebody recorded, with the coach label, recorded dates, attendance and the business goal labels the engagement is working toward. Cadence coverage is printed with its denominator.
04 / Discovery callsEngagements recorded as prospects, newest recorded call date first, with the recorded outcome label, program interest, coach label and goal labels. A prospect records no sessions and a scheduled count of zero, because nothing has started yet.
05 / Session journalEvery recorded session in reverse chronological order, with the recorded summary set in a serif so a written-down conversation reads differently from a field. The filter rail beside it prints how many sessions each filter would show, so filtering never hides how much was filtered out.
06 / InsightsEngagement counts by recorded type, recorded attendance against recorded scheduled counts, recorded discovery outcomes and recorded package references grouped by currency. Every figure prints its denominator and reports "None recorded" rather than an invented zero.
YOUR PROCESS, YOUR STARTING POINT
4 pipelines and 9 workflow drafts. Add the parts that match your work, with a separate sample view for exploring the interface.
Use a ready-made stage sequence or connect drafts to a suitable existing pipeline.
Native trigger, task, wait, and note nodes provide editable examples. Every draft stays inactive until you review and publish it.
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.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
THE KIT, UNPACKED
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.
FROM KIT TO CONNECTED WORKSPACE
Run the guided setup from the extracted kit. Supported integrations can be installed directly; customized integration files get a reviewed merge.
Deploy the included helper from your authoritative backend source before connected edits. Build your web app, then choose any optional pipelines and drafts you need.
Edit practice name, descriptor, and default pipeline name. Sign in with your account and verify the workflows and permissions your team uses.
Seedly CRM 5.8.4 · extension API 1. Node.js 20 or newer. The installer checks supported integration-file versions and does not deploy your web app or backend. 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.
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.
Calling, messaging, signing, payments, and external integrations depend on your Seedly installation, account permissions, plan, and configured providers. Screenshots use sample data and reference imagery. Hosting, installation, and ongoing maintenance are your responsibility.
DEVLAUNCH ALL ACCESS
DevLaunch All Access includes every GoSeedly CRM kit, all 195 available today, along with every class, course, and product we release, and private calls with Aaron.
Every published kit as original editable source, with optional pipelines, workflow drafts, and guided installers. Browse the kits
The full DevLaunch library and software collection, plus each eligible release during your access year, added to your portal as it ships.
Bring the idea, the offer, or the bottleneck, and leave with a plan you can follow.
Want more than one kit? All Access covers the whole CRM kit library and the rest of what we make. See everything it includes on the All Access page.
See DevLaunch All AccessAlready a member? Open your downloads.
For your own compatible Seedly CRM. Seedly software, hosting and installation services are separate. Each full-interface kit uses its own web installation.
BEFORE YOU MAKE IT YOURS
Purchase securely through Whop. Your original source ZIP and installation documentation are delivered manually to the email used at checkout. This is a one-time purchase of this kit; Seedly software, hosting, and installation services are separate.
You obtain and configure Seedly separately. The kit adds original frontend screens, a shared theme, starter definitions, and integration instructions. It does not include Seedly’s codebase, license, hosting, or a separate CRM database.
Cadence keeps its coaching navigation across the original views and the native CRM modules. Full CRM tools remain available within the same signed-in account and application theme. Contacts, Calendar, Estimates, Documents, and other full modules retain the functionality supplied by your own Seedly installation. Existing authored content and provider screens retain their own layouts.
Yes, with a compatibility review. The installer checks the supported integration files. Changed integration files need a reviewed merge; the included AI-agent guide explains how to preserve custom extensions, permissions, providers, and routes.
No. Choose individual pipelines and workflow drafts, use a compatible existing pipeline, or install none. Workflows remain inactive until reviewed and published. They use native triggers, internal tasks, optional notes, and timed waits. A wait does not verify task completion or recheck the current stage. The included drafts do not send customer messages.
Sample records stay in memory and never create customers in your CRM. Leave sample mode to return to your account. Starter setup lets you review removal of unused kit additions; server checks retain edited or published workflows and pipelines with live work or references. Removing the frontend does not delete account records.
The current design and branding apply to the whole web installation. Subaccounts still separate data and access. Use a separate web installation for another full-interface kit; running different kit designs by subaccount in one installation requires additional customization.
Find a workspace that fits the way you work.
Explore all CRM kitsCustomer experiences / Trustpilot
Selected excerpts from reviews of DevLaunch training, software, and services. Individual customer experiences across DevLaunch.
We 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.