GoSeedly Personal Chef & Meal Prep Kit
A menu week for personal chefs and meal prep businesses: every household you cook for as a row, the next seven days as columns, each cook day with its window, its dishes and planned servings, and the client's likes, dislikes and avoid notes in their own words. Weekplate keeps cook days, menus, preferences, dish rotation and clients in one connected workspace.
YOUR WEEKPLATE WORKSPACE
01 — MENU WEEK
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 / Menu weekHouseholds as rows and seven days as columns, with a switch for the last 7 days, the next 7 and the 7 after. Each cook day shows its status, its window and every dish with its planned servings, and each row carries the recorded style, likes, dislikes and avoid notes. A menu still waiting on approval, a cook day not recorded or a weekly household with nothing booked leads in the needs attention strip.
02 / Cook daysOpen cook days with alerted ones first, then cook days from the last 30 days with servings packed and hours recorded in separate columns, then skipped and cancelled days with the reason the client gave.
03 / MenusThe next two weeks of cook days in four columns: planned with no menu yet, menu sent, menu approved and shopped. Each menu lists its dishes and servings with the household's avoid notes repeated word for word beside it.
04 / PreferencesAvoid notes for every live household first, then style, likes and dislikes, each with who it is for, the client's words and the date recorded. Weekplate never checks a dish against them or marks a dish free of anything.
05 / RotationThe dishes each household has had in the last 60 days, how many cook days each was on, when it was last cooked and whether it is already on an upcoming menu.
06 / ClientsActive households with their service, plan, usual cook days, fee per cook day and grocery budget as quoted and the next cook day, then paused households with resume dates, leads with a first cook day booked and recent closures.
07 / InsightsHouseholds by state, cook days by status, servings packed by household, recorded hours by household, recorded fees by plan and recorded groceries by household. Servings, hours and dollars are never added together.
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 10 fictional households: seven active, one paused, one lead and one closed, with 26 cook days (seven planned, one menu sent, two approved, two shopped, 12 cooked, one skipped and one cancelled), seven of them in the next seven days, 45 dishes and 32 recorded preferences, seven of them avoid notes. 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 household holds the service, plan, kitchen address, usual cook days, usual servings, the fee per cook day and weekly grocery budget as quoted, how the chef gets in described in words, start, pause, resume and closed dates, each cook day with its window, status, menu sent and approved dates, recorded hours, fee and groceries, each dish with its course and planned and packed servings, each preference with who it is for and the client's own words, 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 and default pipeline name. 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 household creation, edits and resource setup. They preserve native account permissions, unrelated custom fields and row history, keep servings, hours and money apart, refuse access codes, logins, card numbers, Social Security numbers and health details, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
Weekplate records what the office booked and what the chef reported. Servings are counts; hours, fees and groceries are recorded values, and none is added to another. It does not plan menus, write recipes, read ingredients or labels, order groceries, price cook days, bill or take payments, or send messages. Avoid notes are the client's words, and no dish is ever marked free of anything; the kit makes no food-safety, dietary, medical or nutrition claim. Diagnoses, medications and medical diets, door, gate, garage, lockbox, keypad and alarm codes, Wi-Fi and app logins, 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.
Weekplate keeps its white top bar, lemon current tab and perforated band 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.