DevTools Connect
Colleagues collaborating across a long table with notebooks and laptops

DevTools Connect

Application analytics that respects how engineers actually open tools, abandon them, and work around them.

We audit developer tool usage inside engineering platforms—interviews, telemetry reading, and decision briefs for teams tired of dashboards that argue with the floor.

Request a usage audit See how engagements run

Flagship engagement

Developer Tool Usage Audit

For engineering managers and platform leads who need evidence before consolidating licenses, funding an internal plugin, or rewriting onboarding. We map claimed habits against the events your platform already emits.

Workshop discussion with sticky notes on a glass wall

Three to five weeks · fixed-scope quote

What you receive

A friction map across IDEs, CI, issue trackers, and internal utilities; interview notes that explain the odd spikes; and a brief leadership can use in the next budget conversation—not another vanity dashboard.

Preparation is light: a sponsor, read-only analytics access, and introductions to a cross-section of engineers.

Audit details

Related work

Other engagements

Supporting work that pairs with an audit or stands alone when the question is narrower.

“They caught that our ‘high adoption’ CI template was mostly wrapper jobs. The brief made the consolidation vote less political—even if it meant we kept a tool I personally disliked.”
Hyejin Park · Platform lead, multi-product engineering org

Field Notes

Recent writing

All field notes

Planning a tooling decision this quarter?

Tell us which platforms are in scope and what the audit or briefing needs to unlock. We typically reply within two business days.

Start a conversation