Marketing CRM SaaS

Buyer pain

Campaign requests, client approvals, content calendars, reporting, and billing handoffs stall when every update lives in a different tool.

Persona

Marketing teams and agencies coordinating leads, campaign work, approvals, content calendars, reporting, and billing readiness.

Marketing operations only stay predictable when demand capture, campaign status, client approvals, reporting, and billing context stay visible together.

Mock dashboard metrics

• Open campaigns: 18 - Mock campaigns across planning, approval, and launch.
• Approval queue: 7 - Client approvals needing account follow-up.
• Tenant signups: 0 - Public registration stays disabled during closed alpha.

Dashboard preview

• Timestamp: Updated today 10:40 AM CT
• Open campaigns: 18 - Campaign work grouped by stage, owner, launch date, and approval risk.
• New leads: 12 - Requests needing qualification and campaign fit review.
• Approvals: 7 - Client reviews or creative signoffs holding launch.
• Reports due: 4 - Campaign reports awaiting account-owner review.
• Lead intake: 12 - Inbound demand organized by source, urgency, and owner.
• Campaign pipeline: 18 - Active work grouped by stage, launch date, and blocker.
• Reporting cockpit: 4 - Reports, billing readiness, and client follow-up in one owner view.
• Activity: New campaign request assigned to account lead
• Activity: Client approval moved into creative review
• Activity: Reporting package queued for owner review
• Owner action: Qualify new campaign request
• Owner action: Clear client approval blocker
• Owner action: Review reports due this week
• Next best action: Clear approval blockers before reporting and billing handoffs stack up.

Operator workflow

• Capture: Qualify inbound leads, campaign requests, owners, deadlines, and source context.
• Approve: Track creative reviews, client feedback, launch blockers, and campaign status.
• Report: Connect launched work to reporting, billing readiness, and next-best follow-up.

Static mock screens

• Lead intake: Inbound requests with source, urgency, owner, and campaign fit. (Static preview live)
• Campaign pipeline: Campaign cards organized by stage, launch date, approval status, and blocker. (Closed alpha)
• Reporting cockpit: Owner-facing metrics for approvals, reports due, billing readiness, and campaign health. (Pilot gated)

Operating model

Closed-alpha public product route with invite-only tenant access and signup disabled.

Launch status

Closed alpha product surface for Marketing CRM pilots.

What is live vs paused

Public product route, service card, metadata, aliases, and crawlable content are live.

Public signup, checkout activation, customer onboarding, and production tenant data are paused.

Buyer questions answered

• Can anyone sign up?: No. Marketing CRM is in closed alpha, public signup is disabled, and only invited accounts can sign in.
• What does the first pilot validate?: The first pilot validates lead intake, campaign stages, approval handoffs, reporting needs, and billing readiness.
• Does the public page collect campaign data?: No. The public product page explains the workflow and routes pilot requests without exposing live tenant data.

Pilot readiness checklist

• Closed-alpha gate: Public marketing content is visible, but registration, checkout activation, and onboarding are disabled.
• Campaign model: The product surface models leads, campaign stages, approvals, content calendars, reports, and owner actions.
• Shared architecture: The repo follows the shared CRM stack: Next.js, tenant routing, MySQL, Cloud Run, Stripe gates, and tests.
• Pilot proof: A small pilot would validate whether approval and reporting visibility reduces account-team handoff gaps.

What happens after request pilot

• Map campaign workflow: Document lead sources, campaign stages, approval owners, reporting cadence, and billing handoffs.
• Configure alpha surface: Use synthetic or approved sample records to validate the operating model without public signup.
• Review gated access: Confirm invited users, tenant boundaries, signup-disabled behavior, and billing activation rules.
• Approve live pilot: Resume tenant onboarding only after the closed-alpha workflow and data boundary are accepted.

Proof and fit

• Lead intake, campaign pipeline, approval, reporting, and billing-readiness concepts are available as static previews.
• Public pages are live while tenant signup, checkout activation, and customer onboarding remain closed-alpha gated.
• The product route explains the marketing workflow without calling tenant APIs or exposing a public sandbox.

Capabilities

• Lead intake and campaign pipeline workflow.
• Client approval, content calendar, and blocker tracking.
• Reporting, billing readiness, and Stripe-gated tenant controls.

Architecture at a glance

• Public route: Firebase serves the Marketing CRM product page and aliases as static SaaS content.
• Closed-alpha app: Next.js, tenant routing, MySQL, Stripe gates, and auth remain available behind invite-only access.
• Signup boundary: Public signup, checkout activation, and live tenant onboarding remain disabled until pilot approval.

Marketing CRM SaaS pricing

SaaS/product MVP pilot is published as a typical planning range, not a guaranteed quote.

Typical ranges are planning anchors, not guaranteed quotes. Exact amount and currency are confirmed only after scope, acceptance criteria, customer/workspace, and rollback note are approved.

SaaS pilots usually require a proposal packet and deposit before runtime, database, billing, or customer-data work is activated.

• Lean pilot: $25k-$75k
• Multi-role integrations: $75k-$150k+
• What changes the price: Number of user roles, dashboards, workflows, and authenticated states.
• What changes the price: Billing, auth, CRM, scheduling, voice, email, or third-party API integrations.
• What changes the price: Data model complexity, audit logs, support workflow, and operator reporting.
• What changes the price: Whether paused SaaS runtime is resumed for a controlled authenticated pilot.
• Excluded: Public unauthenticated SaaS sandboxes.
• Excluded: Broad feature catalogs before the first owner workflow is proven.
• Excluded: Ongoing cloud spend, third-party usage fees, and vendor subscriptions unless written into the proposal.