Tagged in at the counter. Handed back from the rack.
A counter workspace for dry cleaners: every drop-off counted with the customer, each piece through cleaning, pressing and assembly, the ready rack with days on the rack against your own hold, alteration work against its promise, and the orders still waiting. Hangtag keeps intake, the shop floor, the rack and alterations in one connected workspace.
Orders past their promise, past your recorded hold or with late alteration work lead. Then the ready rail hangs each bagged order by slot, oldest first, with days on the rack against its hold, and claim slips show every order still in the shop with each piece's stage.
Drop-offs from the last 14 days grouped by day, with pieces by service, the marks the customer pointed out, who took it in, the promised date and time and the recorded amount.
Tagged, cleaning, pressing and assembly lanes of piece cards, each lane counted in pieces, with the order's promised date and any open alteration work.
Orders on the rack by slot with days on the rack, the hold you recorded for each order, reminders logged and payment status as recorded, then recent pickups.
Orders past the hold your shop recorded, orders within seven days of it, and every reminder the office logged. Hangtag sends nothing and gives no legal guidance.
Pieces in process by stage, pieces by service, orders by customer, alterations by work and reminders by method. Pieces, days and dollars are never added together.
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.
Counter orders · 8 stages
Alterations · 7 stages
Uncollected follow-up · 7 stages
Business accounts · 7 stages
02 / NINE WORKFLOW DRAFTS
Give the next step a shape.
Piece count confirmation
Promised date check
Ready notice task
Pickup close-out
Alteration write-up
Alteration return check
First uncollected reminder
Final notice review
Business account review
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 12 fictional orders: six in process (two dropped off today), four on the ready rack and two picked up, with 85 pieces, 5 alteration rows and 4 logged reminders. Sample edits stay in memory and reset on navigation or reload.
No sample customers are inserted into your CRM.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
MORE OF THE WORKING DAY
From the first inquiry to the final handoff.
Editable native forms and document templates give your team a practical starting point.
01 / INTAKE & FOLLOW-UP
Three ready-to-edit forms.
Drop-off note
Alteration request
Business account inquiry
Choose forms individually in Setup & resources, then customize and publish them in the native form builder.
02 / WORKING DOCUMENTS
Three reusable templates.
Counter claim slip
Alteration work order
Uncollected order notice
Open each template in Documents and complete it for the actual job or visit.
03 / THE NEXT STEP
Checklists alongside the work.
Record progress and notes in the kit’s operating views. Keep earlier rows by archiving them, and retain the context for the next person.
Forms collect information for staff review. They do not automatically change the kit’s custom records. Repeating setup preserves existing resource edits.
THE KIT, UNPACKED
Your workspace. Your starting point. Your code to edit.
One contact-linked order holds the claim number, drop-off and promised dates, each piece with its service, count and stage, any spot or mark the customer pointed out, alteration work, the rack date and slot, your recorded hold in days, reminders logged and an editable checklist.
Counter operating view
Intake operating view
Production operating view
Ready rack operating view
Uncollected operating view
Alterations operating view
Insights operating view
Three native form drafts and three editable document templates
Editable order checklists and preserved row history
Four optional pipeline templates and nine inactive workflow drafts
12 fictional in-memory orders
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 business 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 backend helpers are required for connected order creation, edits and resource setup. They preserve native account permissions, unrelated custom fields and row history, refuse access codes, logins, card numbers and Social Security numbers, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
Hangtag records what the shop counted, what the customer pointed out and what the shop did. It does not promise how a spot or mark comes out, give fabric-care advice, say what may happen to an uncollected order, run a point of sale, take payments, plan routes, connect to machines or send reminders. Drop locker, door, gate and alarm codes, Wi-Fi and app logins, payment card numbers and Social Security numbers are refused in recorded text and in the native form drafts.
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?+
Hangtag keeps its frost side rail of hang tags across the kit views and native CRM tools in the same signed-in account. 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.