Disaster Recovery & Business Continuity: HubSpot's Infrastructure for Financial Firms

Step-by-Step Framework for Implementing Compliant Email, SMS, and Social Media Automation

Here's a sobering statistic: Financial advisors spend 30-40% of their time simply switching between different systems.

The 3:47 AM Wake-Up Call

At 3:47 AM on a Tuesday morning, a major cloud service provider suffered a catastrophic data center failure affecting thousands of financial services firms. Within minutes, advisors across the country lost access to client data, communication histories, and critical business operations. Some firms didn't recover for 72 hours. Those without robust disaster recovery plans faced devastating consequences: missed client deadlines, regulatory reporting failures, and reputational damage that took years to repair.

For financial services firms, system availability isn't a convenience—it's a regulatory requirement and fiduciary obligation. When your CRM contains client portfolios, financial plans, communication records, and compliance documentation, downtime means you cannot serve clients, meet regulatory obligations, or operate your business.

The question isn't whether a disaster will occur, but when—and how quickly you'll recover.

For SEC-registered investment advisors, FINRA member firms, and other regulated financial institutions, business continuity planning is mandatory. SEC Rule 206(4)-7 requires RIAs to adopt and implement written policies and procedures reasonably designed to prevent violations of the Advisers Act. FINRA Rule 4370 requires member firms to create and maintain written business continuity plans.

In this comprehensive guide, we'll explore HubSpot's enterprise-grade disaster recovery infrastructure, show you how to integrate HubSpot into your firm-wide business continuity planning, and provide actionable strategies to ensure your firm can weather any crisis while protecting client data and maintaining operations.

Understanding Disaster Recovery vs. Business Continuity

Before diving into HubSpot's capabilities, let's clarify two often-confused concepts:

Disaster Recovery (DR)

Focus: Technology systems and data
Goal: Restore IT infrastructure and data after a disruption
Scope: Technical procedures for backup, recovery, and restoration

Metrics:

• RTO (Recovery Time Objective): How quickly can systems be restored?
• RPO (Recovery Point Objective): How much data loss is acceptable?

Example DR Scenario: Data center failure—how quickly can you restore access to HubSpot data?

Business Continuity (BC)

Focus: Business operations and processes
Goal: Maintain critical business functions during and after a disruption
Scope: People, processes, facilities, communications, and technology

Metrics:

• Time to restore critical business functions
• Alternate work arrangements effectiveness
• Communication protocol success

Example BC Scenario: Office building uninhabitable due to fire—how do advisors continue serving clients?

The Relationship: Disaster recovery is a technical subset of broader business continuity planning. HubSpot provides the DR infrastructure; you must build the BC processes around it.

HubSpot's Multi-Region Data Center Architecture

Enterprise-Grade Infrastructure

HubSpot operates on Amazon Web Services (AWS) infrastructure with sophisticated redundancy and failover capabilities specifically designed for enterprise customers in regulated industries.

Geographic Distribution

Primary Data Centers:

• US-East (Virginia): Primary data center for North American customers
• EU-Central (Frankfurt): Primary for European customers (GDPR compliance)
• APAC (Sydney): Growing presence for Asia-Pacific customers

Key Architecture Features:

Multi-Availability Zone (AZ) Deployment

• Each region spans multiple physically separate data centers
• 10+ miles apart to prevent single disaster affecting both
• Independent power, cooling, and network connectivity
• Synchronous replication between AZs for zero data loss

Cross-Region Replication

• Critical data replicated to secondary regions
• Geographic diversity protects against regional disasters
• Meets regulatory requirements for data residency while ensuring recovery

Global Content Delivery Network (CDN)

• Assets distributed to 200+ edge locations worldwide
• Reduces latency for global teams
• Provides DDoS protection
• Continues serving cached content during partial outages

Infrastructure Resilience Features

Network Redundancy:

• Multiple tier-1 internet service providers
• Redundant network paths within and between data centers
• Automatic traffic rerouting during network failures
• 99.99% network availability SLA

Power and Environmental Controls:

• Uninterruptible Power Supply (UPS) systems
• On-site diesel generators with 48+ hours of fuel
• Redundant cooling systems with N+1 configuration
• Environmental monitoring and automatic alerts

Security and Physical Protection:

• 24/7 physical security with biometric access
• Video surveillance and intrusion detection
• Fire suppression systems (water-free for data centers)
• Seismic and flooding risk mitigation

