Where ideas are tested.
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.
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.
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.
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.
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.
Traditional SEO remains part of the picture, but it now sits alongside newer layers of visibility — 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.
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, judgement, 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. Most useful projects involve a mix of these things rather than one discipline in isolation.
The Laboratory 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.
The goal is not to collect software for the sake of it. The goal is to build faster, think more clearly, and create better systems.
Build and development
-
Lovable
Rapid interface building, prototyping, and turning structured product thinking into working application layers.
-
Replit
Coding, testing, iteration, and building in a faster, more flexible development environment.
-
Firebase
Speed, hosting, data structure, and lightweight app infrastructure when those matter.
-
GitHub
Version control, project structure, and keeping development work organised properly.
-
GitHub Copilot
Accelerating development, reducing repetitive code work, and supporting implementation.
-
WordPress
Service business websites, SEO-driven sites, and projects where flexibility and content management matter.
AI thinking and prototyping
-
ChatGPT
Ideation, planning, copy structure, system thinking, refining offers, accelerating early-stage decisions.
-
Claude
Deeper drafting, reasoning, long-form structure, and more reflective problem solving.
-
Google AI Studio
Experimentation, prototyping workflows, and testing ideas in a more technical, model-adjacent environment.
-
Perplexity
Faster research, synthesis, and checking information across multiple sources.
Creative and media
-
Runway
Creative experimentation, video generation, and media-supported concept development.
-
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 — choosing the right level of complexity for the business, then building something that is actually usable.
A venture archive and control layer.
StartupCoLab is the Laboratory. The name carries two meanings: Startup Company Laboratory — a place to test, build, and refine ventures — and Startup Collaboration — a space for shared thinking, partnerships, and joint experiments. 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. 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.
In that sense, it is less of a startup platform and more of an archive, a filtering system, and a controlled revival board.
Research and development only matters if it leads somewhere useful. For me, that usually means one of three things.
-
01
Infrastructure
Better digital systems that connect the front and back of the business.
-
02
Visibility
Stronger discovery across search, answers, and AI-driven results.
-
03
Operations
Cleaner workflows, better lead handling, and simpler day-to-day systems.
Some experiments become services.
Some become systems.
Some become tools.
Some remain in the archive until the timing makes sense.
Not hype. Not trend-chasing. Just an honest look at the thinking, tools, and experiments behind the work.
- 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
