Actions
Notifications
Loading…
House access
Inquiries & guest requests
Authorized personnel only.
Thanks for applying — our team is reviewing your application now. We typically respond within 24-48 hours. We'll email you the moment we have an answer.
A note from the team:
Onboarding progress
Step 1 of 5
Opening your workspace…
Tell us your full name so your teammates and guests know who they're working with. You can add a profile photo too — it's optional.
Profile photo (optional)
Click the circle to upload. JPEG, PNG, WebP, GIF up to 5 MB.
Navigation
Action items
Notifications
—
—
MemberUpdate your photo, display name, and password. Changes apply to this admin session.
These fields are visible to the NetChefs admin team and used to match you to events. Keep them current.
New event opportunity
Review and respond below.
The first selected city is used as your home base.
Upload reference menus and manage reusable dishes. Event menus you build for bookings live under Menus in the sidebar.
PDF or image · max 20 MB each. Items are added to “All items” for this account; assign them to a menu later.
Click to choose files or drop them here
PDFs, JPEG, PNG, WebP, or GIF.
Onboarding documents and uploaded menus. Files already parsed into a menu are locked — delete the menu first to remove the file.
Loading your files…
This monthMonth
$0.00
No earnings paid yet this month.
Year to dateYTD
$0.00
No paid events this year yet.
All-time earningsAll-time
$0.00
Your lifetime payouts will show here.
Collected (gross)Gross
$0.00
Client payments before commission.
Active eventsActive
0
Open leads and bookings you're working on.
New client message
Reply from your events dashboard.
New event opportunity
Review and respond below.
Saving…
Choose the lead this proposal is for.
No leads match.
Loading leads…
Building your invoice
Reading your documents…
Just the basics — we'll pull in what we already know from the lead.
Client & event
Choose manual entry or let AI read your notes and attachments — venue, pricing, and terms fill in automatically.
Attach quotes, contracts, or venue docs — address and pricing are read from these.
Confirm the event address, then pick the menu your client will see.
Event address
Filled from your upload — adjust if needed.
No menus on this lead yet.
Leave blank to use your region's defaults — most chefs do.
Guest guarantees (75% rule), 4-hour staffing, deposit cancellation tiers, final payment, and signature block.
Build pricing line by line.
Enter Qty × Rate to auto-compute the amount (e.g. 18 guests × $300). Categorize each line to match the printed proposal.
| Section | Description | Qty | Rate | Unit | Amount |
|---|
Review the proposal exactly as it'll appear. Go back to change anything, or continue to choose your next step.
Save your work, share with the client, or jump back to edit anything.
Kitchen commission and fixed chef cost are covered first. Remaining margin split is handled automatically.
Edit line items below. When you click "Issue final invoice", we lock these as the final pricing snapshot, sum the new total, subtract what's already been paid, and bill Stripe for the remainder.
| Description | Amount (USD) |
|---|
Review what will be created before adding to the client's Stripe account.
Choose draft to review in Stripe first, or send now to email the client immediately.
Your invoice
Pick how you'd like to put this menu together. You can always edit every field afterwards.
Type, paste, or dictate the menu in your own words. Mention courses, dishes, descriptions, dietary notes — anything you want on the final menu. We'll structure it.
The guest's preferences (allergies, vibe, exclusions) are passed in automatically — you don't need to repeat them here.
Drafting your menu…
Usually under 15 seconds.
Drop a PDF, photo, or image of an existing menu. We'll parse the dishes into editable courses you can adjust before saving.
The guest's preferences (allergies, vibe, exclusions) are factored in automatically.
Reading your menu…
Image and PDF parsing usually takes 10–25 seconds.
Pick how you'd like to make changes. Either way, the current menu is saved as a version you can revert to.
Tell us what to change, attach reference files (optional), or both. We send the full current menu so your changes are applied on top — nothing is replaced.
The guest's preferences are factored in automatically. You'll review the result before it's saved.
Applying your edits…
Usually 10–25 seconds.
Every edit is saved as a version. Guests only ever see the active version. Revert any time — nothing is deleted.
Loading versions…
Date, venue, arrivals & dietary — shown on menu, PDF & share link when visible.
Group dishes under course sections — each section appears once on the guest menu and PDF.
5 quick steps · about 3 minutes
Tap to pick the ones that fit, or type your own and press Enter to add.
None yet — pick a few below or add your own.
Select every area you work in — you can choose more than one.
Don't see your city? We're expanding — pick the closer one for now and tell us in the bio.
Upload reference menus or PDFs/images here — you won't build menus in this step. After you're approved, structured menus usually appear on your NetChefs profile (and in your Chef Profile → Menu library), often generated from these files.
Optional — if you have a fixed prep location, tell us about it so we can route equipment and logistics easier.
You can leave this blank if you primarily cook on-site at client venues.
Something went wrong.
Welcome to NetChefs. Last step — let's set up your availability so we can start sending you events.
Discovery call
Add a quick internal note for the team about how the call went. This will save to internal notes and update the badge.
Discovery call · Qualified?
Move to Qualified if they're a fit, or Deal Lost with a reason if not.
Discovery call
If you're picking a new time, we'll bump the scheduled call. If not, the lead goes back to needing a discovery call to be scheduled.
Discovery call · Reschedule
The card stays in Lead with the new scheduled time. Add a quick internal note so the team knows what changed.
Discovery call · Reset
The scheduled time will be cleared and the lead's banner flips back to the red/blue "Schedule a call?" prompt. Add a quick internal note so we keep the trail.
Qualified · assign chef
Pick who owns this event. Saving moves the lead to Chef assigned.
Ping Chefs · review first
Nothing is sent yet. You'll preview the chef list and email next, then approve to move the event to Ping Chefs.
Ping Chefs · approve to send
—
Chefs who will be pinged
Email preview
Internal note
Capture context for the team. The prompt on the card will stay visible until the action is actually completed or the lead is unqualified.
Deal lost
Open deposit invoices are voided in Stripe first. If voiding fails, the lead stays unchanged.
Pipeline
Estimated deal value for this event. Visible to admin team only.
Outbound · discovery call
Pick when the call will happen and (optionally) save the best number to reach them. We'll log it as a scheduled discovery call.
Your menu
Outstanding
Open invoices ready for you to settle.
History
Your paid invoices — keep these for your records.
Select a thread from the list, or start a new one.
—
Your NetChefs Concierge can review this conversation.
Drop to attach
Up to 20 MB each. Multiple files supported.
Attach
From this guest's events
No menus or proposals on file yet for this guest. Create them on the event first.
Pick a topic and recipient.
Parse chef PDF and image uploads into structured menu items. Leave blank to use the built-in default.
Choose which admins receive an email when a client or chef sends a new message to NetChefs Concierge. We won't email the same admin more than once per hour per customer/chef so reply storms stay quiet.
Pick which admins get an email each time a brand-new lead is submitted from the public site. Unchecked admins won't be notified. We only email opted-in admins — no broadcast by default.
Pick which admins get an email each time a chef submits or re-submits their profile for review. Unchecked admins won't be notified. We only email opted-in admins — no broadcast by default.
Append-only snapshots of event menus. Every create, edit, revert, or delete writes a new row here — live menus can change, but these backups never disappear.
Auto-fills pipeline event value when unset: $250 × guests + 20%. Applies on new events and when guest count is saved without a manual value.
Full wizard — event, menu embed, terms, pricing, preview.
Event page on the Menu tab, then add-menu method picker and editor.
Guest details → guests → contact steps with prefilled demo fields.
Off by default for now. When off, invoices exclude sales tax even if a proposal or AI draft lists it. Stripe automatic tax stays disabled.
Addresses, signatory, and default tax/gratuity/deposit per region. New York and The Hamptons share one manual-payment list.
Upcoming events
0
No assigned dates yet
Open windows
0
Availability blocks in the next 30 days
Time off
0
Unavailable blocks in the next 30 days
Default posture
Available
Mark time off when you are not working
Green days are available. Dashed gray days are off (weekly off-days or vacation).
Days of the week you're never available.
No weekly off-days yet — you're available every day.
Date ranges you'll be completely away.
No vacations scheduled.
Choose whether you're available by default (mark times off) or unavailable by default (mark specific times open). Switching doesn't delete any blocks you've added.
| Start | End | Kind | Note | Actions |
|---|---|---|---|---|
| No blocks yet. | ||||
Kitchens appear here when they are assigned to one of your events. Open an event to see the full inquiry details.
Loading kitchens…
Locked for now
After your first completed, paid event with NetChefs, this page unlocks with your earnings, payout history, and Stripe setup. Until then, numbers below are previews only—we’ll email you as soon as a booking pays out.
Unlocks after your first paid eventTrack what you've earned with NetChefs and connect your bank account so we can send your money straight through Stripe.
Takes about 5 minutes · Powered by Stripe
This month
$0.00
No earnings paid yet this month.
Year to date
$0.00
No paid events this year yet.
All-time earnings
$0.00
Your lifetime payouts will show here.
Collected (gross)
$0.00
Client payments before commission.
Active events
0
Open leads and bookings you're working on.
Loading your payout account…
Set how this menu appears in the chef's library, add a short note for your team, then edit dish lines below.
Rows save in list order. Remove a row to delete that dish from this menu.
Plan who gets Admin, Operations, Chef, or Client access. We email them an invite link when outbound mail is configured; they must sign up or sign in with that same email, then you can confirm their role here. Kitchen prep locations are managed separately under Kitchens.
Invited chefs who haven't signed up yet, plus accounts still finishing onboarding. Track when you last nudged them.
All caught up — no pending chef follow-ups.
| User | Role | Status | Last sign-in link | Actions |
|---|
Chef sign-ups awaiting your review. Approve to unlock their full dashboard or send a quick note if you need them to update something.
Chef application
Loading…
Send a quick note to the chef telling them what to update. They'll see this on their dashboard and get an email with the same text.
| User | Role | Status | Last sign-in link | Actions |
|---|
| User | Role | Status | Last sign-in link | Actions |
|---|
| User | Role | Status | Last sign-in link | Actions |
|---|
Lucia workspace and Website forms
—
—
Cold email and homepage traffic stay separate — site beacons above, events board pipeline below.
| IP | Location | Funnel |
|---|
Office, VPN, and internal addresses you don’t want counted in visitor analytics.
Automatically appended to Lucia emails and drafts after one blank line.
|
Lucia Navarro
Host Relations · Miami, New York
|
|
Used by the Lucia agent to call workspace endpoints.
No active keys.
One email per interval · all times Eastern
Miami — Direct vs Referral
NY — Direct vs Referral
Create or edit a full outbound prospect profile.
Internal notes
Tagged Outbound and added to the events pipeline. Fill in only what you know — the rest can wait until the discovery call.
Client proposals with optional lead and chef links, uploaded documents, and line-item totals.
| Event | Stage | Chef | Kitchen | Amount | Updated | Actions |
|---|---|---|---|---|---|---|
| Event | Stage | Amount | Actions | |||
| Proposal | Stage | Amount | Updated | Actions |
Delete this proposal?
This removes the proposal and its uploaded documents. You cannot undo this.
Invoices you've sent for your assigned events — track payment status and remind clients when needed.
| Event | Client | Event date | Type | Status | Amount | Sent | Last reminder | Actions |
|---|
Chef Network
Chefs who submitted their application and are awaiting approval or follow-up.
Loading…
Client accounts
Profiles for everyone with the Client role. Events and LTV sum linked inquiries (account or customer email). LTV uses each event's pipeline value.
| Client | Events | LTV | Last sign-in | Member since | Actions | |
|---|---|---|---|---|---|---|
| Loading clients… | ||||||
Loading…
Email preview
Prep network
Prep kitchens and commissaries at a glance: map, capabilities, availability, and how each site supports assigned events. Invite accounts here, then attach them to leads from Events (same workflow as chefs).
You're available by default. Tap the days you're never available — these repeat every week. Leave every day unchecked and save if there are no standing weekly off-days.
Pick the date range you'll be away. Whole days only — your calendar will mark them off.
Drag to reposition. Use the slider or scroll to zoom. Only the circle will be used as your profile image.
We save their email to the pending list and send an invitation message when Resend is configured on the server. If they already have a Supabase Auth account, use Set role instead.
The person must already exist in Supabase Auth. Use the same email as in Auth. For users listed below, you can also use the row action.
Shown on kitchen cards for operations. Add coordinates for an accurate map; otherwise we geocode from the address lines.