Data Replication and Consistency

Real-Time Synchronous Replication:

• All data written to primary storage simultaneously replicated to secondary AZ
• Ensures zero data loss (RPO = 0) for critical data
• Automatic failover to secondary AZ if primary fails
• Typical failover time: under 5 minutes

Asynchronous Cross-Region Replication:

• Near-real-time replication to distant geographic regions
• Protects against complete regional failure
• RPO typically under 15 minutes
• Manual failover for cross-region scenarios (requires HubSpot operations team)

Database Architecture:

• Distributed database clusters with automated sharding
• Automatic rebalancing during failures
• Read replicas for performance and availability
• Point-in-time recovery capabilities

Automated Backup Schedules and Point-in-Time Recovery

HubSpot's Backup Strategy

Financial firms need confidence that client data is protected against accidental deletion, data corruption, or malicious attacks. HubSpot implements multiple layers of backup protection.

Continuous Data Protection

Transaction Logs:

• Every database transaction logged in real-time
• Logs replicated to multiple storage locations
• Enables point-in-time recovery for any moment
• Retention: 30 days of transaction logs

Snapshot Backups:

• Automated snapshots every 24 hours
• Incremental backups capturing only changes
• Full snapshots weekly
• Retention: Daily snapshots for 7 days, weekly snapshots for 4 weeks

Immutable Backups:

• Once written, backups cannot be modified or deleted
• Protects against ransomware and malicious deletion
• Stored in separate security domain from production
• Meets SEC and FINRA immutability requirements for certain records

Recovery Capabilities

Granular Recovery Options:

• Contact-Level Recovery: Restore individual deleted contacts
• Object-Level Recovery: Restore specific deals, companies, or custom objects
• Property-Level Recovery: Revert specific field values
• Account-Level Recovery: Restore entire account to previous point-in-time
• Custom Object Recovery: Restore custom data structures

Point-in-Time Recovery (PITR):

• Restore data to any moment within the 30-day window
• Useful for recovering from mass deletions or data corruption
• Typical recovery time: 2-8 hours depending on data volume
• Available through HubSpot Support for Enterprise customers

Recovery Process Example

Scenario: Marketing coordinator accidentally bulk-deletes 5,000 contacts on October 15 at 2:30 PM

Recovery Steps:

1. Contact HubSpot Support immediately (within 30-day window)
2. Specify recovery point: October 15, 2:29 PM (before deletion)
3. HubSpot Support initiates PITR process
4. Recovery completed within 4-6 hours
5. Contacts restored with all properties, associations, and history intact
6. Workflow states resumed from pre-deletion point

Backup Best Practices for Financial Firms

While HubSpot provides robust backup infrastructure, financial firms should implement additional protection layers.

1. Regular Data Exports

Monthly Complete Export:

• Export all contacts, companies, deals, and custom objects
• Store in firm's document management system
• Provides offline copy independent of HubSpot
• Useful for long-term archival (7+ years)

HubSpot Export Process:

• Settings > Objects > [Object Type] > Export
• Options: All properties, All records, Include associations
• Format: CSV or Excel
• Destination: Secure file share or document management system
• Schedule: First business day of each month
• Responsibility: Operations Manager with backup by Compliance Officer

Automated Export Workflow:

• Use HubSpot's Operations Hub to schedule automated exports
• Automatically upload to secure cloud storage (Box, SharePoint, Google Drive)
• Notification sent to compliance when export complete
• Maintains 3-year rolling archive

2. Critical Data Redundancy

For mission-critical data, implement bidirectional sync with your primary systems:

Portfolio Management System ↔ HubSpot:

• Real-time or daily sync of client data
• Ensures data exists in multiple systems
• Provides alternate data source during HubSpot outage

Document Management System ↔ HubSpot:

• Store critical documents outside HubSpot
• Reference documents in HubSpot with links
• Documents accessible even if HubSpot unavailable

3. Compliance Documentation Backup

Quarterly Compliance Archive:

• Export all email communications
• Export audit logs and approval records
• Export compliance dashboard data
• Burn to immutable media (write-once storage) for 7-year retention
• Store in offsite facility per firm's records retention policy

Incident Response Procedures and Communication Protocols

Understanding Incident Types

Not all incidents are equal. Financial firms should classify incidents by severity and trigger appropriate responses.

Incident Classification Framework

