GoSeedly Wedding & Event Planner Kit
A planner does not work a funnel. A planner works a date that cannot move. Countdown puts the days remaining at the top of every event card, then measures the milestone tasks, the run of show and the vendor sheet back from that one number.
YOUR COUNTDOWN BOARD
01 — COUNTDOWN 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 / Countdown boardEvery event is a card led by a large serif day counter, sorted by days remaining. Under it sit the five weeks-before milestone buckets, each showing how many recorded tasks are done, due and overdue. The event type, date, venue, planner, guest count and budget reference sit on the card.
02 / Event recordSelecting a card tints it and opens the record panel: the brief, the milestone buckets with their derived target dates, the recorded guest and RSVP tallies, the vendor sheet, the run of show and the next step. One control records the next open milestone task as done.
03 / EventsA table of every event record in the selected pipeline, nearest recorded date first, with its countdown, venue, planner, recorded guest count and the number of milestone tasks still open. Overdue counts are flagged separately.
04 / Run of showThe recorded event day timeline for the selected event: a time, an item, an owner label and a vendor label, in recorded time order. These are notes the studio typed. Nothing here is a schedule, a booking or a reminder.
05 / Vendor sheetRecorded vendors across every event, grouped by category, with the contact label, the contract status label, the deposit reference and the recorded balance due date. Nothing is signed, invoiced, charged or sent from the workspace.
06 / Guests and RSVPsA tally sheet rather than a guest list manager. The recorded guest count and the accepted and declined tallies are numbers a person typed, with the response share derived from them. No invitation is sent and no reply is collected.
07 / Studio insightsEvents grouped into countdown bands, milestone completion for each weeks-before bucket with its overdue count, and recorded vendor contract statuses for the selected pipeline. Every number comes from an entered record.
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 eight fictional events at different countdowns, from an event two days out to one more than two hundred days away, each with milestone tasks in every weeks-before bucket, recorded run-of-show entries and a recorded vendor sheet. Example edits stay in the current page’s memory and reset on navigation or reload; sample events 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 event is a native contact-linked opportunity with a recorded event type, event date, venue label, lead planner label, guest count, accepted and declined RSVP tallies, a budget reference, a brief note and a next-step note. Milestone tasks, run-of-show entries and vendor records are stable-ID child records. Unrelated custom fields are preserved and stale record versions are rejected.
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 company 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 planner helper is required for connected creation, editing and starter setup. It preserves native account permissions and unrelated custom fields, keeps the five recorded milestone bucket keys and the stable milestone task, run-of-show and vendor IDs, and checks the current record state before saving. Deploy it from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional.
Milestone tasks, run-of-show entries and vendor records are staff entered; nothing advances on its own. A bucket target date is derived from the recorded event date, and a task is overdue only when it is not done and that target has already passed. The kit collects no RSVPs, manages no guest list and builds no seating chart. It sends no message, books no calendar and checks no availability. It prepares, sends and signs no contract, takes no deposit and records no payment. The budget and deposit references are recorded numbers, separate from opportunity value, invoicing and payments, and are never summed into a ledger.
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.
Countdown keeps its event navigation across the original planning views and 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.