DEV Community

yuki yama
yuki yama

Posted on

AI Restaurant Allergen Matrix Micro-Agency: Automate Menu Allergy Labels and Earn $500–$2,000/Month

#ai #sidehustle

Please note: All earnings mentioned are illustrative simulations.

Title: AI Restaurant Allergen Matrix Micro-Agency: Automate Menu Allergy Labels and Earn $500–$2,000/Month

Why this works now

  • Restaurants are legally and reputationally exposed if allergen info is missing or outdated. In the U.S., the FDA’s “Big 9” allergens must be clearly communicated: milk, eggs, fish, shellfish, tree nuts, peanuts, wheat, soybeans, and sesame.
  • Vendors publish spec sheets and ingredient PDFs that change regularly. Staff don’t have time to re-check everything.
  • With Manus AI, you can ingest supplier PDFs/links and internal recipe spreadsheets, auto-classify Big 9 allergens per menu item, and export a client-ready CSV/HTML matrix, printable menu icons, and a staff-training one-pager in hours, not weeks.

Start by creating your free workflow backbone with Manus: https://manus.im/invitation/OJF7FVBNBC14H?utm_source=invitation&utm_medium=social&utm_campaign=copy_link

What you’ll sell (deliverables the restaurant can use tomorrow)

  • Allergen Matrix (CSV + HTML): A menu-by-allergen matrix (Big 9) that the GM can open, print, and post for staff. CSV for back-office systems. HTML for staff mobile access via QR.
  • Printable Allergen Icons: Clear icons (e.g., W for wheat, E for egg) for menus, chalkboards, and table tents.
  • Recipe Allergen One-Pagers: Each menu item’s allergen list and change log the chef can train staff with.
  • Monthly Re-checks: An automated review of vendor spec changes with a human approval step, delivering a new matrix if anything changes.
  • Support and Edits: 1–2 recipe changes per month included depending on tier.

Realistic income math

  • 3 clients at $125/month + $450 one-time setup each in Month 1–2 = $1,350 in setup cash + $375 MRR.
  • 8 clients at $150/month average + $500 one-time setup each over time = $4,000 setup pay spread across signings + $1,200 MRR.
  • Time: 2–6 hours to onboard a client; 30–60 minutes/month per client after. At 8 clients, your weekly maintenance is about 4–6 hours.
  • Outcome target: $500–$2,000/month with 3–8 clients after 6–10 weeks of consistent outreach and delivery.

Exact Manus AI workflow blueprint (from intake to monthly re-checks)
Create your Manus account with the invite link: https://manus.im/invitation/OJF7FVBNBC14H?utm_source=invitation&utm_medium=social&utm_campaign=copy_link

1) Intake and ingestion

  • Inputs accepted:
    • Supplier spec sheets as PDFs or hosted links (e.g., vendor portal URLs).
    • Internal recipe spreadsheets (CSV/XLSX/Google Sheets).
  • Setup in Manus:
    • Email ingestion: Create an intake address (e.g., allergen@youragency.com) via Google Workspace. In Manus, add an Email trigger so any message with attachments or links forwarded by the client is auto-captured.
    • Watch folder: Create a “Vendor Specs – ClientName” folder in Drive inside Google Workspace. In Manus, add a Drive/Cloud “Watch Folder” trigger so when the client drops a PDF, the flow runs.
    • Spreadsheet sync: If the client uses Google Sheets for recipes, connect the Sheet to Manus as a data source. If they use Excel, put it in the watch folder.

2) PDF parsing with OCR

  • In Manus, add a “Parse Document” step with OCR enabled. This extracts:
    • Ingredients list
    • Allergen statement
    • “May contain”/cross-contact warnings
    • Supplier product name, version code, date
  • Tip: Use page anchors like “Ingredients:” and “Allergen:” as soft hints to improve parsing. Where PDFs are images or scanned, Manus OCR will still read them.

3) Link scraping and versioning (for hosted spec sheets)

  • For URLs, add a “Fetch URL” step before parsing. Manus downloads the latest file. Store a hash/version in the workflow state so you can compare on future runs.

4) Recipe join and normalization

  • Import client recipe data (ingredients per menu item) from the Sheet or CSV. Normalize ingredient names to canonical forms:
    • Example mappings: “bleached wheat flour” → “wheat flour”, “pecan pieces” → “pecans”, “soya lecithin” → “soy lecithin”
  • Use Manus’ data transformation step to standardize units (e.g., grams vs. cups) and ingredient names.

