That's not a technicality — it changes what you get. A web designer makes pages look right. An application developer builds the thing that actually runs your business inside those pages: the calculator your customers use before they book, the backend that lets you change your own rates without calling anyone, the system that does the work, not just displays it.

The core idea

Fifty years ago I started learning to program. What took longer — and matters more — was learning what to program. Any competent developer can write code. Understanding a business well enough to know what it actually needs is the harder, rarer skill, and it's the one that decides whether the result helps you or just looks fine.

So every project starts the same way: understanding your business before touching a keyboard. Not a template. Not a guess. An actual conversation about how you work, what's slow, what's breaking, what you wish worked differently — because software only helps if it fits how you actually run things.

Over the years I've built working application systems across a genuinely wide range of industries — not websites with a contact form bolted on, but real systems people use to run their businesses:

• Nutrient calculation systems (Kraft Canada, and another food-industry client)
• Food research systems for universities and nutritionists
• Travel agency systems, with a focus on group travel
• Bookkeeping, inventory, and warehouse management (Curwood Packaging)
• A real estate brokerage system (Silvaterra)
• A leasing system (3M Canada)
• A full club management system — ladders, tournaments, socials, AGMs — for a 400+ member pickleball club
• A booking platform with a live Rate Calculator, letting guests price their own stay before they ever contact anyone

That last two aren't hypothetical — they're live right now, built and hosted by me. If you want to see what "application integrated into a website" actually looks like rather than just hear about it, that's the proof.

This is what I mean by bringing application-development skill to web work: the difference between a site that just displays your business and one that actually runs part of it.

When there's nothing to go on

Sometimes there's no clean documentation, no source access, no one left who remembers how the old system actually worked. That's not a dead end — reconstructing a system from its behavior alone, without the original spec, is work I've been doing since long before it had a name. Decades ago that meant reverse-engineering an ingredient-calculation system built for programmable calculators. Today it means the same instinct applied to a Joomla site nobody's touched in years.

Redesign, not just port

When it's time to move an old site onto something better, I don't just carry the old structure over onto new infrastructure. If the business has changed — and it usually has — the site should change with it. That's also why I host what I build rather than handing it off: an upgraded system is worth maintaining, not abandoning the day it launches.

For most of my career, hiring came down to one question: does this person have a real feel for the business, or just technical skill? Technical skill is learnable. A feel for the business is rare. That same judgment is what I apply to AI today — it extends what one person can deliver, but the understanding of what your business actually needs still comes from sitting down and listening first. AI is leverage, not a replacement for that.

Godin London Incorporated is me — one developer, no account managers, no layers between you and the person actually building your system. I'm currently taking on just a few clients at a time, by design; that's what keeps the relationship close enough to actually work the way I've described above.

When I'm not building, I'm usually outside under dark skies — I'm a member of RASC Toronto Centre and the Everglades Astronomical Society, and I host the website for RASC London's astronomy community.

If this sounds like the kind of relationship you're looking for, the first conversation costs nothing — let's talk →