Line: Services¶
Enterprise analog: Consulting / professional services firm.
Covers: Freelance and client engagements.
Tracking: Notion Workstreams database — view: Services Work. Gatekeeper: Engagement Manager. See agent setup.
Primary archetype: services-product. Services may add a Software workstream when software is required to deliver the engagement. A distinct market opportunity creates a related Product Initiative through Portfolio.
Workflow¶
Offer → Lead → Propose → Contract → Deliver → Invoice → Complete → Archive
Lead micro-status inventory: cold → contacted → proposed → negotiating → won | lost | rejected
| Stage | Inventories |
|---|---|
| Offer | catalog SKU, rate card (catalog is an Offer binding, not a separate stage) |
| Lead | lead-status |
| Propose | proposal template |
| Contract | engagement terms |
| Deliver | engagement-type; privacy profile; optional Software handoff |
| Invoice | rate / fixed fee |
| Complete | close-out evidence; retrospective work occurs within Complete |
| Archive | disposition of the engagement workstream |
The stage order is decided, but exact entry criteria, exit evidence, allowed transitions, and reopen behavior are not yet complete for every stage. Until those contracts exist in the corpus, Conductor must emit a gap rather than authorize a deterministic transition.
Catalog examples (Workspace)¶
From 03 - Business Pipelines/services/1-offers/catalog.md:
- AI tool evaluation & comparison (€500–2k/report)
- Custom AI solution advisory (€100–150/hr)
- Market research — AI landscape (€2–5k)
- Software development — AI agents / web apps (project; routes via Portfolio to Software with engagement binding)
Roles¶
Practice Lead, BD/Sales, Engagement Manager, Delivery Consultant, Billing.
Cross-line coordination¶
- In: Portfolio adds a Services workstream for an engagement Initiative.
- Billable software: Add a Software workstream with engagement, privacy, client-brand, and deliverable bindings. Both workstreams may remain active.
- Supporting internal app: Add a Software workstream on the same Initiative when the app exists only to enable delivery or analysis.
- Market opportunity: Create a separate Product Initiative linked with
derived_from; do not relabel the engagement as a product bet. - Craft showcase: Add a separate public Software workstream only with explicit client and privacy approval.
Tooling: Client artifacts remain in privacy-local client folders. Notion owns the Initiative and workstream state and stores only privacy-safe links and summaries. Software production occurs in the appropriate repository; a GitHub issue is optional. See tooling-map.md.