
CRM KitsGeneral contractors
Every bid, every sub, every milestone on one line.
Put duration on the screen. Beam draws a white blueprint sheet with twelve week columns, one row per project, and one bar per recorded trade phase, so the sequence a general contractor actually sells is the first thing you see.
The schedule, to scale.
Twelve week columns on a blueprint grid, one row per project record and one bar per recorded phase, tinted by trade label. A red rule marks today, delayed phases are hatched, and selecting a bar opens the sub sheet beside the grid.
Actual interface captures with fictional sample data. Open a screenshot to see it full size.
What’s in the kit
Screens
- Twelve-week Gantt timeline with per-phase bars and a phase sub sheet
- Project and bid records in one table with a kind filter
- Bid desk grouped by recorded outcome with due-date counts
- Subcontractor grouping and milestone weeks across every project
- White blueprint Beam application frame with full CRM tools
four pipelines
- Bids and estimates · 8 stages
- Residential projects · 8 stages
- Commercial projects · 7 stages
- Warranty and punch list · 6 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- Bid due reminder
- Bid follow-up
- Contract signed kickoff
- Subcontractor confirmation
- Phase start check
- Delayed phase review
- Milestone inspection review
- Punch list review
- Warranty check-in
Inactive until you review and publish them. None send customer messages.
Sample workspace
Explore eight fictional projects and four fictional bids, with 42 recorded trade phases and 30 recorded milestones spread across a twelve-week window. Example edits stay in the current page’s memory and reset on navigation or reload; sample records are never inserted into your CRM.
No sample customers are added to your CRM.
Setup and source
- Guided setup and compatibility report
- Private rollback receipt
- AI-agent guide for customized installations
- Original editable source, configuration, and tests
How setup works
Full installation guideCheck your Seedly
Extract the kit and run the guided setup. It checks your installation and flags customized files before it changes anything.
Connect the helper
Deploy the included helper from your backend source, then build your web app and choose any starter pipelines and drafts.
Make it yours
Set company name, descriptor, and default pipeline name. Then sign in and check the workflows and permissions your team uses.
Technical details and compatibility
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 general contractor helper is required for connected creation, editing, and starter setup. It preserves native account permissions and unrelated custom fields, and checks the current record timestamp and namespace revision before saving. Deploy it from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional.
One record is a native contact-linked opportunity, either a bid or a project. Its namespace holds the project type, site address label, superintendent label, contract or bid reference amount, recorded start and end dates, bid due date and outcome, a next-step note, trade phases with stable IDs, and milestones with stable IDs. Other custom fields are preserved.
Phase dates are recorded values. There is no scheduling engine, critical path, float or resource levelling, and changing one phase never moves another. Subcontractor labels assign nobody, reserve nothing and send no message. Milestones are names, dates and a done flag; the kit files no permit, requests no inspection and books no walkthrough. Contract and bid amounts are recorded reference numbers, separate from native opportunity value, with no estimating, takeoff, invoicing, draw requests, retainage or lien tracking. Document storage stays in your own native Documents module.
Four optional pipeline templates and nine inactive workflow drafts. Eight fictional projects and four bids, with 42 phases and 30 milestones, held in memory.
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.
Get the General Contractor Kit

DevLaunch All Access
Every kit and every template.
- All 220 CRM kits for Seedly CRM
- All 270 website templates for Seedly Sites
- Every class, course, and product we release, added as it ships
- Private calls with Aaron
Already a member? Open your downloads.
Questions
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?
Beam keeps its horizontal project navigation across the original timeline 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.
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.
More trades & construction kits
Browse all 220 kits









