The Laboratory is where I explore how web development, search, AI, automation, and digital tools are changing the way businesses are built and run.
Some of this work becomes client-facing systems. Some becomes internal infrastructure. Some remains experimental until the timing is right.
This is where ideas are tested, methods are refined, and newer ways of building are explored before they become part of the core work.
The web is changing
Web development is no longer just about publishing pages.
For a long time, most business websites were little more than digital brochures. They looked the part, but they were often disconnected from the actual operation of the business. Enquiries came in by email. Follow-up was manual. Internal systems lived somewhere else. The website was the front door, but it was not connected to what happened behind it.
That model is getting weaker.
Modern businesses need digital infrastructure, not just web pages. A website now has to work as part of a wider system. It should connect with CRM tools, forms, lead routing, admin workflows, automation, service delivery, and operational processes. The front end of the business increasingly needs to work with the back end.
That shift matters.
A better website is no longer just a design upgrade. It can become a better enquiry system, a stronger lead-handling process, a clearer service platform, or a more useful business tool. In some cases, what used to be called “web design” is now much closer to CRM design, platform design, or operational interface design.
That is one of the main things I pay attention to here.
Search has evolved too
Search is no longer just about rankings.
SEO still matters. It still underpins how businesses are discovered online. But the wider visibility landscape has changed. Search now overlaps with local results, featured answers, AI summaries, recommendation engines, and generative tools that reshape how people find and interpret information.
That means visibility is broader than it used to be.
A business now needs more than a few keyword-stuffed pages and a homepage that vaguely says what it does. It needs service clarity, structured content, entity consistency, useful answers, strong page architecture, and better signals across the wider web. It needs to be found, understood, and chosen.
That is where my thinking has evolved too.
Traditional SEO remains part of the picture, but it now sits alongside newer layers of visibility. Those include answer-focused content structures, clearer information design, and ways of making businesses easier to interpret across both human and machine-driven discovery.
The names may evolve, but the commercial principle stays the same: if your business is difficult to understand, difficult to trust, or difficult to extract answers from, you lose visibility.
How I build now
The way digital systems are built has changed fast.
A few years ago, the standard path was slower, more fragmented, and often more expensive. Today, the process is much more fluid. It is now possible to move between strategy, content, prototyping, coding, design, automation, and testing far more quickly than before.
That does not remove the need for thinking. If anything, it makes good thinking more important.
Modern tools can accelerate the process, but they do not replace structure, judgment, or commercial clarity. They make it easier to build quickly. They do not make it easier to decide what is worth building.
My approach sits somewhere between traditional web development, business systems thinking, AI-assisted prototyping, and practical implementation. Some work still needs code. Some work needs better architecture. Some work needs cleaner workflow design. Some work needs faster research and iteration. Most useful projects involve a mix of these things rather than one discipline in isolation.
That is the point of the Laboratory.
It is where methods are tested, tools are compared, workflows are sharpened, and ideas are either developed, parked, or discarded based on usefulness rather than novelty.
Platforms and tools I use
I use a mix of platforms and tools depending on what the job requires. The goal is not to collect software for the sake of it. The goal is to build faster, think more clearly, test ideas efficiently, and create better systems.
Build and development
Lovable
Used for rapid interface building, prototyping, and turning structured product thinking into working application layers.
Replit
Useful for coding, testing, iteration, and building in a faster, more flexible development environment.
Firebase
Useful when speed, hosting, data structure, and lightweight app infrastructure matter.
GitHub
The backbone for version control, project structure, and keeping development work organised properly.
GitHub Copilot
Helpful for accelerating development, reducing repetitive code work, and supporting implementation.
WordPress
Still highly useful in the right context, especially for service business websites, SEO-driven sites, and projects where flexibility and practical content management matter.
AI thinking and prototyping
ChatGPT
Useful for ideation, planning, copy structure, system thinking, refining offers, and accelerating early-stage decision-making.
Claude
Particularly useful for deeper drafting, reasoning, long-form structure, and more reflective problem solving.
Google AI Studio
Helpful for experimentation, prototyping workflows, and testing ideas in a more technical or model-adjacent environment.
Perplexity
Useful for faster research, synthesis, and checking information across multiple sources during exploration or validation.
Creative and media tools
Runway
Used when creative experimentation, video generation, or media-supported concept development is useful.
Nano Banana
Part of the wider experimental toolset for creative and visual exploration.
Wider stack thinking
Alongside those named platforms, I also work across the practical layers that make digital systems function properly: CMS platforms, automation tools, APIs, databases, structured content, workflow logic, research systems, and connected business infrastructure.
The exact stack matters less than the outcome.
The important thing is choosing the right level of complexity for the business, then building something that is actually usable.
StartupCoLab
StartupCoLab sits inside the Laboratory as a venture archive and control layer.
It is not an active startup in the usual sense. It is a structured place for ideas, experiments, paused projects, sellable concepts, collaborative opportunities, and archived ventures. Some are active. Some support core businesses. Some are parked. Some may eventually be sold or revived. Some are documented and left behind.
The point is not to keep everything alive forever.
The point is to preserve useful thinking without letting side projects fragment focus.
That distinction matters.
Good ideas do not always need immediate execution to remain valuable. Some are more useful as frameworks, reference points, future options, or structured records of work already done. StartupCoLab exists to hold those ideas properly, classify them honestly, and make it easier to decide what deserves action and what does not.
In that sense, it is less of a startup platform and more of an archive, a filtering system, and a controlled revival board.
Why this matters
Research and development only matters if it leads somewhere useful.
For me, that usually means one of three things:
- better digital infrastructure
- better visibility
- better operations
The Laboratory supports all three.
It helps me track how the web is changing, how search is evolving, how modern tools can speed up implementation, and how ideas can be tested without turning every idea into a distraction.
Some experiments become services.
Some become systems.
Some become tools.
Some remain in the archive until the timing makes sense.
That is the role of this page.
Not hype. Not trend-chasing. Just an honest look at the thinking, tools, and experiments behind the work.
Selected areas of focus
- Web development as connected business infrastructure
- Search visibility beyond traditional SEO
- AI-assisted workflows and prototyping
- Automation and operational systems
- Business tools, frameworks, and internal experiments
- Venture archiving and structured idea management
Closing line / CTA
If you are interested in how modern systems, search, and operational thinking can improve the way your business runs, that is exactly the kind of work MrKeating is built around.
Optional shorter version of the CTA block
Interested in the practical side of this?
Explore the core service areas behind the work:
- Digital Infrastructure
- Visibility & Growth
- Operations & Automation