Insights
Notes on technology decisions, written plainly.
No trend pieces and no listicles. These are the questions clients ask before starting a project, answered in the order they usually come up.
Custom software or off-the-shelf: how to decide
A practical framework for choosing between configuring an existing product and commissioning custom software, based on where your process actually differs.
Practical AI automation, and where it should stop
Where language models genuinely reduce work in a business workflow, where deterministic code is cheaper and safer, and how to tell the difference.
Core Web Vitals: what actually moves the needle
A prioritised list of fixes for LCP, CLS and INP on business websites, ordered by how much each one typically gains per hour of work.
Choosing an e-commerce platform for a growing catalogue
How to choose between hosted platforms, open-source storefronts and custom commerce, based on catalogue size, customisation needs and operating team.
How to write a technical brief that gets accurate quotes
The brief structure that separates a project that can be estimated from one that cannot, with the eight sections worth writing before you talk to any developer.
Where AI should not be allowed to decide
The categories of decision that need human accountability, and how to design automation that assists without taking responsibility.
How to redesign a website without losing search traffic
The migration checklist that protects rankings: URL mapping, content parity, staged launches and the first-two-weeks monitoring plan.
Checkout friction: the eight fixes that recover revenue
A prioritised list of checkout improvements, from guest checkout and address handling to payment retries and error messaging.
Rebuild or repair: an honest test for an ageing website
How to tell whether your existing website needs a migration or a targeted fix, using five checks that take an afternoon rather than a month.
Automating invoice and document workflows
A practical architecture for extracting, validating and posting document data, including the exception queue that makes it reliable.
What a business website costs, and what drives the price
The five variables that move website cost, with realistic ranges for a brochure site, a content-heavy site and a commerce build.
Product page SEO for stores that are not Amazon
How to structure product pages so they rank for buying intent: unique copy, structured data, variant handling and internal linking.
Planning a technology budget that survives the year
How to split spend between build, maintenance and improvement so that the second year of a platform is funded before it starts.
AI customer support that does not invent answers
Retrieval, refusal behaviour and escalation rules that keep an AI support assistant accurate and honest.
Choosing a content management system in 2026
How to pick between a headless CMS, a traditional CMS and a page builder, judged on editing workflow, performance and who on your team will use it.
WhatsApp commerce: what works and what does not scale
Where WhatsApp fits in a retail sales process, how to connect it to a catalogue and order system, and the limits to plan for before you rely on it.
Scoping an MVP without building the wrong thing
How to define the smallest release that proves the business idea, and the three questions that stop an MVP from becoming a small version of everything.
Data readiness before AI: the work nobody budgets for
The four data conditions an AI project needs, and the cleanup that has to happen before a model can produce anything useful.
When spreadsheets stop being enough
The signs that a spreadsheet-driven operation needs a real system, and the cheapest first step that is not a full ERP implementation.
The landing page structure that converts
A section-by-section layout for service and campaign landing pages, with the job each block performs and the mistakes that break the flow.
The hidden costs of a cheap website
Where low-cost website builds create expense later: page speed, content lock-in, plugin debt and the migration you eventually pay for twice.
A technical SEO checklist for a site that already has content
The crawl, index and rendering checks worth running quarterly, in the order that finds the most expensive problems first.
How to justify an internal tool
A simple model for calculating whether an internal tool pays for itself, using hours recovered, error cost and the value of visibility.
Accessibility basics that also improve conversion
The accessibility fixes with the widest business impact: contrast, keyboard navigation, form labels and readable type sizes.
In-house team or agency: an honest comparison
The factors that actually predict success with an in-house team versus an external partner, including hiring time, retention risk and knowledge transfer.
Local SEO for businesses with many locations
How to structure location pages, profiles and internal links so each branch can rank without cannibalising the others.
Integrating systems without creating a spider web
How to connect CRM, ERP, payments and internal tools with clear ownership of data, retries and error handling.
What a discovery phase should actually produce
The deliverables a paid discovery should leave behind: a decision-ready scope, a data model sketch, a risk list and an estimate you can defend.
Structured data that is worth implementing
The schema types that change search appearance for most businesses, and the ones that add effort without visible benefit.
Database design mistakes that cost years
The modelling errors that are cheap to fix before launch and expensive afterwards: missing keys, storing derived data and treating status as free text.
What maintenance actually means after launch
The four kinds of post-launch work, how to tell them apart in a contract, and why a launch date is the middle of a project rather than the end.
A design system a small team can actually maintain
The minimum viable design system: tokens, four component states and the documentation that stops it drifting.
Modernising a legacy system without a big-bang rewrite
A staged approach to replacing ageing software: strangle the edges, keep the data, and migrate feature by feature with measurable parity.
Choosing a technology stack without the religion
A practical way to select a stack based on hiring, hosting and ten-year maintenance rather than what is trending this quarter.
Hosting decisions that hold up at scale
How to choose between managed platforms, containers and serverless for a business system, judged on traffic shape and operational capacity.
Multi-tenant architecture for a product you intend to sell
Shared database, separate database or hybrid tenancy: the cost, isolation and operations trade-offs you need to choose between before your first customer.
Native or cross-platform: the trade-offs that matter
A decision guide for business apps, based on device features, team skills and the cost of maintaining two codebases over several years.
What actually drives the cost of a mobile app
The variables behind mobile app budgets: user roles, offline requirements, integrations and app store operations.
Building field apps that work without signal
Offline-first patterns for field teams: local storage, sync queues, conflict resolution and the UX rules that prevent data loss.
What a customer portal is worth, and how to build one
When a self-service portal reduces support load, the features that matter first, and the security decisions that cannot be deferred.
Next step
Tell us what you are trying to fix.
A short conversation is usually enough to know whether we are the right fit. If we are not, we will say so.