01 / Window scheduleEvery window, room by room.
One schedule sheet per open project, led by projects with an alert. Each window shows its size in inches and eighths, mount, product, control and a five-slat stage track from measured to installed.
GoSeedly Window Treatments Kit
Every window measured,
ordered and hung as recorded.
A window schedule for blinds, shades, shutters and drapery studios: every open project with its windows grouped by room, each window’s size exactly as your team wrote it, its product and control, and where it stands from measured to installed. Louver keeps consults, measure sheets, vendor orders, install days and service tickets in one connected workspace.
Checking access…See the interface
One-time purchase · USD · Your Seedly backend · Editable kit sourceYOUR LOUVER WORKSPACE
01 — WINDOW SCHEDULEActual interface captures with fictional sample data. Open a screenshot for a closer look.
TAKE A CLOSER LOOK
Built around the windows you have open today.
One connected workspace, with views built around the decisions your team makes each day.
01 / Window schedule
02 / ConsultsWho you are seeing, and where.
Upcoming consults first, then past ones, with the consult type, consultant, the rooms and interest in your team’s words, the referral partner and the windows recorded so far.
03 / MeasurementsSizes exactly as recorded.
One measure sheet per project with every width and height in its own column, the mount and whether the size came from a check measure, a consult estimate or the customer. Windows not yet measured come first.
04 / OrdersEvery vendor order, window by window.
Orders grouped by vendor, late first, with the windows on each order, the ordered and ship-by dates, quoted lead days, shipped and received dates and the order value in its own column.
05 / InstallsInstall days, ready or not.
A passed install with windows still to hang comes first, then today and the next two weeks, with windows received and installed as counts and motorized windows called out.
06 / Service and warrantyAfter the install, still on record.
Adjustments, repairs, warranty visits and remakes with the window, the issue in the customer’s words and the opened, visit and resolved dates, overdue first.
07 / InsightsThe studio in its own units.
Windows by stage, product and control, accepted quote value, orders by state and quoted lead days by vendor, each in its own ledger, with a project ledger behind every count.
YOUR PROCESS, YOUR STARTING POINT
Useful structure.
Only what you choose.
4 pipelines and 9 workflow drafts. Add the parts that match your work, with a separate sample view for exploring the interface.
Choose your starting structure.
Use a ready-made stage sequence or connect drafts to a suitable existing pipeline.
- Window treatment projects · 8 stages
- Motorized projects · 7 stages
- Service and warranty · 7 stages
- Designer and builder partners · 7 stages
Give the next step a shape.
- Consult preparation
- Check measure review
- Quote follow-up
- Order placement
- Receiving check
- Install walkthrough
- Motorization power check
- Service ticket review
- Partner follow-up
Native trigger, task, wait, and note nodes provide editable examples. Every draft stays inactive until you review and publish it.
Explore before adding records.
Explore 13 fictional projects with 52 windows across 22 rooms, 10 vendor orders and 3 service tickets. Sample edits stay in memory and reset on navigation or reload.
No sample customers are inserted into your CRM.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
MORE OF THE WORKING DAY
From the first inquiry
to the final handoff.
Editable native forms and document templates give your team a practical starting point.
Three ready-to-edit forms.
- In-home consult request
- Service request
- Designer or builder referral
Choose forms individually in Setup & resources, then customize and publish them in the native form builder.
Three reusable templates.
- Window schedule sheet
- Quote summary
- Install day handoff
Open each template in Documents and complete it for the actual job or visit.
Checklists alongside the work.
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
Your workspace.
Your starting point.
Your code to edit.
One contact-linked project holds the property, referral partner, consult date and rooms as recorded, check measure, quoted, accepted and install dates, windows with room, label, width and height in inches and eighths, mount, product, control and price, vendor orders with ship-by, shipped and received dates, service tickets and an editable project checklist.
Window schedule per project with a needs-attention strip
Sizes in inches and eighths, exactly as recorded
A five-slat stage track for every window
Consult ledger and measure sheets
Vendor orders with quoted lead days
Install days with received and installed counts
Service and warranty tickets and insights ledgers in separate units
Three native form drafts and three editable document templates
Editable per-project checklists and a gate, lockbox and alarm code guard
Four optional pipeline templates and nine inactive workflow drafts
13 fictional in-memory projects
Guided setup, compatibility report, and private rollback receipt
AI-agent documentation for customized installations
Original editable source, configuration, and tests
Read the installation guide FROM KIT TO CONNECTED WORKSPACE
Check. Connect.
Make it yours.
Check your Seedly project.
Run the guided setup from the extracted kit. Supported integrations can be installed directly; customized integration files get a reviewed merge.
Connect the required helper.
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.
Set up your own team.
Edit studio name, descriptor and default pipeline name. Sign in with your account and verify the workflows and permissions your team uses.
Compatibility and operational details
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 project creation, edits and resource setup. They preserve native account permissions, unrelated custom fields and row history, refuse gate, lockbox, keypad and alarm codes, card numbers and government identifiers, accept only whole eighths of an inch, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
Everything shown is what the studio recorded. The kit does not measure windows, calculate deductions or ordered sizes, recommend products, place or track vendor orders, schedule installers, pair or control motors, certify energy or child-safety ratings, collect signatures, take payments or send messages.
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
Every kit.
And everything else.
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.
All 195 CRM kits
Every published kit as original editable source, with optional pipelines, workflow drafts, and guided installers. Browse the kits
Every class, course, and product
The full DevLaunch library and software collection, plus each eligible release during your access year, added to your portal as it ships.
Private calls with Aaron
Bring the idea, the offer, or the bottleneck, and leave with a plan you can follow.
DevLaunch All Access
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
Good questions.
Clear answers.
How do I receive the kit?+
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.
Does this include Seedly CRM?+
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.
Is this one connected workspace?+
Louver keeps its pale slate side rail and slat mark across the kit views and the 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.
Can I use it with existing customizations?+
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.
Do I have to import all the starter content?+
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.
Can I remove the examples and starter content?+
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.
Can different subaccounts use different kits?+
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 kits