PRODUCTS
Three products that worked together as one system.
What each one achieved for the business, and how the team delivered it.
DATA
Eficode Data Platform
Brings data from all our integrations into one governed source for the whole business.
Feeds every report, invoice and product
INTEGRATIONS
Eficode Connectors
Marketplace apps that collect how customers' tools are used, never personal or issue data.
Add tool usage data to the Data Platform
CUSTOMER PORTAL
Eficode Journey
The customer portal that replaced manual SLA and billing reporting.
Shows customers their SLAs, billing and tool adoption
Eficode Data Platform: a stable core system for the whole business
Engineering Manager, Jun 2025 – Feb 2026
I took over the data platform in June 2025, midway through its build. It had been built fast under a deadline, and invoicing for about 150 Managed Services customers, every business function and all customer products already ran on its data. I stabilized it, gave everyone one way in, and kept building while it ran.
THE SITUATION
Every incident hit during monthly invoicing, and users were finding the problems before we were.
WHAT I DID
I found the real cause: nothing alerted us and nothing tested the data on the way in. I made the business case, at two to three engineer-days per incident, put two engineers on stability only, and took the accountability to senior management. We added monitoring and unit tests, and when an alert fired, fixing it came first. I also retired the old reporting API by folding it into the platform, the option that needed the least technical work.
CROSS-FUNCTIONAL LEADERSHIP
Every change had to work for the business and for the customer products. Requirements came in through the service desk, and a steering group of business owners prioritized and approved them.
SECURITY AND GOVERNANCE
I led the design and rollout of role-based access control, with data access managed by groups. We tested permissions against a release plan and avoided releasing during key operational activities. Governance was documented: how the platform works, how to get data in and out, and how to make changes.
HANDOVER
The platform was handed over stable and documented. Six engineers from the receiving team joined the platform team, which I kept managing, and that freed capacity for other priorities.
9 → 0
incidents, then two months clean
2 → 9
integrations, added while it ran
1 source
for all business reporting and every product
Eficode Connectors: cross-tool metrics from customers' own tools
Engineering Manager, Nov 2024 – Feb 2026
Eficode needed metrics from customers' own tools, across several vendors, without exposing their IP or personal data. I led the engineering team that built apps for the vendors' own marketplaces. They led to new customer engagements, stronger partnerships with GitHub and Microsoft, and advice based on customers' own metrics.
WHAT I DID
Customers install the apps like any other marketplace app. The design is privacy first: the apps collect only signals about how tools are used, which makes cross-tool analytics possible. Marketplace security reviews and approvals went smoothly. One app covered GitHub Copilot, so customers could see whether their AI adoption was taking hold.
CROSS-FUNCTIONAL LEADERSHIP
The work sat between engineering, product, marketing and partners including Atlassian, GitHub and Microsoft. We built partner and marketplace requirements in from discovery.
3 apps
Atlassian, GitHub and Bitbucket
~11 months
for all three
0
personal or issue data collected
DELIVERY
Oct 2025 Bitbucket Cloud
Third app shipped
Jun 2025 GitHub and GitHub Copilot
Cloud and Data Center
Mar 2025 Jira, Confluence and JSM
First app shipped
The order followed business goals and partnerships. Once we had templates, each new app launched quickly. GitLab and Azure were scoped and next when I left.
Eficode Journey: customer reporting from hours to minutes
Engineering Manager, Oct 2022 – Feb 2026
I led the engineering team that built Eficode's customer portal from scratch. It replaced manual SLA reporting with standardized SLA and billing reports for every customer, and opened the way for a new Advisory & Support product line.
Hours → minutes
monthly reporting per customer
50–60%
of customer organizations active monthly
THE SITUATION
SLA reporting was manual, inconsistent and error-prone, and billing periods were stressful for service managers. The goal was to build customer trust and put everything we shared with customers in one place.
ENGINEERING
We built Journey with CI/CD and released many times a day. The biggest technical step was the April 2025 backend rebuild: each part runs as an independent service, so one failure does not take down the rest, 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.
~3,600 h
a year of service-manager time freed
DELIVERY
Nov 2025 Lens
Trends over time, showing whether a change such as adopting Copilot was taking hold
Apr 2025 Recommendations
Standardized, automated advisor recommendations with impact and effort estimates
Dec 2024 Tooling Advanced Metrics
Tool adoption and usage data, growing as each app shipped
Jun 2024 Main Dashboard
A landing page that guided users to the actions they need
Sep 2023 Billing view
Standardized billing reports with monthly and yearly views
Spring 2023 SLA reports & System status views
Two-click SLA reports and a live tool and system status page
CONTACT
Let's talk about your engineering organization.
Engineering leadership, delivery, or the operating model behind both: I'm happy to talk.