You are helping me complete a Cloudflare Partner Portal deal registration. https://www.partners.cloudflare.com/partners/s/register-deal Goal: Research the account, prepare accurate deal registration inputs, then help fill the Cloudflare Partner Portal form as much as possible. Do not submit the form unless I explicitly say: “Submit the deal registration.” Workflow: 1. Read my account notes. 2. Research the company using public sources: official website, LinkedIn, annual reports, registries, news, DNS/provider footprint, and reliable databases. 3. Build a review table before touching the portal. 4. Separate confirmed facts from assumptions. 5. Ask me for missing or risky fields before proceeding. 6. After approval, use the in-app browser to fill the portal. 7. If a field is difficult to automate after 2–3 attempts, stop and hand it to me instead of wasting time. 8. Pause for me at login/MFA, sensitive data entry confirmation, validation errors, and final submit. Account notes: [PASTE NOTES HERE] Required review table columns: - Field name - Proposed value - Source or reasoning - Confidence: High / Medium / Low - Questions for me Data to collect: Company: - Company name - Legal entity name - Website - Country, state/province, city, address - Industry - Employee count - Annual revenue estimate - Registration number - VAT / tax number if available Contact: - Main customer contact name - Title - Email - Phone - LinkedIn if useful - Decision makers Opportunity: - Deal name - Opportunity type - Expected close date - Estimated annual contract value - Currency - User count - Current provider / competition - Pain points - Business drivers - Technical drivers - Timeline - Probability Cloudflare fit: - Relevant Cloudflare products - Why Cloudflare is a good fit - Why GlobalDots is involved - GlobalDots services required - POC / migration / managed service scope Provider footprint: Check whether the customer appears to use Cloudflare, Akamai, AWS, Azure, GCP, Fastly, Imperva, Microsoft 365, Zscaler, or other relevant providers. State only what is evidenced. Portal filling preferences: - Distributor: use No unless I say otherwise. - Reseller Sales Rep: use my logged-in/requestor details unless I provide another rep. - Reseller SE: if involved but details are missing, ask me. If I say to use my name, use the logged-in/requestor details. - Opportunity type: choose the closest Cloudflare portal option, usually Zero Trust, Security, Performance & Security, or Email Security. - Primary Use Case: choose the closest portal option. For SAP/private app access, prefer Access. - Budget discussed: if ACV/range was shared, choose the matching “Yes” option. - Marketing/SPIFF: choose No unless notes say otherwise. - Public sector: No unless clearly public sector. - Customer under attack: No unless notes say otherwise. Browser automation rules: - Use the in-app browser. - Pause for me to log in or complete MFA. - Before entering contact emails, phone numbers, or other sensitive data into the portal, ask for explicit confirmation describing exactly what will be transmitted to Cloudflare. - Do not submit the form unless I explicitly say: “Submit the deal registration.” - If Salesforce/date/dropdown controls are flaky, try at most 2–3 reasonable automation attempts, then ask me to take over that field. - After each page, summarize what was filled and ask me for any missing required fields. Deal description format: Customer background: [2–3 sentences] Business challenge: [2–4 bullets] Proposed Cloudflare solution: [2–4 bullets] Partner value from GlobalDots: [2–4 bullets] Next steps: [2–4 bullets] Tone: Professional, concise, partner-friendly, and suitable for Cloudflare’s partner team. Do not invent uncertain facts.