Case study 01 · Admiral Markets

2019–2023 · Fintech · Internal SaaS platform

Owning the evolution of a business-critical CRM ecosystem

The formal role was Project Manager / Business Analyst. The operating reality was internal platform ownership across roadmap, requirements, delivery, support, vendors and long-term system viability.

Formal title
Project Manager / Business Analyst
What the role required
Internal platform ownership across systems, people and delivery

The CRM served multiple business functions and depended on a broad connected ecosystem. The work was to make change possible without losing operational stability — coordinating decisions and delivery, not claiming authorship of every underlying system.

01

Scope

One platform, several competing systems of work

The role connected business demand with technical delivery across four concurrent streams.

  • CRM Service Desk and operational support
  • Current development backlog
  • Integrations and cross-system dependencies
  • Strategic roadmap and migration initiatives
02

Operating model

From request intake to accepted release

Responsibilities covered discovery, requirements and SRS, estimates, contractor coordination, release planning, UAT, acceptance and post-release improvement. Roadmap choices were tied to capacity, risk, cost and maintainability.

  • Roadmap and backlog management
  • Requirements, acceptance criteria and solution assessment
  • Cross-team dependency and vendor coordination
  • TCO, build-vs-buy and contractor cost analysis
03

Decision support

Making constraints visible before they became incidents

When growing support demand, staff loss and fixed budget made the existing allocation impossible, the analysis separated evidence from assumptions and gave leadership explicit choices.

  • Problem: four workstreams competing for the same limited capacity
  • Evidence: active CRM users grew 20% in 2022 while Service Desk demand increased
  • Risks: strategic delays, support degradation and key-person dependency
  • Options: proportional split, dedicated capacity, or reduce scope and plan transition

Selected impact

Measured platform impact

Metrics are reported in the source CV and represent shared team outcomes coordinated through this role.

90%
of releases met initial estimates
10×
fewer reported CRM issues
faster request resolution
~30%
lower CRM development and maintenance cost