Speak to our team+44 20 3769 7682+1 325 244 5212
Insights

Thinking that ships.

Our unfiltered take on AI, engineering, design, and how modern teams build products that last. Articles, playbooks, reports, and interviews from the team that writes the code.

Topic
Format
51 posts
ArticleIndustry Playbooks

AI maintenance triage and Awaab's Law: what to automate first

AI maintenance triage for property managers: what Awaab's Law Phase 2 changes on 30 November 2026, what to automate first, and what to keep with a person.

Read more
ArticleAI & Agents

Why every workflow is about to have a reasoning layer

Rule engines got us far. But the next generation of enterprise workflows won't follow if-else trees — they'll reason through ambiguity.

Read more
PlaybookEngineering

From monolith to microservices without the rewrite

The big rewrite never works. We've decomposed 4 monoliths incrementally — without a single day of downtime.

Read more
ReportStrategy

The AI-native enterprise: what it actually looks like in 2026

AI-native isn't a chatbot on the homepage. It's AI in the decision loop — procurement, hiring, pricing, ops. Here's what that looks like.

Read more
PlaybookAI & Agents

Multi-model routing in production: 7 models, one orchestrator

Not every prompt needs GPT-4. We route across 7 models based on complexity, cost, and latency — here's the architecture.

Read more
PlaybookDesign Systems

Building a design system that engineers actually use

A design system that lives in Figma but not in the repo is a PDF with extra steps. Here's how we bridge the gap.

Read more
ArticleEngineering

The strangler fig pattern: modernizing legacy systems incrementally

The strangler fig grows around its host. Your new system should too. Here's the pattern that lets you replace legacy one route at a time.

Read more
ArticleAI & Agents

The semantic layer pattern: why your AI can't understand your data

Your AI can read your database. It just can't understand it. The semantic layer is the missing translation between schema and meaning.

Read more
ArticleStrategy

Build vs. buy vs. partner: the decision framework for AI products

If it's core, build it. If it's commodity, buy it. If it's complex and non-core, partner. But most teams get the classification wrong.

Read more
ArticleEngineering

Event-driven architecture: when to use it and when it will ruin you

Event-driven is elegant on the whiteboard and brutal in production debugging. Here's when it's worth the trade-off.

Read more
ArticleDesign Systems

Token-driven design: from Figma variables to CSS custom properties

Design tokens aren't just colour swatches. They're the API contract between design and engineering. Here's how we implement them.

Read more
ArticleAI & Agents

Prompt engineering is dead. Prompt architecture is what ships.

Single-shot prompt crafting doesn't scale. Production AI needs prompt architecture — versioned, tested, and composable.

Read more
ArticleStrategy

Why your digital transformation failed (and what to do about it)

It wasn't the technology. It was scope creep, committee governance, and measuring activity instead of outcomes.

Read more
PlaybookEngineering

Building multi-tenant SaaS: isolation patterns that scale

We've shipped 3 multi-tenant platforms. Each used a different isolation pattern. Here's how we chose.

Read more
ArticleDesign Systems

Accessibility is not a feature: inclusive design as architecture

Accessibility isn't a checkbox. It's a constraint that makes your design system better — if you treat it as architecture.

Read more
PlaybookAI & Agents

Building AI agents that actually complete tasks, not just chat

Chatbots answer questions. Agents finish jobs. Here's the architecture pattern that makes the difference.

Read more
InterviewStrategy

The equity-for-engineering model: aligning incentives in tech partnerships

When we own equity, we care about uptime at 2am. Not because of an SLA — because it's our product too.

Read more
ArticleEngineering

API design that doesn't break: versioning, contracts, and evolution

Version in the header, not the URL. Use consumer-driven contracts. And never, ever deprecate on a Friday.

Read more
ArticleDesign Systems

Motion design systems: choreographing UI transitions at scale

Random easing curves and magic numbers don't scale. A motion system gives every transition a reason and a rhythm.

Read more
ReportAI & Agents

RAG is not enough: when retrieval-augmented generation hits the wall

RAG works until it doesn't. We hit the wall at 50k documents — here's what we learned and what we built instead.

Read more
ReportStrategy

Cloud cost optimization: the 68% savings we found hiding in plain sight

A client was spending $14k/month on AWS. We got it to $4.5k. Most of it was zombie resources nobody knew existed.

Read more
ReportEngineering

Real-time bidding systems: architecture for sub-200ms response

Vendors bid on jobs in real time. The system must rank, validate, and award in under 200ms. Here's the architecture.

Read more
ArticleAI & Agents

The cost of AI theater: why demos don't survive production

The demo wowed the board. Then it hit real data, real latency, and real edge cases. Here's why most AI projects die in staging.

Read more
InterviewDesign Systems

The pixel grid aesthetic: why we chose pixel art as a brand motif

Pixel art forces you to say more with less. Every cell is a decision. That's exactly how we think about engineering.

Read more
ArticleStrategy

Product-led growth for B2B SaaS: engineering the flywheel

PLG isn't a free trial. It's onboarding that teaches, activation that sticks, and expansion that sells itself.

