PitchZone is our SaaS platform that guides applicants step by step through all questions in the ICANN Applicant Guidebook. With adaptive question logic, multilingual support, role-based collaboration, and AI-assisted drafting, PitchZone reduces the application timeline from months to weeks. What required armies of consultants in 2012 can now be accomplished by a lean, well-prepared team.
The platform is designed for organisations that want to maintain control of their application process while benefiting from expert guidance at every stage. All responses are stored securely, version-controlled, and exportable in the format required for ICANN submission. Legal review and sign-off by pitch.law attorneys is built into the workflow.
The 2026 Applicant Guidebook contains over 200 questions covering technical capacity, financial viability, operational policies, registry services, DNS abuse prevention, and the applicant's intended use of the TLD. In the 2012 round, applicants typically engaged multiple advisory firms, assembled fragmented documentation across email threads and shared drives, and spent months coordinating between legal, technical, and financial workstreams. The result was expensive, error-prone, and heavily dependent on individual consultant availability.
PitchZone was built to solve these problems. The platform presents the AGB questions in a structured sequence with adaptive logic (questions that are not relevant to your application type are automatically skipped), provides contextual guidance for each question drawing on pitch.law's ICANN expertise, and supports role-based collaboration so that legal, technical, financial, and operational team members can work on their respective sections simultaneously.
Adaptive Question Logic. The platform adapts to your application type (brand TLD, open gTLD, community TLD) and presents only the questions relevant to your profile, with dependencies between questions automatically managed.
AI-Assisted Drafting. For narrative responses to qualitative questions, AI-assisted drafting tools generate structured starting points based on your inputs and the AGB requirements. These drafts are reviewed and refined by the applicant team and pitch.law's attorneys.
Role-Based Collaboration. Legal, technical, financial, and operational workstreams can be assigned to appropriate team members with progress tracking, review workflows, and sign-off protocols. Everyone works from the same platform rather than exchanging document versions by email.
Version Control and Export. All responses are version-controlled with a full audit trail. Completed question sets can be exported in the formats required for ICANN submission.
PitchZone is designed for brand owners, governments, community organisations, and registry operators considering a new gTLD for ICANN's 2026 round. It supports both first-time applicants who need structured guidance and experienced operators applying for additional strings who want an efficient preparation platform.
Brand owners, governments, and community organisations considering a new gTLD for ICANN's 2026 round. PitchZone supports both first-time applicants and experienced operators applying for additional strings.
No, it works alongside it. PitchZone structures the application process and captures your responses systematically. Legal review, compliance verification, and ICANN submission are handled by pitch.law attorneys integrated into the platform workflow.
For a well-prepared applicant with clear strategic objectives and dedicated internal resources, PitchZone reduces the preparation timeline to weeks rather than the months typically required with traditional advisory approaches. The exact timeline depends on the complexity of the application and the readiness of supporting documentation.
Yes. PitchZone is available both as part of pitch.law's full advisory engagement and as a standalone SaaS platform. Standalone users benefit from the platform's guidance content and AI-assisted drafting. Legal review and sign-off by pitch.law attorneys is available as an add-on service.
%402x.svg){kind=icon}
%402x.svg){kind=icon}
%402x.svg){kind=small}