Case studies
Failures that do not take the site down and do not write errors to the logs — they just quietly cost money. Every case comes with the numbers and a way to check the same thing in your own setup.
Business automation usually starts from the wrong end: a company commissions a good-looking dashboard while the money keeps leaking out of how enquiries are handled. Here is the test for choosing the first process, and the three that turn out to be worth it almost every time.
Read the case →Analytics was installed, the code was in place, no errors in the console. And not one visit in the statistics. The cause was a single line that made the browser replace the counter function with a script tag.
Read the case →Every evening the owner received a summary of how the sales team had performed. The summary lied: a third of the conversations were missing from it, and one segment was inflated threefold. The cause was a single line of code.
Read the case →The catalogue in the accounting system and the catalogue on the website drifted apart quietly: no errors in the logs, no complaints from customers. Here is why incremental sync physically cannot see some changes, and how to find this in your own shop.
Read the case →