Six sectors, and the constraints that define them
Domain knowledge is not a marketing claim — it is knowing which requirements are negotiable and which will fail an audit. These are the sectors we build for.
Systems where "mostly available" is not a specification
Clinical software is judged on the worst day, not the average one. Availability, audited access and data protection are structural requirements, designed in at the start rather than added before a review.
- Patient-facing platforms. Scheduling, intake, communication and results access with identity handled once, properly.
- Clinical workflow tools. Documentation support and task management that fit a clinician's actual day rather than an idealised one.
- Integration over replacement. Connecting to existing clinical systems instead of asking a hospital to abandon them.
- Audited access. Every record view attributable, retained and reportable.
- AI with a clinician in the loop. Retrieval over protocols and documentation support — assistance, never autonomous clinical decisions.
Money movement, where correctness is the product
Financial systems fail in expensive and public ways. The engineering discipline that matters here — idempotency, reconciliation, immutable history — is unglamorous and non-optional.
- Payment and transaction systems. Idempotent operations, reconciliation and settlement that survives a retry or a partial failure.
- Ledger design. Double-entry, append-only history and balances that are derived rather than stored and hoped for.
- Onboarding and verification. Identity and document checks with automated extraction and clear manual review paths.
- Regulatory reporting. Reports generated from the transaction record, reproducible for any historical date.
- Anomaly detection. Pattern monitoring on transaction flow, with alerts that a human triages.
Where the catalogue and the warehouse have to agree
Online retail fails at the seams. Stock says one thing, the storefront says another, and somebody reconciles the difference by hand every morning before trading starts.
- Storefront engineering. Shopify, WooCommerce, headless or custom — chosen by what fits the commercial model, not by preference.
- ERP and stock integration. Products, pricing, availability and orders synchronised both ways with explicit conflict rules.
- Payments and fulfilment. Gateways, subscriptions, partial shipments and returns handled as first-class flows.
- AI merchandising. Recommendations and semantic search that respect stock and margin rather than similarity alone.
- Performance and SEO. Core Web Vitals treated as a commercial metric, measured on your real pages.
Portfolios, pipelines and the documents underneath them
Property businesses run on two things software usually handles badly: long-lived relationships and a great deal of unstructured paperwork.
- Property and portfolio management. Units, tenancies, maintenance and financial performance in one record rather than four systems.
- Listing platforms. Search, media handling and syndication to portals, with pricing and availability kept in sync.
- CRM for long cycles. Enquiry through to completion, where the relevant history is measured in years.
- Document intelligence. Lease and contract extraction — dates, break clauses, escalation terms — into structured fields you can query.
- Portfolio analytics. Occupancy, yield and maintenance cost reported across the whole estate.
Software that works on site, not just in the office
The defining constraint is the environment: gloves, sunlight, no signal, and a workforce that will abandon any tool that takes longer than the paper form it replaced.
- Project management. Programmes, milestones, variations and cost tracking against budget in real time rather than at month end.
- Workforce and plant. Scheduling, certification expiry, timesheets and equipment allocation across multiple sites.
- Offline-first field apps. Inspections, snagging and progress capture that work with no connection and sync when signal returns.
- Document control. Drawing revisions where everyone is provably on the current version.
- Vision-assisted reporting. Site photography classified and attached to progress records automatically.
When the process has outgrown the software
The common pattern: a system chosen years ago at a smaller size, now surrounded by spreadsheets and workarounds that quietly became the real process.
- ERP and business systems. Finance, procurement, inventory, HR and projects on one ledger.
- Internal tooling. The applications a specific team needs and no vendor sells.
- Workflow automation. Approvals, routing and reporting that no longer depend on someone remembering.
- Integration. Making the existing estate behave as one system rather than several that disagree.
- Knowledge retrieval. Policies, procedures and history made searchable and answerable.
Your industry next
Sector experience shortens discovery; it is not a prerequisite. If your problem is a data model, a process and a set of constraints — and it always is — we can work with it. We will be direct about where our knowledge stops and yours has to fill the gap.