RevenuePilot CRM CodeCanyon Parity Depth Guide

This guide is for marketplace demos and buyer review. It shows the deeper workflows added after the baseline RevenuePilot CRM parity pass.

What To Demo

• Show customer balances, overdue aging, dunning, reconciliation, invoice-open tracking, refunds, gateway event logs, and replay.
• Use this to prove the CRM is not only invoicing, but also has collections and payment operations depth.

1. Open /crm/finance/statements.

• Show project timelines, milestones, tasks, progress, and at-risk delivery rows.
• Open a project detail page and demo progress updates, clone-from-template, and file version upload.

1. Open /crm/projects/gantt.

• Add a comment, follower, reminder, subtask, and dependency.
• Show that client-facing work can be approved from the portal.

1. Open a task detail page.

• Generate the public proposal acceptance link.
• Open /proposal-accept/{token} and accept or reject the proposal.

1. Open a proposal detail page.

• Generate the signing link.
• Open /contract-sign/{token} and sign the contract.

1. Open a contract detail page.

• Run the mailbox adapter to create a support ticket.
• Record a sandbox gateway webhook event and replay it from finance statements.

1. Open /crm/mailboxes and /crm/payment-gateways.

• Comment on and approve tasks.
• Respond to proposals, sign contracts, upload folder files, submit orders, answer surveys, and vote on knowledge base articles.

1. Open portal pages.

Buyer-Facing Proof Points

• Perfex-style operations: projects, tasks, time, invoices, support, contracts, proposals, expenses, surveys, goals, files, recurring work, and payments.
• RISE-style client workspace: portal actions for tickets, files, orders, surveys, proposals, contracts, tasks, invoices, and knowledge base.
• Grow-style Laravel workflow: task timers, project templates, recurring work, public proposal/contract flows, payment links, and operational logs.
• RevenuePilot differentiation: campaign-to-cash, data quality, AI-ready operations, integration health, and marketplace demo proof.

Screenshot Checklist

Capture these after running php artisan crm:demo-seed:

• Landing page: /
• Admin login: /login
• CRM dashboard: /crm/dashboard
• Finance statements: /crm/finance/statements
• Project Gantt: /crm/projects/gantt
• Task board: /crm/tasks/board
• Proposal public acceptance: /proposal-accept/{token}
• Contract public signing: /contract-sign/{token}
• Portal dashboard: /portal/dashboard
• Portal knowledge base article with usefulness vote

Acceptance Criteria

• Every action form uses SweetAlert confirmation and Toastr flash feedback.
• Every app-owned list uses the documented tbl-* table shell.
• Public proposal and contract routes are separate from quotation signing.
• Portal actions are scoped to the portal user company.
• Integration and payment actions are sandbox-ready with logs, retries, and replay.