5) Allergen mapping logic with rule-based validation

  • Big 9 detection:
    • Wheat: Trigger true if “wheat”, “flour” (unless “gluten-free flour” with composed rule), “semolina”, “farina”, “spelt”, “durum” appear.
    • Egg: “egg”, “albumen”, “ovum”, “mayonnaise” (unless egg-free mayo).
    • Milk: “milk”, “casein”, “whey”, “ghee”, “butter”, “cheese”.
    • Soy: “soy”, “soy lecithin”, “tofu”, “edamame”, “shoyu”, “soy sauce”.
    • Peanuts: “peanut”, “groundnut”, “arachis oil”.
    • Tree nuts: “almond”, “walnut”, “pecan”, “pistachio”, “cashew”, “hazelnut”, “macadamia”, “pine nut”, “brazil nut”. Include “nut meal/paste”.
    • Fish: “salmon”, “tuna”, “cod”, “anchovy”, “fish sauce”.
    • Shellfish: “shrimp”, “prawn”, “lobster”, “crab”, “mussel”, “clam”, “oyster”, “scallop”.
    • Sesame: “sesame”, “tahini”, “sesamum indicum”.
  • Cross-contact rules:
    • If “may contain” or “produced in a facility with X” is present, mark cross-contact for X. Display as “May contain X” separately from “Contains X”.
  • Precedence:
    • Contains > May contain > Free from claim.
    • If both “gluten-free” and “wheat starch” appear, require human review.
  • Confidence:
    • Assign a confidence score per allergen. Conflicts (e.g., “egg-free” but “albumen” found) reduce confidence and flag for approval.
  • Overrides and whitelists:
    • For common false positives (e.g., “coconut aminos” is a tree nut by botanical definition but not always regulated as such in some locales), configure a case-by-case override with notes. Always defer to local regulation and the supplier’s official statement.

6) Human-in-the-loop approvals

  • In Manus, add an “Approval Task” node:
    • Per menu item, show parsed ingredients, vendor statements, detected allergens, cross-contact notes, confidence, and diffs from last run.
    • The reviewer (you or chef) can Accept, Edit, or Flag for info. Comments are stored as an audit trail.
  • Notifications:
    • Send an approval request email to the client via Google Workspace.
    • Optional: Auto-remind at 24 and 72 hours using Zapier or Make connected to the Manus webhook.

7) Export to CSV and HTML

  • CSV:
    • Push the final approved dataset to an Airtable base (one table for menu items, one for allergens). Export as CSV and email to stakeholders automatically.
  • HTML matrix:
    • Use a simple HTML template in Manus. The workflow fills a table with menu rows and Big 9 columns, using “Yes/May/No” labels and tooltips with detail. Host the static HTML in your client’s Drive public folder or site. Provide a QR code link in the deliverable email.
  • Change log:
    • Manus appends an itemized change log (e.g., “July 12 update: supplier spec for Brioche Bun v3 → v4; Wheat still yes; Sesame now may contain”).

8) Printable menu icons and staff one-pagers

  • Icons:
    • Build a set of 9 icons in Canva Pro: high-contrast, printable at 0.5–0.75 inches. Provide PNG and SVG. Include a usage key and branding for your agency.
  • One-pagers:
    • Use Canva Pro to produce:
    • Front: Big 9 icons with definitions.
    • Back: “How to answer guest questions”, “What to do if unsure”, emergency contact protocol, and where to find the latest matrix (QR link).
  • Delivery:
    • Store assets in a Drive folder within Google Workspace. Manus sends the folder link after approval is complete.

9) Scheduled monthly re-checks

  • Add a Scheduler trigger in Manus to run on the 1st of each month at 6 a.m.
  • Steps:
    • Re-fetch all hosted spec sheet links and vendor portals.
    • Check version/hash against last month; re-run parsing only on changed docs.
    • Generate diffs and route to approval.
    • Email new CSV/HTML and printables if changes were approved. If no changes, email a “No change” certificate with timestamp.
  • Optional automations:
    • Push tasks to your CRM base in Airtable.
    • Send an invoice if variable work exceeded the tier limits via Zapier.

Pro tip: Spin up your Manus account here so you can follow along step by step: https://manus.im/invitation/OJF7FVBNBC14H?utm_source=invitation&utm_medium=social&utm_campaign=copy_link

