Supabase-Powered React CRM Module
Budget / SalaryHourly project
TypeFreelance project
LocationRemote
Posted2 hours ago
I need the first slice of a custom CRM built with React, TypeScript, and Supabase. This initial milestone centres on lead, customer, and contact management for an engineering-manufacturing business.
The data model must capture three distinct layers of information for every record:
• basic contact details and company information
• sales notes, follow-ups, and full communication history
• any technical requirements, drawings, or product-related documents we receive
On the front end I want a clean, responsive interface that presents a visual sales pipeline with drag-and-drop stages so the team can instantly see where each opportunity sits. Creating, editing, and re-ordering stages should be effortless.
Key requirements
• React + TypeScript SPA, Vite or Next.js is fine
• Supabase for auth, row-level security, Postgres schema, and real-time updates
• File storage in Supabase for drawings and spec sheets
• Clear separation between data services and UI components so the codebase scales as we bolt on quoting, production-tracking, and invoicing later
Deliverables
1. Git repo with well-structured, documented code
2. Supabase SQL/JSON seeds and policies ready for one-click deployment
3. Responsive UI implementing the visual pipeline, record views, and inline editing
4. Brief README covering setup, env variables, and future-module hooks
We need a custom CRM and quoting platform for 10–25 users across Sales, NPD (new product development) and management.
What already exists
A detailed functional specification (about 15 sections).
A clickable prototype of every module. The screens, workflows and calculations are already agreed. Your job is to build it properly, not to design it from scratch.
What you’ll build
Companies and contacts, with a full customer history.
RFQ management: automatic numbering, several part numbers per RFQ, 16 stages with time-in-stage tracking, and old RFQs entered with their original dates.
NPD technical feasibility: a configurable checklist, decisions, approvals and decision history.
Quotations with revisions that are never overwritten, plus searchable price history and charts of how prices changed over time.
Product master: mapping between customer part numbers and our product codes, and documents with revision control (drawings, specifications, PPAP).
Raw-material prices and exchange rates with dated history.
Recipe-based product costing: material % by weight, conversion costs and scrap allowance. Each quote saves a snapshot of the costs it was based on, so later price changes never alter it.
Profitability: gross margin, markup, raw-material share of cost, and products ranked by profitability.
Sales pipeline board in the style of HubSpot: drag-and-drop between stages, customisable cards, editable stages, and a list view.
Programmes and start-of-production (SOP) tracking, activities and follow-ups, a dashboard and reports exported to Excel.
Import of historical RFQs, quotes and prices from Excel, with a validation step before anything is saved.
Stack (required)
React + TypeScript (Vite)
Supabase: PostgreSQL, Auth, Storage, Row-Level Security
Hosting on Vercel, Netlify or Firebase Hosting
Non-negotiable requirements
Permissions enforced in the database (Row-Level Security), not just by hiding buttons. Four roles: Super User, Sales, NPD and Read-only. NPD users must never be able to read prices, costs or margins.
A full audit trail: who created, changed or approved each record, what changed and when.
Approved quotes, cost snapshots and approved drawings can’t be edited. Changes create new revisions.
Correct money handling: every amount stored with its currency, plus the exchange rate and its date.
Automated tests for the costing and margin calculations, checked against our Excel costing models.
Ownership: code lives in our GitHub repository from day one, with a pull request for each module. We own all intellectual property.
Milestones (fixed price per milestone preferred)
Milestone Scope
1 Logins, roles and security rules, audit log, companies and contacts, RFQs, NPD feasibility, documents, activities
2 Product master, materials and exchange rates, recipe costing, quotations with snapshots, price history
3 Pipeline board, historical import, programmes, profitability, dashboard and reports, go-live, handover documentation
We test each milestone ourselves (user acceptance testing) before it’s paid.
Nice to have
Experience with manufacturing, ERP, CPQ (quoting) or CRM systems.
Comfortable using AI coding tools such as Claude Code or Cursor to work faster.
Available for overlapping hours with Indian Standard Time.
To apply, please answer:
Link to a React + Supabase (or PostgreSQL) app you built that uses Row-Level Security, and describe your part in it.
How would you make sure an NPD user can never see cost or margin data, even through the API?
How would you store quotation revisions and cost snapshots so historical figures never change?
Your estimate in hours and price for each milestone, and your available hours per week.
You’ll receive the full specification and prototype after signing an NDA.
The data model must capture three distinct layers of information for every record:
• basic contact details and company information
• sales notes, follow-ups, and full communication history
• any technical requirements, drawings, or product-related documents we receive
On the front end I want a clean, responsive interface that presents a visual sales pipeline with drag-and-drop stages so the team can instantly see where each opportunity sits. Creating, editing, and re-ordering stages should be effortless.
Key requirements
• React + TypeScript SPA, Vite or Next.js is fine
• Supabase for auth, row-level security, Postgres schema, and real-time updates
• File storage in Supabase for drawings and spec sheets
• Clear separation between data services and UI components so the codebase scales as we bolt on quoting, production-tracking, and invoicing later
Deliverables
1. Git repo with well-structured, documented code
2. Supabase SQL/JSON seeds and policies ready for one-click deployment
3. Responsive UI implementing the visual pipeline, record views, and inline editing
4. Brief README covering setup, env variables, and future-module hooks
We need a custom CRM and quoting platform for 10–25 users across Sales, NPD (new product development) and management.
What already exists
A detailed functional specification (about 15 sections).
A clickable prototype of every module. The screens, workflows and calculations are already agreed. Your job is to build it properly, not to design it from scratch.
What you’ll build
Companies and contacts, with a full customer history.
RFQ management: automatic numbering, several part numbers per RFQ, 16 stages with time-in-stage tracking, and old RFQs entered with their original dates.
NPD technical feasibility: a configurable checklist, decisions, approvals and decision history.
Quotations with revisions that are never overwritten, plus searchable price history and charts of how prices changed over time.
Product master: mapping between customer part numbers and our product codes, and documents with revision control (drawings, specifications, PPAP).
Raw-material prices and exchange rates with dated history.
Recipe-based product costing: material % by weight, conversion costs and scrap allowance. Each quote saves a snapshot of the costs it was based on, so later price changes never alter it.
Profitability: gross margin, markup, raw-material share of cost, and products ranked by profitability.
Sales pipeline board in the style of HubSpot: drag-and-drop between stages, customisable cards, editable stages, and a list view.
Programmes and start-of-production (SOP) tracking, activities and follow-ups, a dashboard and reports exported to Excel.
Import of historical RFQs, quotes and prices from Excel, with a validation step before anything is saved.
Stack (required)
React + TypeScript (Vite)
Supabase: PostgreSQL, Auth, Storage, Row-Level Security
Hosting on Vercel, Netlify or Firebase Hosting
Non-negotiable requirements
Permissions enforced in the database (Row-Level Security), not just by hiding buttons. Four roles: Super User, Sales, NPD and Read-only. NPD users must never be able to read prices, costs or margins.
A full audit trail: who created, changed or approved each record, what changed and when.
Approved quotes, cost snapshots and approved drawings can’t be edited. Changes create new revisions.
Correct money handling: every amount stored with its currency, plus the exchange rate and its date.
Automated tests for the costing and margin calculations, checked against our Excel costing models.
Ownership: code lives in our GitHub repository from day one, with a pull request for each module. We own all intellectual property.
Milestones (fixed price per milestone preferred)
Milestone Scope
1 Logins, roles and security rules, audit log, companies and contacts, RFQs, NPD feasibility, documents, activities
2 Product master, materials and exchange rates, recipe costing, quotations with snapshots, price history
3 Pipeline board, historical import, programmes, profitability, dashboard and reports, go-live, handover documentation
We test each milestone ourselves (user acceptance testing) before it’s paid.
Nice to have
Experience with manufacturing, ERP, CPQ (quoting) or CRM systems.
Comfortable using AI coding tools such as Claude Code or Cursor to work faster.
Available for overlapping hours with Indian Standard Time.
To apply, please answer:
Link to a React + Supabase (or PostgreSQL) app you built that uses Row-Level Security, and describe your part in it.
How would you make sure an NPD user can never see cost or margin data, even through the API?
How would you store quotation revisions and cost snapshots so historical figures never change?
Your estimate in hours and price for each milestone, and your available hours per week.
You’ll receive the full specification and prototype after signing an NDA.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.