About the role
Role Title: Sales / Revenue / CS Operations Expert
Role Type: Contractor
Location: Remote — U.S. or Canada only
Opportunity Snapshot
Pay: $40–85/hour
Project kickoff: Already active — we’re onboarding candidates now
Location: Remote — U.S. or Canada only
You’ll need: Hands-on configuration experience in a CRM (Salesforce, HubSpot, or similar) plus at least two connected tools — quoting, billing, ticketing, or project tracking
Your tasks: Work through realistic SaaS revenue and CS operations scenarios and explain the reasoning behind your decisions
micro1 is selecting Sales / Revenue / CS Operations Experts to contribute to a customer’s AI training initiative. Your domain knowledge is what matters here — no prior AI experience required.
We’re looking for people who have personally configured and maintained CRM platforms and the revenue tools around them. The work rewards practical judgment: resolving policy conflicts without overcomplicating the process, and knowing what actually makes teams adopt a workflow.
Scope of Work
1. Work through realistic operations scenarios — CRM configuration decisions, workflow design, integration tradeoffs — and explain the reasoning behind each choice. 2. Resolve conflicts between operational policies: which rule takes precedence, why, and what you would deliberately leave unchanged. 3. Diagnose data accuracy problems across connected systems — duplicates, mismatched numbers, inconsistent definitions — and explain how you’d find the root cause. 4. Explain what makes a workflow get adopted or worked around by sales and CS teams. 5. Flag ambiguous or underspecified scenarios instead of resolving them silently.
Preferred Qualifications
1. 4+ years hands-on in sales, revenue, or customer success operations in SaaS. 2. Personal responsibility for configuring and maintaining a CRM — direct platform experience required, not requesting changes from another team. 3. Hands-on experience with at least two connected tools outside the CRM: quoting, billing, ticketing, or project tracking. 4. Strong operational judgment, particularly in resolving policy conflicts without overcomplicating the process. 5. Able to explain your reasoning clearly to technical and non-technical audiences.
Originally posted on Himalayas