Value Lifecycle Platform

🔗 Live demo: value-lifecycle-platform.vercel.app — running on Vercel + Neon. The demo-account picker is off in production (accounts aren't listed publicly), so sign in with a demo email + password. To show the one-click role picker on a deployment, set SHOW_LOGIN_MEMBER_PICKER=true.

Before it works, create a Postgres database (a free Neon DB is recommended) and run prisma db push + seed against it — the button asks for DATABASE_URL, DIRECT_URL, AUTH_SECRET and AUTH_TRUST_HOST during import. Full walkthrough: DEPLOYMENT.md.

An end-to-end web app for three complementary roles across the full value lifecycle:

• Value Engineer (VE) — runs structured value studies (8-phase VE Job Plan), analyses functions/cost/performance, generates alternatives, and builds a quantified business case.
• Value Realization Manager (VRM) — implements approved recommendations (7-phase realization lifecycle), drives adoption, measures outcomes, and proves realized value against the business case.
• Customer Success Manager (CSM) — runs the continuous, per-account lifecycle (8 stages: onboarding → health → renewal → expansion), with a health scorecard, renewal/growth plans and AI-assisted EBRs. See docs/CS-MODULE-DESIGN.md.

The VE → VR handover is first-class (every realization track links back to its source study, business case, baselines, KPIs and success criteria), and a Customer Success engagement references the account's studies and tracks — surfacing their value, never duplicating it.

Supports three configurable industry profiles out of the box — Construction & Infrastructure, Manufacturing & Product Development, and Enterprise Software / SaaS — with industry as configuration, not code.

📘 New here? Read the User Guide — how to run a value study end-to-end, from a fresh problem through the handover to proven realized value.

See ARCHITECTURE.md for the full design, data model and user flows, and docs/MAINTENANCE.md for maintainer notes — migrations, the demo-kit regeneration chain, and build/deploy gotchas.

🧭 Proposed: docs/CS-MODULE-DESIGN.md — a draft design for a Customer Success pillar (continuous 8-stage lifecycle) alongside VE and VR. Not yet built.

Stack

Next.js 15 (App Router) · TypeScript · Prisma · PostgreSQL · Tailwind CSS · docx / exceljs exports.

Prerequisites

• Node 18+ and PostgreSQL running locally.

Setup

# 1. Install
npm install

# 2. Configure the database URL
cp .env.example .env
#   edit .env → DATABASE_URL="postgresql://<user>@localhost:5432/value_consultancy?schema=public"

# 3. Create the database
createdb value_consultancy

# 4. Create the schema + generate the client
npx prisma db push

# 5. Seed config (industries, phases, KPIs, templates) + demo data
npm run db:seed

# 6. Run
npm run dev   # http://localhost:3200

What's seeded

• Config: 3 industry profiles, 8 VE + 7 VR phase-guidance templates, ~20 KPI definitions with formulas, VE/VR content templates.
• Demo org Meridian Value Advisory with 5 users (one per role).
• Study VE-2026-014 (construction) — fully handed over to a live realization track VR-2026-014 with work packages, benefits, KPI actuals and a QBR.
• Study VE-2026-021 (SaaS) — in review, with a business case, ready to hand over.

Sign in at /login (unauthenticated requests are redirected there by middleware). In local dev the sign-in screen lists the demo workspace's members, so you can jump straight in as Value Engineer, Value Realization Manager, Customer Success Manager, Reviewer, Stakeholder/Viewer or Admin — navigation and permissions adapt. The demo workspace signs in one-click when DEMO_PASSWORD is set (otherwise pick a member to prefill their email and type the password). The member picker is off in production by default (SHOW_LOGIN_MEMBER_PICKER=true re-enables it); demo accounts share the DEMO_PASSWORD password — see DEPLOYMENT.md.

Create your own workspace at /register — each sign-up creates a new, isolated organization with the signer as Admin. Admins get a Team page (/settings/team) to add members, assign roles, reset passwords, and remove access. No email server needed (admins set an initial password to share).

This is the beginning of the README. Read the rest at the original. Read the full README ↗