This static page replaces the original scored survey logic with a clean presentation of the two client-facing report packages described in the instruction file. The visual structure, classes, and styling approach are preserved while all executable behavior has been removed.
2 Two PDF packages · Static content only · No executable logic
OVERVIEW
The instruction file defines two separate premium deliverables for a tour operator. Each package contains one cover letter and one report, written for clean client-facing PDF export.
Package 1: Cover Letter 1 + Starter Profit Assessment Report.
Package 2: Cover Letter 2 + Deep-Dive Profit Analysis Report.
Source of truth: The instruction prompt file now governs the content and intent of this page.
PACKAGE 1
This package is the concise, entry-level deliverable. It is designed to give the operator an immediate understanding of profit position, pricing strength, and key leakage areas while naturally leading into the deeper paid analysis.
Cover Letter 1
1 page
The cover letter should thank the operator for completing the survey, introduce the Starter Profit Assessment Report, direct the reader to begin with the Profit & Pricing Score, and mention the availability of the Deep-Dive Profit Analysis Report.
Starter Profit Assessment Report
2–3 pages + upsell block
The report should include these exact sections in order: Cover Page, Your Profit & Pricing Score, Top 3 Strengths, Top 3 Profit Leak Areas, Additional Profit Per Guest Potential, and Pricing Structure Risks.
A prominently styled upsell block must appear after Section 6 and before the footer disclaimer. It should explain six specific reasons to upgrade to the $199 Deep-Dive Report and include a bordered call-to-action link.
PACKAGE 2
This package is the comprehensive consulting-style deliverable. It must go beyond the starter report, avoid repeating its content, and provide deeper analysis, scenario work, and an actionable 90-day execution plan.
Cover Letter 2
1 page
The cover letter should thank the operator, introduce the Deep-Dive report, and walk the reader through the report in six short numbered steps tied to report section numbers and contents.
Deep-Dive Profit Analysis Report
Approximately 12 pages
The report should include these exact sections in order: Cover Page, Executive Summary, Business Snapshot, Profitability Overview, Pricing Analysis, Booking Channel Analysis, Capacity and Load Factor Analysis, Tour Mix and Product Performance, Discounting and Promotions, Customer Experience and Review Performance, Operational Efficiency, Missed Revenue and Hidden Profit Opportunities, 90-Day Action Plan, Priority Scorecard, and Strategic Closing.
CONTENT RULES
The instruction file requires commercially useful, client-facing writing based only on the specified CSV row. It also defines caution rules, tone rules, disclaimers, section order, and formatting expectations for each package.
Use only the specified CSV row as the business data source.
Treat survey answers as directional business inputs, not audited financial statements.
Use plain US English and avoid filler, generic praise, and unsupported precision.
Tie every recommendation to evidence from the selected row.
Do not repeat Starter Report content inside the Deep-Dive Report.
PACKAGE 1 SECTIONS
1. Cover Page
2. Your Profit & Pricing Score
3. Top 3 Strengths
4. Top 3 Profit Leak Areas
5. Additional Profit Per Guest Potential
6. Pricing Structure Risks
Upsell block appended after Section 6 and before the footer disclaimer.
PACKAGE 2 SECTIONS
1. Cover Page
2. Executive Summary
3. Business Snapshot
4. Profitability Overview
5. Pricing Analysis
6. Booking Channel Analysis
7. Capacity and Load Factor Analysis
8. Tour Mix and Product Performance
9. Discounting and Promotions
10. Customer Experience and Review Performance
11. Operational Efficiency
12. Missed Revenue and Hidden Profit Opportunities
13. 90-Day Action Plan
14. Priority Scorecard
15. Strategic Closing
STATIC IMPLEMENTATION NOTES
The original file used dynamic survey and results behavior. In this static refactor, interactive logic is intentionally removed and represented only as readable static content and implementation notes.
No <script> tags remain.
No inline JavaScript handlers remain.
No dynamic score calculation, form progression, or PDF generation remains in this file.
Future behavior should be implemented outside this static HTML document.
