Digital consulting from a freelancer that stays concrete

Most digital projects don't fail because of missing technology, they fail because of missing clarity. There are too many tools, too many opinions, too many half-finished construction sites. Good consulting clears exactly that up: listen first, then check, then propose a path that fits your team and your budget.

Digital consulting from a freelancer is the compact version of that. No deck from a sales team, no junior doing the actual work. One point of contact who writes the audit, strategy, and roadmap themselves and then, optionally, implements it too. That reduces friction, lowers cost, and raises the odds that something useful comes out at the end.

When digital consulting actually helps

Consulting pays off whenever a decision is coming up and nobody on the team has the time or the distance to prepare it properly. That happens more often than it feels like.

Typical triggers: a relaunch is coming and nobody knows whether the current CMS should stay. Traffic is dropping and the analytics numbers contradict each other. A new product needs a landing page, but the positioning isn't clear. Or an internal tool needs to get built, and nobody can say whether buying, renting, or having it custom-built is the right answer.

In all of these cases, moving straight to implementation without prior consulting usually leads to double work. An audit costs a fraction of what a poorly set-up project generates in rework. A typical, illustrative example: a mid-sized company invests 25,000 euros in a new website, realizes after six months that it's targeting the wrong audience, and starts over. A prior strategy audit would have cost 2,500 euros in this scenario.

Consulting also makes sense when you already have an idea but need a second pair of eyes. Sparring is often more valuable than a full strategy, because it sharpens your existing thinking instead of replacing it.

What a serious audit actually checks

An audit isn't a checklist you run through top to bottom, it's a targeted investigation of where your project creates friction. The scope depends on the goal, but four levels come up almost every time.

First, the technical level: load time, Core Web Vitals, hosting, CMS configuration, security, mobile rendering. This is where you can often save 20 to 40 percent load time once images, caching, and scripts are configured properly.

Second, the content level: is the page structure logical, does the copy speak to the right audience, do the conversion paths actually lead to an action? Many websites have strong homepages and weak subpages because nobody took the time to cluster user questions properly.

Third, the data level: are analytics and cookie consent set up correctly, are goals being measured, does anyone in-house know what the numbers mean? In many projects it turns out Google Analytics is running, but nobody knows which events actually matter.

Fourth, depending on the engagement, the process level: how does content get into the CMS, how do changes get approved, where do AI-driven automations make sense? An audit can also reveal that the real problem isn't the website at all, but the workflow behind it.

The result is a document with findings, prioritized recommendations, and an effort estimate. Not an 80-page PDF, but 15 to 25 pages you can read in an hour.

The process: from first contact to roadmap

The process is kept deliberately lean, because consulting otherwise eats up more time in project management than in the actual work. How fast it runs depends almost entirely on how quickly access and answers come in, not on the work itself.

First there's a short introductory call, 20 to 30 minutes, free. It's about checking whether the topic fits and whether the chemistry works. If it does, a 60 to 90 minute kickoff follows, where goals, context, and constraints get clarified. You share access to analytics, CMS, and hosting, plus the most important internal documents.

Then comes the actual analysis phase, during which the systems get checked and the content gets reviewed. In between, there are usually two or three short follow-up questions, so no wrong assumptions end up in the result.

The roadmap comes at the end. It contains prioritized actions for the next 30, 60, and 90 days, each with an effort estimate and expected impact. Not a wish list, but a list that clearly states what's mandatory and what's optional. A 60-minute results meeting closes out the process, where everything gets discussed and open questions get resolved.

If you want implementation afterward, I can take that on. If not, you have a document your team or another provider can pick up and keep building on.

What consulting with a freelancer costs

The price for digital consulting varies a lot, because scope and experience differ enormously. Realistically, serious freelance consulting runs between 120 and 180 euros per hour or 900 to 1,400 euros per day. Anything below that is usually either beginner work or a loss-leader offer with upselling attached.

Concrete numbers: a 90-minute sparring session runs 200 to 300 euros. A compact audit with a roadmap for a small to mid-sized website starts at 1,200 euros and goes up to around 3,000 euros. A more comprehensive strategy project with workshops, user interviews, and a technical audit runs between 4,500 and 9,000 euros. For ongoing consulting as a retainer, 1,500 to 3,500 euros per month is common, usually with 8 to 15 hours of use.

With a freelancer, agency overhead disappears, so you get more actual working time for the same money. The downside is there's no parallel resource: if I'm out for two weeks, your project slips. For most consulting projects that's not an issue, because the results aren't under time pressure anyway. If they are, that should get discussed upfront. Details on effort and pricing are in the price comparison, which also covers the consulting share of projects.

How to prepare for consulting

The clearer the context, the better the result. An hour of prep on your side often saves half a day in the audit and makes the recommendations more concrete. It doesn't need to be polished documents, bullet points are often enough.

Useful things to bring: a short description of the company and target audience, the three most pressing questions, current numbers (traffic, revenue, conversion, whatever's relevant), a list of the tools in use, and, if you have them, earlier analyses or proposals. A sentence on what hasn't worked in the past also helps, because it keeps old mistakes from repeating in the roadmap.

Access is the second point. For a technical audit, I need at least read access to analytics, Google Search Console, the CMS, and, if possible, hosting. For protected systems, screenshots or a short screen-sharing session are often enough. Everything goes through encrypted password sharing, and access gets revoked once the project ends.

The third point is time. Plan for 3 to 5 hours on your side, spread across the project: kickoff, follow-up questions, results meeting. If you or a decision-maker aren't reachable during the process, everything slips. Consulting is a dialogue, not a task you drop off and pick up later.

If you want to move straight into implementation after the consulting, say so early. Then the roadmap can be written to flow directly into an implementation proposal, for example for a website relaunch or a new landing page.