Level 1 - Critical (System-Wide Outage):

• HubSpot completely unavailable
• Data breach or suspected unauthorized access
• Mass data loss or corruption
• Response Time: Immediate (15 minutes)
• Leadership Notification: CEO, CCO, CTO
• Client Communication: Within 2 hours if client-facing impact

Level 2 - High (Significant Functionality Loss):

• Key features unavailable (email sending, workflow execution)
• Performance degradation affecting business operations
• Integration failures with critical systems
• Response Time: 30 minutes
• Leadership Notification: CCO, CTO
• Client Communication: If extends beyond 4 hours

Level 3 - Medium (Limited Impact):

• Non-critical features unavailable
• Minor performance issues
• Single-user access problems
• Response Time: 2 hours
• Leadership Notification: IT Manager
• Client Communication: Not required unless affects client deliverables

Level 4 - Low (Minimal Impact):

• Cosmetic issues
• Documentation problems
• Enhancement requests
• Response Time: Next business day
• Leadership Notification: Not required
• Client Communication: Not required

Incident Response Procedures

Phase 1: Detection and Verification (0-15 minutes)

Detection Sources:

• HubSpot Status Page monitoring (status.hubspot.com)
• User reports of issues
• Automated monitoring alerts
• Integration failure notifications

Verification Steps:

• Confirm incident is real (not isolated user problem)
• Assess scope (affects one user vs. entire firm)
• Check HubSpot Status Page for known issues
• Classify incident level
• Initiate appropriate response protocol

Initial Response Actions:

• Document incident start time
• Capture screenshots/evidence
• Create incident ticket in firm's system
• Notify incident response team

Phase 2: Containment and Assessment (15-60 minutes)

For HubSpot-Related Incidents:

Contact HubSpot Support (Enterprise priority support):

• Phone: Dedicated enterprise support line
• Email: Enterprise support portal
• Slack: Direct channel for Enterprise customers
• Provide: Account ID, incident description, business impact

Assess Business Impact:

• Which business functions are affected?
• Can clients be served through alternate means?
• What regulatory deadlines are at risk?
• What revenue is at risk?

Implement Interim Workarounds:

• Switch to backup communication methods
• Access data through exports or integrated systems
• Reroute workflows to manual processes
• Notify staff of workaround procedures

Document Everything:

• Timeline of events
• Actions taken
• People involved
• Communications sent

Phase 3: Communication (Ongoing)

Internal Communication Protocol:

Immediate (within 15 minutes):

• Notify incident response team via dedicated Slack channel or SMS
• Alert affected users via email with workaround instructions
• Post to internal status page or intranet

Hourly Updates (for Level 1 and 2 incidents):

• Current status
• Expected resolution time
• Workarounds available
• Next update time

Resolution Communication:

• Announce resolution across all channels
• Confirm systems functioning normally
• Document lessons learned
• Schedule post-incident review

External/Client Communication Protocol:

Trigger: Level 1 incident extending beyond 2 hours with client-facing impact

Communication Template:

Subject: Service Update - [Brief Description]

Dear [Client Name],

We are writing to inform you of a temporary service disruption affecting 
our client communication systems.

What Happened:
[Brief, honest explanation without technical jargon]

Impact on You:
[Specific impact to this client, if any]

What We're Doing:
[Steps being taken to resolve]

How You Can Reach Us:
[Alternate contact methods]
- Phone: [Number]
- Email: [Backup email]
- [Other methods]

Expected Resolution:
[Realistic timeframe or "working as quickly as possible"]

We sincerely apologize for any inconvenience and will provide updates 
as we have them.

Best regards,
[Firm Leadership]

Regulatory Communication:

If incident involves data breach or extended outage affecting regulatory compliance:

• Consult legal counsel immediately
• Determine notification obligations (varies by state and regulator)
• Draft formal notification to regulators
• Coordinate with PR firm for public statements (if required)

Phase 4: Recovery and Restoration (Timeline Varies)

When HubSpot Services Resume:

Verify System Functionality:

• Test core features (contact access, email sending, workflows)
• Verify data integrity (no corruption or loss)
• Confirm integrations reconnected
• Test user access and permissions

Resume Operations Gradually:

• Start with critical functions (client communication)
• Resume automated workflows after verification
• Return to normal staffing patterns
• Monitor closely for 24-48 hours

Data Reconciliation:

