Integration, automation, and data-pipeline work — available as subcontract capacity

I'm Dave Swanson, an independent developer in Illinois. I build back-office integrations, internal automation, and agent tooling, mostly for small organizations. I take subcontract work under another firm's delivery lead, and I trade referrals with other independents.

  • Available now
  • 10–20 hours a week
  • $100–$140/hr, subcontract rate

What I build

System-to-system integration

Webhook services and API integrations between business systems that were never meant to talk to each other. Writes are idempotent and keyed to source IDs, so a replayed event updates the existing record instead of creating a second one.

Data migration and reconciliation

Scripted, re-runnable pipelines that move history between systems and prove the totals match. Every line keeps its original document number and source, so anything can still be traced back after the old system is switched off.

Internal automation and support tooling

Ticket routing, approval workflows, and document filing across Microsoft 365, Zendesk, and SharePoint. Usually the point is removing a manual lookup that one person has become the bottleneck for.

Agent tooling and LLM workflows

Drafting and lookup assistants with a human approval step, scored by an evaluation harness against what a person actually sent. Each runs on its own credential, scoped to a single mailbox or site.

Stack

Languages
  • Python
  • PowerShell
  • JavaScript
  • SQL
Cloud
  • Azure Functions
  • App Service
  • WebJobs
  • Storage
  • Key Vault
  • RBAC
  • Container Registry
  • Docker
Data
  • PostgreSQL
  • SQL Server
  • pandas
Frameworks
  • Django
  • Flask
  • Next.js
Automation & testing
  • Playwright
  • Evaluation harnesses
Business systems
  • NetSuite (SuiteScript, SuiteQL, REST)
  • Microsoft Graph
  • Entra ID
  • SharePoint
  • Zendesk
  • DocuSign
  • Dynamics GP
AI
  • Anthropic API
  • Model Context Protocol
  • Azure OpenAI

Azure rather than AWS, and back-end rather than front-end. I'd rather say so here than have you find out in week two.

Selected work

Three projects from the last three years, built for a Chicago workforce-development nonprofit of about 70 staff. The client isn't named and the figures are system-level, but the engineering is described as built.

Contracts & Finance Systems

Connecting contract management to accounting

Flask webhook service on Azure App Service · idempotent upserts via custom NetSuite RESTlets · OAuth 1.0a signing implemented by hand

Grants, budgets, and vendor bills flow from the contract-management system into NetSuite, each keyed to its source ID so a repeated event updates the existing record instead of creating a second one. Payments write back the other way, so the two systems agree without anyone re-entering a number.

Read the case study

Contracts & Finance Systems

Migrating seven years of accounting history

Re-runnable migration pipeline · 239,086 lines loaded once · reloads replace rather than append

Trial-balance history migrated from Microsoft Dynamics GP into NetSuite through a scripted, re-runnable pipeline. Every line carries its original document number, source, and date, so staff can trace any entry back to the retired system.

Read the case study

Payment Integrity & Records

A training-voucher system built as a contingency

Django 5.2 on PostgreSQL 16 · business rules as database constraints · append-only funding ledger, balances computed not stored

A voucher system where the business rules live in the database: overlapping vouchers are refused outright, separation of duties is a constraint rather than a policy, and funding is an append-only ledger whose balances are computed, never stored.

Read the case study
View all work

How I work with a delivery lead

If you’re the delivery lead and I’m touching your client’s production systems, here’s what you’re getting.

  • Dry-run first, pilot one record, then run the rest. Every bulk write is previewed, tested on a single record, and checked before the full run.

  • Verify after writing. I re-read the live system rather than trusting a success message. A fair number of the fixes in the projects above came from tools that reported success and had written nothing.

  • One credential per automation, scoped to the single mailbox, site, or resource it needs — and tested both ways, so it works where it should and is refused everywhere else.

  • No real personal data in code. Fixtures and tests use synthetic data; participant records stay out of repositories.

  • Handoff documentation in plain language. On the case-management migration, a colleague took over the entire workstream from those docs, including approval of every production write.

Get in touch

Available now, 10–20 hours a week, starting immediately. I'm open to subcontract work under your delivery lead and to trading referrals with other independents — I'm not looking to be prime on your client work.

$100–$140 an hour, subcontract rate. That reflects the US market. If you’re engaging from outside it, email me and we’ll talk.

Email me · dave@cut-once.dev