Website & Marketing team handoff — safe updating guide

Who this is for: anyone updating the Productive IT website (productiveit.in), the BrandGrowth OS product pages, or marketing copy. Read this once and you'll know what you may edit freely, what needs a second pair of eyes, and what must never be touched without the founder.

The one rule: one VPS hosts several systems side by side — the main website, BrandGrowth OS, and the mail stack (Mailu). Everything is designed so marketing can work without risk to the product, as long as you stay in your lane below.

---

1. The map — what lives where

System	Where it lives	Who edits it
Main website (home, products, about, blog…)	/var/www/productiveit.in on the VPS (static files), config /etc/nginx/sites-enabled/productiveit.in	Marketing/website team (this doc)
BrandGrowth OS (the app)	/opt/brandgrowth-os (Next.js), runs as systemd unit brandgrowth-os, proxied at /products/brandgrowth-os/	Dev only (repo + scripts/deploy.sh)
Mail (Mailu)	Docker stack, domains brandtroveglobal.com (live) / productiveit.in (still Zoho)	Founder
DNS	GoDaddy (ns69/ns70.domaincontrol.com)	Founder

2. Safe to edit freely (marketing lane)

• Anything under /var/www/productiveit.in — homepage copy, product page text, blog posts, images, CSS for the main site.
• Adding BrandGrowth OS mentions, screenshots, campaign banners.
• The main site's navigation menus and footer (including the BrandGrowth OS link — keep pointing at /products/brandgrowth-os).
• Golden rule for the main site: after any edit, reload the homepage and the product page in a private browser window. If it renders and links work, you're safe — static files can't take the app down.

3. Needs a heads-up (post in the team channel first)

• Changes to docs/WEBSITE_HANDOFF.md, docs/HOW_TO_USE.md (user-facing copy truth).
• New pages under /products/ (URL collisions with the app's basePath are the one real hazard — check with dev before adding a path starting with /products/brandgrowth-os).
• Any change to robots.txt, sitemap.xml, or SEO redirects (/etc/nginx/snippets/productiveit-seo-redirects.conf) — worth a dev glance so analytics/SEO stays consistent.
• Replacing BrandGrowth OS screenshots with new-UI captures (we'll happily re-grab them live so they match the current theme).

4. Never touch without the founder (protected list)

• /etc/nginx/sites-enabled/productiveit.in — the location /products/brandgrowth-os/ block proxies the app; a typo here takes the product and possibly the main site offline.
• /opt/brandgrowth-os/** — application code, .env (contains database + SMTP + AI keys), systemd unit.
• Anything Docker (docker, docker compose commands), the Mailu stack, DNS records at GoDaddy, TLS certificates (/etc/letsencrypt).
• Backups: /srv/backups/**, /opt/brandgrowth-os/backups/**, the offsite sync.
• The database directly (plans, feature_flags, users, orgs) — ask dev; there are safe procedures.

5. Updating BrandGrowth OS product-page content (the app's marketing pages)

The app's public pages (landing, pricing, how-it-works, legal) are code in the repo under app/src/app/(marketing)/, so copy edits there are made like code changes:

1. Ask dev (or open a repo change request) with the exact new copy.
2. Dev edits the page, rebuilds, deploys via scripts/deploy.sh — minutes, zero downtime.
3. Pricing prices/limits are the exception: they're database rows, editable on the VPS without a deploy (see the header comment in app/src/app/(marketing)/pricing/page.tsx).

6. Facts you can quote in marketing (verified, as of 2026-09-18)

• URL: https://productiveit.in/products/brandgrowth-os — signups open.
• Auth: email+password with verification, Google / GitHub / Microsoft sign-in, 2FA with recovery codes.
• Engines: Visibility Radar, BrandMatch, Sponsorship Intelligence, Partnership ROI, Opportunity Engine, Action Plan, weekly intelligence email, AI assistant.
• Pricing: Free / Pro ₹999/mo / Business ₹2,999/mo / Enterprise custom; pay by direct UPI/bank to info@productiveit.in (online checkout coming later).
• Email sender: noreply@brandtroveglobal.com (SPF/DKIM aligned, DMARC monitored) — deliverability is verified end-to-end; don't quote inbox-placement guarantees beyond that.
• Backups: daily encrypted-at-rest dumps + continuous WAL, offsite copy off-box.
• Don't claim: "AI-powered global celebrity database with prices" — the engines are evidence-first; influencer pricing is an estimate tier, not verified rates.

7. When something looks broken

Symptom	Likely cause	Action
Main site fine, app 502/timeout	app server down	ping dev; check systemctl status brandgrowth-os (founder)
App fine, a main-site page 404	file/URL mismatch	check filename + nginx try_files behavior; static issue only
Both down	nginx/host issue	call the founder immediately
Forms say "couldn't reach the service"	app unreachable OR user's network	retry, then check healthz URL; report to dev with timestamp

Fast triage for everyone: https://productiveit.in/products/brandgrowth-os/api/v1/healthz → {"status":"ok"} means the product is up; the problem is elsewhere.

8. Contact matrix

Area	Owner
Product/app dev, deploys, database	Dev (Codebuff sessions)
Domain, DNS, mail, payments, VPS billing	Founder (Upasana)
Main-site content, campaigns, social	Marketing/website team
Security incidents	Founder immediately → then dev