Packaging and pricing (keep it simple)

  • Starter: $300 setup + $75/month
    • Up to 25 menu items
    • Monthly re-check, one approval round
    • CSV + HTML matrix
  • Standard: $450 setup + $125/month
    • Up to 60 items
    • Monthly re-check + mid-month hotfix on request
    • CSV + HTML + printable icons + one-pager
  • Pro/Multi-location: $600 setup + $200/month
    • 100+ items or multiple menus
    • Twice-monthly re-checks
    • Priority support, branded assets, per-location matrices

Scope guardrails

  • What’s included: ingest vendor PDFs/links, recipe spreadsheet mapping, 1 approval cycle, CSV/HTML export, icons/one-pagers as per tier.
  • What’s extra: custom nutrition fields, new menu launches beyond the item cap, mid-month multiple changes, vendor portal logins requiring MFA cycles.
  • Contract and signature: Use a simple SOW and collect e-sign with DocuSign.

How to start today using public data (portfolio-first approach)

  • Pick a cuisine you know (e.g., burger bistro, cafe, tapas). Download 10–20 public spec sheets and a sample menu:
    • Vendor spec sheets: Search “site:tysonfoodservice.com allergen pdf”, “site:usfoods.com allergen statement pdf”, “brand + ‘spec sheet pdf’”.
    • Breads/buns: look up “brioche bun allergen pdf”, “gluten-free bun spec”.
    • Sauces/condiments: “aioli allergen pdf”, “mayo allergen sheet”.
    • Proteins: “salmon spec sheet pdf”, “chicken tender allergen pdf”.
    • Note: Always respect copyright and usage terms for public documents; do not scrape behind logins without permission.
  • Build a sample recipe spreadsheet with 10 items (Burger, Salad with Vinaigrette, Veggie Wrap, etc.). Columns: Item, Ingredients (comma-separated), Modifiers (e.g., “no croutons”), Notes.
  • Run your Manus pipeline end-to-end on this data and produce:
    • CSV + HTML matrix
    • Icons + one-pager
  • Package your sample as “Bistro Allergen Matrix Demo by Your Agency” in a Google Workspace folder. Share a view link in pitches.

Allergen mapping details to get right

  • Sesame edge cases:
    • Tahini, sesame oil (note that highly refined oils may be exempt in some jurisdictions; include a clarification note and rely on supplier statements).
  • Tree nuts vs coconut:
    • Coconut is classified as a tree nut in some contexts but often treated differently. Use supplier declarations; when in doubt, flag for approval with a clear note.
  • Wheat vs gluten-free flours:
    • Gluten-free flour blends can include oat or other grains; if oats are gluten-free certified, note it; otherwise, flag.
  • Soy lecithin:
    • Common in chocolate and baked goods. Mark Soy “Contains” unless the supplier’s statement clarifies otherwise.
  • Anchovy-containing sauces:
    • Caesar dressings and Worcestershire often contain fish (anchovy). Add explicit rules to detect.

Restaurant obligations and disclaimers

  • Your deliverables help organize and communicate existing supplier data; they do not replace medical advice or the restaurant’s duty to verify allergens with suppliers.
  • Add this footer to every matrix and one-pager:
    • “Allergen information is based on supplier statements and in-house recipes. Cross-contact may occur. For severe allergies, please alert staff. Always verify current information before serving.”
  • Keep approvals tight: always require a named staff member to click Approve in Manus before you publish updates.

Outreach scripts to land your first 3–8 clients
Target: Independently owned restaurants, 1–3 locations, 20–120 menu items, with visible menus online and active Instagram.

Cold email script (owner/GM)
Subject: 30-minute fix for Big 9 allergen labeling at [Restaurant Name]
Hi [First Name],
I built a simple service that turns your supplier PDFs and recipe spreadsheet into a clean Big 9 Allergen matrix for staff and guests. It auto-rechecks vendor spec changes monthly and sends you an updated CSV + printable sheet.

Typical setup: $300–$600 one-time, then $75–$200/month. Takes less than 1 hour of your team’s time.

I made a live demo so you can see it in 30 seconds:
– Sample matrix: [link]
– 1-page staff handout: [link]

If this saves your team 3–5 hours/month and reduces risk, would a quick 12-minute call tomorrow at 10:30 or 2:00 work?

Best,
P.S. Workflows run in Manus: https://manus.im/invitation/OJF7FVBNBC14H?utm_source=invitation&utm_medium=social&utm_campaign=copy_link

