Explore VERTEX
What we do
We connect assessment, architecture, engineering, migration and operation around the systems your business already uses.
Page purpose
Use What we do to choose the path closest to your decision.
The What we do hub is a navigation and selection layer, not a service page or engagement scope. It helps a visitor begin with the shape of the decision rather than a preferred technology: a missing capability, a recurring operating problem, a system that needs attention, or a transition that needs evidence. Its role is to distinguish the available routes and explain what question each destination is designed to help examine.
Use this hub when the initial brief is broad or several parts of the estate are involved. Compare capability, solution, system, industry, technology and evidence routes, then follow the route that best matches the current question. The page does not diagnose an estate, prescribe every discipline or promise an output; it should narrow the next click and reveal the questions that still need organization-specific evidence.
Starting questions
When is this hub the right starting point?
- A broad modernization need is difficult to translate into a useful starting point.
- Service catalogues mix disciplines, technologies and business problems without explaining their relationship.
- Visitors can reach a technically relevant page that does not match their decision stage or ownership.
- Multiple system concerns make a single product- or platform-led route misleading.
Choose a route
Decisions that lead to the specialist page.
- Whether the starting question concerns a discipline, an operating problem or a named system.
- Whether the reader needs orientation, decision guidance, delivery detail or inspectable evidence.
- Whether enough context exists for a focused conversation or further self-guided exploration is useful.
Expected clarity
What should be clearer after exploring?
- A clear choice between capability, solution, system, industry, technology and evidence routes.
- A shared understanding of how discovery, delivery and continued operation fit together.
- A smaller set of relevant pages and questions for the next internal conversation.
What you will find
The content paths available here.
- An orientation map across the main website hubs.
- Plain-language distinctions between service, problem, system and technology routes.
- Cross-links that preserve the reader's decision context.
- Prompts for selecting a practical next step without prescribing an engagement.
Decision questions
Choose a route without unnecessary browsing.
Where should I start if several systems are involved?
Start with the operating problem or outcome that crosses those systems, then use the solution route to identify relevant boundaries. Follow system and capability links only after the cross-system process, ownership and constraints are visible; this avoids treating each application as an isolated project.
What does choosing a route decide?
It decides which perspective to explore next, not the eventual engagement. The appropriate next step still depends on available evidence, decision authority, risk, dependencies and the degree of uncertainty that discovery reveals.
Related decision