CRM 360 Development
₹12500-37500 INR
Posted 1 minute ago
•
Ends in 6 days
₹12500-37500 INR
Paid on delivery
I am ready to move CRM 360 from concept to a working web application and need a full-stack developer who is comfortable taking ownership of both the React.js front end and the FastAPI/Python back end that will speak to a Microsoft SQL Server database. First release scope The very first build must cover customer and contact records, lead management, and task / employee activity tracking at the same time—nothing can wait for a later sprint. All three modules need to respect three distinct user roles: administrator, manager, and employee, each with the appropriate permissions baked in from day one. Tech expectations You should already have hands-on experience with React hooks, context, and modern component patterns; Python 3.11+; FastAPI (async routes, dependency injection, Pydantic models); and MS SQL Server design and query optimisation. Clean REST endpoints, JWT-based auth, and a straightforward dev/test/prod deployment flow will be part of the deliverable. What I’m looking for in your bid Tell me about projects where you have built or extended a similar stack and how you solved role-based access, data modelling, and performance challenges. I value concrete experience over long proposals, so keep it focused on what you have done. Acceptance criteria • Running React app with fully functional customer, lead, and task modules • FastAPI backend exposing tested endpoints for all CRUD operations • Role permissions enforced end-to-end • MS SQL Server schema and seed data scripts supplied • Short README covering local setup and deployment steps I’m ready to start as soon as I find the right fit, and I’m open to suggestions on improving the architecture as we go.
Project ID: 40821951
About the project
12 proposals
Open for bidding
Remote project
Active 6 secs ago
Place your bid
Bid amount Email addressBenefits of bidding on Freelancer
Set your budget and timeframe
It's free to sign up and bid on jobs
12 freelancers are bidding on average ₹17,168 INR for this job


Hi, I can build CRM 360 end to end: React.js UI, FastAPI/Python backend, and MS SQL Server schema. I’ll implement customer/contact, lead, and task/employee activity modules together, with JWT auth and role-based permissions for admin, manager, and employee enforced in UI and API. I’ve handled similar full-stack CRUD systems, normalized databases, and performance tuning. Start the chat so we can discuss it further. Regards, Sai Bhaskar


Hello, CRM 360 with customers, leads, and tasks all live in the first release, plus admin, manager, and employee roles from day one, is a clean scope if the foundations are set right. I would model people, leads, and activities as one shared schema with ownership and status rules up front, then build the three modules on top so permissions stay consistent instead of getting patched in later. On past React and FastAPI apps talking to SQL Server I used JWT with role claims, FastAPI dependencies to lock every route, and React context so the UI only shows what each role can actually do. For speed I index lead status, owner, and activity dates, and keep list endpoints async so screens stay quick when history grows. You get a working React app for those three modules, tested CRUD APIs, role checks end to end, schema and seed scripts, and a short README for local setup and deploy. Happy to suggest small architecture tweaks as we go so reporting and audit trails do not become a headache later.


Hi, all three modules and three roles must work together on day one, so the permissions set the scope. The closest I have built is a lead form to mini CRM with a New, Contacted and Won board, and a SaaS dashboard sample with user roles. First I would write the SQL Server schema and seed data for the full model, then build customer and contact records with JWT login and role checks on the FastAPI side, not only in the React screens. The riskiest part is the permission check, so I would test every role against every record. Lead and task tracking would be quoted after this piece. Will your SQL Server sit on your own network or in the cloud?


Your CRM 360 first release needs all three core modules—customer/contact management, lead management, and task/employee activity tracking—working together from day one, with administrator, manager, and employee permissions enforced throughout the application. I can work on the React.js frontend and Python backend, keeping the application structured around your specified React.js, FastAPI, and Microsoft SQL Server stack. My approach would include: - Building reusable React components using hooks and context for application state and role-based UI access. - Developing REST APIs with FastAPI, Pydantic models, and dependency injection for all three modules. - Designing the SQL Server database schema around customers, contacts, leads, employees, tasks, and their relationships. - Implementing JWT authentication and backend-level role permissions so users can only access authorized operations and records. - Testing CRUD endpoints, permission handling, and important data flows before deployment. I'll also provide the SQL schema, seed data scripts, and a README covering local setup and deployment across development, testing, and production environments. I'm open to discussing architectural improvements while keeping your first-release requirements intact. Regards, Naresh Joshi


Hello, You're building a CRM with three core modules (customers, leads, tasks) that all need role-based permissions from the start, plus a React/FastAPI stack talking to MS SQL. The trickiest part here is nailing the data model early, since permissions, relationships, and reporting needs will ripple through every module, you can't afford to refactor later. I'd start by mapping the permission rules for each role against the data schema, then build the FastAPI endpoints with Pydantic validators and dependency-injected auth checks. The React side would use context for role-aware UI rendering, with reusable hooks for CRUD ops. For SQL Server, I'd optimize the high-traffic queries (like lead assignment or task timelines) with indexed views upfront. I delivered something very close to this last month, a document chatbot that answers questions from uploaded PDFs with similar role-based access and async FastAPI routes. How locked in are you on MS SQL versus Postgres? It'd handle the JSON-heavy permission logic more cleanly, but I can work with either.
内容来自 Freelancer News,版权归原作者所有。
阅读原文 ↗