Skip to content
View packages

CRM KitsCaterers

Every event quoted, staffed, and plated.

A caterer does not win an event with a stage name. It wins the event with a number, assembled line by line out of a menu and a headcount. Platter makes the quote sheet the main screen: menu lines on the left, the brief those numbers depend on on the right, in olive and white with serif course headings.

Quote builder in the GoSeedly Catering Kit with fictional sample records

The sheet is the work.

A quote queue grouped by recorded quote status sits beside the sheet, so the quotes waiting on somebody else come first. Selecting an event opens its menu lines next to its brief, with the recorded quote reference and the per-guest figure on a rule at the bottom.

Actual interface captures with fictional sample data. Open a screenshot to see it full size.

What’s in the kit

Screens

  • Quote builder with a status-grouped quote queue beside a two-column menu and brief sheet
  • Line reference arithmetic enforced in the editor and again on the server, with unpriced lines adding nothing
  • Event book, prep board by recorded day, recorded menu library and staffing roll-up
  • Quote record rules for sent and decision dates, and a prep task that cannot be marked done without a due date
  • Archive-only prep tasks with stable IDs, while a menu line or staffing row can be removed deliberately
  • Olive and white Platter application frame with serif course headings and full CRM tools

four pipelines

  • Event inquiries and quotes · 8 stages
  • Confirmed events · 7 stages
  • Corporate accounts · 7 stages
  • Tastings and menu development · 7 stages

Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.

nine workflow drafts

  • Inquiry response
  • Tasting scheduling
  • Quote follow-up
  • Deposit reminder note
  • Final headcount
  • Staffing confirmation
  • Prep list note
  • Event day check
  • Post-event review note

Inactive until you review and publish them. None send customer messages.

Sample workspace

Explore nine fictional events spread across the eight stages of the sample pipeline, from a wedding dinner already accepted to a gala being re-quoted and a wedding lunch that was declined, each with its menu lines, staffing counts and prep tasks. Example edits stay in the current page’s memory and reset on navigation or reload; sample events 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
Read the installation guide
  1. Check your Seedly

    Extract the kit and run the guided setup. It checks your installation and flags customized files before it changes anything.

  2. Connect the helper

    Deploy the included helper from your backend source, then build your web app and choose any starter pipelines and drafts.

  3. Make it yours

    Set company name, descriptor, 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 catering helper is required for connected creation, editing and starter setup. It preserves native account permissions and unrelated custom fields, re-checks the quote line arithmetic and the quote record 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.

An event is a native contact-linked opportunity with a namespaced event type, recorded date and service time, venue label, service style, headcount, dietary notes, quote record, next-step note, menu lines, staffing rows and prep tasks. The recorded quote reference stays separate from native opportunity value. Other custom fields are preserved.

Every number is a reference somebody entered, or arithmetic on what somebody entered. Nothing is invoiced, deposited, collected, signed or recognized as revenue. There is no inventory, purchasing, recipe costing or food cost percentage. Staffing rows are role labels, counts and call times that roster nobody and touch no payroll. Event dates, service times and call times reserve nothing and create no calendar entry. Nothing in the kit messages a client, a venue or a staff member. Totals are grouped by currency and never added across currencies. The pipeline stage stays your CRM’s own: the kit adds no stage model and no stage mutation, and the recorded quote status is a separate field.

Four optional pipeline templates and nine inactive workflow drafts. Nine fictional in-memory events with menu lines, staffing counts and prep tasks.

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 Catering Kit

Checking access…

DevLaunch All Access

Every kit and every template.

See DevLaunch All Access

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?

Platter keeps its catering navigation across the original event 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.

Browse all 220 kits

Customer experiences / Trustpilot

What customers say
about DevLaunch.

Read all reviews on Trustpilot ↗

Selected excerpts from reviews of DevLaunch training, software, and services. Individual customer experiences across DevLaunch.