FolksCRM

FolksCRM is the Sales & CRM member of the Folks product family. It runs on a single Microsoft SQL Server engine and is organised into fourteen modules that take a prospect from the very first marketing touch all the way to a settled invoice. Everything is built on the same SQL-first discipline used across FolksHR and FolksPMS — no ORM, no LINQ in business logic, and every operation routed through a named stored procedure.

1.1 The fourteen modules

1.2 The revenue pipeline at a glance

Records carry forward. A campaign earns a lead; a qualified lead converts to an account + contact + opportunity; a won opportunity becomes a quote, then an order, then an invoice that ages in receivables.

1.3 The technology stack

Every session starts at the login screen. Once authenticated, the left navigation is built from your role's privileges — you only ever see the menus and buttons you are allowed to use.

2.1 Signing in

1. Enter your username and password; click Sign in.
2. The login DevSP validates credentials and returns your user record, roles and a token seed.
3. The token is stored in localStorage and attached as Authorization: Bearer <token> on every subsequent call.
4. You land on the home dashboard mapped to your role's default path.

2.2 The standard page anatomy

Almost every list screen in FolksCRM shares the same toolbar and grid so the muscle memory transfers from module to module.

• Search & filter strip — server-side; sends your criteria to the list DevSP.
• Add — opens a modal or right-side drawer form (hidden if you lack the Add privilege).
• Data grid — server-paged, sortable columns, status badges, row actions.
• Export — pushes the current filtered set to CSV/PDF.
• Refresh — re-runs the list DevSP without losing your filters.

2.3 Roles you'll meet

UM is the foundation module — it owns identity, role-based access, the employee directory, the menu/privilege engine, the audit log and the workflow inbox. It is ported verbatim from FolksHR and is functionally frozen; only its Blazor markup may be restyled. Every other module wires its SecurityService here.

3.1 What it manages

3.2 Key pages

Master Data is the single home for cross-cutting lookup tables, so the same currency, industry or stage list is reused everywhere instead of being duplicated per module. It is owned by administrators and loaded once at app start.

4.1 The lookups

4.2 The Master Data Console

An Account is a B2B company or organisation — the anchor for the sales hierarchy, addresses, the account team and the full 360° history. Every opportunity, quote, order and invoice ultimately rolls up to an account.

5.1 Account form — key fields

5.2 The 360° detail page

Open any account to a tabbed drawer that aggregates everything in one place via DevSP_Account_GetById_Full and DevSP_Account_GetTimeline.

• Profile — firmographics, owner, parent.
• Addresses — billing/shipping/other.
• Team — add/remove members with a role on the account.
• Timeline — merged activities, opportunities, quotes/orders and invoices, newest first.

5.3 Common actions

A Contact is a person. Unlike accounts, a contact can be linked to several accounts at once (many-to-many) with one marked primary — perfect for consultants, partners and group buyers. Contacts also hold communication preferences for compliant outreach.

6.1 Linking & preferences

6.2 Contact 360°

A Lead is an unqualified prospect. Leads can be captured by hand, through a web-to-lead form, or imported in bulk. They are scored, assigned, qualified — and finally converted in a single click into an Account, a Contact and an Opportunity.

7.1 The lead lifecycle

7.2 Grid & Kanban

Toggle the list between a classic grid and a Kanban grouped by lead status. KPI tiles across the top come from DevSP_Lead_DashboardCounts.

7.3 Conversion — what it builds

The convert wizard runs one atomic DevSP_Lead_Convert:

1. Insert (or reuse) an Account from the lead's company.
2. Insert (or reuse) a Contact from the lead's person.
3. Optionally create an Opportunity (you can set name & amount in the wizard).
4. Stamp the lead's converted_to_* ids and timestamp.
5. Write an activity-log row and emit a workflow listener for the new owner.

The Opportunity is the active deal — the heart of the funnel. It carries an amount, a stage, an expected close date, products, competitors and a team, and feeds the pipeline forecast.

8.1 The stage Kanban

