What we do, and the problems we get called for.

Marketing sites, customer portals, internal tools, SaaS products. Most of our new work runs on React and Next.js with Tailwind, with .NET on the back end when the project needs it.

We care about the parts you only notice later: pages that load fast, and code the next developer can read. Your team should be able to edit content on its own.

New Umbraco builds, upgrades from versions 7 and 8, headless setups with a Next.js front end, and long-term support for existing Umbraco sites.

A site that nobody looks after gets slower and less secure every month. We keep yours up to date: framework and CMS updates, package upgrades, bug fixes, small changes and content help.

You get developers who already know your project, so a fix doesn't start with three days of reading. This applies to sites we built and to sites we take over.

An audit is a structured look at your application and the way it's hosted. We check dependencies with known vulnerabilities, authentication and permissions, exposed endpoints and admin panels, configuration and secrets, headers, backups and logging. You get a written report: what we found, how serious it is, what to fix first.

After the audit we can fix the issues and set up ongoing monitoring, so you hear about problems from us first.

Good content only ranks when search engines can crawl the site and its pages load well on a phone. An SEO audit looks at the technical side: page speed and Core Web Vitals, crawlability and indexing, sitemaps and robots rules, titles and meta descriptions, headings, structured data, broken links and redirects, duplicate content, and multilingual setup.

You get a prioritized list. Then we implement it in your code or CMS, which is the part most audits leave to you. For site migrations and redesigns, we plan the redirects up front so existing rankings survive the launch.

We focus on the technical foundation, because that's what good content and links rely on.

We audit websites and applications against the Web Content Accessibility Guidelines (WCAG), usually at level AA. That means testing by hand with a keyboard and a screen reader as well as with automated checkers, because automated tools only catch part of the problems. We look at color contrast, headings and structure, form labels and errors, focus order, alternative text, captions, and custom components like menus, modals and date pickers.

The report lists each issue, where it is, which guideline it fails and how to fix it. Then we fix it, and add automated accessibility checks to your test suite so new problems are caught before they ship.

Payment providers, CRMs, ERPs, email platforms, booking systems, shipping, accounting, single sign-on. We connect your website or app to the services your business already runs on, through their APIs or webhooks, and build the error handling that keeps an outage on their side from becoming one on yours.

We take over projects from developers or agencies who are no longer around, figure out what state they're in, and get them stable. When the code itself is the problem, we refactor it step by step until changes are safe again.

If releasing your site involves FTP, a checklist, or one specific person's laptop, we'll replace that with a pipeline. Code is built and tested automatically, preview environments are created for each change, and production deploys happen the same way every time, with a way back if something goes wrong.

We set this up on GitHub Actions, Azure DevOps or your host's own tools, depending on where your code and servers already live.