Start a conversation
Insights

Written by the people who do the work

There is no content calendar here. These are working notes on problems we actually meet, published when we have something worth saying and something to lose by saying it badly.

Applied AI Architecture Operations
Discuss a topic Solution patterns
Everything published so far

8 pieces on engineering and applied AI.

Ordered as written. Each one is meant to survive you disagreeing with it.

AI & Automation

Building practical AI workflows

Most AI projects fail on intake and error handling, not on the model. A practical guide to choosing workflows, grounding output and shipping with confidence.
AI Strategy

When should businesses use AI agents?

Agents are the wrong default for most processes. Here is the decision test we use, the questions that disqualify a candidate, and where autonomy actually pays.
Legacy Modernization

Modernizing legacy applications

Rewrites inherit only the requirements somebody already understood. Modernisation works better as a sequence of small, reversible extractions around a facade.
SaaS Platforms

Designing SaaS for scale

Scaling the wrong axis is the expensive mistake. Tenancy model, tenant-scoped data access and entitlement design decide whether growth stays cheap or turns painful.
API Architecture

API-first architecture

An API is a contract with people you have not met. Designing it before the implementation changes what gets built and how safely it can change later.
Applied AI

Human-in-the-loop AI

The approval step is the easy part. The real design work is the review surface, the queue order, and turning corrections into evaluation data.
Cloud & DevOps

Cloud-native application architecture

Cloud-native means stateless where it pays, boundaries that own their data, and failure designed for. Moving a lift-and-shift application into Kubernetes achieves none of it.
Workflow Automation

Automating operational workflows

Most operational automation needs no model at all. Idempotency, explicit states, exception queues and scheduled reconciliation do the bulk of the work.
Recurring subjects

The questions underneath these articles.

Most pieces are a specific case of one of these larger arguments. Each links to the capability page where the work gets done.

01

Deciding where a model belongs

Plenty of operational decisions are deterministic. A rule that runs every time is cheaper, faster and easier to explain than an inference that occasionally disagrees with itself.

Applied AI and automation
02

Keeping autonomy inside a boundary

An agent with a defined scope, a stopping condition and a named accountable person is a feature. An agent with none of those is an incident waiting for a quiet week.

Human in the loop
03

Modernising without a maintenance window

The system that cannot be switched off is the one that constrains every plan. Sequencing matters more than the target architecture diagram.

Legacy modernisation
04

Boundaries between systems

Most integration pain comes from two systems each holding a different definition of the same entity. The API is the easy part of that conversation.

API and integration
Editorial position

We publish judgement, not announcements

Product updates, new roles and company news belong on our own channels. What belongs here is engineering judgement: how we would approach a problem, what we would avoid, and where we think the industry is going wrong. No vendor comparisons and no engagement bait. If a piece is worth your time it should still be worth it after you have disagreed with half of it.

Read the solution patterns How we work
Apply it

Turn a point of view into a scope.

The articles describe how we think. These pages describe what that looks like as an actual engagement.

Capabilities

Where the work happens

Each capability page covers fit, sequence and risks.

Sectors

The same argument, different constraints

Where compliance and access change the answer.

Company

Background

Who we are and what we build ourselves.

  • About LivingTech One standard across products and client work.
  • Folow Our platform, built to the same rules.
  • Careers How we hire when no role is listed.
  • Contact Bring a constraint, not a brief.

Reading is free. The conversation is more useful.

If one of these articles describes something you are dealing with, tell us the constraint. We will tell you what we would do about it.

Start a conversation Explore capabilities