GoSeedly Food Truck Kit
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.
YOUR HATCHDAY WORKSPACE
01 — CALENDAR
Actual interface captures with fictional sample data. Open a screenshot for a closer look.
TAKE A CLOSER LOOK
One connected workspace, with views built around the decisions your team makes each day.
01 / CalendarA 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.
02 / RequestsEvery request of the festival year with its kind, received date, reply-by date, the dates the host asked for and its status. A request past its reply window leads, in red with the words Reply overdue.
03 / BookingsConfirmed bookings with served, planned and called-off days counted, the next service day with its hours and spot, the truck and crew labels, miles one way as recorded and the permit label and date as the office recorded them.
04 / FeesTwo ledgers: we pay (booth, stall, share of sales and permit fees) and we receive (deposits, event payments and minimums), each line with its amount or rate label as the host wrote it, due date and status. Money is totalled per direction and status only.
05 / Prep listsEvery confirmed service day from today through the next fourteen days with its prep rows: item, quantity in its own unit and to prep, prepped or loaded. A day within seven days with no prep list is flagged.
06 / SpotsBookings grouped by spot with days served, servings recorded, miles one way as recorded, the last served day and the next planned day, each in its own column.
07 / InsightsFilter buttons for each alert, then service days by month, bookings by status, fees by direction and status and servings by booking kind. Servings, days, miles and money are never added together or drawn on one scale.
YOUR PROCESS, YOUR STARTING POINT
4 pipelines and 9 workflow drafts. Add the parts that match your work, with a separate sample view for exploring the interface.
Use a ready-made stage sequence or connect drafts to a suitable existing pipeline.
Native trigger, task, wait, and note nodes provide editable examples. Every draft stays inactive until you review and publish it.
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.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
MORE OF THE WORKING DAY
Editable native forms and document templates give your team a practical starting point.
Choose forms individually in Setup & resources, then customize and publish them in the native form builder.
Open each template in Documents and complete it for the actual job or visit.
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
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.
FROM KIT TO CONNECTED WORKSPACE
Run the guided setup from the extracted kit. Supported integrations can be installed directly; customized integration files get a reviewed merge.
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.
Edit business name, descriptor, default pipeline name and the festival season months. Sign in with your account and verify the workflows and permissions your team uses.
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.
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.
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
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.
Every published kit as original editable source, with optional pipelines, workflow drafts, and guided installers. Browse the kits
The full DevLaunch library and software collection, plus each eligible release during your access year, added to your portal as it ships.
Bring the idea, the offer, or the bottleneck, and leave with a plan you can follow.
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
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.
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.
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.
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.
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.
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.
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 kitsCustomer experiences / Trustpilot
Selected excerpts from reviews of DevLaunch training, software, and services. Individual customer experiences across DevLaunch.
We use essential storage to keep the site working. With your permission, we also use analytics and the Whop Pixel to understand visits and advertising results. Optional analytics stay off until you choose.
Read our Cookie Policy and Privacy Policy.