Handbook: define PS scoping & SoW process

[robmarcer]

Expands the stub Professional Services handbook page into an actual process, to fix two recurring problems:

1. SoWs being written from second-hand notes (a colleague has the meeting, captures what they think is needed, then hands it off for a SoW).
2. Team members prescribing how something should be built before we understand the full customer need.

What it adds

Three principles governing every PS engagement:

1. Whoever writes and delivers the SoW takes part in scoping it with the customer. No SoWs from second-hand briefs.
2. We agree what the customer needs before we propose how to build it. Solution ideas are welcome but non-binding until scope is agreed; the PS deliverer owns the final design.
3. We do not discuss costing until the SoW content is agreed. Costing follows scope.

Plus a process flow diagram, SoW writing guidance (technical-first, costings last, in-scope only), and the existing knowledge-sharing requirement is preserved.

Opened as a draft for team review/discussion of the wording.

[netlify]

✅ Deploy Preview for flowforge-website ready!

Name	Link
🔨 Latest commit	9eb2b60
🔍 Latest deploy log	https://app.netlify.com/projects/flowforge-website/deploys/6a43bdf18269b1000816a816
😎 Deploy Preview	https://deploy-preview-5264--flowforge-website.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 65 (🔴 down 11 from production) Accessibility: 96 (no change from production) Best Practices: 100 (no change from production) SEO: 91 (no change from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.