DataDrone builds 0-1 SaaS products and the team that ships them. No bosses, no managers — the playbook manages, the copilot tracks. Every role owns a small, defined space with extreme accountability. Our B2B outreach engine runs daily — sourcing leads, sending personalized outreach, routing responses, booking meetings, closing deals. Behind all of it: a CRM that tracks every lead, every touch, every deal, every status. We need someone who makes the CRM a tool the revenue team trusts.
What You'll Do
You'll own the operational configuration of the CRM. Pipeline stages that match the sales process. Views that show each operator exactly what they need. Reports that tell the truth about pipeline health. Data hygiene that keeps the database clean. Schema enforcement that ensures every record has the data it needs. You're not a CRM admin who maintains the system — you're the CRM operator who makes it work for the people who use it daily.
Daily Rhythm (How You Operate)
- Daily: respond to operator requests fast — a CRM frustration that lasts a week is a CRM that stops being used.
- Per request: build or fix operator-specific views and filters within 4 hours.
- Per change: document every configuration change as you make it.
- Always: enforce the lead schema through configuration — required fields, valid values, status transitions — not by asking nicely.
Key Responsibilities
- Configure and maintain CRM pipeline stages matching the sales process
- Build and optimize operator-specific views and filters
- Create and maintain reporting dashboards — pipeline value, velocity, forecast
- Run weekly data hygiene — duplicates, orphans, stale records, schema compliance
- Enforce the lead schema — required fields, valid values, status transitions
- Document every configuration change
- Maintain CRM configuration documentation and lead schema docs
What We're Looking For
- You've configured a CRM for a B2B sales team. Not just used it — configured: fields, views, reports, automation rules, pipeline stages.
- You understand data hygiene: deduplication, orphan management, stale record cleanup. You do it regularly, not reactively.
- You can build views and reports that operators actually use. Not 20-column views nobody reads — focused views that answer one question.
- You can enforce data quality through configuration: required fields, validation rules, status transitions. Not through asking people nicely.
- You maintain documentation. Every configuration, every automation rule, every field purpose — documented.
- You respond to operator requests fast. A CRM frustration that lasts a week is a CRM that stops being used.
Bonus Points For
- CRM admin experience (modules, workflows, blueprints, custom functions)
- Experience with lead scoring integration between marketing automation and CRM
- Experience with pipeline reporting and sales forecasting
- Experience managing CRM data quality at scale (1,000+ records)
- Experience migrating or cleaning up legacy CRM configurations
The Mindset We Hire For
- The CRM is a tool, not a database. If operators work around it, the CRM failed — not the operators. Your job is to make the CRM the easiest way to do the work.
- Clean data is non-negotiable. Duplicate records cause double-outreach. Stale records inflate pipeline reports. Blank fields break automation. Hygiene is weekly, not quarterly.
- Reports must tell the truth. A pipeline report that includes stale deals is a lie. The Growth Lead makes decisions from these numbers. Accuracy is your responsibility.
- Schema enforcement over training. Don't rely on "please fill in all fields." Enforce it: required fields, validation rules, transition logic. The system prevents bad data, not the human's willingness to comply.
- Every field earns its place. A field nobody uses is a field that slows down every operator who scrolls past it. Audit ruthlessly. Deprecate without sentiment.
- Document as you configure. A CRM configuration in your head is a single point of failure. Docs are the deliverable.
Success in This Role
- 30 Days — CRM mapped. Hygiene run. Operator friction identified. Lead schema compared to spec.
- 90 Days — Data quality consistently high. Operators trust the CRM. Reports trusted for forecasting. Configuration handoff-ready.
Tools You'll Use
CRM (admin), analytics, Slack, Google Drive, AI copilot.
Why Join Us
You won't inherit a CRM that nobody uses and nobody maintains. You'll own the operational layer of a CRM that powers a daily outreach engine, a multi-stage sales process, and a pipeline the leadership team makes decisions from. Your configuration determines whether the revenue team trusts the data — or works around it.
5 hours of focused CRM work per day. Precision over volume.
Self-Check Before You Apply
- Can you map a CRM's full configuration — every module, field, view, report, and automation rule — in under a day?
- When was the last time you ran a deduplication scan? (If it was more than 2 weeks ago, your hygiene cadence is too slow.)
- Do operators on your current CRM use shadow spreadsheets? (If yes, the CRM is failing them.)
- Can you build a pipeline report that a sales leader trusts without manually cross-checking?
- When an operator says "I can't find my leads," how fast do you fix their view? (4 hours or less is the standard.)
- Is every field in your current CRM documented with its purpose — or are some "from something we tried a while ago"?