A software company with two established disciplines.

Our approach

Software projects generally disappoint for reasons unrelated to engineering. The requirements were never documented. A system was procured before the process it was intended to support was understood. Integration was deferred to a later phase. The people required to operate the system daily were consulted last.

We therefore begin at the other end: what takes place in this organisation in the course of ordinary business, and what would materially improve it? The technology decision follows that assessment, and is usually the least significant element of the engagement.

The same principle applies to resourcing. A specialist who is technically capable but unsuited to the team represents a failed placement, and this is generally apparent within the first two weeks. We would rather address that at week two than at month six.

How we are structured

• Senior by composition. The engineers present at the first meeting remain on the work.
• Independent of any vendor. No technology to defend and none to promote.
• Complete transfer. Source code, build pipeline, documentation and infrastructure.
• Breadth of delivery. Consumer applications, compliance platforms, integrations and desktop software, under one engineering standard.
• United Kingdom based. On site where the engagement requires it, remote where it does not.