GoSeedly Jewelry Store Kit
An independent jeweler runs on the numbered envelope a repair or a custom piece travels in. Facet draws every open job as an envelope card sorted by promised date, past-promised first, with the five stops it moves through, and puts the customers’ recorded anniversaries and birthdays in the column beside it. Picked up envelopes stay out of the rack until you filter for them, and the Jobs ledger always lists every stop.
YOUR FACET ENVELOPE RACK
01 — RACK
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 / RackEach open job is an envelope card: the number in large figures, the item in the store’s own words, the job kind, a five-stop line from the counter to picked up, the promised date and the recorded estimate and deposit. Picked up envelopes are hidden here by default and reachable through the stop filter. Beside the rack, the occasions inside their recorded lead days.
02 / JobsNumber, customer, item, job kind, where the envelope is now, days at that stop, the promised date and the recorded estimate, deposit and balance.
03 / Custom designCustom commissions counted across sketch, quote, deposit, CAD or wax approval, casting, setting and final approval, with whether an approval has been recorded and on what date.
04 / Out to tradeEnvelopes at an outside shop with the shop label, the date they were sent and the expected return, and a written label when one is past that date.
05 / Ready for pickupEnvelopes recorded as ready and not collected, with the date they were finished, the days waiting, whether a notification was recorded and the balance due.
06 / Clients and occasionsEvery client with their envelopes, their wish list labels in plain words, and their recorded occasions as a month and a day with the lead days and whether outreach was recorded.
07 / InsightsPast promised, awaiting approval, past expected return and no notification recorded, each one a filter back into the rack. No forecasts and no valuations.
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 20 fictional job envelopes across all five stops and all five job kinds, with 5 custom commissions, 4 envelopes out to trade, 5 ready for pickup, 12 clients and 12 recorded occasions. Sample edits stay in memory and reset on navigation or reload.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
MORE OF THE WORKING DAY
Editable native forms and document templates give your team a practical starting point.
Choose forms individually in Setup & resources, then customize and publish them in the native form builder.
Open each template in Documents and complete it for the actual job or visit.
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
One contact-linked opportunity is one job envelope: envelope number, customer label, the item description in the store’s own words, job kind, the stop it is at with the date it reached it, promised date, estimate and deposit as recorded references, a take-in condition flag and text, the custom stage with its approval flag and date, the trade shop label with sent and expected dates, the notified flag, the picked-up date, recorded occasions, wish list labels and a job checklist.
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 store 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 backend helpers are required for connected envelope creation, edits and resource setup. They preserve native account permissions, unrelated custom fields and row history, check revisions before saving, and enforce the domain rules on the server as well as in the browser. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
Past promised, days at stop, days waiting, trade jobs past their expected return, occasions inside their lead days and balance due are derived when the page is read and are never stored. Occasions record a month and a day with no year. The kit is not an appraisal, valuation, grading or authenticity tool, not insurance documentation, not an inventory or point-of-sale system, not memo or consignment accounting, not a metal or gemstone price feed, not a payment or layaway processor, not a scheduling engine and not a messaging system. It never stores payment card data or government identifiers and refuses free text that looks like either.
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.
Facet keeps its true-black rail and white canvas 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.
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.