Google Workspace consultant

Workspace is easy to run badly and hard to run well, because almost every important control is a default that someone has to deliberately change. A consultant should explain which defaults and interactions matter for your requirements, then provide evidence and a maintainable change plan.

The engagements that produce most value are unglamorous: org unit structure that matches how the business actually works, licence tiers assigned by role rather than uniformly, a documented admin model with named deputies, and a security baseline that someone internal can maintain without calling us every month.

Most organisations buy one tier for everyone because it is administratively simple. It is also, for anything above about thirty seats, usually the most expensive option available. Frontline and archived user licences exist precisely so that not everyone needs a full knowledge-worker seat.

The exercise is straightforward: list every user, classify by what they genuinely need, and model the cost at the correct tier mix. The scope and potential saving depend on the actual bill, eligibility, retention needs and licence terms. Confirm any proposed reduction before treating it as a saving.

Being a reseller and being an adviser are in tension. A reseller earns on licence volume, which creates an incentive to recommend more seats at higher tiers. We handle licensing where clients want a single relationship, but the advisory work is billed by the day so the recommendation is not funded by the outcome.

In practice that means we will tell you when the answer is fewer licences, when a Google product is not the right tool, and when the honest recommendation is to change nothing and spend the budget on training instead.

Every engagement ends with an admin runbook written for the person who will actually do the job, and a recorded training session with your internal administrators. The runbook covers routine tasks, the escalation path, and the decisions we made with the reasoning behind them.

The decision log matters more than it sounds. In eighteen months, somebody will ask why external sharing is configured the way it is, and the difference between a documented decision and an undocumented one is the difference between a five-minute answer and a fortnight of re-litigation.

A useful consultancy proposal should identify the administrative problem, permissions needed, decisions you retain, and the outputs your internal team can use without the consultant. Ask for a tenant baseline, risk-ranked recommendations, a change log and an administrator handover, with licence savings or security improvements treated as hypotheses until measured.

Separate a fixed-scope configuration review from ongoing support. Confirm whether the quoted work includes implementation, a post-change test, administrator training and a follow-up period; otherwise two similar day-rate proposals may describe very different deliveries.

A tenant review should identify decisions and evidence, not assume permission to change the tenant. Ask whether implementation, rollback tests, administrator training and follow-up are included. Require a decision log separating accepted recommendations from deferred risks.

For a short engagement, provide your user count, edition, current admin structure and the specific decision that is blocked. Agree a least-privilege access plan; checks not observable with that access should be customer-run or reported as limitations. Licensing savings remain an estimate until the bill and eligibility are checked.