Frequently asked questions

Vantage Point is a senior-led, AI-augmented Salesforce and HubSpot consulting firm. We implement, integrate, migrate and support CRM, marketing automation, data and AI platforms, mainly for financial services and other regulated industries.

We focus on regulated industries: wealth management and RIAs, asset management, private equity, banking and credit unions, insurance, mortgage lending, fintech and debt settlement, plus healthcare, commercial real estate and professional services.

Your project is designed and delivered by experienced consultants, not handed to junior staff after the sale. The people you meet in discovery are the people who do the work.

Vantage Point is headquartered in Dallas, Texas, with a Central and Eastern Europe practice in Sofia, Bulgaria. We work with clients across the US, the UK and Europe.

We are a Salesforce partner, a HubSpot Solutions Partner, a member of the Claude Partner Network and the OpenAI partner network, and a member of the Braze Alloys partner network. We also implement technologies such as MuleSoft, Slack, Informatica and Contentful.

Vantage Point was founded in 2018 and has completed more than 400 engagements for over 150 clients, with a 95% client retention rate.

Whichever fits. We work on both, so our recommendation depends on your processes, complexity, data and growth plans rather than on which platform we sell.

Yes. Our founder spent more than a decade as COO of an RIA before starting Vantage Point, and most of our clients are RIAs, broker-dealers, asset managers, banks, insurers and lenders. We design around households, custodians, compliance review and advisor workflows from day one.

Because the right platform depends on the firm. Some need Salesforce's depth and industry data models, others need HubSpot's ease of use and marketing, and many run both. Working on both lets us recommend what fits rather than what we sell.

Yes. Once we understand your project, we connect you with a client who has done something similar, in a comparable industry where possible.

Yes. We are a member of the Claude Partner Network and the OpenAI partner network, and we help firms roll out Claude and ChatGPT safely alongside Salesforce and HubSpot.

Most start with a free CRM assessment call. From there we recommend either a fixed-scope package, a paid discovery phase for larger or less defined projects, or ongoing support.

Both. Well-defined projects are usually fixed-scope with clear deliverables. Larger or evolving work can run on time and materials, and ongoing support is offered as a block of hours, a retainer or managed services.

Every SOW states what is in scope and out of scope, what you provide, our assumptions, the acceptance criteria for each deliverable, training scope, and an optional post-go-live support block.

Yes. The initial assessment call is free and comes with no obligation. Deeper health checks with a scored report and roadmap are a paid engagement.

Yes. We work with firms from a handful of users to large enterprises, and we scope work so smaller firms can start with a focused package and grow.

Yes. We regularly work with Salesforce and HubSpot account teams so licensing and implementation plans line up.

Yes. Common starting points are a fixed-scope package, a short pilot focused on one use case, or a prepaid block of hours. Larger programs can start with a paid discovery or a short viability sprint before the full commitment.

It depends on the engagement. Fixed-scope projects are typically billed in milestones, blocks of hours are invoiced up front, and retainers or managed services are billed monthly. Your statement of work sets out the schedule.

For well-defined scopes, yes. We set a go-live date in the plan and state the client dependencies it relies on, such as timely data access, decisions and testing. For larger programs, the date is confirmed after discovery.

Licences are bought from Salesforce or HubSpot, and we work with their account teams so licence plans and implementation scope line up. Our fees for consulting are separate from licence costs.

Focused HubSpot or Salesforce implementations often take four to eight weeks. Larger implementations with migrations and integrations typically take two to six months. Discovery gives you a firm timeline.

Discovery, design, build in a sandbox, data migration and integration, user acceptance testing, training, go-live, then hypercare and ongoing support. Each phase ends with a deliverable you sign off.

A senior consultant leads your project, supported by specialists for integration, data or AI work where needed. You get a named point of contact throughout.

Yes. Training is scoped in every SOW, with sessions tied to the deliverables, and role-based materials. Additional training can be added at any time.

Every implementation includes a hypercare period to resolve issues quickly. After that, you can move to a block of hours, a retainer or managed services, or run the system yourselves.

