restaurant-pitch-doc

To create a one-minute sales pitch for a restaurant prospect, generate a concise pitch document from audit findings, lead research, and prototype notes. This produces a structured one-page brief with a 60-second read, call opener, leaks/fixes, demo path, and close.

A restaurant battle card for outreach should include identified revenue leaks, three to five strengths, and a before/after narrative explaining how your redesign fixes the pre-dining experience. All claims must be traceable to local audit artifacts and lead research notes.

Yes, you can generate outreach summaries from audit findings, prototype READMEs, and built site code. The process extracts revenue leaks and redesign value from these local artifacts to form a structured pitch document tailored for restaurant prospects.

To identify revenue leaks in a restaurant prospect's website, analyze local artifacts like audit.md, source lead research, and built site code. The analysis highlights broken standard practices and revenue losses to address in your pitch document.

Yes, you need existing audit artifacts to generate a restaurant pitch document. You must first read local files like audit.md, README.md, content.example.ts, key routes, and any Google review synthesis to ensure all pitch claims are traceable to source materials.

The best way to structure a pre-call brief for restaurant sales is using a template that includes a 60-second read, call opener, leaks/fixes section, demo path, and close. This ensures a concise, one-page document that lands effectively during outreach.