MARK PHILIPPE M.

Systems Architect | Integrations That Still Work in Year Six

Most of what I build runs unattended, against other people's APIs, in businesses where a failure costs money the same day. Getting something working the first time and keeping it working for years are different problems. The second one is where I spend my time. The record is the clearest thing I can point to: - Nearly seven years and five contracts on one client's SMS sales pipeline. The first job was a troubleshooting ticket. - 1,247+ paid hours across six years for a distributor with no technical staff of its own. - Eleven contracts in three and a half years for a city government, each one opened after the last had proved out. - Six years keeping a single stock pool in sync across a storefront and several marketplaces, so it never oversells. None of those started as a big project. Each began with something broken or something small, and the client came back. What clients hire me for: - Integrations that have to survive real volume: rate limits, retries, webhook timeouts, duplicate writes, reconciliation that has to balance. - Shopify and e-commerce: checkout, payments, fulfilment, and stock synced across several channels at once. - Operations that have outgrown spreadsheets, usually on Airtable, Xero, Unleashed or n8n. - Diagnosing an integration nobody at the business can explain any more. - Twilio voice and SMS: call routing, IVRs, number pools, deliverability, and logging both back into a CRM. If you built it yourself and it broke: A lot of my work starts here now. Someone has built most of a system with AI tools, it works on their machine or with ten records, and then it meets an API rate limit, a five-second webhook ceiling, two processes racing to write the same record, or a month end that will not reconcile. I am happy to pick that up, and I will tell you what is actually wrong before I quote anything. How I work: - I ask about the business problem before the stack. - I design for the failure rather than the happy path: validation, retries, audit trails, exception handling. - A person stays in the loop wherever a mistake would cost money or trust. AI drafts, someone approves. - I hand over documentation your team can actually use. Stack: PHP, Laravel, WordPress, Shopify, Node.js, Python, FastAPI, n8n, Make, Zapier, Airtable, Xero, Unleashed, Twilio, Stripe, PayPal, AWS, Google Cloud Functions, Claude, OpenAI. If you already know the fix and just need it built, I can do that. If you are not sure what the fix is yet, that is usually where I am worth the most.