A working record of revenue systems architecture — mapping how businesses actually operate, modeling the systems behind them, and rebuilding the infrastructure that turns fragmented tools into coherent, maintainable systems.
A partner told a South America travel company its leads were going missing daily. Reconciling every enquiry across form, partner sheet and CRM showed their own team had been hand-keying most of what the old integration dropped, and caught a live bug in the new engine.
A gate in a newly live n8n lead router would have held back any enquiry with a blank last name. The fix shipped the same morning, through a local simulator, n8n’s own parser, a mutation check, a diff against the live copy and a smoke test that reached no partner.
A South America travel company sends Google Ads enquiries to one partner and everything else by destination. How the n8n router detects a paid click, routes phone calls on CallTrackingMetrics tags, stamps which system wrote each row, and why live chat still can’t be attributed.
Delivering leads from an n8n routing engine into a partner’s Salesforce org: client_credentials on My Domain, a dependent picklist decoded from validFor, picklists that accept anything, and test records that can never be deleted.
The day an n8n lead router went live, Salesforce answered its token request with “scope parameter not supported” and every write failed, while every test stayed green. The cause, why no offline test could see it, how the fix was proven with a write that reached nothing but Salesforce, and why I called off the replay.
A South America travel company’s lead routing had grown into 51 active Pabbly Connect workflows that no longer matched the rule they were meant to follow. It now runs as one tested rule in n8n, proven in shadow on real leads, with every lead logged.
A desktop mega menu stopped opening, and clearing the cache fixed it for about half a day at a time. The cause wasn’t the plugin — it was a nonce baked into cached HTML, and WordPress core rejecting any REST request that carries a stale one.
A travel client’s site had lab TTFB under 100 ms and field TTFB near two seconds. The cache was cold for 72% of top pages after every purge, mobile worse than desktop. A throttled curl warmer fixed it, and then its own report fooled me for weeks.
Eight undocumented behaviours in Shepherd Veterinary Software’s Open API, found while building a two-way sync for a veterinary practice client — including a full-replace update endpoint that silently deletes any collection you leave out of the body. All verified against the live production API, including writes.
How I wired named authors and reviewers into 744 WordPress pages as one schema.org @id entity graph in Rank Math and JetEngine, and the two Rank Math behaviours that only surfaced by watching live markup disappear.
278 pages of travel guidance had quietly gone stale — some of it stating the opposite of current law. Here is how 102 of them were researched, corrected and deployed in days rather than weeks, and the four things that went wrong along the way.
A private lender’s Salesforce org had overlapping Workflow Rules, Process Builder, and record-triggered Flows around loan operations. I stabilized the high-risk paths by mapping control fields, verifying migration parity, reducing unnecessary saves, and testing the behavior that actually reaches users.