Director of Information Systems

Veridian Service Partners · Dallas, TX · 1 mo ago

RemoteRemoteInformation TechnologyFull-time

About the role

The Role We run on our systems. Leads, appointments, contracts, jobs, payroll and reporting all move through a connected stack, and when that stack works nobody notices it. When it does not, every market feels it at once. This role owns that stack. Not a single application — the whole thing, and the connections between the pieces. You will own the CRM, the in-home sales platform, the project management system we are standing up, the integrations that move data between them, and the standards for how AI is used in the systems and tooling this function governs. This is a build, not a maintenance job. We are three markets and one brand today. The plan takes us across the Sunbelt with three brands. The systems that got us here will not get us there, and you will be expected to set the sequence yourself. That judgment is the job.

Responsibilities

Own the CRM (systems i360 / improveit 360) – configuration, permissions, territories, lead sources, product setup, and the governed data layer the business reports from.
Own Leap / SalesPro – pricing configuration (not strategy); enforce pricing, discount thresholds, and approval rules set by leadership; recommend, implement, and integrate tools when sales reports issues; ensure configured reality matches approved policy.
Own the project management system (greenfield) – selection, implementation, and rollout across markets for internal workstreams, market launches, cross‑functional projects, and system rollouts (not field job management or scheduling).
Own the wider stack integrations – Rippling, Sage, Ramp, Google Workspace and growth tooling; ensure data agreement and connections; you are not the administrator of all but own how they connect.
Own integrations and data – lead‑to‑appointment‑to‑contract‑to‑job‑to‑invoice flow; build and hold definitions; resolve reporting discrepancies; make the stack survive expansion via configuration rather than project work.
Own the market launch stack – the configured set of systems, routing, territories, pricing, compensation, and reporting that a new market or brand turns on with.
Author and maintain AI standards – define appropriate use, data proximity, output quality; draft with Legal, HR, and Finance; adopt by executive team; enforce; identify where AI genuinely removes work; train, monitor, and surface policy drift to the executive team.
Lead the Salesforce Administrator and Growth Specialist, Integrations; decide what to build, buy, or hand to a partner; be the person the business goes to when a system blocks work; run the intake queue (requests from Sales, Operations, Finance, Growth) prioritized by a cross‑functional council on a published cadence; ensure operations gets committed capacity, not leftover capacity, and finance signs off shared definitions.

What Success Looks Like

Inside your first month you have baselined the measures this function runs on: time to launch a market, reporting integrity, intake cycle time, tool count and spend, and adoption.

By 90 days you have mapped the stack end to end and told us what is fragile, what is duplicated, and what is quietly costing us money. You have an opinion on the project management system and a recommendation.

By 6 months, the project management system is live in at least one market. The integrations you inherited are documented. The AI standard exists and people have been trained on it.

By 12 months, opening a market is a configuration exercise rather than a scramble. Sales, Finance and Operations pull the same number from the same place. Your team has grown and you hired well.

Who This Is For

You will report to the Chief Growth Officer, who owns this function and will give you scope, budget and air cover. You will be the most senior systems voice in the company. The architecture calls are yours to make and yours to defend. That makes this a good job for someone who has done it before and a hard job for someone who has not. If you need a technical leader above you to sharpen your thinking, this will be frustrating. If you have been the most senior systems person in a growing company and liked it, this will feel familiar.

What You Bring