Blog

While setting up a new app, the AI quietly tucked a full database connection string into the app's config. It was a real security flaw, and the only reason it got caught is that I know where to look. Vibe coders, this one is for you.

We shipped big new features to our golf app, then remembered the people who never update. Here is the update nudge we built, why we control it from the server, and the awkward things the AI would not raise on its own.

Connecting AI to our real database, not a description of it, turned client data onboarding from a scheduled developer job into a conversation. Here is what it got brilliantly right, and the two times it confidently nearly sent us down the wrong path.

Rebuilding the premium experience on two sports apps taught me a paywall is not a feature list. Here is what actually moved conversion, and where the AI led me astray.

Letting an AI assistant send emails sounds like a quiet win until it quietly sends one to the wrong person. Here is the shared cache problem, the recipient problem, and the guardrails that actually fixed it.

I wanted a simple weekly check of newsletter signups. The AI proposed a public API endpoint that would serve every subscriber's email address to the internet. Here is why that was the wrong answer, what the right one was, and why it matters that the AI never flagged the risk.

Ranking in your town is a different game to ranking nationally. It runs on your Google Business Profile, your reviews, and pages that prove you serve a place. Here is the local SEO playbook we use for trade and service businesses.

I asked Claude to predict where my three apps would be in 12 months. The first answer was a linear extrapolation that under-predicted by a factor of three. Here is what changed when I pushed back, and what I would tell anyone using AI for the same job.

For months I resubmitted the sitemap and requested indexing every day, and Google still wouldn't index most of our pages. So I stopped guessing and used Claude to look at the actual data. The answer wasn't what I expected, and neither was where the AI got it wrong.

Most trade websites are digital business cards. The ones that win jobs do four things differently: clear pricing, an obvious quote path, real proof, and a page that loads before the customer loses patience. Here is what we have learned building them.

We added an AI scorecard scanner to Golf Handicapp and watched it become one of the main reasons people choose the app. Here is what small businesses can learn from it about adding AI to a product.

Most indie apps leave the App Store and Google Play fields on default. Here is what is worth your time, what is not, and the tools we use to get screenshots looking sharp in an afternoon.

Good onboarding does more than walk users through setup. It builds investment, creates habits, and naturally leads people toward premium features without a hard sell.

Search is changing. AI assistants are answering questions that used to send people to your website. Here is how we structure every site we build so that AI models can find, read, and recommend your business.

The honest answer is: it depends. Build costs can range from £1,000 to £50,000+ depending on what you need. Here's how to get a realistic figure without wasting anyone's time.

Slow websites lose customers and drop in search rankings. Here is what Core Web Vitals are, why Google cares about them, and how to make sure your site is up to speed.

You do not need a fully finished product to get started. An MVP lets you test your idea, learn what works, and grow from there, without spending a fortune upfront.

Content management systems like Contentful are powerful tools, but if no one on your team is using yours, you could be paying for something you do not need. Here is how to decide what is right for your business.

Why a website alone is no longer enough, and how keeping your digital presence active can help you win more customers and grow your business.