Frequently Asked Questions
-
I’m open to discussing anything. I work on short-term assignments (a few days to a few weeks, e.g. a data quality audit or survey design) and longer embedded roles spanning several months, sometimes running alongside other clients. If you're not sure which fits your need, get in touch.
-
Responsive, friendly, and easy to reach. I put real weight on clear communication throughout a project, flagging issues as soon as they come up rather than letting them surface for the first time at a deadline, and I treat agreed timelines as commitments. Beyond the technical work, a good working relationship matters to me, I'd rather build something collaborative than just deliver a report and disappear.
-
My expertise is in the method, not the topic. Most of my work has been in health and migration, but I've also worked across education, agriculture, private sector development, entrepreneurship, digital solutions, and governance. If your work involves quantitative data and needs rigorous handling, that's the fit, regardless of sector.
-
Usually starts with a short call to understand what you need and whether I'm the right fit, followed by a scope and proposal if it makes sense to move forward.
-
Yes, this is a large part of what I do. Inheriting datasets, tools, or codebases built by someone else and making them usable (or catching what's wrong with them) is a specific strength, not just something I tolerate.
-
Yes, happy to work within whatever confidentiality or data protection requirements your organisation needs, including signing NDAs where required.
-
Both, depending on the project. Clearly scoped pieces of work (a survey design, a data quality review) are often a better fit for a fixed fee. Longer or more open-ended engagements typically run on a day rate.
-
You can get a decent looking survey or piece of analysis out of AI in minutes. What's harder to get is confidence that it's actually right, and for the kind of decisions this data usually feeds into, funding, policy, programme design, that confidence is the whole point. It comes from having done this enough times to know what good looks like, not from generating a first draft. I use AI myself, it's a genuine part of how I work, but the judgement about what to trust, what to check, and what a result actually means in context is what you're hiring, not just an output.