Instagram DM script
Hey [Restaurant IG Handle] — I help small restaurants keep allergen info current. I turn your supplier PDFs + recipe sheet into a clean Big 9 matrix staff can check on their phones. It re-checks vendor changes monthly and emails updates. It’s $300–$600 to set up, then $75–$200/mo. Want me to show a 1-minute demo for one of your menu items? No cost.

Phone call opener
“Hi, is [GM/Owner] available? My name is [Name]. I run a tiny service that keeps your allergen matrix current by reading supplier PDFs automatically. Most teams spend 3–5 hours/month on this; we cut it to 15–30 minutes with an approval step so you stay in control. Setup is a few hundred; after that it’s a small monthly. Could I email a 30-second demo? If it’s useless, ignore it. If it’s helpful, we’ll book a 12-minute call.”

Follow-up structure

  • Day 0: Email + IG DM
  • Day 2: Reply-all bump with “short demo inline” showing 1 item’s matrix
  • Day 5: Phone call
  • Day 9: Case study email (include before/after time saved)
  • Day 14: Final nudge: “Should I close this file?”

Qualifying questions (ask before quoting)

  • How many active menu items?
  • Do you have a recipe spreadsheet (Google Sheets or Excel)?
  • Where do you store vendor spec sheets?
  • How often do products change?
  • Who would approve monthly updates?

Service delivery SOP (to scale without chaos)

  • CRM: Track leads, clients, and menu item counts in an Airtable base. Fields: Tier, Item count, Intake email/Drive folder, Approval contact.
  • Intake hygiene: Give each client a unique intake email and Drive folder in Google Workspace. Require that all updates go there.
  • Naming: “YYYY-MM VendorName ProductName vX.pdf” for files. Store in client’s folder. Manus reads this for versioning.
  • Approvals: Require 1 named approver and 1 backup. No publishing without green light.
  • Contracts and billing: Send e-signable SOW in DocuSign. Collect card or ACH on file at signature.

1-day launch checklist (from zero to first demo)
Hour 1–2: Foundation

Hour 3: Data backbone

  • Create an Airtable base with tables: Leads, Clients, Menu Items, Vendor Specs.
  • Add a simple CRM view: Pipeline by stage.

Hour 4–5: Build the Manus workflow

  • Triggers: Email ingestion and Drive watch folder (for “01 Demos/Vendor Specs”).
  • Steps: Fetch URL (for hosted sheets), Parse Document with OCR, Transform data (normalize ingredients), Allergen Mapping rules, Approval Task, Export to Airtable, Generate HTML, Email results via Google Workspace.
  • Scheduler: Monthly at 6 a.m.

Hour 6: Create demo materials

  • Download 10–15 public spec sheets from common items (buns, sauces, proteins).
  • Draft a 10-item sample menu spreadsheet.

Hour 7: Icons and one-pager

  • Design Big 9 icons in Canva Pro.
  • Build a “How to use the allergen matrix” one-pager in Canva Pro.

Hour 8: Export and package

  • Run the workflow; approve in Manus; export CSV and HTML; save to “01 Demos/Output”.
  • Put everything in a shareable folder in Google Workspace.

Hour 9: Sales assets

  • Write your cold email, IG DM, and phone script. Paste into the “00 Sales Assets” folder.
  • Create your e-sign template in DocuSign.

Hour 10–11: Prospect list and first sends

  • Build a list of 40 local independent restaurants (with emails/IG handles) in Airtable.
  • Send 20 personalized cold emails and 20 IG DMs with your demo links.

Hour 12: Book and confirm

  • Reply fast to any interest. Offer 12-minute zoom slots tomorrow. Prepare to show the live Manus approval step to build trust.

Execution tips to reduce errors and rework

  • Use explicit references: When mapping allergens, always store the exact phrase and page number where it was found, so you can show receipts during the approval.
  • Edge-case bucket: Create a “Needs Clarification” tag for items like imported desserts, specials, and third-party baked goods without clear disclosures.
  • Don’t over-automate the final decision: Your approval step is a feature, not a bug. It protects you and your client.
  • Keep the HTML matrix brutally simple: one screen, no scrolling on mobile, tooltips for “May contain”. Fancy can wait.