Drag a card to a new column and DevSP_Opportunity_ChangeStage updates the stage, writes a stage history row (with duration-in-stage) and emits a workflow listener if the stage is gated.

8.2 Deal detail tabs

8.3 Forecast & close

The forecast dashboard groups pipeline by stage × month × owner, weighting each deal by its stage probability. Mark a deal Won or Lost with a reason; a won deal can be converted to a Quote in one click (Chapter 12). A weekly snapshot DevSP preserves the pipeline for trend analysis.

Activities are the day-to-day work that moves deals. An activity is polymorphic — it can be linked to a Lead, Account, Contact, Opportunity, Quote or Order — so wherever you are, you can log what happened and schedule what's next.

9.1 Activity types & views

• My Activities — grouped Today / This week / Overdue.
• Team Activities — manager view across reports.
• Calendar — month/week/day for meetings & calls.

Campaigns drive demand and tie back to lead attribution. Build a target list by criteria, author an email template, schedule an execution, then track opens, clicks, replies and bounces — and compute ROI against budget.

10.1 Campaign flow

10.2 Tracking & attribution

The catalog feeds every line item on opportunities, quotes and orders. It holds products, a category tree, pricebooks (default + customer-specific), discount rules and on-hand inventory per warehouse.

11.1 Pricing resolution

When a line needs a price, DevSP_Product_GetPriceForContext resolves it from the right pricebook for the customer, quantity and date, then applies the best applicable discount rule:

11.2 Inventory

A Quote is the formal price offering between Opportunity and Order. It supports a line builder, header & line discounts, a multi-level approval chain, revisions that preserve history, PDF generation and customer accept/reject.

12.1 Quote statuses

12.2 The line builder

12.3 Approval & conversion

1. Submit for approval emits a workflow listener to the approver(s).
2. Approver approves/rejects with comments; on approve the status advances.
3. Generate the PDF payload and send to the contact.
4. Record the customer's accept/reject.
5. Convert to Order in one click — lines carry over (Chapter 13).

An Order is a committed deal that drives fulfillment and invoicing. Create it from an accepted quote in one click, or manually. Confirm to lock editing, then ship in full or in parts and watch per-line shipped-vs-ordered update live.

13.1 Order statuses

13.2 Creating a shipment

The composite shipment DevSP inserts the shipment + its lines, increments each OrderLine.qty_shipped, and recomputes the order status — all in one transaction.

Billing is money-in. Create an invoice from an order (or manually), issue it, record full or partial payments, generate receipts, and watch receivables age across buckets — with a dunning list for overdue accounts.

14.1 Invoice statuses & payment

Recording a payment runs DevSP_Invoice_RecordPayment_Composite: it writes the payment, generates a receipt, then recomputes the invoice status and balance.

14.2 Receivables aging

A scheduled aging-snapshot DevSP refreshes the buckets; the dunning-candidates DevSP produces the list of overdue invoices to chase, which the FE renders as an email queue.

Workflow is the generic approval/notification engine. Other modules just emit a "listener" row; this module owns the inbox, the router, the SLA escalation and the notification dispatch.

15.1 How a request flows

1. A module calls DevSP_Workflow_Trigger(Module, EntityType, EntityID, Event, Payload) after its primary write.
2. The engine picks the matching definition and writes the first step for the right approver.
3. The approver sees it in their inbox and approves/rejects with comments.
4. On approve → advance to the next level or mark the instance Complete; on reject → notify the originator.
5. If a step is older than its due time, the escalation sweep bumps it to the next-up approver.

15.2 What triggers workflow

The Reports module is pure-read cross-module analytics. Each dashboard is one or more read-only DevSPs; admins can register new report definitions that point at any DevSP and schedule them to email recipients.

16.1 The five role dashboards

16.2 The conversion funnel

The headline report tracks the rate at each hand-off — Lead → Opportunity → Quote → Order → Invoice — so you can see exactly where deals leak.

17.1 Status reference

17.2 Common issues

17.3 Scheduled jobs (v1 = manual "Run Job")