Blog
Notes from our client work: cleaning up hacked WordPress sites, speeding up slow WooCommerce stores, and deciding when a custom application should replace the spreadsheet. Written for business owners who run a website without a developer on staff.
Wholesale ordering at most brands runs on email, phone calls, and a PDF order form that a rep re-types into the system. It works, in the sense that orders arrive. It also means data entry errors, no visibility into stock, pricing mistakes when the spreadsheet is stale, and reps spending selling hours on clerical work. A wholesale portal replaces that
Most businesses stay with a web developer about two years past the point it stopped working. The relationship usually started well, the developer knows the site’s history, and switching feels risky, so the frustration gets absorbed as normal. Sometimes it is fixable with one direct conversation. Sometimes the business has grown past what the arrangement can deliver. This article covers
At some point a growing business has more technical work than favors and freelancers can absorb: the website, the store, the integrations between systems, the reports someone keeps building by hand. The reflex is to post a developer job. Sometimes that is right. Often the math says something different, because one hire buys one skill set for a full-time price,
Website maintenance is easy to skip because nothing visible happens when it is done well. The site looks the same on Tuesday as it did on Monday. What changed is underneath: software patched before an exploit circulated, a backup verified before it was needed, a failing form caught before a month of leads vanished. This article covers what a real
You run ads, you check GA4, and the purchases are not there, or a third of them are missing, and every channel suddenly looks unprofitable. We have fixed this for stores where the ad budget was being steered by numbers that were wrong. Shopify purchase tracking breaks in a small number of predictable places, and the fix depends on which
“The site feels slow” is where most performance projects start, and it is not enough to act on. Slow at what? For whom? A homepage that renders in six seconds and a checkout that hangs are different problems with different fixes. Hosts are happy to sell a bigger plan either way, and half the time the bigger plan changes nothing
A broken checkout is the most expensive bug a store can have, because it fails quietly. The site looks fine, products load, and revenue is zero. Most owners find out from a customer email or from noticing the order list went silent. We debug these for stores regularly, and the causes cluster into a short list. This checklist works through
Ask five providers what a custom web application costs and you will get five numbers that differ by a factor of ten. None of them are lying. They are answering different questions, because “web application” covers everything from a one-screen internal tool to a platform your customers log into every day. This article gives you the ranges, what moves a
Every business runs on a few load-bearing spreadsheets. An order tracker, a production schedule, a pricing sheet that only one person understands. They start as the fastest way to solve a problem, and for a while they are. Then the team grows, the file gets shared, and the workflow that lives inside it starts costing money in ways nobody tracks.
In March 2026 we cleaned up a backdoor campaign that hit several WordPress sites in the same week. Each one showed the same pattern: visitors were being sent to fake browser update pages, the Plugins screen looked normal, and the malicious code sat in a folder most site owners have never opened. That folder is wp-content/mu-plugins, and security researchers have