Lead Business Systems Architect

Position Overview

This is a rare opportunity to own the architecture of an entire company’s internal systems at a pivotal moment in its growth. The Lead Business Systems Architect will hold decision authority over the business systems roadmap, define how data flows across every department, and personally drive the integrations, automations, and adoption that make the whole operating model run better.

Position Responsibilities

• Own the business systems architecture and roadmap, maintaining a prioritized, leadership-visible plan for all internal systems and defining the source-of-truth model for core business objects including customers, contacts, opportunities, quotes, orders, cases, vendors, products, and activities.
• Extend Salesforce across every department, including a hands-on evaluation of the existing Service Cloud build and a determination of whether to complete it or recommend a better-fit case management platform, then build out the solution for Customer Experience, Product, and other teams with full reporting and visibility.
• Drive the HubSpot to Salesforce integration to completion and design the integrations across the website, Dialpad, Acumatica ERP, and data infrastructure, eliminating duplicate entry, disconnected records, manual handoffs, and reporting gaps.
• Architect and launch a company knowledge base that becomes the trusted source for processes, product knowledge, customer handling, and system guidance, structured from day one to support AI-assisted search and retrieval.
• Map current workflows across departments, identify where disconnected systems and unclear handoffs slow the business, redesign those processes, build durable automations, and measure results in hours saved, manual steps removed, response times, data quality, and adoption.
• Manage integration partners, consultants, and software vendors, keeping architecture and priorities owned in-house while holding vendors to a high standard and evaluating every tool through a business-first lens.
• Partner with the VP of Engineering on platform and website integrations, data infrastructure connectivity, and any work requiring engineering resources, and collaborate with Marketing on HubSpot lifecycle workflows, attribution, and the marketing-to-sales handoff.
• Lead cross-functional change in person, building trust with executives and frontline employees alike, driving adoption face to face, and serving as a credible advisor who can make the business case for software investments and future hires.

Position Qualifications

• A demonstrated track record of translating complex business problems into durable systems architecture, then personally executing the build from data model and integration design through adoption and measurable outcomes.
• A minimum of 7 years of progressive experience in business systems architecture, revenue operations systems, enterprise systems, or business process transformation at a growing company.
• Hands-on Salesforce architecture ownership covering data model, permissions, workflows, Service Cloud, and adoption across multiple departments. This is not a narrow Salesforce administration profile.
• Hands-on ownership of a support, ticketing, or case management platform such as Service Cloud, Zendesk, or ServiceNow, and its integration with CRM. Connor named this the single most meaningful screen for this search.
• Proven ability to integrate CRM, marketing automation, telephony, e-commerce or website, ERP, and reporting into a connected stack, with a track record of eliminating manual handoffs and data silos.
• Demonstrated ability to lead cross-functional change in person, working effectively with executives, frontline staff, and vendors without relying on formal authority.

Preferred

• Acumatica ERP integration experience specifically.
• HubSpot, Dialpad, Service Cloud, or knowledge base platform depth.
• Background in distribution, B2B e-commerce, building automation, HVAC, or another complex product environment.
• Exposure to enterprise AI or LLM tooling and knowledge retrieval systems as context, not as a primary responsibility, since this is not an AI engineering role.
• Comfort operating as a senior individual contributor with broad authority and no team to manage, in a lean, fast-moving environment where ownership extends from roadmap to execution detail.