Six capability areas, assembled around the programme, not sold as a product catalogue. Vendor-agnostic by design, capability-led in practice.
Vendor-led delivery is what got most of the stuck programmes stuck. A partner sells what a partner sells, and the programme contorts to fit. Company 31 does the opposite. We lead with the capability the outcome requires, then pick the technology that fits, and the integration layer that keeps competing systems honest.
Manuel has delivered across every category on this page in the last ten years. The squad he assembles around a programme is drawn from specialists he has shipped alongside before, each chosen for the surface the programme actually needs.
Hyperscale public cloud and hybrid estates. Landing zones, migration, cost control, resilience, and the governance layer around them. This is where most programmes live or die on the non-functionals — security, identity, observability, and cost.
Data platforms, analytics, machine learning, and generative AI enablement. Evidence before enthusiasm, and governance from day one rather than day ninety.
CRM, ERP, and line-of-business systems that have to work together under one operating model instead of three. Implementation is the easy half; the process design is the hard half, and we lead with that.
APIs, event streams, workflow, and automation. The connective tissue between the applications, the data, and the humans doing the work. Usually the difference between a programme that is technically live and a programme that has actually landed with the business.
Identity, posture, compliance, and risk. Essential Eight, ISO 27001, SOC 2, and the operating rhythm that keeps them honest once the auditor leaves. Cyber is not a bolt-on at the end of the programme — it is a workstream from the charter.
Custom applications, portals, and customer-facing builds. Designed to the real constraints of the user and the process, built with modern web and mobile stacks, shipped with the same governance as the rest of the programme. Proof in the click-through, not the pattern library.
A Rescue engagement might be cyber and governance first, data and integration second, and only glance at business applications. A Build engagement for a membership body might lead with business applications and digital product, with cloud and integration underneath. The pillars are not a menu to choose from. They are the surface a credible delivery partner has to be able to cover, and then assemble the right subset around your programme.
Blockchain as a business model. Anything whose value proposition collapses if you ask it a second question. Consulting that ends at the slide deck. Marketing tech that is really just a contact form. If you need one of those, Company 31 is not the right partner, and Manuel will say so on the call.
Company 31 uses no tracking cookies, no advertising pixels, and no third-party analytics. There is no contact form — enquiries go straight from your mail client to Manuel's inbox. A single localStorage key remembers that you have dismissed this notice. See the privacy statement for detail.
