Investor Relations Websites

How to Choose an Investor Relations Website Provider

VendorGroup

Compare investor relations website providers using practical demonstrations of publishing, accessibility, integrations, support, migration, and contract terms.

Choose an investor relations website provider by testing how the proposed service will work for your company. Design matters, but so do publishing controls, filing access, accessibility, support, and the ability to move your information later.

Start with a concise requirements brief and ask each candidate to respond to the same scenarios. This makes proposals easier to compare than a feature list alone.

Define the work before requesting the price

List the pages, archives, documents, integrations, approval steps, and operating responsibilities the company needs. Identify the current problems and any fixed milestones. Separate confirmed requirements from optional enhancements.

Include the issuer-specific website requirements supplied by counsel. A provider should explain how it will implement those instructions, not claim that a generic package resolves every regulatory question.

Use the content guide and essential checklist to prepare the brief. Ask candidates to identify exclusions and assumptions explicitly.

Request demonstrations built around real tasks

Have the provider walk through a results update: preparing the page, attaching documents, obtaining approval, publishing, and verifying the live output. Then ask it to demonstrate a correction and explain the version record.

Test the filing archive with a known issuer and document. Ask how amendments, old filings, and service interruptions are handled. The demonstration should show the public result as well as the editor's view.

Ask how a last-minute event change reaches the page, listing, registration service, and support team. These exercises reveal the handoffs your staff will actually use.

Evaluate accessibility through evidence

Request the proposed conformance target, scope, testing methods, findings process, and remediation ownership. Include downloadable documents and third-party tools where they form part of the investor experience.

W3C explains that no automated tool alone can determine accessibility. [1] A badge, overlay, or scan score should therefore not replace the provider's explanation of its assessment and retesting process.

Ask to see a representative issue resolved through the workflow. Confirm what is included in the project and what creates additional cost.

Understand the operating agreement

Clarify hosting responsibilities, named support contacts, service hours, escalation routes, and measurable commitments. Distinguish acknowledgment of a request from restoration of a failed service.

Review access controls for the CMS, domain, hosting, and supplier accounts. CISA recommends MFA, especially for administrative access. [2] Ask how the proposed service implements that control and manages staff departures.

Request backup and restoration evidence appropriate to the agreement. Identify responsibility for software changes, feed failures, document updates, and accessibility issues discovered after launch.

Compare total scope and exit terms

Normalize the proposals into setup, migration, recurring service, usage-based charges, and optional work. Confirm assumptions about archive volume, document remediation, integrations, and support requests. The cost guide provides the comparison framework.

Review ownership and export rights for content, designs, assets, data, and accounts. Ask what remains usable if the company changes providers. The provider-change guide explains why these terms belong in the original agreement.

For timing, require milestones and dependencies rather than a date detached from scope. The redesign timeline guide shows how to evaluate the proposed schedule.

Make the selection reviewable

Score each candidate against the same requirements and keep notes from demonstrations. Separate evidence from sales assurances. Verify any references or case studies you choose to rely on, and avoid assuming that another company's project predicts your own outcome.

The final decision should explain why the selected service fits the company's publishing and operating needs, what it will cost under the agreed assumptions, and which responsibilities remain internal.

Questions companies ask

Should a specialist provider always win?

Evaluate demonstrated fit. Relevant experience can inform the review, but the proposed workflow, evidence, agreement, and team still need assessment.

Is the lowest recurring fee the best value?

Compare the full scope, including setup, migration, licenses, support limits, and exit costs. A fee is meaningful only with its assumptions.

What is the most useful demo request?

Use an actual investor communication workflow and include an error or correction. See how the team and system handle the complete task.

What should be settled before signing?

Agree on deliverables, acceptance, ownership, responsibilities, service terms, fees, and transition arrangements. Resolve material ambiguities in writing.

VendorGroup's IR website offering includes website design, hosting, and support. [3] Apply the same evidence-based questions when evaluating its fit for your company.

Related VendorGroup resources

Primary sources

  1. W3C WAI — Evaluating Web Accessibility
  2. CISA — Require Multifactor Authentication
  3. VendorGroup — Investor Relations Websites

Contact

VendorGroup®