Notes from building and running integrations.
Practical writing on inventory, automation, reconciliation, and keeping the connections between your systems honest.
Useful rather than promotional.
Notes on connecting business systems to each other: what tends to go wrong, how to tell which option actually suits you, and the unglamorous parts that decide whether an integration still works in six months.
Written from the work rather than from product documentation. If a question here is one you are living with, we are happy to talk it through.
Latest posts.
How to stop two sales channels overselling the same inventory
Overselling happens when two channels can both sell the last unit. A practical look at why it occurs, the four design decisions that prevent it, and what to fix first.
Read itWhen does Make.com stop being cheaper than self-hosted n8n?
Hosted automation is priced per operation; self-hosted is priced per server. A plain look at where the crossover sits, and the costs on both sides that are easy to leave out.
Read itPer-agent help desk pricing: when it stops making sense
Per-seat help desk licensing scales with your team, not with your value from it. How to tell whether you have outgrown it, and what an honest comparison with self-hosting looks like.
Read itWhy your marketplace payouts never match your sales report
Marketplace statements rarely map one-to-one onto bookings. The structural reasons why, and how to build a reconciliation that surfaces the gaps instead of absorbing them.
Read itWhy an accounting integration must be safe to run twice
Retries are normal in any integration. In accounting they can create duplicate invoices and books that no longer reconcile. What idempotency means in practice, and how to design for it.
Read itMonitor the integration, not just the server
Uptime monitoring tells you the server is running. It does not tell you the sync stopped, the credential expired, or the messages stopped sending. What to watch instead.
Read it