Yes. We start with a health check to find what is broken, then fix data, automation, access and adoption issues in priority order.

We review your current systems and data, interview the people who use them, and agree requirements, priorities and risks. The output is a written design, a data mapping where relevant, and a firm plan and estimate.

We test as we build, then your team runs user acceptance testing in a sandbox using real scenarios from a test list we prepare together. Go-live happens once those scenarios pass.

Yes. A pilot focused on one team or use case is a good way to prove value and surface requirements before rolling out more widely.

Plan for a project owner who can make decisions, a few hours a week from key users during design and testing, and someone who can provide data and system access. We keep meetings focused and share progress asynchronously.

Three models: a block of hours for occasional needs, a retainer for steady monthly work with reserved capacity, and managed services for business-critical systems with service levels and roadmap governance.

Yes. Many clients use our managed services as their admin and RevOps team, covering user support, changes, release management and data quality.

It depends on the model. Blocks of hours expire after a set period, while retainer hours can roll over within the term. Details are set out in your agreement.

Not necessarily. Many clients rely on our managed services for administration and train internal champions over time. Larger firms often have an in-house admin, with us covering architecture, integrations and peak workloads.

A retainer covers day-to-day administration, user support, changes, release reviews, data quality and integration monitoring, delivered by a team with Salesforce, HubSpot and integration skills, so you are not dependent on one person.

Yes. Support can include connected systems such as Slack, DocuSign, MuleSoft, telephony, marketing tools and AI connectors, so one team owns the issues that cross system boundaries.

Response times are set in your support agreement. Critical issues are prioritized immediately, and every client has a named point of contact.

Yes. Financial Services Cloud is a core specialty, including household models, financial accounts, action plans, custodian integrations and migrations from Redtail, Wealthbox and other advisor CRMs.

Yes. We scope, build and test Agentforce agents for regulated firms, starting with a narrow, measurable use case and the data, permission and guardrail work that makes agents safe.

Yes. Vantage Point publishes its own AppExchange products, including RecordIQ, Field Set, Dynamic Forms and Advanced Data Table.

Often the problem is configuration and adoption, not the platform. We compare optimizing, migrating and a hybrid approach, and recommend the option with the best return for your situation.

It depends on your use cases. FSC adds households, financial accounts, relationships and action plans that most wealth, banking and insurance firms need. Firms with simple pipelines can start on Sales Cloud and move to FSC later.

Recent ones include SOAP API login() for integrations, Lightning Sync, legacy workflow rules and Process Builder, older Open CTI telephony approaches and Exchange EWS connections. Each has a migration path; we can check which affect your org.

All of them: Marketing, Sales, Service, Content, Data and Revenue Hub, plus Breeze AI agents and HubSpot's integration with Salesforce.

Often, yes. Reviewing marketing contact status, seat types and HubSpot credit usage usually finds savings, and we can automate the cleanup so it stays that way.

Usually partner or user access with the permissions needed for the work. Some integrations, such as connecting AI tools, require a super admin to authorize them.

Professional covers most marketing, sales and service needs. Enterprise is usually justified by custom objects, advanced permissions and teams, sandboxes or multiple business units.

Usually one account with brands, teams and permissions, which keeps reporting and contacts in one place. Separate accounts can make sense when entities must be kept apart for regulatory or ownership reasons.

Yes. HubSpot's native Salesforce connector syncs contacts, companies, deals and activity, so marketing can run in HubSpot while sales and service stay in Salesforce.

Yes. Connecting each user's inbox and calendar logs emails and meetings to the right records, with settings to exclude personal or sensitive messages.

Yes, with the right setup: enterprise AI plans that don't train on your data, connectors that respect each user's permissions, approval steps for actions, logging, and a clear AI policy.

Both are strong. We are partners of both Anthropic and OpenAI, and we recommend based on your use cases, integrations, admin controls and pricing.

Look at data quality, clear use cases, governance and user readiness. Our AI readiness assessment scores these and recommends where to start.

