Metawork.Studio — MetaBot

Metawork.Studio · MetaBot

MetaBot is the web product at metawork.studio/bot — a Pipedrive setup and configuration assistant. It runs the onboarding interview, walks visitors through setup and design decisions, and drives the methodology that makes Pipedrive actually work for clients (pipelines, custom fields, automations, lead-capture, post-sales handoff).

MetaBot is the web product at metawork.studio/bot — a Pipedrive setup and configuration assistant. It runs the onboarding interview, walks visitors through setup and design decisions, and drives the methodology that makes Pipedrive actually work for clients (pipelines, custom fields, automations, lead-capture, post-sales handoff).

It is the conceptual layer: workflows, decision paths, the safety envelope, the Pipedrive-vs-HubSpot rubric, the Make boundary, the affiliate flow, and the handoff CTAs to Nikolai and the team.

For Pipedrive API operations, MetaBot calls MetaPipe — a separate MCP that exposes safe Pipedrive tools (read + safe writes, no DELETE). MetaPipe is built and maintained independently (see Projects/Metawork.Studio/MetaPipe).

┌──────────────────────────────────────────────┐
│ MetaBot (web product)                        │
│ • metawork.studio/bot                        │
│ • Onboarding interview (7 questions)         │
│ • Setup + design workflows                   │
│ • Pipedrive vs HubSpot decision rubric       │
│ • Safety envelope (4-bucket model)           │
│ • Make/Zapier boundary rules                 │
│ • Affiliate links + MWS handoff CTAs         │
└─────────────────┬────────────────────────────┘
                  │ uses tools from
                  ▼
┌──────────────────────────────────────────────┐
│ MetaPipe (MCP)                               │
│ • Pipedrive read tools (deals/persons/orgs/…)│
│ • Pipedrive safe writes                      │
│ • help_delete_* (returns instructions, never │
│   calls DELETE)                              │
│ • Internal-test first, customer-facing later │
└──────────────────────────────────────────────┘

Where things live

Area	Repo / Path
MetaBot specs (canonical)	`gitlab.com/metawork/metabot` → `docs/`
MetaBot website (Next.js, planned)	`gitlab.com/metawork/metabot` → `web/` (not started)
Sold-skill draft (paused, see handoff below)	`gitlab.com/metawork/metabot` → `skill/`
MetaPipe MCP	separate repo (built in parallel)
License server (parked)	`gitlab.com/metawork/mws-license-server`

Current state (2026-05-08)

M1 specs: ✅ all locked — safety envelope, stuck-moment taxonomy, Make boundary, anti-extraction policy, onboarding interview
M2 sold skill: 🅿️ deferred. The skill draft (skill/SKILL.md) is in repo; the licensing layer is paused — see _handoffs/2026-05-08-metabot-licensing-paused.md for full state and resume steps
M3 web bot: ⏳ not started. This is the active priority once MetaPipe is testable
M4 stuck detection + lead capture: ⏳ depends on M3
M5 Make handoff: ⏳ depends on M3
M6 launch: ⏳ depends on M3-M5

Reading order

gitlab.com/metawork/metabot → docs/handoff.md — full project state
docs/two-variants.md — needs revisiting given the MetaBot/MetaPipe pivot, but still the right entry point for the architectural frame
docs/billing-and-licensing.md — pricing + license decisions (paused, resume later)
docs/safety-envelope-matrix.md — the 4-bucket operation model (Allow / Confirm / Blueprint-only / Block)
docs/onboarding-interview.md — the 7-question intake
docs/stuck-moment-taxonomy.md — when to hand off to Nikolai
docs/make-boundary-rules.md — cross-system automation handoff

Non-negotiables (apply to every session on MetaBot or MetaPipe)

v2 Pipedrive API preferred, v1 only when v2 doesn't cover
Always include won + lost deals in deal queries — never status=open only
Count before/after every bulk operation — non-negotiable, has prevented real data loss
Never delete a stage without moving deals first (this is a Block-bucket op for the bot)
Label updates require fetch-first-merge — raw PATCH on label_ids is the overwrite trap
Always "Metawork Studio" in full (never bare "Metawork")
"Nikolai and the team" for handoff language
Pipedrive Premier Partner, HubSpot Solutions Partner, Make Partner — credentials worth naming when relevant