package/gcp-onboarding-workshops
GCP Onboarding Workshops
Two days on your architecture, with your project names on the slides and a sandbox your engineers can break.
~$8,000 per two-day cohort
Starts with Discovery & Scoping
Floors reflect typical engagements. Larger, regulated, or multi-region estates are scoped and quoted after Discovery.
Where this usually starts
You migrated, or you built something new, and now a team of fifteen engineers owns infrastructure they did not design. They can follow a runbook. They cannot yet tell you why the runbook says what it says, which means they cannot tell when it is wrong.
The default answer is to buy seats on a public course. That works for individual certification and it does not work for team onboarding, because a public course teaches a generic reference architecture and your engineers spend the whole two days silently translating. The examples use project names they have never seen. The network diagram is not their network diagram. Whatever transfers has to survive that translation, and most of it does not.
The second default is to have your own senior engineer run a session. That is often better, and it costs you a fortnight of the one person whose time you can least afford, produces material nobody maintains, and skips whatever that engineer already assumes is obvious.
How this differs from a public course
The material is written against your estate. Before delivery, the architecture is read the same way a review would read it — org structure, network, identity model, the workloads that matter — and the walkthroughs are rebuilt around what is actually there. Engineers see their own project names, their own VPC layout, and the specific decisions their organization made, along with the reasoning behind those decisions.
That preparation is the reason the price is what it is. The two delivered days are the visible part; the architecture read and lab build sit underneath them.
Tracks
- Foundations. Resource hierarchy, projects and folders, IAM and service accounts, billing structure, org policy, and how to read what already exists in your organization without breaking it.
- GKE. Cluster and node pool architecture, workload identity, autoscaling behaviour under real load, resource requests and limits, and debugging a pod that will not schedule.
- Networking. VPC design, Shared VPC, peering and routing, private access to Google APIs, load balancing, and hybrid connectivity if you have Interconnect or HA VPN in place.
- Security. IAM depth, VPC Service Controls, Secret Manager and KMS, Workload Identity Federation, and how to read Security Command Center findings without drowning in them.
Labs
A sandbox project is provisioned for the cohort before day one and stays live for a period after delivery, so people can go back and finish what they were in the middle of. Labs are hands-on and run against real Google Cloud resources, not a simulator.
Cohorts work best between eight and twenty people. Below eight, the discussion thins out. Above twenty, the hands-on portion stops being hands-on and the session becomes a lecture.
What this is not
Sumech Technologies is not a Google Cloud Authorized Training Partner and does not deliver Google’s official curriculum. This workshop is Sumech’s own material: own slides, own architecture walkthroughs, own lab exercises. It does not use Google’s course names and it is not a substitute for the official catalogue.
Google Cloud Skills Boost content is Google’s, and Skills Boost licensing is not included or resold here. If you want the official catalogue alongside this workshop, you purchase Skills Boost credits directly from Google. That is usually the right combination — official curriculum for breadth and certification paths, this workshop for the specifics of your own estate.
Certification training is likewise out of scope. The material overlaps with certification content because the underlying platform is the same, but the workshop is built for people who need to operate your architecture, not pass an exam.
How the engagement runs
- Week 0 Discovery & Scoping Track selection, cohort size, and a read of the architecture the material will be built against. Produces the fixed quote.
- Week 1–2 Material build Slides and walkthroughs rewritten against your estate. Sandbox project provisioned and labs built and tested end to end.
- Delivery Two consecutive days Remote or on-site. Roughly half instruction, half hands-on. On-site attendance is quoted separately from the workshop fee.
- After Sandbox stays live Cohort keeps access to the sandbox for a defined window to finish labs. Slides and lab guides are yours to keep and reuse internally.
These figures are starting points, not quotes. Final pricing depends on the size and complexity of your estate and is fixed in writing at the end of Discovery & Scoping.
What this engagement does not cover
Named here rather than discovered later. This is the list that makes the fixed price hold when scope starts moving.
- Skills Boost licensing
- official Google certification training
- ongoing enablement
What this is based on
- Material written by an engineer holding seven Google Cloud certifications, five at Professional tier, plus HashiCorp Terraform Associate.
- Architecture walkthroughs drawn from landing zones and migrations delivered in production, not from reference diagrams.
- Networking and security tracks backed by Professional Network Engineer and Professional Security Engineer certification.
What buyers ask
Is this official Google Cloud training?
No. Sumech Technologies is not a Google Cloud Authorized Training Partner. This is Sumech’s own workshop — own slides, own labs, own architecture walkthroughs — and it does not deliver Google’s official curriculum or use Google’s course names.
If your team also needs the official catalogue, you buy Skills Boost credits directly from Google. Those credits are not resold or bundled here.
Will this prepare our engineers for certification?
Not directly, and it is not sold as exam preparation. The subject matter overlaps, because both cover the same platform. But the workshop is organized around operating your architecture, and certification exams are organized around a syllabus. People who want to certify should work the official material as well.
Remote or on-site?
Both work. Remote delivery is the default and the labs are built for it. On-site is available where the team benefits from being in one room, and travel is quoted separately from the workshop fee rather than folded into it.
What size cohort works?
Eight to twenty. Below eight the discussion gets thin and you are paying cohort price for a small group. Above twenty the hands-on portion degrades into a lecture with an audience. Larger teams are better served by two cohorts than one oversized one, and the second cohort costs less because the material is already built.
Questions about pricing, terms, and ownership across every engagement are on the FAQ.
Start with Discovery & Scoping
$4,500 fixed, 3–5 days. A current-state review, a gap analysis, a written scope, and a fixed quote for this engagement. Half the fee is credited against the work if you proceed within 60 days.