Systems Builder

DataDrone Inc.; Cheyenne, Northern (WY, KY); Hybrid; USD 95,000 - 135,000; Full time

Job summary

DataDrone Inc. builds 0-1 SaaS products and the team that ships them. You’ll own every operational system powering business operations—from CRM and CDP instrumentation to automation workflows and the outreach engine’s architecture. You build it, you document it, you maintain it.

When systems run reliably, the sales team sells, the outreach team reaches, and the success team retains—because your infrastructure carries them. 5 hours of focused systems work per day is baked in.

Qualifications

• CRM beyond basic setup with custom modules and workflows.
• Experience building production automation workflows.
• Ability to troubleshoot system integrations and data sync.
• Documented runbooks delivered with each build.
• Strong data integrity practices.

Responsibilities

• Build and maintain CRM configuration (modules, fields, workflows, blueprints, integrations).
• Instrument and maintain CDP event tracking, signal logic, and journey configurations.
• Build and maintain automation workflows (lead enrichment, message generation, response routing).
• Build and maintain messaging automation (delivery, sequence execution).
• Build and maintain the outreach system’s architecture.
• Monitor integration health across all systems — alert on failure within 5 minutes.
• Document every system with runbooks — the documentation IS the deliverable.
• Maintain CRM, CDP, and messaging-journey playbooks.

Skills

CRM configuration

Automation workflows

System integrations

Documentation

Runbooks

Monitoring & alerting

REST APIs

Tools

n8n

Zapier

Make

REST APIs

Job description

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. Behind the product, a stack of operational systems keeps the engine running: CRM, CDP, automation, integrations, and the outreach machine.

What You'll Do

You’ll own every operational system that powers the business operations. CRM, CDP instrumentation, automation workflows, messaging automation, and the outreach engine’s architecture. You build it, you document it, you maintain it. When systems run reliably, the sales team sells, the outreach team reaches, and the success team retains — because your infrastructure carries them.

Daily Rhythm (How You Operate)

• Daily: monitor integration health across all systems — alert on failure within 5 minutes.
• Per build: test in staging before production — CRM, automation, and integration changes alike.
• Weekly: keep CRM schema and data clean — no orphaned fields, duplicates, or unused workflows.
• Per system: ship the runbook alongside the build — the documentation IS the deliverable.
• Always: build for the operators who use it daily, not for yourself.

Key Responsibilities

• Build and maintain CRM configuration (modules, fields, workflows, blueprints, integrations)
• Instrument and maintain CDP event tracking, signal logic, and journey configurations
• Build and maintain automation workflows (lead enrichment, message generation, response routing)
• Build and maintain messaging automation (delivery, sequence execution)
• Build and maintain the outreach system’s architecture
• Monitor integration health across all systems — alert on failure within 5 minutes
• Document every system with runbooks — the documentation IS the deliverable
• Maintain CRM, CDP, and messaging-journey playbooks

What We're Looking For

• You’ve configured a CRM beyond basic setup — custom modules, workflows, automation rules, scripting.
• You’ve built automation workflows (n8n, Zapier, Make, or equivalent) that run in production daily.
• You can troubleshoot integrations between systems — API failures, webhook mismatches, data sync issues.
• You document what you build. Not after. During. The runbook is part of the deliverable.
• You understand data integrity — deduplication, validation, error handling. Not just "it works" but "it works correctly every time."
• You can work with non-technical operators. You build systems they use daily. If they can’t use it without your help, the system or the documentation failed.

Bonus Points For

• Deep CRM configuration experience (scripting, blueprints, custom functions)
• Self-hosted automation experience (complex multi-step workflows)
• CDP experience (event instrumentation, behavioral signals, journey orchestration)
• Experience with multi-channel outreach architectures (autonomous + partner-driven)

The Mindset We Hire For

• If only you can fix it, you failed. Every system you build must be operable and troubleshootable by someone else using your documentation.
• Silent failures are unacceptable. If something breaks and nobody knows for 3 hours, the monitoring failed. Monitoring is not optional — it's part of the system.
• Clean schema, clean data. Orphaned fields, duplicate records, and unused workflows are technical debt. You keep the systems clean.
• Error handling is not an afterthought. The happy path is the easy part. What happens when the API times out, the webhook is malformed, the field is null? That's where your engineering shows.
• Build for operators, not for yourself. You're not the daily user. The operators are. Build systems they understand, with interfaces they can navigate, and documentation they can follow.
• Test before production. Always. CRM changes, automation changes, integration changes — tested first.

Success in This Role

• 30 Days — Every system mapped. Health checks run. Documentation gaps identified. Operator relationships established.
• 60 Days — Documentation gaps closed. Reliability risks addressed. CRM clean. Operators independent.
• 90 Days — Zero silent failures. All playbooks current. Systems handoff-ready. Operators trust the infrastructure.

Tools You'll Use

CRM (admin + scripting), analytics, self-hosted automation, messaging platform, cloud infrastructure, version control, Slack, Google Drive, AI copilot.

Why Join Us

You won't maintain someone else's spaghetti integrations. You'll build operational infrastructure from the ground up — or rebuild what exists to a standard where it's documented, monitored, and operable by the team, not just by you.

The systems you build power the entire revenue engine. When outreach runs daily, it's your automation. When CRM tracks every deal, it's your configuration. When CDP fires churn interventions, it's your instrumentation. You're the infrastructure the business runs on.

5 hours of focused systems work per day. No firefighting culture — because your monitoring catches issues before they're fires.

Self-Check Before You Apply

• Can you draw the architecture of the last CRM you configured — every module, every workflow, every integration?
• When was the last time an automation you built failed silently for more than 1 hour? (If recently, that’s a monitoring gap.)
• Is every system you’ve built documented well enough that someone else can maintain it?
• When you build an automation, does your first version include error handling — or do you add it "later"?
• Can you explain your CRM schema to a non-technical operator and have them understand why each field exists?
• When an integration breaks, do you fix it AND add a health check — or just fix it?

If three or more are yes, that’s you — apply.