Time and cost breakdown per client

  • Setup (2–6 hours):
    • Intake and folder setup: 20–30 minutes
    • Parsing and mapping: 60–180 minutes depending on item count
    • Approval cycle: 15–45 minutes
    • Exports and training sheet: 20–40 minutes
  • Monthly maintenance (30–60 minutes):
    • Re-check runs: 10–20 minutes
    • Approvals: 10–20 minutes
    • Exports and email: 10–20 minutes
  • Gross margin: After 3–4 clients, expect 75–85% margins; costs are your time + software subscriptions for Google Workspace, Airtable, and small automations via Zapier or Make.

Quality control checklist (per release)

  • Confirm all vendor PDFs were parsed this cycle (no errors or timeouts).
  • Scan the diff: Any “Contains” status that flipped must be highlighted in the release note.
  • Verify the HTML QR link loads on iOS and Android.
  • Reprint icons at 100% scale; check that text is legible in grayscale.
  • Ensure signature of the approver is recorded in Manus with a timestamp.

Common objections and how to answer

  • “We already have a spreadsheet.” Great; we plug your sheet into Manus so it stays updated automatically, and you approve changes before they go live. You keep the spreadsheet.
  • “We’re small and our menu doesn’t change.” Perfect; the Starter tier runs a monthly check. If nothing changes, you get a “No change” certificate for your records.
  • “Can’t my staff do this?” They can, but it takes 3–5 hours/month and gets deprioritized. We do it in 30 minutes with an audit trail and vendor doc links embedded.

Mini case example (what to show on calls)

  • Menu: 28 items; bread-heavy brunch cafe.
  • Vendor sources: 16 PDFs, 3 hosted links.
  • Findings:
    • Sesame changed from “No” to “May contain” on brioche buns (supplier v3 → v4).
    • Fish detected in Caesar anchor (anchovy in dressing).
  • Output:
    • CSV + HTML matrix; icons sheet with W, E, S, F, etc.
    • One-pager for staff: new sesame handling note at sandwich station.
  • Time: 3.5 hours setup; 35 minutes monthly.
  • Cost to client: $450 setup + $125/month.
  • Value: Eliminated 4–6 hours of manual checking; caught a sesame change before a complaint.

Tool stack summary and where they fit

Scripting the allergen matrix HTML (simple structure you can replicate)

  • Columns: Item, Milk, Egg, Fish, Shellfish, Tree Nuts, Peanuts, Wheat, Soy, Sesame
  • Cell states:
    • Yes: red “Yes”
    • May: amber “May”
    • No: green “No”
  • Tooltips: On hover or tap, show “Found: [terms] in [vendor file name vX]” with date.
  • Footer: “Approved by [Name] on [Date]. Next scheduled check: [Date].”

Scaling from 1 to 12 clients without breaking

  • Standardize your intake emails and folder names in Google Workspace.
  • Clone a Manus template workflow per client to isolate data and approvals.
  • Store your rule dictionaries in a shared step that you can import, so updates benefit all clients.
  • Build a “Release” form in Airtable that you complete each cycle; it becomes your internal QA sign-off.
  • Quarterly cleanups: Archive old vendor specs and keep the last 2 versions live.

Legal and risk notes

  • You are not certifying allergen safety; you are organizing supplier-provided information with a client-approved signoff.
  • Always include the client approval step. No publish without it.
  • Keep a 12-month archive of approved outputs for audits.

Action plan for your first week

  • Day 1: Complete the 1-day launch checklist; send 40 cold messages; book 2–3 demos.
  • Day 2–3: Run a custom demo for the most responsive lead using two of their actual items. Offer a $300 setup Starter tier to start quickly.
  • Day 4–5: Close 1–2 clients. Deliver within 72 hours. Ask for a 2-sentence testimonial and permission to show a blurred matrix screenshot.
  • Day 6–7: Polish your HTML template and icon set, tighten mapping rules, and add FAQs to your one-pager.

Your first three commitments to every client

  • Consistency: Monthly re-check runs like clockwork.
  • Clarity: CSV + an ultra-simple HTML matrix that staff can read at 6 a.m. before coffee.
  • Accountability: Named approvals, diffs, and a change log every time.

Ready to build it now? Your Manus workflow is the engine that powers all of this. Create your account with this invitation link and follow the steps above: https://manus.im/invitation/OJF7FVBNBC14H?utm_source=invitation&utm_medium=social&utm_campaign=copy_link

CTA — Start your AI Allergen Micro-Agency today

Top comments (0)