Ghost and headless CMS work, editorial workflow and scheduled publication, membership and subscription publishing, and the migrations that move a publication between platforms without losing URLs or archives.
A publication is a delivery problem in different clothes. Something has to ship on a schedule, through review, under a brand, to an audience that notices when it does not. The practices that make a publication reliable are the same ones that make a software system reliable; the vocabulary is different.
What we build
Theme development, Content API integration, custom membership flows and the glue code that makes a headless CMS behave like one editors can actually use rather than one that is only comfortable for engineers.
Paid and free tiers, gated content, payment and renewal flows, and the retention engineering — dunning, resubscribe paths, email deliverability — that decides whether a subscription business compounds or leaks.
Draft, review, approval and schedule, with the pipeline-level evidence that an editor needs to track a piece without a status meeting. Scheduled publication that is monitored like any other scheduled job rather than hoped at.
Moving a publication between CMS platforms with URLs preserved, redirects complete, archives intact and search indexes rebuilt. The failure mode here is permanent — a lost URL is a dead backlink — which is why the migration is tested against the archive, not against a sample.
Core Web Vitals budgets, structured data, canonical URLs, feed hygiene and crawl behaviour, treated as acceptance criteria the site has to pass rather than an afterthought bolted on when traffic flattens.
The hard parts
A vendor who cannot tell you where their own discipline is difficult has either not done it or is not going to tell you the truth about your project either.
The CMS will be replaced within the next decade; the archive will not. A content model designed for one platform’s field types is a migration disaster in waiting, which is why the data model is designed first and the CMS second.
An editor who has been burned by a missed publication once will shadow-schedule everything thereafter, which costs the whole organisation hours per week forever. Scheduled publication must be monitored and reliable before anyone is asked to depend on it.
URLs change, redirects miss edge cases, images are stripped, embeds break. The honest version of a migration project assumes an archive-wide crawl diff is required before cutover, not a sampling plan drawn up to fit the schedule.
Stack
The full stackThis is what we reach for when the decision is ours. When you already have an estate, we work in it — the stack is part of the engagement, not a precondition of it.
Roles we staff
The reasoning, published
Every capability has a matching domain in the knowledge library. Read it before you talk to us — it is the fastest way to tell whether we know what we are doing.
Discovery as a weekly habit rather than a phase. Customer contact, opportunity solution trees, assumption mapping, and how to run discovery alongside delivery without rebuilding a miniature waterfall.
Practitioner · 10 minHow to move from a feature roadmap to outcome commitments without losing the trust of stakeholders who want dates. Writing measurable outcomes, choosing leading indicators, and the ways OKRs fail.
Practitioner · 11 minHow to buy it
Capability answers who works on it. The engagement model answers what we are accountable for, how it is priced and how it ends.
Other capabilities
Probabilistic systems
LLM applications, retrieval systems, agents and applied ML built to a standard you can put in front of a regulator — with evaluation harnesses, cost controls and failure behaviour designed in rather than discovered in production.
Software that acts
Systems that choose their own next step — tool-using agents, orchestrated workflows and automation that spans your existing systems — designed so that what they are permitted to do, and what happens when they are wrong, are decided up front.
Irreversible deployment
Protocol and application development where a deployment cannot be rolled back and a defect is a withdrawal. Contract engineering, security review, upgradeability design and the on-chain boundary decision.
Gated releases
iOS, Android and cross-platform applications delivered continuously despite a third party sitting between your merge and your users — staged rollouts, feature flags, release trains and a native-versus-cross-platform decision made on economics.
The paved road
The substrate the other three stand on: cloud infrastructure, deployment pipelines, observability, data platforms and the internal paved road that determines how fast every team above it can move.
Software that moves
ROS2 applications, perception and state estimation, embedded and motor control, and the simulation-first workflow that lets behaviour be proven in a simulator where failure costs nothing before it meets hardware.
Evidence over opinion
Checks, runs, metrics and incidents across web, publishing, AI and blockchain systems — flow metrics with their denominators, daily verification of live products, and alerting designed not to cry wolf.
The work between the systems
Integration between the systems you already run, scheduled jobs with named ownership, cross-system reactions and the auto-recovery that keeps them honest — because an automation that fails silently is worse than no automation.