Frequently Asked Questions

What types of organisations do you work with?

I work with European organisations and businesses of all kinds: companies that care about where their data goes, how their subscription fees circulate, and whether their technology choices align with their values. I have particular experience with social enterprises and B corps, but I also work with SMEs, nonprofits, cooperatives, and mission-driven organisations. If any of that sounds like you, we'll likely be a good fit.

What does a typical engagement look like?

Every project is different, but most fall into a few patterns: software selection (helping you choose a CRM, project management tool, email, or other platform), vendor assessment (checking whether a tool actually does what it claims, making sure a web developer will build what you actually need), migration planning (figuring out how to leave your current system), or technical translation (helping you communicate with developers and agencies). Some clients need a one-off consultation; others want ongoing support.

How much do you charge?

I price based on the scope and complexity of the work. For a straightforward software recommendation, that might be a fixed fee. For longer advisory relationships, I work on a retainer. I'm happy to discuss your situation and give you a clear idea of costs before we commit to anything.

Do you implement the software yourself?

Generally, despite having experience doing this, no. My role is to help you make the decision and plan the transition. Not to become your IT department. I'll stay involved during implementation if that's useful, but the goal is to leave you with clarity and confidence, not dependency on me.

What is data sovereignty?

Data sovereignty means having control over where your data is stored, who can access it, and what legal jurisdiction applies to it. For European organisations, this often means understanding whether your data is truly protected by EU law or whether it's actually subject to US (or other) surveillance laws because of where the servers are or who owns the company.

Do I need to stop using American software?

Not necessarily. The goal isn't ideological, it's informed decision-making. Sometimes an American tool is genuinely the best option, and the data risks are acceptable for your situation. Sometimes a European alternative exists that you simply didn't know about. Sometimes an open source solution exists that meets your needs. The point is to choose knowingly, rather than discovering the implications three years later when you need to migrate.

What does “GDPR-compliant” actually mean?

Less than you might hope. Many vendors claim GDPR compliance without explaining what that means in practice. It might mean they have a data processing agreement ready to sign. It might mean their servers are in the EU. It might mean almost nothing. I help you read the fine print and understand what you're actually agreeing to.

Are European cloud services really more private?

Sometimes yes, sometimes no. Some “European cloud” offerings are genuinely European-owned and operated under EU law. Others are European subsidiaries of American companies, still subject to laws like the CLOUD Act. Some use European data centres but route support tickets through US teams. The details matter, and I help you find them.

Can you act as our Data Protection Officer?

No. I'm not a DPO and I don't provide legal advice. My role is to help you understand the practical implications of your technology choices: where data actually lives, what vendors' claims really mean, and what questions you should be asking.

If your situation requires formal legal guidance, data protection impact assessments, or DPO services, I'll tell you. I'm happy to work alongside your legal team or recommend someone with the proper credentials. What I won't do is offer expertise I don't have.

How do you evaluate whether a tool is right for us?

I spend real time with the software – days or weeks, not a half-hour demo. I read the documentation, test the edge cases, contact the support team, and try to break things. I also spend time understanding your team's actual workflows, because the best tool on paper isn't always the best tool for how you work.

What is vendor lock-in and why does it matter?

Vendor lock-in happens when switching away from a tool becomes so expensive or difficult that you're effectively trapped. This can happen through data formats that don't export cleanly, integrations that only work with that vendor's ecosystem, or contracts that make leaving painful. I help you spot lock-in risks before you commit.

How do I know if I can actually leave a platform?

Key questions to ask: What format does the data export to? Is it a standard format other tools can import? Does the export include your full history, or just current records? Are there API limits that make bulk extraction slow or expensive? I test these things before recommending a tool.

What happens in an initial conversation?

We talk about what you're trying to achieve, what's working, what isn't, and what's worrying you. I ask questions – probably more than you expect. By the end, we'll both have a clearer sense of whether I can help and what that might involve. There's no obligation, and I won't try to sell you something you don't need.

How long does a software selection project take?

Typically two to six weeks, depending on how many options we're evaluating and how complex your requirements are. Some decisions are straightforward; others need more investigation. I'd rather take the time to get it right than rush you into a choice you'll regret.

What if I just need a quick sanity check?

That's fine too. If you're reviewing a vendor proposal and something feels off, or you want a second opinion before signing a contract, a single conversation might be all you need. Not everything has to be a full engagement.

What is this “ritual mimicry” in technology decisions you talk about?

Ritual mimicry is my term for going through the motions of choosing without actually choosing. It's what happens when you “go with the flow”: adopt whatever the vendor suggested, what was already there, or pick the tool that everyone else seems to use – without ever stopping to ask whether it's actually the right one for you.

Why do organisations fall into ritual mimicry?

Because software decisions feel technical, urgent, and low-stakes in the moment. You've got real work to do, and the tool seems fine. It's only later, when you're trying to migrate, or when a data breach happens, or when you realise your subscription fees are adding up or funding something you disagree with, that the hidden costs become visible.

How do I break out of ritual mimicry?

Start by asking questions you might have skipped: Is this really what I need or just what I think I need? What happens if I need to leave? What am I really agreeing to? etc. You don't need to become a technology expert, you just need someone willing to look past the marketing and check the details. That's what I do.