Skip to content

4.0 - OPERATIONS

Description

Operations manages the end-to-end client lifecycle, from seamless onboarding to the technical delivery of diagnostic insights and business intelligence. It bridges the gap between high-level strategy and daily execution by implementing robust Operating Models and providing ongoing systemic support. This function is rooted in the "Engineering the discipline to perform" philosophy.

Objectives

  • Standardize Onboarding: Ensure a professional, "Respectfully Bold" first impression that aligns clients with GoThrive Digital's high-governance standards (POPIA/ISO27001).
  • Accelerate Insight: Deploy the Pulse! assessment tool to deliver fast, data-driven diagnostics that bypass traditional "consulting fluff."
  • Architect Scalability: Design and implement short, focused Operating Models (using EOS, Scaling Up, or OKR frameworks) that allow clients to achieve sustainable scale.
  • Enable Visibility: Build automated Scorecards and Dashboards using BI tools (Metabase, PowerBI) to provide leaders with real-time "systemic clarity."
  • Maintain Integrity: Provide a reliable Support Desk to ensure the longevity and accuracy of the systems and AI-integrated workflows (n8n, Google AI) we manage for clients.

Work Products

  • Client Onboarding Kits: Documentation covering compliance, data privacy (POPIA), and engagement governance.
  • Pulse! Diagnostic Reports: Detailed findings and gap analyses derived from proprietary staff questionnaires.
  • Operating Model Blueprints: Custom implementation maps for organizational structure, meeting cadences, and accountability charts.
  • BI Dashboards & Scorecards: Live data visualizations hosted on PostgreSQL, Metabase, or PowerBI environments.
  • Service Level Agreements (SLAs): Defined support structures for the monthly support desk and systems maintenance.

Website Operations (gothrive.co.za)

The corporate website is a Next.js app, git-driven from the gothrive/website-gothrive repo on Gitea. There is no CMS and no CI — a git pull on the host is the deployment.

Deploy loop (standard workflow):

  1. Clone / edit / push — shallow clone https://gitea.jcrx.co.za/gothrive/website-gothrive.git, edit content under content/insights/ (articles) or content/legal/ (legal pages), add images under public/insights/, commit, push to main.
  2. Pull on host — ssh nstcs@192.168.1.130 "cd /home/nstcs/servers/website-gothrive && git pull".
  3. Verify live — curl -s -o /dev/null -w "%{http_code}\n" https://digital.gothrive.co.za/insights/<slug> (expect 200), and confirm the content actually rendered.
  4. Cleanup — after final approval of the changes, delete the local clone (rm -rf) to save space. Never leave clones lying around.

Key facts:

  • Content-only changes (markdown/images) go live instantly — pages are force-dynamic; new articles appear on the homepage carousel, insights index, and sitemap automatically.
  • App-code changes additionally require ssh nstcs@192.168.1.130 "sudo docker restart website-gothrive" (~1–2 min next build).
  • Dependency changes (package.json) require rebuilding the base image (make build-push) and redeploying via Komodo.
  • Git is the source of truth AND the backup — the host checkout is just a mirror of main; nothing lives only in the container.
  • Full detail lives in the repo: docs/RUNBOOK_Content_Updates.md and docs/RUNBOOK_Deploy.md.