• Check for any data created during outage that didn't sync
• Verify workflow executions that should have occurred
• Reconcile email sends and delivery
• Update contact records with offline interactions

Phase 5: Post-Incident Review (Within 7 Days)

Conduct Formal Review Meeting:

• What happened and why?
• What worked well in our response?
• What could be improved?
• What preventive measures can we implement?
• Update incident response procedures

Documentation:

• Complete incident report
• Timeline of events
• Business impact analysis
• Response effectiveness assessment
• Recommendations for improvement
• Sign-off by CCO and CTO

Regulatory Reporting (if required):

• File required notices with regulators
• Maintain records for examination
• Implement remediation measures
• Update business continuity plan

Testing Disaster Recovery Plans Quarterly

Why Testing Matters

An untested disaster recovery plan is a work of fiction. Testing reveals gaps, validates assumptions, and builds muscle memory for when real disasters strike.

Regulatory expectations:

• SEC: Advisors must have "reasonable procedures" for business continuity
• FINRA Rule 4370: Requires annual review of business continuity plans
• Best Practice: Quarterly testing ensures readiness

Types of Disaster Recovery Tests

1. Tabletop Exercise (Quarterly)

Purpose: Talk through scenarios without actually disrupting systems

Process:

• Scenario Selection: Choose realistic disaster scenario
• Participant Assembly: IT, compliance, operations, leadership
• Scenario Walkthrough: Step-by-step discussion of response
• Document Decisions: Record what would be done at each step
• Identify Gaps: Note missing procedures, unclear responsibilities, needed resources

Example Tabletop Scenarios:

Scenario 1: HubSpot Complete Outage

Time: Tuesday, 10:00 AM
Situation: HubSpot is completely unavailable - no access to any features
Duration: Unknown, possibly 8-12 hours

Discussion Questions:

• How do we first learn of the outage?
• Who is notified and how quickly?
• What client meetings or deadlines are affected today?
• How do advisors access client contact information?
• Can we execute trades or process transactions?
• How do we send scheduled client communications?
• What workarounds exist for each affected function?
• When do we notify clients?
• How do we document the incident?

Scenario 2: Ransomware Attack

Time: Friday, 8:00 AM
Situation: Ransomware encrypted several workstations. IT has isolated affected systems. Attackers potentially accessed HubSpot via compromised credentials. Ransom demand: $500,000 Bitcoin.

Discussion Questions:

• Who is in charge of incident response?
• Do we involve law enforcement?
• How do we assess what data was compromised?
• What is our policy on paying ransom?
• How quickly can we restore from backups?
• What are our client notification obligations?
• What regulators must we notify?
• How do we prevent credential misuse in HubSpot?

Documentation:

• Meeting notes with decisions made
• Action items and responsible parties
• Timeline for addressing gaps
• Updated procedures based on learning

2. Data Recovery Test (Semi-Annual)

Purpose: Verify ability to restore data from backups

Process:

• Select Test Scope: Choose subset of data (e.g., 100 test contacts)
• Create Test Environment: Separate HubSpot sandbox or isolated list
• Simulate Deletion: Delete test data
• Execute Recovery: Follow documented recovery procedures
• Verify Restoration: Confirm all data, properties, and associations restored
• Document Results: Time to recover, any issues encountered, lessons learned

Success Criteria:

• Recovery completed within RTO target (e.g., 4 hours)
• 100% of data restored accurately
• All associations and history intact
• Team executed procedures without major errors

3. Failover Test (Annual)

Purpose: Verify ability to continue operations using alternate systems

Process:

• Schedule Maintenance Window: Friday evening or weekend
• Notify Staff: Practice scenario treating HubSpot as unavailable
• Activate Alternate Procedures: Use backup systems for 4 hours
• Test All Critical Functions:
  • Accessing client contact information (from exports or integrated systems)
  • Sending client communications (direct email, alternate platforms)
  • Documenting client interactions (backup CRM or manual logs)
  • Accessing compliance records (from archives)
• Return to Normal: Resume HubSpot operations
• Debrief: What worked? What didn't? What needs improvement?

Example Failover Activities:

• Advisor conducts client meeting using exported contact data instead of HubSpot
• Marketing coordinator sends newsletter using alternate email platform
• Operations staff logs new client inquiry in backup system
• Compliance officer accesses audit records from quarterly export

4. Full Disaster Simulation (Annual)

