Domain expertise for impact data and reporting software

Organisations we work with

What you get

• Practitioner reality in your roadmap

  Jeroen’s experience with 120+ organisations shows how impact data is really collected, used and reported. That helps you check your assumptions against how practitioners work, before you build.

• Frameworks mapped correctly

  IRIS+, GRI, ESRS datapoints, VSME and the SDGs: we review how your data model and indicator library line up with the standards your users report against.

Why we do what we do

Read the film as text

1. We all want to know
2. our place in the world.
3. Thin grey lines join dots into a web.
4. We like to believe that what we do is part of something larger.
5. It is.
6. Together we make our surroundings, our brands, our communities.
7. We shape the work of others, as they shape ours.
8. The web grows dense.
9. We live in one web of cause and consequence.
10. Each path tells a story, part of a larger narrative.
11. A system of meaning.
12. So what is our impact?
13. Whose lives do we touch?
14. What changed? For whom? How much? And what part was ours?
15. Intended or not, for better or worse.
16. Knowing that changes what you do next.
17. A dark line draws a path through the web. Impact management helps you see it, steer it, and use it.
18. A large word: Lead. A purple path runs through the web. Lead with purpose, and fund your mission.
19. A large word: Improve. A green path runs through the web. Learn what doesn’t work and design for better.
20. A large word: Engage. A blue-green path runs through the web. Share your story, and bring others into it.
21. A large word: Account. A blue path runs through the web. State your claim, and prove it.
22. A large word: Discover. A yellow path runs through the web. Find your next impact before it happens.
23. “How do you measure impact?”
24. It sounds hard.
25. It isn’t.
26. It’s not about the how.
27. It’s about
28. Portraits of people fill the screen.
29. A large word: Who.
30. About rights-holders, whose lives are touched.
31. And stakeholders, whose choices shape them.
32. The people stand side by side, at the same height. A wave of colour runs through the web. Every voice, every perspective, equally weighed.
33. The web turns many colours. Pluriform and equivalent.
34. Who determines what.
35. And what determines how.
36. That’s it. No more, no less.
37. We count what can be counted, and listen to the rest.
38. Coloured paths wind across the web. We find the stories that connect the dots, and make sense of the whole.
39. We love our craft:
40. to ask the questions,
41. to measure what matters,
42. and narrate what works.
43. One dark path remains. Let’s reveal your path.
44. The word narrate, with the line: impact in numbers and stories.

What we often hear

• “Our features are strong, but customers hardly use them.”

  We map practitioners’ workflows and pain points with you, so you design around their reality rather than ideal scenarios.

• “Our data model doesn’t fit how IRIS+, GRI and ESRS are built.”

  We review your impact data model and indicator mapping against IRIS+, GRI and ESRS, and flag gaps and ambiguities before customers find them.

• “Prospects ask whether our tool ‘does CSRD’. Sales and product each give a different answer.”

  We check which ESRS and VSME datapoints your product really covers and where it falls short, so sales and product give prospects the same answer.

• “I don’t know which features impact managers really need.”

  We help you validate your roadmap with customers: which questions they need answered, for whom and how often, so you prioritise what drives use.

What you may be wondering

• Aren’t you a competitor to my product?

  No. We look at the content of your product, not at your customers. What we make together stays yours.

• Do you know enough about software?

  We review the impact side: the data model, the indicators and the workflows. The technology stays with your team.

• Do I need to have everything reviewed straight away?

  No. Start with one question, for example which ESRS or VSME datapoints your product really covers.

To read

• Collecting data without drowning in it

  Collect only what you use, and ask less of the people it is about.