PRODUCTS
Three products that worked together as one system.
Three products, one system: what each achieved, and how the team delivered it.
THE CORE
Eficode Data Platform
May 2025 – February 2026
Centralized, governed and secured data, used in real time by every business function and by customer-facing products.
THE SIGNALS
Eficode Connectors
Nov 2024 – February 2026
Privacy-first plugins in the vendors' own marketplaces that collect signals about how tools are used, never personal or issue data.
THE PORTAL
Eficode Journey
Oct 2022 – February 2026
The customer portal where reports and metrics are shown, including tool adoption and usage data from the Connectors.
Eficode Data Platform: a stable core system for the whole business
Engineering Manager, May 2025 – February 2026
The platform went two months without incidents while the whole business used it for reporting and customer-facing products relied on it. I took over in May 2025 and led the team that stabilized and developed it.
THE SITUATION
The platform connected to multiple internal and external systems, and its data served both audiences. Internally, every business function relied on it for daily operations. Externally, it fed several customer-facing products. The data was centralized, governed and secured in one place, which made data analytics possible.
WHAT I DID
Two decisions stand out. We stabilized the platform with monitoring and unit tests, and we decommissioned another service and folded it into the platform, choosing the option that needed the least technical work, because the decision came down to stakeholders' preferences.
CROSS-FUNCTIONAL LEADERSHIP
All business functions used the platform daily and it also fed customer-facing products, so every change had to work for both audiences. Requirements came in through the service desk, and a steering group of business owners prioritized and approved them.
SECURITY AND GOVERNANCE
Most recently I led the design and implementation of role-based access control (RBAC) to strengthen security and governance across the platform. Data access was managed by groups. To avoid disrupting the products that depend on the platform, we tested permissions against a release plan before going to production and avoided releasing during key operational activities.
DELIVERY
Monitoring played a major role: when an alert fired, fixing it became the priority. Stabilizing the platform exposed a number of key issues, which we fixed, and it then became very stable. We had strong CI/CD across a couple of environments, plus integration and acceptance testing.
OUTCOME
The platform went two months without incidents.
The whole business used its data for reporting.
Governance was clearly documented: how things work, how to get data in and out, and how to make changes.
The technical handover to another team was completed, stable and documented. Six of its software engineers joined the platform team, which I continued to manage, expanding the resource pool and freeing capacity for other strategic priorities.
Eficode Connectors: cross-tool metrics through vendor marketplaces
Engineering Manager, Nov 2024 – February 2026
Three marketplace connectors shipped in about eleven months, giving Eficode metrics from customers' own tool environments without exposing their intellectual property or personal data. I led the engineering team.
THE SITUATION
Eficode wanted its advisory work to rest on tailored, metrics-based recommendations. That required extracting data from customers' tools, across several vendors, while protecting customers' intellectual property and personal data.
WHAT I DID
We built the connectors as plugins in the tool vendors' own cloud marketplaces, so customers install them like any other app. The design is privacy and compliance first: they collect no personal or issue data, only signals about how the tools are used, which is what makes cross-tool analytics possible without exposing IP or personal data. The marketplace security reviews and approvals went smoothly.
CROSS-FUNCTIONAL LEADERSHIP
The work sat between engineering, product, marketing and partners including Atlassian, GitHub and Microsoft. We worked closely to align what was technically feasible with what the business needed, and built partner and marketplace requirements in from the discovery phase.
DELIVERY
Oct 2025
BitBucket Cloud
Third connector shipped
Jun 2025
GitHub and GitHub Copilot
Cloud and Data Center
Mar 2025
Jira, Confluence and JSM
First connector shipped
The sequence followed business goals, requirements and partnerships, and once we had templates and ways of working, we could launch each new connector quickly. GitLab and Azure were scoped and next in the sequence when I left.
KEY OUTCOMES
Multiple organizations gained greater value from their existing toolsets.
The connectors led to new engagements with existing and new customers.
Partnerships with GitHub and Microsoft were strengthened.
Eficode's advisory approach shifted toward tailored, metrics-based recommendations.
Eficode Journey: customer reporting from hours to minutes
Engineering Manager, Oct 2022 – February 2026
Monthly reporting per customer fell from hours or days to minutes, and 50–60% of Managed Services customer organizations used the portal every month. I led the engineering team that built it from scratch.
THE SITUATION
Eficode's SLA reporting was a manual, time-consuming process that was inconsistent and error-prone, and billing periods were stressful for service managers. The goals were to streamline reporting, build customer trust, centralize information sharing and open the way for a new Advisory & Support product line.
ENGINEERING
Journey was built with proper CI/CD, which let us release new features daily and keep improving the product over time. The biggest technical step was the April 2025 backend rebuild, which made the portal more modular and more reliable: each part runs as an independent service, so a failure in one does not take down the others, and monitoring catches failures as they happen.
PRIORITIZATION
Not every feature paid off equally, so we let usage guide investment. The System status view was a low investment with fairly low usage, while the Billing view was the first feature to meaningfully increase monthly active users.
DELIVERY
Nov 2025
Lens
Trends over time, showing whether a change such as adopting Copilot was taking hold
Dec 2024
Tooling Advanced Metrics
Tool adoption and usage data, growing as each Connector shipped
Sep 2023
Billing view
Standardized billing reports with monthly and yearly views
Apr 2025
Recommendations
Standardized, automated advisor recommendations with impact and effort estimates
Jun 2024
Main Dashboard
A landing page that guided users to the actions they need
Spring 2023
SLA reports & System status views
Two-click SLA reports and a live tool and system status page
KEY OUTCOMES
Monthly reporting time per customer fell from hours or days to minutes.
Human error in reporting was reduced to a minimum.
Customer trust in the Managed Services organization increased significantly.
The portal enabled the new Advisory & Support product line.
50–60% of Managed Services customer organizations became monthly active users.
CONTACT
Let's talk about your engineering organisation.
Engineering leadership, delivery, or the operating model behind both: I'm happy to talk.