01 / ReadinessThe gate, then the dig day.
Each upcoming job carries the locate ticket reference, requested date and recorded window beside its scheduled dig day. A dig day the gate does not cover is struck through and says why.
GoSeedly Excavation & Site Work Kit
A dig-readiness board with a load and haul ledger. Grade puts the utility-locate gate beside the scheduled dig day, counts every load by material and unit, and shows where each machine is booked.
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 / ReadinessEach upcoming job carries the locate ticket reference, requested date and recorded window beside its scheduled dig day. A dig day the gate does not cover is struck through and says why.
02 / JobsSite and client labels, the company's own scope labels, the recorded job state, the dig day, the gate in words and the contract amount.
03 / BidsOpen bids ordered by their recorded due date, with the plan set revision, the bid amount and the bid age in days.
04 / LocatesEvery ticket by recorded expiry, with the state in words, the window the office typed and the days left before it runs out.
05 / Loads and haulEstimated against hauled by material label, with the loads counted, the dump or pit site and a meter per row. Cubic yards and tons are totalled separately.
06 / EquipmentMachines and trucks rolled up from the recorded assignment rows, with the days assigned, the jobs they sit on and any overlapping booking flagged.
07 / InsightsCounts by job state, barred dig days, tickets expiring within seven days, double-booked machines and loads counted. Nothing is forecast.
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 14 fictional site jobs: five open bids, nine scheduled or active jobs with six cleared gates and three barred dig days, 22 haul rows across cubic yards and tons, and eight machines with one double booking. 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 site job holds the site and client labels, scope labels, plan set revision, bid and contract amounts, the locate ticket reference with its requested, valid-from and expires dates, the scheduled dig day, haul rows, equipment assignment rows and an editable 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 business 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 record creation, edits and resource setup. They preserve native account permissions, unrelated custom fields and row history, enforce the locate, haul and equipment rules on the server, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
The gate clears only when a cleared ticket is recorded and the dig day falls inside the recorded window. The kit does not submit, renew or look up a one-call ticket, does not determine that it is safe or lawful to dig, and does not replace the locate service or any duty of care. There is no takeoff from plans, no GPS or telematics, no scale-ticket integration, no scheduling engine and no messaging.
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.
Grade retains its application frame 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.