GoSeedly Bathtub & Tile Reglazing Kit
A day route for bathtub and tile reglazing companies: each technician's stops in order with the surfaces, access and a keep-dry strip that shows when each tub is back in use, from the finish time and the keep-dry hours your office records. Glazeday keeps photo estimates, the route week, surfaces, rental unit turns and warranty dates in one connected workspace.
YOUR GLAZEDAY WORKSPACE
01 — DAY ROUTE
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 / Day routeToday's route with one lane per technician and stops in order. Each stop shows the arrival window, the surfaces with their colors, access confirmed or not, and a keep-dry strip on one hour scale with the back-in-use time and the need-by. Jobs with access not confirmed, keep-dry running past the need-by, a passed route day or a warranty call past its promise lead.
02 / WeekA technician by day grid of the next seven route days, with any past route day not recorded done in its own first column.
03 / EstimatesOpen estimates with photo status, surfaces, days open and the quoted amount, accepted jobs waiting for a route day with their need-by, and every quote answered in the last 60 days.
04 / SurfacesEvery tub, tile surround, shower pan, tile floor, sink and countertop on an open job with its color as chosen and the chips or repairs noted. Square feet are kept for tile and countertops only.
05 / Unit turnsProperty manager jobs grouped by property, each unit with its route day, back-in-use time, move-in date as the manager gave it and access.
06 / WarrantyReglazed jobs with the term as written and the warranty-through date, the ones ending soonest first, then warranty calls with any past their promised date leading.
07 / InsightsJobs by stage, surfaces by kind, recorded square feet, jobs by recorded keep-dry hours, quotes by status and warranty calls by issue. Hours, square feet, 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: two estimates, one accepted job waiting for a route day, six jobs on a route (one past its route day) and three reglazed jobs, with 22 surfaces, 2 warranty calls and three rental unit turns. 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 and unit, the photo estimate and quote, the route day, stop and arrival window, access, the finish time, keep-dry hours and need-by as recorded, the warranty term as written, surfaces, warranty calls 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, 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.
Glazeday records what the office was told and wrote down. Keep-dry hours are your office's own durations; Glazeday adds them to the finish time and predicts nothing. It does not recommend coatings or products, give chemistry, ventilation or curing advice, make health or safety claims, decide warranty coverage, optimize routes, connect to property management systems, bill or send messages. Gate, door, lockbox and alarm codes, portal 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.
Glazeday keeps its white route rail 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.