CRM KitsFood trucks
Every stop. Every prep list.
A booking calendar for food trucks: every festival, market, brewery night, office lunch and private party on one calendar, with the request behind it, the fees the truck pays and receives, and the prep list for each service day. Hatchday follows the spring-to-fall festival season, shows the quiet winter honestly and records permits only as the labels and dates the office typed.
See the next four weeks of stops at a glance.
A season ribbon counts confirmed service days in each month of the festival year, then the needs-attention strip, then four weeks of service days from the start of this week, each chip with its hours, spot and state. Beside it: requests waiting for a reply, fees due and the next seven days with each day's prep list state.
Actual interface captures with fictional sample data. Open a screenshot to see it full size.
What’s in the kit
Screens
- Calendar operating view with a season ribbon
- Requests operating view
- Bookings operating view
- Fees operating view
- Prep lists operating view
- Spots operating view
- Insights operating view
- Three native form drafts and three editable document templates
- Editable booking checklists and preserved row history
four pipelines
- Event bookings · 7 stages
- Festival applications · 8 stages
- Recurring spots · 7 stages
- Private and office events · 7 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- Reply to the booking request
- Terms follow-up
- Write the prep list
- Close out the service day
- Application follow-up
- Booth fee check
- Load-in review
- Spot renewal talk
- Deposit check
Inactive until you review and publish them. None send customer messages.
Forms and documents
- Truck booking request
- Festival or market invitation
- Event day details
- Booking confirmation sheet
- Service day prep list
- Service day closeout
Editable native forms and document templates. Forms collect information for staff review.
Sample workspace
Explore 15 fictional bookings for one festival year: festivals, a farmers market, brewery nights, office lunches, a wedding, a birthday and a holiday market, with 59 service days and 135 checklist steps. Fee lines, prep rows and served days follow today's date, so the calendar is busy in season and quiet in winter. 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 business name, descriptor, default pipeline name and the festival season months. 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 booking 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.
One contact-linked booking holds its host, spot label, booking kind, festival year, truck and crew labels, request status with its received, terms sent, decision and cancelled dates and reply window, miles one way and the permit label and date as recorded, plus every service day with its hours, spot detail, status and servings recorded, every fee line with its direction, amount or rate label and due and paid dates, prep rows in their own units and an editable checklist.
Hatchday records what the office typed. It makes no health permit, food safety, fire marshal, commissary or allergen claim and never says a truck, a permit, a kitchen or a menu is approved, inspected, valid or safe; a permit is a label and a date. It does not take orders, run a point of sale, take payments or deposits, invoice, work out a share of sales, plan routes, track the truck, check the weather or send messages. Gate, door, commissary, walk-in, lockbox, keypad and alarm codes, POS, register, tablet, Wi-Fi and app logins and passwords, payment card numbers and Social Security numbers are refused in recorded text and in the native form drafts.
Four optional pipeline templates and nine inactive workflow drafts. 15 fictional in-memory bookings.
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 Food Truck 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?
Hatchday keeps its coral top bar and awning edge 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 hospitality, events & creative kits
Browse all 220 kits