Read more
ArticleEngineering

The platform engineering manifesto: from DevOps to developer experience

DevOps gave us automation. Platform engineering gives us abstraction. The difference is who the customer is.

Read more
PlaybookAI & Agents

Guardrails, not guardrails theater: real-world AI safety patterns

Adding a content filter isn't safety. Real guardrails are architectural — input validation, output grounding, and graceful degradation.

Read more
PlaybookDesign Systems

Dark mode done right: color semantics beyond light and dark

Inverting colours isn't dark mode. Semantic colour tokens, contrast ratios, and elevation mapping is.

Read more
PlaybookStrategy

Technical due diligence for PE: what to look for in the code

PE firms buy companies, not code. But bad code kills margins. Here's the technical due diligence checklist we run.

Read more
ArticleEngineering

Database per service vs. shared database: the trade-offs nobody tells you

Database-per-service sounds clean until you need a cross-service join. Shared database sounds dirty until you see the deployment speed.

Read more
ReportAI & Agents

AI readiness: what enterprise finance teams get wrong

Finance teams buy AI tools before they fix their data. We audited 12 enterprise finance stacks — here's the pattern.

Read more
ArticleDesign Systems

Component API design: props, slots, and the composability spectrum

Too many props and you've built a config monster. Too few and it's inflexible. Here's the composability spectrum.

Read more
ArticleStrategy

The SME paradox: enterprise-grade engineering at startup speed

You don't need 50 engineers to build enterprise software. You need 8 senior ones who've done it before.

Read more
PlaybookEngineering

CI/CD pipelines that actually catch bugs: beyond green checkmarks

Green CI doesn't mean working software. We added contract tests, visual regression, and load gates — here's the pipeline.

Read more
ArticleAI & Agents

Voice-first interfaces: conversational AI beyond the chatbot

Text-in, text-out is table stakes. The next interface layer is voice — and it demands a completely different architecture.

Read more
ArticleDesign Systems

Responsive typography: fluid scales without the complexity

One line of CSS replaced 6 media queries. Here's the fluid typography system we use across every project.

Read more
ArticleEngineering

WebSocket vs. SSE vs. polling: choosing the right real-time pattern

WebSockets are bidirectional but stateful. SSE is unidirectional but simple. Polling is neither but works everywhere.

Read more
InterviewStrategy

From services to products: how a consultancy builds its own IP

We started as a services company. Now we own 4 products. Here's the model — and why it only works with senior teams.

Read more
ReportAI & Agents

Fine-tuning vs. in-context learning: the decision framework

Fine-tuning is expensive and slow. ICL is cheap and fragile. The right answer depends on 4 variables — here's the framework.

Read more
InterviewEngineering

Building an ERP from scratch: lessons from Downstream

SAP didn't fit. Oracle was too slow to customise. So we built Downstream ERP from scratch — in 8 months.

Read more
ReportDesign Systems

Design system governance: who owns the tokens when the team scales

At 3 engineers, the system maintains itself. At 14, it needs governance. Here's the model we settled on.

Read more
InterviewAI & Agents

Agentic workflows in property management: a case study

A tenant reports a leak. An AI agent triages it, schedules the contractor, and updates the landlord — without a human in the loop.

Read more
ArticleEngineering

Mobile-first field service apps: React Native at scale

Offline-first sync, GPS tracking, camera capture, and push notifications — all in one React Native app used by 200+ technicians.

Read more
ArticleDesign Systems

Canvas-based data visualization: when SVG and DOM aren't enough

SVG chokes at 10k nodes. Canvas handles 100k without breaking a sweat — but you lose the DOM. Here's the trade-off.

Read more
InterviewAI & Agents

How we built WyseAgent: multi-source legal reasoning at scale

WyseAgent queries legislation, case law, and internal policy simultaneously. Here's how we built multi-source reasoning that lawyers trust.

Read more
PlaybookEngineering

Zero-downtime deployments: blue-green, canary, and rolling strategies

Blue-green for stateless. Canary for risky. Rolling for everything else. Here's the deployment playbook we use across all products.

Read more
ReportStrategy

The downstream opportunity: why oil and gas needs modern ERP

Downstream oil and gas runs on 20-year-old ERPs. The compliance burden alone costs millions. Modern ERP changes the equation.

Read more
ArticleAI & Agents

AI for field service: triage, dispatch, and predictive maintenance

AI triage cuts dispatch errors by 40%. Predictive maintenance catches failures before they cost. Here's the stack.

Read more
ArticleEngineering

Observability beyond logging: traces, metrics, and the three pillars

Logs tell you what happened. Metrics tell you how much. Traces tell you why. You need all three.

Read more
ArticleAI & Agents

The compliance AI gap: why BS7858 screening needs machine reasoning

BS7858 screening is paper-heavy and error-prone. AI can automate 70% of it — but only if the reasoning is auditable.

Read more
ReportEngineering

Technical debt quantified: how to measure and prioritize what to fix

We score tech debt on 4 axes: blast radius, velocity impact, security risk, and migration cost. Here's the framework.

Read more