Purpose: Test complete business continuity plan under realistic conditions

Process:

• Choose Complex Scenario: Office unavailable + system outages
• Unannounced Element: Surprise timing for some staff (not leadership)
• Activate Business Continuity Plan: Full execution of all procedures
• Test Duration: 4-8 hours
• Observe and Document: Evaluators watch and record effectiveness
• Comprehensive Debrief: All participants provide feedback

Example Full Simulation:

Scenario: Office building evacuated due to gas leak. All staff working remotely. HubSpot experiencing performance issues (degraded but not down). Phone system partially affected.

Required Activities:

• All staff transition to remote work within 1 hour
• Activate alternate communication systems
• Conduct at least 3 client meetings remotely
• Process 5 client service requests
• Send scheduled marketing email using degraded system
• Hold team meeting via video conference
• Document all activities for compliance
• Demonstrate ability to serve clients normally

Creating Your Quarterly Testing Schedule

Q1 (January-March):

• Tabletop Exercise: HubSpot outage scenario
• Review and update business continuity plan
• Update contact information for emergency notification

Q2 (April-June):

• Data Recovery Test: Practice restoring deleted records
• Tabletop Exercise: Cybersecurity incident scenario
• Verify backup systems are current and accessible

Q3 (July-September):

• Tabletop Exercise: Natural disaster scenario (hurricane, wildfire)
• Review vendor (HubSpot) business continuity capabilities
• Test failover to alternate systems

Q4 (October-December):

• Annual Full Disaster Simulation
• Comprehensive review of year's testing results
• Update procedures based on lessons learned
• Present results to board and regulatory review

Testing Documentation Requirements

For Each Test, Document:

• Test Plan: Scenario, objectives, success criteria, participants
• Test Execution: Step-by-step record of what happened
• Results: What worked, what didn't, recovery times achieved
• Gaps Identified: Problems, missing procedures, training needs
• Remediation Plan: How to address gaps, responsible parties, deadlines
• Sign-Off: CCO and CEO approval

Maintain Testing Records:

• Store in compliance files
• Organize by quarter and year
• Make available during regulatory examinations
• Demonstrate continuous improvement over time

Integration with Firm-Wide Business Continuity Planning

HubSpot as Component of Enterprise BC Plan

HubSpot disaster recovery is one piece of your firm's broader business continuity strategy. Effective integration requires:

1. Critical Business Function Analysis

Identify Functions Dependent on HubSpot:

Document Dependencies:

• What other systems integrate with HubSpot?
• If HubSpot is unavailable, what else breaks?
• Which staff members cannot perform their jobs?
• What client deliverables are at risk?

2. Define Recovery Objectives

Set Targets for HubSpot-Dependent Functions:

Recovery Time Objective (RTO): Maximum tolerable downtime

• Client Communication: 1 hour (critical)
• CRM Access: 2 hours (high)
• Marketing Automation: 24 hours (medium)
• Reporting: 5 days (low)

Recovery Point Objective (RPO): Maximum acceptable data loss

• Contact Data: Zero (replicated real-time)
• Email Communications: 1 hour (acceptable to lose unsent drafts)
• Workflow States: 15 minutes (recent activity replicated)

Strategies to Meet Objectives:

• RTO < 1 hour: Requires immediate access to alternate communication methods (backup email lists, phone numbers)
• RPO = 0: Requires real-time data sync to backup system or more frequent exports

3. Alternate Work Site Strategy

Primary Office Unavailable - Where Does Work Happen?

Remote Work Model (Most Financial Firms):

• Staff work from home offices using VPN
• Access HubSpot via web interface (device-agnostic)
• Use video conferencing for team coordination
• Cloud-based systems enable location flexibility

HubSpot Advantages for Remote Work:

• Cloud-based (no on-premise infrastructure needed)
• Mobile app for iOS and Android
• Accessible from any internet-connected device
• No special software installation required

Requirements for Remote Access:

• VPN for secure connectivity (especially with IP whitelisting)
• Multi-factor authentication enforced
• Staff have laptops or home computers
• Home internet connectivity (have backup cellular hotspot)

Alternate Office Location (if needed):

• Coworking space with high-speed internet
• Partner firm office (reciprocal agreement)
• Executive offices at different location
• Hotel business centers (temporary)

4. Communication Tree

Establish Emergency Notification Procedures:

