<aside>
About Brainforge
At Brainforge, we're on a mission to transform data into actionable insights that drive business success. As a rapidly growing data and AI consulting company, we partner with clients across industries to deliver cutting-edge Data, AI, and Strategy & Analytics solutions. Join our team and help clients get real value from what we ship.
Transforming raw data into actionable insights
We help businesses boost revenue, save time, and make smarter decisions with Data and AI
Follow Us
Brainforge | An Insights Company
www.linkedin.com/company/brain-forge/
</aside>
<aside>
Why this seat now?
- Early client success is the gap: Onboarding, first calls, sprint hygiene, and packaging — not inventing the delivery OS from scratch.
- Complement, don't replace, Head of Delivery: This role makes existing accounts healthier and more expandable; Head of Delivery still owns portfolio standards and leadership.
- Account manager with an enablement bent: Drive adoption of what we deliver; turn work into accelerators and curriculum.
- Known quantity, tighter box: Integrated already; success is focus — existing clients, no partner work, maintain standards (don't invent them).
- Comp fits the scope: Lower base than senior delivery leadership; variable tied to retention, expansion, and enablement adoption — services metrics, not SaaS ARR.
</aside>
<aside>
Client Enablement Lead
Full-time · Remote, US-based · Reports to: TBD (Head of Delivery / CSO leadership)
Shaped after enablement-led CS roles (e.g. Applied AI Enablement Lead) — adapted for Brainforge services, not SaaS seats.
📌 Role overview
Buying an engagement and actually getting value from it are two different things. This role closes that gap.
The Client Enablement Lead owns early customer success and ongoing account enablement for an assigned book of clients. You are the primary operator for onboarding, sprint hygiene, packaging, and curriculum — the person who turns delivery work into reusable accelerators and keeps documentation and playbooks current against company standards.
This is a customer-facing seat with a TPM / account-manager bent and a strong enablement focus. You provide basic technical guidance and hands-on setup support; engineers and architects own depth. You do not replace Head of Delivery, own architecture, or act as a Sales Engineer.
What you'll do
1. Drive account health, retention & expansion (assigned book)
- Own early success: onboarding, first calls, kickoff clarity, and a clean path from SOW → first value
- Run (or co-run) sprint cadence: planning, status, blockers, and packaging outcomes so work is usable beyond the sprint
- Set and maintain engineer hour / capacity expectations with delivery leads so clients and the team have a clear plan
- Partner with delivery and account leadership on retention and expansion signals — without owning partner/channel work
2. Educate & enable client teams
- Lead practical workshops, working sessions, and 1:1s that make data/AI delivery usable for non-technical and semi-technical stakeholders
- Build and run an enablement curriculum (playbooks, checklists, training collateral) so clients can operate what we've built
- Turn repeated delivery patterns into accelerators and reusable packages clients and internal teams can adopt
3. Guide basic technical setup — with a clear boundary
- Walk client IT / ops stakeholders through basic setup and handoff (access, environments, docs, light integrations) where needed
- Provide technical guidance and hands-on setup support without acting as technical architect or Sales Engineer
- Escalate architecture, complex integration, and deep SE work to the right owners
4. Keep standards alive (don't invent them)
- Maintain client and platform documentation against existing Brainforge standards so artifacts stay current and packaged well
- You do not create org-wide standards from scratch; you keep agreed standards running and surface gaps to standards owners
- Raise the bar on handoffs: clear docs, accelerators, and "what good looks like" for an engaged account
5. Voice of the client (delivery-facing)
- Synthesize field feedback into crisp asks for delivery, productized offerings, and GTM — focused on adoption and account success
- Support renewal and expansion conversations with evidence of value delivered and enablement progress
Out of scope
- Partner / channel development or partner-related programs
- Defining company-wide engineering or documentation standards from scratch
- Acting as Head of Delivery, technical architect, or Sales Engineer
- Broad "own the whole book" AM without enablement / TPM execution
This role is / is not
This role is:
- Early CS + TPM muscle on existing clients
- Account management with an enablement / packaging bent
- Curriculum and accelerator builder; docs maintainer against standards
- Basic technical guidance with a hard stop before architecture / SE
This role is not:
- A substitute for Head of Delivery
- Standards author for the company
- Partner lead or channel enablement owner
- Deep technical architect or Sales Engineer
Ideal qualifications
Must-have
- 5–8+ years in customer success, solutions consulting, technical enablement, TPM, or client-facing delivery (services / B2B preferred)
- Experience owning outcomes tied to account health, retention, and expansion
- Strong facilitation; can make technical delivery approachable for non-technical stakeholders
- Comfortable with basic technical guidance and setup support; clear about when to escalate
- Demonstrated ability to build or run enablement curriculum, playbooks, or packaged accelerators
- Operator mindset: sprints, hours/capacity hygiene, documentation discipline, packaging for reuse
Nice-to-have
- Background in data platforms, analytics, or applied AI delivery
- Experience in regulated or operationally complex industries
- Prior TPM or professional-services CS experience
- Already familiar with Brainforge ways of working and client context
💰 Compensation
- Base: $125,000 – $140,000, depending on experience
- Variable: ~30% of target total compensation → OTE ≈ $162,500 – $182,000, plus equity if applicable
Variable payout is based on performance against three metrics on your assigned book of clients (services / retainer model — not SaaS ARR):
| --- | --- | --- |
SaaS → Brainforge proxies (why not ARR / WAU):
- NRR still works if the recurring base = retainer + active contracted run-rate
- Expansion ARR → expansion revenue (incremental contracted $ from existing clients)
- Product WAU / feature adoption → operating adoption (clients using and running what we delivered; enablement + packaging + doc health)
Do not tie variable primarily to company-wide software ARR, partner pipeline, whole-bench utilization, or inventing standards.
📍 Location & logistics
</aside>