CRM KitsFencing and decking contractors
Every run measured. Every board counted.
A fencing and decking company does not sell a thing, it sells a measured quantity. The first real event on every job is somebody walking the property with a wheel and writing down runs: 120 feet along the back line, 64 feet down the side, one gate here, one gate there. Everything after that is arithmetic on those numbers. Post is built on that axis instead of a calendar: one wide row per project, each recorded run drawn as a bar scaled to its length, ink ticks for the gates a run carries, a hatched bar for a deck surface, and the material list and build day range printed underneath.
The axis is feet, not days.
One row per project. Each recorded run is a periwinkle bar scaled against the longest recorded run on the page, so a 120 ft run is exactly twice the width of a 60 ft one and a 600 ft commercial perimeter runs the full page. A deck draws one hatched bar scaled to its recorded square feet, and the style chip at the start of the bars reads privacy, picket, ranch rail, chain link, composite deck or wood deck down the left edge.
Actual interface captures with fictional sample data. Open a screenshot to see it full size.
What’s in the kit
Screens
- Measure sheet whose horizontal axis is recorded quantity, with a bar per run scaled from the longest recorded run on the page
- Ink gate ticks and a hatched deck surface drawn in pure CSS, with no image, SVG or icon file anywhere in the kit
- One shared measurement rule used by the editor, every view and the server, so a stored total can never disagree with its run rows
- Linear feet and square feet kept as two separate totals with their own project counts
- Material readiness in three honest groups: waiting, fully delivered, and no line recorded
- Build days ordered overdue first, with the projects measured but not yet scheduled listed separately
- Archive-only run and material records with stable IDs, so a measurement or an order is never erased
- Single slate chrome bar over a white canvas with full permission-filtered CRM tools
four pipelines
- Residential fencing · 8 stages
- Deck builds · 7 stages
- Commercial and agricultural fencing · 7 stages
- Repairs and staining · 7 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- Site measure review
- Estimate follow-up review
- Permit submitted record
- HOA approval check
- Materials ordered record
- Delivery check review
- Build start reminder
- Build complete walkthrough
- One year check-in
Inactive until you review and publish them. None send customer messages.
Sample workspace
Explore ten fictional projects across all six styles, from a 222 ft privacy fence to a 1,160 ft commercial chain link perimeter and two deck surfaces, with 26 recorded runs carrying 11 gates and 31 material lines. Four lines are recorded as undelivered across three projects, one project is waiting on an HOA approval and another on a permit, one ran past its planned end with no actual end, two are building today, and one is measured with no material line, no build block and no crew recorded at all. Example edits stay in the current page’s memory and reset on navigation or reload; sample projects 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, promise line, 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 project helper is required for connected creation, editing and starter setup. It preserves native account permissions and unrelated custom fields, re-checks the measurement arithmetic along with the gate, deck, material, approval, build date and crew rules, and compares the current record state before saving. It exposes no stage mutation at all, so pipeline stages stay in your CRM’s own views under your existing roles. Deploy the helper from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional.
A project is a native contact-linked opportunity with a namespaced style, site address label, material label, height reference, crew label, a derived recorded total, permit and HOA review flags with their approved dates, planned and actual build dates, project notes, an immutable supported currency, run records with their lengths and gate counts, and material lines with their ordered and delivered flags. The recorded contract reference stays separate from native opportunity value. Other custom fields are preserved.
Every number on screen is one somebody wrote down, and the one derived value is the sum of the rows under it. The recorded total must equal the sum of the runs that are not archived and must be blank when no live run exists; the editor recomputes it on every edit and the server refuses a stored value that disagrees, so the sheet can never contradict the runs. Linear feet and square feet are never added together anywhere, including on Insights. Gate ticks are spaced evenly because the kit records how many gates a run carries, not where they sit. A recorded gate needs a run at least three feet long and a fence style, because a deck has no gate, and a deck records one live surface so re-measuring archives the earlier row. A delivered material line requires its ordered flag, because nothing arrives on site that nobody ordered. A recorded permit or HOA approval date requires the matching flag recorded as required. A planned or actual end requires its start and may not precede it, a crew label requires a recorded planned start, and an actual start earlier than the planned start is accepted because a build moves in both directions. There is no estimating or pricing engine, no supplier ordering or inventory integration, no permit or HOA system integration, no crew scheduling engine, no invoicing or payments, no customer messaging, and no CAD or site drawing. The bars are a scaled measurement sheet rather than a plan, and their vertical order carries no geography. The pipeline stage stays your CRM’s own: the helper exposes no stage mutation at all, so recording a measurement never moves a card and moving a card never records a measurement.
Four optional pipeline templates and nine inactive workflow drafts. Ten fictional in-memory projects with 26 recorded runs, 11 gates and 31 material lines.
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 Fencing & Decking Kit
Checking access…
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?
Post keeps its fencing and decking navigation in one chrome bar across the original measure 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
