Whatever the software
has to do.

Custom software

Applications built around how your business actually works, not how a package thinks it should.

Most businesses end up bending their process to fit software somebody else designed, then paying per seat for the privilege. We build the application the other way round - starting from the way the work already runs, and automating the parts people currently hold together with spreadsheets, email threads and memory.

• Internal tools, portals, dashboards and line-of-business systems
• Desktop, web and mobile, or all three against one backend
• Reporting and exports that match the numbers you already use
• Role-based access, approvals and a full audit trail as standard

Legacy modernisation

Old, slow, unsupported software rebuilt on current technology - without losing what it knows.

Software that has run the business for fifteen years is not a mistake, it is an asset with a maintenance problem. We rebuild it on a current stack, keep the rules and the history that make it valuable, and retire the parts that only exist because of a limitation nobody remembers. The data comes with it, reconciled against the old system before anything is switched off.

• Access, VB6, Delphi, classic ASP, legacy PHP and unsupported frameworks
• Data migration with reconciliation against the system being replaced
• The old rules documented as they are rebuilt, so they stop being folklore
• Phased cutover, so the business never depends on a single switch-flip day

AI inside your software

Applications that read, summarise, classify and answer - instead of only storing and displaying.

The useful version of AI in a business application is rarely a chat box in the corner. It is the invoice that reads itself into the ledger, the ticket that arrives already categorised and routed, the report that comes with the summary written, and the search that answers a question instead of returning forty rows. We build those into the software you already have as well as into new work.

• Document and invoice extraction, straight into your existing records
• Classification, routing and triage on incoming work
• Question answering over your own documents, with the source shown
• Drafting and summarising, always with a person approving the result

AI automation

The repetitive work between your systems, running on its own and showing what it did.

Every business has work that is genuinely mechanical: rekeying the same data into a second system, chasing an approval, producing the same report every Monday, watching an inbox. We automate those end to end, with the judgement calls handled by a model and the consequences still handled by a person who can see exactly what ran.

• Workflows across email, files, forms, CRM, finance and ticketing systems
• Scheduled and event-driven jobs with retries and alerting when they fail
• Human approval on anything with a financial or legal effect
• A visible log of every run, so an automation is never a black box

Websites & web platforms

Fast, accessible sites and customer-facing platforms that do more than sit there.

From a marketing site that loads instantly on a phone on mobile data, to a customer portal with logins, payments and documents behind it. Built to be edited by your own team afterwards, measured properly, and quick enough that speed stops being something anyone raises.

• Marketing sites, portals, booking systems and customer self-service
• Content editable by your team without a developer in the loop
• Accessibility and load speed treated as requirements, not as extras
• Search, analytics and conversion tracking configured before launch

Mobile apps

iOS and Android apps for people who are on their feet, not at a desk.

Field engineers, drivers, site supervisors and sales teams do not work at a keyboard, and software designed as though they do fails them. We build mobile apps around one-handed use, bad signal and gloved hands - offline where it has to work offline, and with the camera, GPS and signature capture the job actually needs.

• Native and cross-platform builds from one codebase
• Offline-first data capture that syncs when signal returns
• Camera, GPS, geofencing, barcode scanning and on-screen signatures
• Push notifications, app store submission and staged rollout

SaaS platforms

Multi-tenant products with plans, billing and onboarding - built to be sold, not only used.

If the plan is to sell the software rather than only run it, the architecture has to carry that from the first commit. Tenant isolation, per-customer configuration, plan limits, self-service onboarding and billing are not features to add later - retrofitting them is most of a rewrite.

• Tenant isolation, organisation accounts and per-plan limits
• Self-service sign-up, trials, seat management and suspension
• Single sign-on, and per-customer branding on customer-facing screens
• Usage metering and the operator tooling to run the platform day to day

Software redesign

Same system underneath, rebuilt on the surface so people stop dreading it.

Sometimes the logic is sound and the problem is everything around it: twelve clicks to do one thing, a screen nobody can read, a workflow that assumes a process changed four years ago. We redesign the interface and the flow against how the work is really done - keeping the engine and replacing the cockpit.

• Interface and workflow redesign on top of an existing system
• Watching real users work before anything is drawn
• A design system, so later screens stay consistent without us
• Rolled out gradually, with the old screens available during the change

Systems integration

Your separate systems connected centrally, so a number is entered once and appears everywhere.

Most businesses run five or six systems that were never designed to speak to each other, and the integration is a person copying between them. We connect them properly - through their APIs where they have them - so records stay in step, and give you one place to see what synced, what failed and why.

• API, webhook, file and database integrations between existing systems
• One central record where several systems disagree today
• Sync monitoring with alerting, retries and a replayable failure queue
• An internal API layer, so the next system you buy is a connection not a project