CRM KitsPropane and heating oil dealers
Every tank. Every route.
A route board for propane and heating oil dealers: every customer tank grouped by route with its size, its fuel, the last fill and the gallons your driver recorded, and the days since that fill counted against the delivery interval your office set, with overdue deliveries leading in words. Lastfill keeps route day sheets in your recorded stop order, automatic and will-call customers, the will-call queue, budget plans and pre-buy contracts as recorded, tank inspection dates and service calls in one connected workspace. It never estimates a tank level or a run-out date, and it never says a tank or an installation is safe or meets any rule.
See every tank on every route, overdue first.
A needs-attention strip with each account's alert in words, then one section per route with a row per tank: stop, account, the tank plate with size and fuel, owned or leased, automatic or will-call, the last fill with the gallons recorded, and the days since that fill against the tank's recorded interval, counted from the season open when no fill is recorded since. Overdue tanks lead each route, beside the next seven days of interval ends, will-call promises, service visits and inspection dates.
Actual interface captures with fictional sample data. Open a screenshot to see it full size.
What’s in the kit
Screens
- Route board operating view
- Route day operating view
- Customer tanks operating view
- Will-call queue operating view
- Budget and pre-buy operating view
- Inspections operating view
- Service calls operating view
- Insights operating view
- Three native form drafts and three editable document templates
- Editable account checklists and preserved row history
four pipelines
- Delivery accounts · 7 stages
- Will-call deliveries · 7 stages
- Service calls · 7 stages
- Budget and pre-buy · 8 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- New customer paperwork
- Tank set preparation
- First fill record
- Will-call promised date
- Will-call ticket
- Service visit scheduling
- Service follow-up
- Pre-buy offer follow-up
- Next season offer
Inactive until you review and publish them. None send customer messages.
Forms and documents
- Will-call delivery request
- New customer and tank set inquiry
- Service call request
- Route day sheet
- Budget plan or pre-buy summary
- Tank record sheet
Editable native forms and document templates. Forms collect information for staff review.
Sample workspace
Explore 12 fictional accounts with 14 tanks (10 propane, 4 heating oil) on four routes, 11 automatic and 3 will-call, across two heating years, with the gallons the sample drivers recorded, will-call requests, service calls, budget plans and pre-buy contracts. Every sample date is a real calendar day, so the board reads like the season on any date: winter routes, a summer panel with next season's sign-ups and a new customer each fall. Sample edits stay in memory and reset on navigation or reload.
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, default pipeline name and the heating season dates. 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 backend helpers are required for connected account creation, edits and resource setup. They preserve native account permissions, unrelated custom fields and row history, keep gallons, days and money in their own units, refuse access codes, passes, logins, bank and autopay details, card numbers, Social Security numbers and other ID numbers, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
One contact-linked account holds the account kind and status, the customer, the service address and account number, every tank with its size in gallons, fuel, owned or leased, automatic or will-call, the heating and summer intervals in days, the route and stop, where to find it and its set and inspection dates as recorded, every delivery with the gallons, price per gallon, ticket and driver as recorded, every will-call request with its requested, promised and scheduled dates, every service call with its kind, the customer's words and its dates, every budget plan and pre-buy contract for a heating year as recorded, and an editable checklist.
Lastfill records accounts, tanks, deliveries, will-call requests, service calls, budget plans, pre-buy contracts and inspection dates as your office typed them. Overdue means only that the days since the last recorded fill are more than the tank's recorded interval for the season, and in the heating season a tank with no fill recorded since the season opened counts from the open date, so opening day starts every tank on its interval instead of flooding the board; Lastfill never estimates a tank level, a fill percentage or a run-out date, reads no weather, degree days, tank monitor or meter, and never says a tank, a regulator, a line, an appliance or an installation is safe or meets any rule. It plans no routes, dispatches no trucks, bills, charges or collects nothing, runs no autopay and messages no one. Gate, garage, door, keypad and alarm codes, passes, portal and tank monitor logins and passwords, budget plan autopay bank details, card numbers and Social Security numbers are refused in recorded text and in the native form drafts, whose answers are capped so the whole answer is checked, while tank sizes, gallons, prices per gallon, routes, stops, county roads and account numbers under six digits are accepted.
Four optional pipeline templates and nine inactive workflow drafts. 12 fictional in-memory delivery accounts.
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 Propane & Heating Oil Delivery Kit
Checking access…
DevLaunch All Access
Every kit and every template.
- All 220 CRM kits for Seedly CRM
- All 190 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?
Lastfill keeps its dark asphalt side rail with the numbered stops along a dashed silver center line, the road strips, the tank plates and the tank-over-route mark 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.
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 home services kits
Browse all 220 kits
