PRODUCT: Catering Booking Manager WHO AND OUTCOME A small-business owner needs to complete this job: One plan for the whole event. Start with business name and the first real entry; no enterprise setup.
SCREENS AND FIELDS Main workspace: Event booking, with search, relevant date/status filters, a primary New entry action, and a visible list of current work. Selecting an entry opens a detail panel containing editable fields, chronological activity, totals, attachments where specified and the next valid action. Fields: Event/date/location, menu versions, guest count, per-head and fixed charges, deposits, staffing, equipment checklist. Use an explicit empty state and an optional Load sample business action; sample data never appears to be real.
STATE TRANSITIONS Enquiry → Quote → Menu approved → Confirmed → Preparing → Completed → Settled. Transitions must be recorded with timestamp. Explain missing requirements inline; do not enable a completion state before its requirements are met. Preserve important previous versions and corrective actions.
BUSINESS RULES Guest-count revisions recalculate quote and preserve approved version; confirmed menu is recorded; kitchen quantities derive from selected recipes/portions. Use decimal monetary arithmetic and USD currency. Validate dates, positive quantities, required identities and duplicate references. Show derived amounts immediately and prevent double submission using server-side idempotency.
ACCEPTANCE EXAMPLE AND OUTPUT 100 guests×325=>32500;5000 deposit=>27500 remaining. Export menu, preparation checklist and client quote without internal margins.
IMPLEMENTATION Use a small persistent database and private attachment storage where needed. One owner account is sufficient; only add restricted customer links or operator access when the workflow explicitly requires it. Enforce access server-side, never only through hidden UI. Data must survive refresh and reopen. Include backup/export and safe corrections; confirm destructive deletion. No ERP AI dependency, table designer, role matrix or generic enterprise dashboard. External messaging/payment/tax integrations must be real and explicitly configured; otherwise provide clearly labeled manual recording or message preparation. Never simulate successful payment, filing, OCR, message sending or delivery.
VERIFY Test create-edit-reload, the example above, invalid input, duplicate submission, state changes and exported totals. Verify private links cannot access another customer's records where applicable.
APP-SPECIFIC VISUAL DESIGN DESIGN IDENTITY: TABLE & CO. — Formal event folio. COLOR TOKENS: background #293a35; primary text #f5f0df; primary accent #e4dcc0. Derive quiet borders and secondary surfaces from this palette. Use contrast-checked status colors and text labels. Do not apply the gallery's black shell to the app. TYPOGRAPHY: Georgia display with Geist body. Use self-hosted fonts when available, 16px body, 14px labels, tabular numerals for money. Display sizes below are desktop targets, not mobile minimums. DESKTOP COMPOSITION: Use a forest canvas with ivory serif typography and fine dividing rules. Left: event name, venue and large day/month date. Right: oversized guest count, menu-section counts and menu approval state. Deposit received and Event details anchor the footer. Opening an event reveals dietary counts, service timing, staff, equipment and balance. Prefer an event folio over dashboard widgets. RESPONSIVE BEHAVIOR: Stack event identity, guest/menu details, then payment schedule; service timeline remains readable as a list. DETAILS AND BEHAVIOR: The preview is a visual direction, not the complete field list. Implement every functional requirement in the app specification. Sample headings and fictional brand names are editable; show demo data only in an explicit example mode. Preserve this composition, typography and material treatment instead of falling back to a generic admin dashboard. Add meaningful empty, loading, validation, disabled and failure states. Interactive controls need visible focus and at least 44px touch targets. Actual application text must remain readable; do not copy the gallery thumbnail's scaled-down text sizes.
IMAGE COMPOSITION (REFINES THE BASE DESIGN ABOVE) Use the dinner-table photo as an immersive background. Preserve visible candles/table setting around the left event identity; place guest/menu counts on a translucent forest panel at right. Keep payment footer readable. Reference photo: https://images.unsplash.com/photo-1536392706976-e486e2ba97af?auto=format&fit=crop&w=1200&q=85 Source: https://unsplash.com/s/photos/elegant-dinner-table Use this supplied image URL or a suitable owner-provided image of the same subject. Reserve image dimensions, use deliberate object-fit cover crops, preserve the subject, lazy-load below-the-fold images, and keep controls and text on contrast-checked overlays or solid surfaces. Do not replace photography with emoji, icon placeholders or CSS illustrations. On narrow screens reduce image height only as needed while preserving the functional mobile layout. These are illustrative sample photos, not evidence about real customers or transactions.
US LOCALE Use USD ($) with en-US grouping and cents, American English, US names and addresses, MM/DD/YYYY dates, 12-hour times, Fahrenheit, and US customary units. Sample amounts are fictional USD values, not converted exchange rates. Treat sample tax rates as illustrative only; require the business to configure applicable rates and taxability. Use US small-business imagery and preserve the supplied image provenance.
IMPLEMENTATION AND DESIGN CONTRACT Build this working app, not a promotional page. Use the exact inputs, states, formulas and exports above. Use a responsive workspace with labeled controls, 16px body text, visible keyboard focus, sufficient contrast, and a clear primary action. Follow the app-specific palette and typography above. Use self-hosted fonts; body 16px/400 and labels 14px/500. Size headings and results according to the app-specific hierarchy above; ordinary section headings default to 28px/600. Use 44px minimum control heights. Follow the app-specific corner radii, panel treatment, spacing and desktop composition above; where unspecified, use 8px controls and 24px section gaps. Primary buttons use the primary token with a contrast-checked label. Use thin neutral borders, not a shadow on every element. Below 768px follow the app-specific mobile layout above and keep primary actions reachable. Keep sample data behind Load example and visibly label it; do not mix it with real user data.
No ERP AI dependency, enterprise table-configuration screen, or permission matrix. Use the smallest architecture that fulfills this specific workflow. Keep secrets server-side. Only add authentication where the brief requires protected shared data. Prefer local file processing and allow users to clear their data.
Verify each numeric example and primary workflow specified above, including empty, invalid and failed states. Confirm that downloaded files contain the displayed results. Report any unavailable integration plainly; do not ship a button that simulates success. Deliver the complete app and only the setup steps needed for real integrations.