Nobody owns the whole.
That is the job.

Large programmes rarely fail on technology strategy. They fail on the scatter. A registration tool from one supplier, a dashboard from another, a payments integration nobody owns, three incompatible data collection apps, and a spreadsheet quietly holding the reporting together. When something breaks at a seam, the argument is about whose seam it is. The programme pays for that argument in time, in money, and in figures nobody can walk back to an input.

Intellogi is the technology function those programmes do not have in-house. We start before the specification exists. We turn programme objectives into a requirement: what is needed, what already exists, what should be bought rather than built, and what should not exist at all. We hold the shape of the estate — systems, data model, integration points, access tiers, hosting, security posture, and how it will be governed. We then build and integrate the parts that have to exist, including the connections to whatever is already running. We operate what we build. We transfer it: documentation, runbooks, named owners, trained engineers. The engagement has an end, designed from day one.

Small and senior is the right shape for this, not a limitation. A large programme does not need headcount sold by the seat. It needs a few people who can define the requirement, hold the architecture, and stay answerable when a seam fails. We do not grow a team to fill a chart. We stay small enough that one counterpart can still see the whole.

We work from offices in London, United Kingdom and Hyderabad, India. The overlapping hours are not a convenience. They are what makes Run real: support, incident response, and data-quality monitoring across UK and India time zones.

We will not take a specification we did not help write and call that a complete engagement. We will not build a piece of the estate and leave the seams to someone else. We will not ship without a transfer plan. We will not stay because the handover was never designed. If the work is a brief to implement and leave, we are the wrong counterpart.