Yes. Claude connects to both through MCP connectors, so users can search, summarize and, where permitted, update CRM records with their own permissions.

HubSpot subscriptions include a monthly allowance of credits that Breeze features and agents use. Allowances depend on your plan, and admins can control whether more credits are bought automatically.

They do different jobs. Agentforce runs agents inside Salesforce on your CRM data and processes; Claude and ChatGPT are general assistants that can connect to the CRM. Many firms use both, with clear rules for each.

Enterprise plans from the major providers state that customer data is not used for training by default. We review each tool's settings and terms with you, and switch on AI features only after that review.

Most firms start with Claude Team for a pilot group and move to Enterprise for admin controls, single sign-on, audit needs and larger rollouts. We recommend based on your size, security requirements and the connectors you need.

Custodians and portfolio systems, agency management and loan origination systems, core banking, accounting, email and calendar, phone, eSignature, data warehouses, archiving providers and AI assistants, using native connectors, APIs or MuleSoft.

Native connectors are fine for one or two standard integrations. MuleSoft makes sense when you have many systems, need reusable APIs, high volumes, or strong monitoring and security.

Yes. We integrate custodian data from firms such as Schwab, Fidelity, Pershing and Altruist, usually directly or through a portfolio management system, into Financial Services Cloud or HubSpot.

You own them, with documentation and monitoring. Many clients include integration monitoring and fixes in a support agreement with us.

Then we build one, using the system's API through an integration platform such as Workato or MuleSoft, a lighter tool like Zapier for low volumes, or custom code. If a system has no API, scheduled file exports or a read-only database connection often work.

Not if it is designed properly. We agree which system owns each field, map external data to dedicated fields where needed, and test in a sandbox before switching on updates.

Yes. We integrate Aircall, Service Cloud Voice, RingCentral, Dialpad and others for click-to-call, call logging, routing and recordings.

Small, clean migrations can take a few weeks. Larger migrations with years of history, attachments and complex relationships usually take two to three months including testing.

No. We reconcile record counts and key values between source and target, test in a sandbox first, and keep source IDs so every record can be traced.

Yes. Most work happens in sandboxes. Cutover is planned for a quiet period, with a final delta load so nothing entered in the old system is missed.

Redtail, Wealthbox and other advisor CRMs to Salesforce, Salesforce to HubSpot and back, Dynamics and spreadsheets to CRM, Pardot and Marketing Cloud to HubSpot or Braze, help desks to Service Hub, and MuleSoft CloudHub upgrades.

Mostly before. Removing duplicates and junk first makes the load faster and cheaper. Some cleanup is easier in the new system with its own tools, and we agree the split in the mapping.

Usually yes, but they are the hardest part. Volume, storage limits and how the old system exports files decide the approach, and some firms archive older files instead of moving them.

Old automation, unused fields, duplicate or empty records, and history nobody uses. Anything you might need for compliance can be archived in a searchable format instead of loaded into the new CRM.

Large migrations can hit daily API limits. We use bulk loading, schedule loads carefully and, when needed, ask Salesforce for a temporary limit increase.

Yes. We design CRM, marketing and AI setups with SEC, FINRA and privacy requirements in mind, including access controls, archiving, approvals and audit trails. We do not provide legal advice, so we work with your compliance team.

We work inside your systems with the minimum access needed, use sandboxes and masked data where possible, and follow your security and data-handling policies.

We document data flows, access controls and vendor dependencies in your CRM and AI tools so your compliance team can evidence controls, and we configure the technical controls themselves.

Yes, with approval workflows, archiving of sent emails, consent management and compliant templates. We set these up in HubSpot, Account Engagement and Marketing Cloud.

We keep only the sensitive data you need, restrict it with field-level security and permission sets, mask it in sandboxes, and add encryption with Salesforce Shield where required.

Yes. For health-related businesses we design the CRM so protected health information stays in the clinical or member system, and the CRM holds only what marketing and relationship work needs.

Yes. Both support SAML single sign-on through providers such as Microsoft Entra ID and Okta, and multi-factor authentication. We configure them as part of implementation.