Job Title: Technical Solutions Consultant (Remote)

Location: Remote (Must work core Eastern Time hours)

Salary: $125,000 – $185,000 Base + Bonus (Level dependent)

Reports to: VP Client Strategy

Daily partners: CRO, COO, VP Product, CS (CSMs/TAMs), Sales Engineering (as needed)

Why this role exists

TitanX wins when we’re the expert in the room for outbound execution: CRM + SEP (sales engagement platform) + dialer + reporting expectations. The market doesn’t need more activity theatre or dashboards. Customers need a clean, fast path to more real conversations per hour, without breaking their process, compliance posture, or reporting.

This role exists to make TitanX:

• Easier to buy (confidence in “how this actually works here”)
• Faster to go live (no heavy onboarding)
• Harder to rip out (embedded in their operating rhythm)

It also takes full ownership of a function currently carried by leadership bandwidth. This is a commercial pilot operator role with strong systems fluency, not a “support” role and not internal RevOps.

Core responsibilitiesA) Run pilots like a production line (without losing the craft)

• Own the end-to-end pilot execution plan across dozens of concurrent pilots
• Keep momentum: schedule discipline, follow-ups, decision gates
• Identify blockers fast and resolve or escalate cleanly
• Drive adoption behaviours, not just “setup completion”

B) Make buying feel safe

• Remove “technical uncertainty” as a reason to stall
• Translate stack reality into a simple operating plan the customer trusts
• Know when to say “no” (or “that’s not best practice”) without being awkward, rude, or vague

C) Package the pilot into a closeable deal

• Collect deal-critical context throughout (not at the end in a panic)
• Produce crisp, reusable artefacts:
• Pilot Plan (1 page)
• Success Criteria + Definition of Done
• “What We Learned / What’s Next” closeout note

D) Codify what works so the company gets faster

• Maintain short playbooks by common stack patterns (SFDC/HubSpot + SEP + dialer)
• Maintain a “known gotchas” list that prevents repeat pain
• Feed Product/CS the signal (breakpoints + patterns), not anecdotes

What this is not

• Not internal RevOps for TitanX
• Not a bespoke integration engineering role
• Not a dumping ground for general product support
• Not “turn up and be helpful” — this is a disciplined operating motion

What we need Must-haves

• High-volume pilot leadership: you can run 30–40 structured pilots/month without chaos
• Commercial sharpness: you understand deal mechanics, decision dynamics, and stakeholder mapping
• Systems fluency: you can confidently navigate Salesforce + HubSpot realities (objects, permissions, logging, workflows)
• Operating discipline: checklists, crisp follow-ups, and ruthless clarity on owners/next steps
• Customer presence: calm, clear, credible; you can lead a room and simplify complexity
• Written clarity: you can write a one-page plan that people actually follow

Strong preference

• Familiarity with Sales Engagement Platforms (Outreach / Salesloft / Gong Engage) in the real world
• Comfort with dialer/telephony concepts (local presence, deliverability basics, logging expectations)
• Experience bridging Sales ↔ CS ↔ Product without creating meetings as a hobby

“Technical” expectations (kept sane)

You do not need to be an engineer. You do need to understand:

• Permissions and why they matter
• Where data should land (and how it typically breaks)
• How to diagnose: config vs access vs mapping vs vendor change vs product issue
• How to communicate that diagnosis simply and professionally

What “great” looks like (outcomes)

• Deals stop stalling on uncertainty (“we just need to check with RevOps…”)
• Pilots become predictable, repeatable, and fast
• Customers feel TitanX is part of their operating system, not bolted on
• Handoffs are clean and post-sale teams aren’t inheriting mystery meat
• The company gets faster every month (because patterns are codified)

Scope boundaries

In scope

• Pilot execution: planning, scheduling, facilitation, adoption, closeout
• Stack fluency validation: ensuring TitanX fits their operating reality
• Structured triage and escalation (with reproducible evidence)
• Playbooks/checklists/templates that scale the motion

Out of scope

• Owning TitanX’s internal admin work (you’re not our Salesforce admin)
• Custom middleware / bespoke builds as the default
• Being the catch-all for non-pilot product issues