IntraWeb Nexus — Business Operations Platform
Full-stack client portal, staff operations console, and n8n automation layer connecting HubSpot, Stripe, Clerk, and Supabase for IntraWeb delivery.
Project Overview
IntraWeb Nexus is the operating system behind IntraWeb Technologies: a multi-tenant client portal and staff admin console, paired with curated n8n workflows that move leads, deals, documents, and billing events between HubSpot, Stripe, Clerk, and Postgres. The marketing site (iw-site-q2) handles conversion; the portal remains the system of record for delivery.
The Challenge
Delivery status, approvals, invoices, and change requests lived across CRM threads, email, and spreadsheets. Qualified demand did not reliably become a provisioned client workspace, and staff lacked a single operations surface for triage, billing visibility, and integration health.
The Solution
Built a Turborepo monorepo with an authenticated Next.js portal (Clerk + Supabase RLS-oriented schema), Stripe billing, HubSpot CRM mirroring, and an in-repo n8n workflow package. Automations orchestrate provisioning and document generation; humans approve milestones, proposals, and change orders in the portal. Social Ops review is an experimental vertical slice—not claimed as production-complete.
Key Features
- •Client dashboard: progress, milestones, documents, messaging, billing, change orders, notifications
- •Staff admin OS: operations queue, clients/projects, billing reconciliation, integration events, data health
- •Webhook fabric: Clerk, Stripe, HubSpot, and n8n inbound actions with integration event logging
- •Curated n8n catalog: lead intake, sales provisioning, proposals/contracts, onboarding, client success, reporting
- •Privacy data-subject request flow on the marketing site with internal execution support
- •Role-based staff access (admin, ops, support, viewer) with audited sensitive mutations
Impact
Centralized client delivery state in one authenticated portal; standardized CRM-to-workspace provisioning paths; versioned automation assets beside application code; improved staff visibility into failed integrations and at-risk work. Measured client ROI metrics are not claimed in this portfolio entry.
Key Learnings
Orchestration belongs beside the product, not inside it—but outbound portal events need checked-in receivers or they become silent no-ops. Schema can outpace UX (members/invites). Service-role server access demands disciplined query filters. Honest status labels (Implemented vs Partial vs Experimental) matter more than a longer feature list.
Technologies Used
Version & Status
What's New
- •Social Ops vertical slice (ingest, staff review, outbox) — experimental
- •Expanded architecture and automations documentation in the Nexus monorepo
- •Continued hardening of billing, HubSpot mirror, and portal webhook contracts
Coming Soon
- •Complete curated receivers for portal outbound webhook paths
- •Full client member invitation UX aligned with existing membership tables
- •Social auto-publish beyond review/outbox slice