GoSeedly Business Directory Kit
A directory is a category tree before it is anything else. Listed builds the category rail out of the listing records themselves, puts the searchable listing grid beside it, and opens the selected listing in a sheet that holds its claim record, its placement record and its inquiries. White chrome, one magenta accent.
YOUR LISTED DIRECTORY DESK
01 — DIRECTORY
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 / DirectoryEvery recorded category label with its listing count sits on the left, the searchable listing grid in the middle, and the listing sheet on the right. Grid rows carry the business name, the category, the city label, a plan tier chip, a claim badge and the recorded renewal date. A category exists because listings say it does; rename it on the listings and the rail changes with them.
02 / Claim requestsRecorded claim requests ordered so the ones somebody is waiting on lead: pending verification, then rejected, then verified. Each row shows the listing, the claimed by label, the recorded claim date and the verification status. Verification is a recorded staff decision, not an ownership check.
03 / PlacementsEvery featured and premium listing grouped from the directory date you choose: already past its recorded renewal date, then due in 30 days, 31 to 60, 61 to 90 and later. Each row shows the tier, the recorded start, the renewal date and the monthly reference. Nothing expires on its own.
04 / InquiriesEvery recorded inquiry across all listings, newest first, with its listing, date, inquirer label, message summary and routing status, filterable by status. An inquiry records what the office already did with it. The kit sends no email and forwards no message.
05 / CategoriesEvery recorded category label with its listing count, its claimed count and how many of its listings sit on a paid tier. All three are derived from the listing records loaded for the selected pipeline, not from a separate category table.
06 / InsightsThe listing mix by plan tier, the recorded claim rate, inquiry routing counts that exclude archived rows, and the monthly placement reference total reported once per currency present rather than added across currencies.
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 twelve fictional listings across six recorded categories, with their claims, placements and inquiries. Example edits stay in the current page’s memory and reset on navigation or reload; sample listings are never inserted into your CRM.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
THE KIT, UNPACKED
A listing is a native contact-linked opportunity with a namespaced business name, category and subcategory labels, city label, website and phone labels, plan tier, claim record, placement record with its monthly reference, listing notes and inquiry records. The monthly placement reference stays separate from native opportunity value. Two listings for the same business in two categories stay independent. Other custom fields are preserved.
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 directory helper is required for connected creation, editing and starter setup. It preserves native account permissions and unrelated custom fields, and checks the current record state before saving. It exposes no stage mutation at all: the listing sheet’s stage control calls the host’s own pipeline mutation under the same permission, so saving listing details never moves a listing. Deploy the helper from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional.
Nothing here is public. There is no directory frontend, no publishing, no SEO, no sitemap and no search ranking, and the website and phone labels are labels. There is no map, geocoding or proximity search, and no scraping, data import or third-party listing feed. Claim verification is a recorded staff decision: no ownership is checked, no document is inspected and no owner is contacted. An inquiry’s routing status records what the office already did; nothing is forwarded or messaged. Placements collect no payment, and a renewal date that has passed is shown as past without changing a tier or cancelling anything. The recorded claim rate returns unavailable rather than an invented zero when there is no valid listing, and reference totals are never added across currencies.
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.
Listed keeps its directory navigation across the original directory 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.