Skip to main content

Leadership & teams

Who is accountable, and for what

We publish roles rather than headshots. What matters when something goes wrong is knowing which function owns the decision — and that the person who scoped your project is the one delivering it.

Leadership functions
8
Delivery disciplines
8
Escalation
Named contact per engagement
Base
London EC1V 2NX

Accountability

Leadership functions

Every engagement has a named individual behind each of these roles, introduced at kickoff. Escalation paths are agreed before work begins, not improvised during an incident.

Managing Director

Accountable for the company overall — commercial terms, client relationships at board level, and the standards everything else is held to.

  • Commercial and contractual accountability
  • Executive-level client relationships
  • Company governance and compliance
  • Final escalation point for any engagement

Head of Engineering

Owns technical quality across every project: architecture decisions, code standards, and the review process that keeps them honest.

  • Architecture review and technical sign-off
  • Coding standards and peer review culture
  • Engineering hiring and capability development
  • Technical feasibility on new proposals

Head of Consultancy

Leads the advisory practice — the strategy, process, and operating-model work that determines what should be built in the first place.

  • Discovery and strategy engagement leadership
  • Process analysis and operating model design
  • Business case and roadmap authorship
  • Independent review of third-party proposals

Delivery Director

Responsible for projects landing on time and on budget, and for telling you early when either is at risk.

  • Programme and sprint governance
  • Budget tracking and burn reporting
  • Risk identification and escalation
  • Client communication cadence

Head of Cloud & Infrastructure

Owns the platforms our software runs on — architecture, cost, resilience, and the recovery plans that get tested rather than filed.

  • Cloud architecture and cost governance
  • CI/CD and platform engineering standards
  • Security hardening and access control
  • Backup, recovery, and incident readiness

Head of Design

Leads research and interface design, and is responsible for the products being genuinely usable by the people who have to use them.

  • User research and usability testing
  • Interface design and design systems
  • Accessibility standards (WCAG 2.2 AA)
  • Brand and design consistency

Head of Data & AI

Responsible for data platforms, reporting integrity, and an honest assessment of where automation genuinely pays off.

  • Data architecture and pipeline design
  • Metric definitions and reporting integrity
  • AI feasibility assessment and pilots
  • Data governance and quality monitoring

Client Partner

Your named commercial contact from first conversation through to renewal — one relationship rather than a handoff between departments.

  • Single point of commercial contact
  • Scope, proposal, and statement of work
  • Quarterly service and roadmap reviews
  • Coordination across delivery teams

Delivery teams

The disciplines we staff from

Teams are assembled per engagement from these disciplines. Composition is agreed with you in the statement of work and can flex as priorities change.

Software Engineers

Full-stack, back-end, and front-end specialists across our supported language and framework set.

Cloud & DevOps Engineers

Infrastructure-as-code, CI/CD, containers, and observability across AWS, Azure, and Google Cloud.

Product Designers

User research, interaction design, and accessible design systems built for reuse.

Business Analysts

Process mapping, requirements definition, and the translation layer between operations and engineering.

Data Engineers & Analysts

Pipelines, warehousing, modelling, and reporting that stands up to scrutiny.

QA Engineers

Automated and exploratory testing, accessibility auditing, and release verification.

Delivery Managers

Sprint governance, budget control, risk management, and client reporting.

Management Consultants

Operating model, commercial analysis, and change management for adoption.

Seniority

The people who scope your project build it

A common and entirely legitimate concern is that the senior team who win the work are never seen again. We do not operate a separate pitch team. Whoever runs your discovery is accountable through delivery, and if that changes we tell you and explain why.

Working with your team

We are trying to make ourselves unnecessary

Documentation, runbooks, and knowledge transfer are built into delivery rather than promised at the end. If you decide to bring the work in-house, we support that transition — retainers should be renewed because they are useful, not because leaving is difficult.

Next step

Want to speak to the people who would do the work?

The first call is with someone senior enough to give you a real answer, not a qualification script.

sales@interwebservices.co.uk128 City Road, London, EC1V 2NX, United Kingdom