RevOps Lead

Hike is building the operating system for device-based care. We make software and hardware for the $60B+ DMEPOS market: Hike Intelligence automates intake and revenue cycle with AI agents, Hike Clinical runs point of care, and SoleForge, our 65,000 sq ft facility in Peoria, IL, 3D prints custom medical devices at a scale few facilities in North America can match.

We raised $22M from investors including SAGA Ventures, founded by Max Altman. Our founder's family has worked in orthotics and prosthetics for three generations, and we know these workflows better than anyone in the world. We build for clinicians because we come from them.

The revenue motion works at Hike. Outbound books meetings, meetings turn into pipeline, pipeline turns into national partnerships, and SoleForge turns those partnerships into shipped devices. What we don't have yet is a system underneath it all that can be trusted at scale.

Right now revenue runs on Hubspot but we are investing heavily in our CRM and supporting tools and will likely be shifting to Salesforce, which will need a real implementation, a tooling stack that grew by accident, and reporting that's held together by whoever built the last spreadsheet. That's fine for the stage we just left. It will not survive the stage we're entering.

That is the job. Build the operating system for our revenue org the way we build the operating system for our customers. Own Hubspot / Salesforce end to end, wire the stack around it, design the processes that move a lead from a cold list to a closed partnership, and turn the data into a forecast leadership can bet on.

You will own revenue operations for the company. Not administer it. Own it. When someone asks why the number moved, the answer comes from your systems, your data model, and your reporting. You report directly to leadership and you are the source of truth.

1. Own CRM. Architect and implement it properly, not patch it. Data model, objects, validation, automation, permissions, and integrations. You are the admin, the architect, and the person who decides what "clean" means. If the org has drifted, you fix it. Where it's greenfield, you build it right the first time.

2. Build the revenue stack and the data layer. CRM is the core, but it doesn't stand alone. Own the tooling around it — enrichment, sequencing, dialers, CPQ, BI, and the integrations that keep them in sync. Kill what doesn't earn its seat. Make sure every system writes back to one source of truth.

3. Design the process and the insight. Lead routing, territory, stage definitions, deal desk, forecasting cadence, and comp operations. Then turn all of it into reporting the team actually uses — pipeline health, conversion by stage, rep performance, forecast accuracy. Numbers, not vibes.

• Own the end-to-end Salesforce implementation: data model, automation, integrations, and hygiene

• Build and administer the full revenue tech stack across sales, marketing, and CS

• Design and run the forecasting process leadership uses to plan

• Define lead routing, territories, stage gates, and deal desk workflow

• Operate compensation plans and quota tracking, and keep them accurate to the dollar

• Build reporting and dashboards that make the funnel legible from top to bottom

• Keep CRM data clean enough that every number in the business traces back to it

• Partner with sales, marketing, finance, and CS so their systems talk to each other

• Instrument new motions as we launch them — new channels, new segments, new products

• 5+ years in revenue, sales, or business operations, with real ownership of the systems

• Deep Salesforce expertise: you have implemented and administered it, not just used it. Certifications a strong plus

• A track record you can show: implementations you led, stacks you built, processes you designed, and what changed because of them

• You have built revenue infrastructure from an early stage, not just maintained a mature one

• Strong analytical instincts: you turn messy data into forecasts and decisions

• Fluent in modern revenue tooling and comfortable putting AI to work on ops, enrichment, and analysis

• Hands-on. If you haven't been in a CRM building something yourself in two years, this is not your job

• Healthcare, medtech, or DME experience is a plus, not a requirement. Hunger to learn the market is required

• In person in San Francisco

• A revenue motion that already works. You build the system under a fire, you don't start one

• Direct line to leadership and a seat in go-to-market strategy, not a back-office function

• Total ownership of the systems the whole company runs on

• Clear path to a Head of / Director of RevOps scope as the org scales

• Top-of-market comp