A gift shop lives on the order somebody paid a deposit on three weeks ago. Ribbon puts a fourteen day pickup strip on a white canvas under a zinc charcoal bar, with a turquoise ready state and a gift wrap flag drawn right on the card.
Each day column holds the orders due for pickup that day as compact cards, with the customer label, the item count, a gift wrap flag and the readiness word. The corporate accounts row sits underneath, and a past due strip appears when an order has slipped.
Open a card to edit the order type, pickup date, wrap request, message card text and readiness, then the item rows with their quantities and personalization labels. Recipient rows appear only on a corporate order.
Every order in the selected pipeline as one ruled table, with a countdown that reads in words, the sourced count against the item count, the recipient count on corporate orders and the recorded total. The stage select beside each row is the native CRM control.
Corporate accounts are grouped by the label somebody typed, ordered by the next recorded order date. Under each account sit the recipient rows of its orders, with the address label, a delivered marker and the order they belong to.
Seasonal orders are grouped by recorded season label with the most recent reorder date on the group head. It is the list somebody reads in September to decide what to buy again before the season arrives.
Readiness and order type counts, orders per day across the fourteen day window, item rows against units, sourced against not sourced, recipients delivered, and recorded totals grouped by currency.
YOUR PROCESS, YOUR STARTING POINT
Useful structure. Only what you choose.
4 pipelines and 9 workflow drafts. Add the parts that match your work, with a separate sample view for exploring the interface.
01 / FOUR PIPELINES
Choose your starting structure.
Use a ready-made stage sequence or connect drafts to a suitable existing pipeline.
Custom orders · 8 stages
Corporate gifting · 7 stages
Seasonal and holiday orders · 7 stages
Wholesale and consignment · 7 stages
02 / NINE WORKFLOW DRAFTS
Give the next step a shape.
Order confirmation note
Personalization check task
Item sourcing task
Ready for pickup task
Post-pickup thank-you task
Corporate recipient list task
Delivery confirmation note
Pickup reminder
Seasonal reorder reminder
Native trigger, task, wait, and note nodes provide editable examples. Every draft stays inactive until you review and publish it.
03 / SAMPLE WORKSPACE
Explore before adding records.
Explore sixteen fictional orders in the separate sample view, with thirty-three item rows and seventeen recipient rows across three corporate accounts. Fifteen sit inside the fourteen day window and one is past due. Example edits stay in the current page’s memory and reset on navigation or reload; sample orders are never inserted into your CRM.
No sample customers are inserted into your CRM.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
THE KIT, UNPACKED
Your workspace. Your starting point. Your code to edit.
One order is a native contact-linked opportunity with a namespaced order type, pickup date, gift wrap flag, message card text, readiness state, season label, corporate account label, last reorder date, an optional order total and notes, plus item rows and recipient rows with stable IDs. Other custom fields are preserved.
Fourteen day pickup strip with a corporate accounts row, past due and undated strips
Order sheet with item rows and corporate recipient rows
All orders table by recorded pickup date with the native stage control
Corporate account and seasonal reorder groupings
Shop insights drawn from recorded workspace data
Zinc charcoal and turquoise Ribbon application frame with full CRM tools
Four optional pipeline templates and nine inactive workflow drafts
Sixteen fictional in-memory orders with thirty-three item rows and seventeen recipient rows
Guided setup, compatibility report, and private rollback receipt
AI-agent documentation for customized installations
Original editable source, configuration, and tests
Run the guided setup from the extracted kit. Supported integrations can be installed directly; customized integration files get a reviewed merge.
02
Connect the required helper.
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.
03
Set up your own team.
Edit shop name, descriptor, and default pipeline name. Sign in with your account and verify the workflows and permissions your team uses.
Compatibility and operational details
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 gift shop helper is required for connected creation, editing and starter setup. It preserves native account permissions and unrelated custom fields, re-checks every cross-field rule, and compares the current record timestamp and order revision before saving. Deploy it from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional.
Readiness, the sourced flag and the delivered flag are staff-entered records. A recorded pickup date reserves nothing, creates no native Calendar appointment and sends no reminder; a date that has passed moves the order into a past due strip rather than hiding it. Seven cross-field rules are enforced on both the client and the server: a ready or picked up order needs a pickup date, a picked up order needs every item recorded sourced, a corporate order needs a corporate account, only a corporate order records recipients, a seasonal order needs a season label, a reorder date belongs to a seasonal order, and a recipient is only recorded delivered once the order is ready. The kit has no point of sale, inventory, product catalog, supplier ordering, shipping, payment processing, customer messaging or storefront.
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.
Checking access…
DEVLAUNCH ALL ACCESS
Every kit. And everything else.
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.
All 195 CRM kits
Every published kit as original editable source, with optional pipelines, workflow drafts, and guided installers. Browse the kits
Every class, course, and product
The full DevLaunch library and software collection, plus each eligible release during your access year, added to your portal as it ships.
Private calls with Aaron
Bring the idea, the offer, or the bottleneck, and leave with a plan you can follow.
DevLaunch All Access
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.
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
Good questions. Clear answers.
How do I receive the kit?+
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.
Does this include Seedly CRM?+
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.
Is this one connected workspace?+
Ribbon keeps its single chrome bar across the original gift shop 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.
Can I use it with existing customizations?+
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.
Do I have to import all the starter content?+
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.
Can I remove the examples and starter content?+
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.
Can different subaccounts use different kits?+
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.
Selected excerpts from reviews of DevLaunch training, software, and services. Individual customer experiences across DevLaunch.
Your privacy, your choice.
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.