Skip to content
RYAN BRENTS / SERVICES / INTEGRATIONS
LIVE · ATL

Integrations

Your systems don't have to hate each other. APIs, EDI, ERP-to-everything — designed from the workflow, not the schema.

THE WORK — /INTEGRATIONS
01API integrationREST, SOAP, GraphQL, webhooks. Design, build, and operate the layer between your systems.
02EDI850s, 855s, 856s, 810s. Unfashionable, unavoidable, and something I've done many times.
03ERP ↔ everythingWMS, TMS, e-commerce, labs, CRMs, and document stores. Bidirectional sync, reconciliation, and the edge cases that break everyone else's build.
04Event-driven architectureQueues, streams, websockets — for when request-response stops scaling.
THE PROOF — CASE 001

The cheese factory WMS ↔ Ross integration.

Two systems that refused to talk, on a live plant floor where downtime costs real money by the hour.

SEE THE WORK →
Integrations — signal-routing art
THE WRITING — RELATED
2026-07The integration archetypes nobody names2026-08Your retailer mandated EDI. That's not the same as EDI working.
SEE ALSO

tell me what's not talking to what — one email starts it

NO CALENDAR LINKS · NO FUNNEL · JUST MAIL