GoSeedly Demolition Contractor Kit
A job board for demolition contractors: every awarded job in its docket with the permit, utility disconnect and asbestos survey status as labels the office recorded, and every haul-off load until it leaves the site. Razeline keeps bids, paperwork, crew starts, haul-off and closeout in one connected workspace.
YOUR RAZELINE WORKSPACE
01 — JOB BOARD
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 / Job boardFour docket columns: awarded, start booked, underway and haul-off and closeout. Each card carries six paperwork tags (permit, electric, gas, water, sewer and asbestos survey) with the status word the office recorded, and one pip per load. A passed start date, a passed paperwork follow-up, a load past its promised date and a passed target finish lead.
02 / BidsSite walks and open bids with the bid sent date and days open, then jobs awarded and lost in the last 60 days with the recorded bid amount.
03 / PaperworkPermits, utility disconnects and surveys in their own ledgers with the agency, utility or surveyor, the status, reference and dates as the office recorded them, passed follow-ups first. Labels only: Razeline never says a site is safe or cleared and never decides whether demolition may proceed.
04 / Crew daysUnderway jobs with the started date, target finish and planned crew days, then booked starts by date with each job's labels in words, then awarded jobs with no start booked.
05 / Haul-offRequested and on-site loads, past their promise first, then the hauled ledger with destination, ticket reference and the tons printed on the ticket, then cancelled loads.
06 / CloseoutJobs with demolition finished and not closed, with loads still open and the final walk booked, then jobs closed in the last 60 days.
07 / InsightsJobs by docket, paperwork rows by kind and status, loads by state, recorded tons by material, planned crew days by job kind and bid amounts by job kind. Loads, tons, days and dollars are never added together.
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 12 fictional jobs: eight on the board (two awarded, two with a start booked, two underway and two in haul-off and closeout), two open bids, one lost and one closed, with 52 paperwork rows, 15 loads and 96 checklist steps. 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 job holds the site walk, bid and award, the booked start, started, target finish, finished, final walk and closed dates, planned crew days, each permit, disconnect and survey row with its status, reference and dates as recorded, each load with its size, material, dates, destination, ticket and tons, 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 job creation, edits and resource setup. They preserve native account permissions, unrelated custom fields and row history, keep paperwork labels exactly as recorded, 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.
Razeline records what the office requested, has on file and hauled. Paperwork statuses are labels only: it never says a site is safe, cleared, abated or compliant, gives no abatement, disposal or safety advice and never decides whether demolition may proceed. It does not read survey reports, file permits, order disconnects, connect to scales or GPS, route crews, book calendars, bill or send messages. Gate, lockbox, key safe, Supra, Knox box, door 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.
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.
Razeline keeps its concrete top bar and hatch band 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.