Company · Team
The team is shaped by the project.
A small project does not need ten people. A complex project must not depend on a single individual.
We scale the team when the project requires it.
Roles we cover
- project lead
- business analysis
- architecture
- UX/UI
- frontend
- backend
- mobile development
- AI and data
- DevOps and infrastructure
- QA
- security
- documentation
- production crew
- event technical crew
How the team is assembled
Small project
A project lead and one or two people delivering. No layers in between.
Product or system
Lead, analysis, UX/UI, development, testing and DevOps.
Complex public project
Additional project management, documentation, security and subcontractor coordination.
Production and event
A production and technical crew connected to the digital side of the project.
The roles we cover
A team is not a list of people; it is a list of roles that can be covered for a project. Below is what each role does. Epix, together with its specialist partner network, can bring these into a project; the actual composition depends on the project, and not every project includes all of them.
Project management
Runs scope, schedule, risk and dependencies, and reports to the client. Makes sure decisions are recorded and taken by the right person.
Business analysis
Maps the process, user roles, rules and exceptions, and turns them into a specification and acceptance criteria.
Architecture
Defines modules, system boundaries, the data model and the integration approach; records technical decisions with the reasoning.
UX/UI
Information architecture, user journeys, wireframes, prototype and a design system the build reuses.
Frontend
User interfaces, large lists and tables, forms and real-time views.
Backend
Business logic, APIs, the data model, background processing and performance as the system grows.
Mobile
iOS and Android apps, notifications, offline use, camera, scanning, location and device connections.
AI and data
AI solution design, data preparation and quality, knowledge retrieval, evaluation, reporting and analytics.
DevOps and infrastructure
Environments, releases, containers, cloud or on-premise, observability, backups and restore.
QA
Test scenarios, manual and automated testing, regression, integration testing and defect tracking. Separate from the development team where required.
Security
Security architecture, access review, environment hardening and requirements for regulated environments.
Documentation
Technical, user and administrator documentation, plus handover and training material.
Production
Filming, editing, photography and event content when multimedia is part of the project.
Event technical crew
LED, video, sound, lighting, live streaming and on-site operators.
The core and the network
Epix Group has twenty people. That is the core team which leads projects, delivers them and stays on them after go-live. Around it sits a vetted specialist partner network with more than 190 experts available, brought into a project when it needs knowledge or capacity the core team does not hold.
For the client the distinction is invisible, and it should be: one contract, one contact, one accountability.
Why the team is not assembled in advance
A team fixed before the project fits it only by accident. A small project with ten people gets slower, not faster, because more time goes into coordination than into work. A demanding project with two people depends on nobody falling ill.
- who leads the project and is accountable to the client
- which roles the project actually needs
- what the core team covers and what the network covers
- who covers a key person when they are away
- who stays with the project after go-live
Related work
Related solutions
Sounds like your project?
Send us the project description, your existing system, the tender documents or the event date.