Skip to content

Can we measure how our engineers work with AI from history we already have?

Short answer

Yes, if your engineers' AI tools keep local history, which Claude Code, Codex, Cursor and VS Code do. Reading that history gives you a baseline covering weeks that have already happened, without waiting months for new data. Ascenda's 30-day Report is built on this.

Why it matters

Most measurement starts on the day you install it, so the first useful comparison is months away. If you're deciding about an AI rollout now, you need a picture of now and of the weeks before.

How Ascenda helps

The AI Exposure & Work Composition Report runs over 30 days:

  • engineers who consent import their existing AI tool history, through Flow or from the command line
  • it needs a cohort of ten or more and no integration with your systems
  • it ends in a written deliverable covering exposure and work composition, friction and self-reported state, in aggregate

The 90-day Study is the next stage and runs live, which is where declared changes and their readouts come in.

Engagements are priced per engagement and quoted after the setup call.

Next step

Start with a 30-day Report

The Report works from your engineers' imported history for a cohort of ten or more, with no integration, and ends in a written deliverable. The 90-day Study is the next stage and runs live.