Four registered activities, three engagement models, and a clear statement of the work we turn down.
Each of the four is a registered SIC activity of the company. Work outside them is declined rather than stretched to fit.
Business and domestic software built to a written specification: web applications, internal platforms, integrations between systems that were never designed to talk to each other, and the data layers underneath them.
SIC 62012Independent advice on architecture, build or buy decisions, vendor selection, integration strategy and technical due diligence. Delivered as a written recommendation with the trade-offs set out, not a slide deck.
SIC 62020Mapping how work actually moves through an organisation, identifying the steps that do not require a person, and sequencing the change. Management consultancy other than financial management.
SIC 70229Ongoing operation of the systems we build under a defined service agreement, plus delivery capacity for teams that need engineering resource without a permanent hire.
SIC 82990Line of business applications, customer-facing web applications, mobile applications for iOS and Android, administrative back offices, reporting and analytics layers, and integration work joining existing systems. Delivery includes automated testing, deployment pipelines and written technical documentation as standard rather than as a chargeable extra.
Architecture review, technical due diligence on a supplier or an acquisition target, build or buy analysis, platform selection, data model review, and remediation planning for systems that have become expensive to change. Engagements are time-boxed and produce a written report with costed options.
Process mapping, identification of manual steps suitable for automation, workflow redesign, and a sequenced implementation plan with the dependencies and change impact stated. This is management consultancy other than financial management. We do not provide financial, tax, legal or regulatory advice.
Application support and maintenance under a defined service agreement with agreed response targets, monitoring and incident handling, scheduled change windows, and embedded engineering capacity for client teams that need delivery throughput without permanent headcount.
Most operational software problems are integration problems wearing a different hat. An integration layer gives every system one place to read from and write to, and gives the organisation one audit trail instead of six.
The pipeline is set up in the client's own accounts, under the client's own credentials, before the first feature is written.
Pricing is confirmed in a written proposal before work starts. We do not begin chargeable work on a verbal instruction.
A defined piece of analysis with a fixed price, a fixed duration and a named deliverable. Used to scope a build, assess an existing system, or test whether a process is worth automating at all.
A build priced against an agreed specification, delivered in increments, with a written change control process for anything outside the original scope.
A monthly commitment of engineering and support time under a service agreement, for clients with a continuing pipeline of change rather than a single project.
Stating this up front saves both sides a meeting.
Most engagements start with a short written brief and a scoping call. If we are not the right firm for the work, we will say so at that point rather than after an invoice.