Web Development
Sites, stores, internal applications and custom integrations. One partner from scoping to production.
What you get
Sites and stores
Business sites, e-commerce, events: the same demand for structure and speed.
Internal tools
Dashboards, business back offices and automations that replace shared Excel files.
Integrations
APIs, ERP, CRM, invoicing: getting your tools to talk to each other.
Four fields we work in every day
WordPress
Custom extensions and themes, Gutenberg blocks, roles and editorial workflows. Native hooks only, no core modifications.
Custom extensions →
WooCommerce
Shortened checkouts, carriers, volume pricing, subscriptions, accounting exports and ERP connectors.
Online store →Headless
WordPress kept as the back office, content exposed over REST or GraphQL, a decoupled front end. Your editors keep their tools.
Decoupled architecture →
Next.js front end
React and TypeScript, server rendering, optimised images, a component design system. Core Web Vitals green from launch day.
Next.js & React →How we work together
No vague packages: a written scope, a firm price, deliverables you can actually test.
Do you work with agencies?
Yes, as a technical subcontractor, white-labelled if needed.
Will you sign an NDA?
Gladly, even before scoping.
What if the project goes off the rails?
The written scope is the reference: any addition is priced separately, never imposed.
Custom extensions
When the WordPress repository does not answer your need — or answers it with ten plugins stepping on each other — we write the one that is missing. Fields and content types specific to your business, focused admin screens, roles and permissions, imports and exports.
The code relies only on native hooks: neither core nor theme is touched. Deactivate the plugin and the site still stands. You receive the Git repository, the documentation and one month of fixes included.
See the Custom WordPress Extensions page →Online store
On WooCommerce as on PrestaShop, we start with the product page and the checkout: fewer steps, fewer fields, shipping costs shown early. That is where the order is won or lost.
In the back office: variants, multi-warehouse stock, volume pricing, B2B quotes, carriers, invoices and accounting exports — wired to your ERP when you have one, so nothing gets re-typed.
See the Online store page →Decoupled architecture
In headless mode WordPress stays the back office your team knows, but it no longer renders pages: content is exposed over REST or GraphQL and consumed by an independent front end. The result is a presentation layer you can rebuild without touching the content, and vice versa.
Decoupling pays off with high traffic, several channels (site, app, kiosk) or complex interfaces. On a simple site a good theme costs less — and we will tell you so. The switch can happen section by section, keeping your URLs and redirects.
See the Next.js & React page →Next.js & React
The front end is written in React and TypeScript on Next.js: server rendering, pre-generated pages, optimised images and code splitting. Core Web Vitals are measured before launch, not hoped for afterwards.
We deliver a design system of reusable components, so every new page costs less than the last. Metadata, structured data, sitemaps and redirects are handled in code — not handed to yet another plugin.
See the Next.js & React page →