Primary Communication Method: Dedicated emergency contact system (separate from HubSpot)

• Mass notification service (AlertMedia, OnSolve, Everbridge)
• Group text messaging via personal phones
• Phone tree with designated backup contacts

Emergency Contact Information:

• All staff personal cell phones
• Personal email addresses (not work email if systems down)
• Secondary contacts (spouse, family member)
• Updated quarterly, verified annually

Notification Sequence:

1. CEO/Crisis Manager initiates notification (within 15 minutes of incident)
2. Leadership team notified simultaneously
3. All staff notified within 30 minutes
4. Key clients notified within 2 hours (if client-facing impact)
5. Vendors/partners notified as appropriate
6. Regulators notified if required (24-72 hours depending on incident type)

5. Vendor Management and Dependencies

HubSpot as Critical Vendor:

Include in Vendor Risk Management Program:

• Annual review of HubSpot's SOC 2 and security certifications
• Quarterly review of HubSpot Status Page incident reports
• Evaluation of HubSpot's disaster recovery capabilities
• Assessment of HubSpot's business continuity plan
• Verification of HubSpot's insurance coverage

Vendor Redundancy Strategy:

• Identify alternate CRM/marketing platforms (backup vendor)
• Maintain relationships with competitors (ability to switch if needed)
• Diversify critical functions across multiple platforms where possible
• Don't put all eggs in one basket

Integration Risks:

• If HubSpot fails, what integrated systems are affected?
• Portfolio management system sync breaks?
• Document management links inaccessible?
• Website chat and forms stop working?

Mitigation:

• Build integration failover logic (graceful degradation)
• Queue data during outages for later sync
• Manual workarounds for each integration
• Regular testing of integration failure scenarios

Building Resilience Through Preparation

Disaster recovery and business continuity planning aren't about preventing disasters—that's impossible. They're about ensuring your financial firm can withstand disruptions, protect client data, meet regulatory obligations, and resume operations quickly.

HubSpot provides enterprise-grade infrastructure specifically designed for regulated industries: multi-region data centers, automated backups, point-in-time recovery, and robust uptime guarantees. But technology alone isn't enough. Your firm must build comprehensive procedures, train staff thoroughly, test regularly, and integrate HubSpot into your broader business continuity strategy.

The firms that survive disasters aren't the ones that never experience problems—they're the ones that prepare thoroughly, respond quickly, communicate transparently, and learn continuously from every incident.

Key Takeaways

✓ Leverage HubSpot's Infrastructure: Understand and rely on HubSpot's multi-region architecture and backup systems

✓ Add Redundancy Layers: Supplement with your own exports, integrated systems, and offline backups

✓ Document Everything: Create detailed incident response procedures and recovery steps

✓ Test Regularly: Quarterly testing reveals gaps and builds response capability

✓ Integrate Broadly: HubSpot DR is one component of firm-wide business continuity

✓ Communicate Clearly: Have plans for internal and external communication during crises

✓ Learn and Improve: Every incident and test is an opportunity to strengthen resilience

In an industry where trust is your most valuable asset and regulatory compliance is non-negotiable, investing in robust disaster recovery and business continuity capabilities isn't optional—it's fundamental to being a professional, responsible financial services firm.

About Vantage Point

Vantage Point helps financial services firms implement enterprise-grade HubSpot solutions with comprehensive disaster recovery and business continuity planning. Our team combines technical expertise with regulatory knowledge to ensure your firm can weather any crisis while protecting client data and maintaining operations.

Ready to strengthen your firm's resilience? Contact Vantage Point for a business continuity assessment and implementation roadmap tailored to your financial firm's unique regulatory requirements and risk profile.

This concludes our Week 2 series on "Compliance & Security: HubSpot for Regulated Financial Firms." We've explored GDPR and SOC 2 compliance, SEC and FINRA communication requirements, data security best practices, compliant marketing automation, and disaster recovery capabilities. Together, these articles provide a comprehensive framework for financial firms to leverage HubSpot's powerful capabilities while meeting the strictest regulatory standards.

About the Author

David Cockrum is the founder of Vantage Point and a former COO in the financial services industry. Having navigated complex CRM transformations from both operational and technology perspectives, David brings unique insights into the decision-making, stakeholder management, and execution challenges that financial services firms face during migration.

• • • Email: david@vantagepoint.io
    • Phone: (469) 652-7923
    • Website: vantagepoint.io