Overview
You're joining as the second RevOps hire at Sydecar, a Series A fintech that sells SPV (Special Purpose Vehicle) management software to venture managers, syndicate leads, and family offices. You'll spend your days building reports, cleaning CRM data, supporting sales and customer success with operational tasks, and helping leadership understand what's working (and what isn't) in the GTM motion.
Role Snapshot
| Aspect | Details |
|---|---|
| Role Type | RevOps Analyst (GTM operations support) |
| Sales Motion | Supporting both inbound and outbound motions |
| Deal Complexity | N/A (operations role) |
| Sales Cycle | N/A (operations role) |
| Deal Size | N/A (operations role) |
| Quota (est.) | N/A (measured on project delivery and data accuracy) |
Company Context
Stage: Series A
Size: 78 employees
Growth: Hiring their second RevOps person signals they're scaling GTM and need infrastructure
Market Position: Niche player in fintech infrastructure for private market deal execution - selling to a specific, technical buyer persona (venture managers who understand SPV mechanics)
GTM Reality
Pipeline Sources:
- Likely a mix of inbound (venture managers searching for SPV solutions) and outbound (targeting syndicate leads and emerging managers)
- Network effects matter - venture managers talk to each other, so referrals are probably significant
- Product is technical and compliance-heavy, so buyers are doing serious evaluation
Team Structure: Small GTM team at 78 people - you're supporting sales, CS, and leadership with one other RevOps person
What You'll Actually Do
Time Breakdown
Dashboards/Reports (35%) | Salesforce Admin (25%) | Ad-hoc Analysis (25%) | Meetings (15%)
Key Activities
- Salesforce hygiene: Cleaning up duplicate records, fixing stage assignments, making sure AEs are actually updating close dates. You'll spend hours in list views fixing data quality issues because garbage in = garbage out for all your reports.
- Pipeline reporting: Building (and rebuilding) pipeline dashboards for sales leadership. You'll get requests like "show me conversion rates by lead source" and realize the lead source field hasn't been consistently filled out for 6 months.
- GTM metric tracking: Pulling numbers for weekly/monthly business reviews - win rates, sales cycle length, average deal size, customer retention. You'll become the person who knows where every GTM metric lives and how it's calculated.
- Tool administration: Managing the tech stack (Salesforce, probably HubSpot or similar, BI tool like Looker or Tableau). You'll handle user access, build automations, troubleshoot integration issues when Salesforce and the billing system aren't syncing.
- Ad-hoc analysis: Sales VP wants to know why Q3 pipeline is down 20% - you'll dig into the data to figure out if it's fewer opps created, lower conversion rates, or deals slipping. CS lead needs to understand which customer segments have the highest NRR - you'll segment the data and build the analysis.
The Honest Reality
What's Hard
- Data quality is always a mess: Sales reps don't update Salesforce consistently. You'll spend significant time just getting clean data before you can do actual analysis. It's frustrating when your reports are wrong because an AE marked a deal "closed-won" that never actually signed.
- Everyone wants something yesterday: You'll get pinged constantly for "quick" reports that aren't actually quick. Prioritization is tough when the CEO, VP Sales, and Head of CS all think their request is urgent.
- You're building from scratch: Second hire means a lot of processes don't exist yet. You won't have documentation for how things work - you'll be creating it. That's ownership, but also means lots of trial and error.
- Being the data translator: You'll sit between technical data and non-technical stakeholders. Sales leaders want answers in plain English, but the data is messy and nuanced. Explaining why a simple question doesn't have a simple answer gets repetitive.
- Low visibility work: Much of what you do is infrastructure - when it works, nobody notices. When it breaks, everyone complains. You won't get credit for preventing problems, only for fixing them.
What Success Looks Like
- Leadership trusts your numbers and uses your dashboards to make decisions (not building their own Excel models)
- Sales and CS teams actually use the reports you build and ask for iterations/improvements
- You ship a major project (like territory planning model, or automated customer health scoring) that tangibly improves GTM efficiency
- Salesforce data quality improves measurably (fewer blank fields, more consistent stage progression)
- You become the go-to person for "how do we measure X?" questions
Who You're Supporting
Internal Stakeholders:
- Sales team: AEs and SDRs who need pipeline visibility, territory analysis, and deal tracking
- Customer Success: CS managers tracking retention, expansion, and customer health
- GTM Leadership: VP Sales, Head of CS, CRO who need strategic metrics for board reporting and planning
What They Care About:
- Accurate, timely data they can rely on for forecasting and planning
- Dashboards that answer their questions without needing to ping you every time
- Systems that don't break or require constant manual workarounds
- Analysis that helps them understand WHY metrics are moving, not just WHAT is happening
Requirements
- 1-3 years in a RevOps, sales ops, or analytics role (or strong internship experience in GTM operations)
- Comfortable with Salesforce (or similar CRM) - you should know how to build reports, create custom fields, understand object relationships
- SQL is helpful but not required - you'll likely need to pull data from databases at some point
- Excel/Sheets proficiency - pivot tables, vlookups, formulas should be second nature
- Experience with a BI tool (Looker, Tableau, Mode) is a plus
- You can communicate data insights to non-technical audiences without drowning them in jargon
- Based in NYC - this is an in-office role at a 78-person startup
- Early career but hungry to learn and comfortable with ambiguity (there's no playbook here)