Engagements
How we work with application owners
Adoption analytics for internal business applications only holds if fieldwork respects how people actually close months, fulfil orders, and hand off artefacts. This page describes the rhythm we use.
1. Scope without inventing systems
We name one cloud suite and a bounded list of internal applications. If the inventory is unclear, the first workshop is the inventory — not a premature heatmap.
2. Evidence before colour
Cells earn colour from interviews, usage exports you already hold, or observed workflows. Sparse evidence stays labelled as sparse so leadership does not over-read the chart.
3. Briefing that names owners
Recommendations point to artefact owners and calendar moments (closing week, peak season) rather than abstract capability gaps.
What we ask of your side
- A sponsor who can open doors to application owners
- Lawful access to licence and usage exports you already produce
- Honest attendance at the readiness or findings session
- Clarity on whether we may observe live workflows on site
Where we meet
Remote interviews are standard. On-site days in the Gyeonggi / Seoul corridor are available when observation matters — for example closing rehearsals or warehouse fulfilment desks that feed an internal application.
- Short fit call — suite, application count, timing constraints
- Proposal with fee basis and interview volume
- Kick-off and inventory workshop
- Fieldwork window with scheduled owner sessions
- Synthesis, draft review with sponsor, leadership briefing
- Optional quarterly pulse against the same baseline