← Back to Documentation Technical Documentation

Base Plan vs. Custom Plan: When Each One Makes Sense

Zero Bloat: the modular deployment principle

RevSign OS deploys in layers, not as a closed package. The Base Plan solves the asynchronous infrastructure —capture, scoring, validation and signal routing into the tools the team already uses— without asking the client to learn a new interface. The jump to the Custom Plan doesn’t rebuild anything: the database and the agent logic stay intact, a layer of visual control and deep integration gets added on top.

Comparison

Base Plan vs. Custom Plan
Dimension Base Plan Custom Plan
Stack Supabase (RLS) + Claude Cowork multi-agent + Vercel Edge Functions + Sendable + GitHub Everything in Base + Next.js/Tailwind + Supabase Auth/Realtime + MCP servers
User surface None new: the team stays in their CRM/email Unified dashboard (Command Center)
Who operates it The system, in the background; alerts via Sendable The team, from the dashboard, with real-time data
Change latency Logic changes via GitHub, no UI to update Logic changes + interface changes
Extensibility Via Edge Functions and the data layer Via MCP servers into legacy systems/ERPs
Technical team requirement Low: no in-house interface to maintain Medium: there’s an in-house frontend in production

Decision criteria

  • If the team already lives inside a CRM and just needs that CRM to receive better signals, the Base Plan solves the whole problem.
  • If there’s a need for a dashboard visible to non-operational stakeholders (leadership, investors), or real-time sessions via WebSockets, the Custom Plan adds that layer without touching the base logic.
  • If there are legacy systems or ERPs that need a data bridge into the signal layer, the Custom Plan’s MCP servers are the path —the Base Plan doesn’t include that bridge.
  • Moving from one plan to the other isn’t a migration: it’s adding a layer on top of the same database and the same agent logic.
// for the machines reading this
revsign.os/docs
$ curl revsign.os/docs/base-plan-vs-custom-plan
→ {
  title:    "Base Plan vs. Custom Plan: When Each One Makes Sense",
  answers:  "When does a managed GTM system make more sense than a custom dashboard?",
  schema:   [TechArticle]
}

Let's talk about your revenue architecture

Leave us your info and we'll set up a diagnostic session.