Project _ Mach-iq

byNithish B

# ROLE You are a Principal Product Architect, Manufacturing ERP Consultant, Precision Engineering Domain Expert, Senior SaaS Architect, UX Designer, and Full Stack Engineering Lead. Your job is NOT to build screens. Your job is to design and build a scalable enterprise SaaS product that solves one of the biggest operational bottlenecks inside precision engineering companies. Think like someone designing the future "Salesforce for Precision Engineering." Do not cut corners. Question assumptions. Challenge bad product decisions. Recommend better architecture whenever appropriate. --- # PRODUCT NAME Working Name: MachIQ This is a temporary product name. --- # PRODUCT VISION MachIQ is a Vertical SaaS platform built exclusively for precision engineering manufacturers. Our mission is to reduce quotation turnaround time from days to minutes while standardizing commercial operations. The software must become the operating system for manufacturing commercial teams. Long-term vision: Lead Management ↓ RFQ Management ↓ Estimation ↓ Quotation ↓ Customer Negotiation ↓ Purchase Order ↓ Production Planning ↓ Delivery ↓ Invoice ↓ Analytics Version 1 focuses ONLY on RFQ and Estimation. --- # THE PROBLEM Today the workflow looks like: Customer sends RFQ ↓ Email ↓ Engineering Drawing (PDF / STEP) ↓ Senior Estimator ↓ Manual Material Calculation ↓ Machine Selection ↓ Cycle Time Calculation ↓ Excel Cost Sheet ↓ Management Approval ↓ Quotation PDF ↓ Customer Problems: • Estimation depends on one senior engineer • Quoting takes several hours or days • Material prices constantly change • Machine hourly costs constantly change • Quotes are inconsistent • Companies ignore RFQs because of limited bandwidth • Slow quotation leads to lost business We are NOT replacing estimators. We are making estimators dramatically more productive. --- # TARGET CUSTOMER Precision Engineering Companies Initially: Coimbatore Future: India Global Ideal Customer: Revenue ₹10 Cr–₹75 Cr Employees 25–150 Machines 5–30 CNC/VMC RFQs 30–300/month Current software: Excel WhatsApp Email Tally ERP (optional) --- # PRODUCT PHILOSOPHY MachIQ is NOT: ERP Inventory Production Planning CAD Software Machine Monitoring AI replacing engineers MachIQ IS: Commercial Workflow Software. The estimator remains in control. The software organizes information, calculations, costing, quotations and RFQs. --- # CORE PRODUCT FLOW Login ↓ Dashboard ↓ Customer ↓ Project ↓ RFQ ↓ Upload Drawing ↓ Estimate ↓ Generate Quote ↓ Track Status Everything should revolve around Projects. One Project can contain multiple RFQs and revisions. --- # VERSION 1 MODULES Authentication Organizations Customers Projects RFQs Material Library Machine Library Estimation Workspace Cost Engine Quote Generator Tracker Settings Audit Logs No ERP. --- # MULTI TENANCY Every company is a tenant. Implement proper Row-Level Security. Every organization should only see its own data. Never trust frontend filtering. Security is mandatory. --- # DATABASE Design production-ready PostgreSQL schema. Use: Organizations Users Customers Projects RFQs RFQ Files Materials Material Price History Machines Machine Rate History Estimates Estimate Line Items Quotes Settings Audit Logs Future-ready schema. --- # COST ENGINE The estimator should never manually remember rates. Implement centralized: Material Library Machine Library Settings Estimator Override Snapshots Old quotations should never change when rates change later. Every quotation must preserve historical pricing. --- # ESTIMATION ENGINE Estimator enters: Material Machine Runtime Tool Cost Labour Cost Margin Software calculates: Subtotal Tax Final Price Profit Support custom cost components. Do NOT hardcode. Design a flexible estimate line-item model. --- # PROJECT STRUCTURE Customer ↓ Project ↓ RFQ ↓ Estimate ↓ Quote ↓ Future Purchase Order Projects should become the central object. --- # PRODUCT INTELLIGENCE Version 1 should NOT perform OCR or CAD parsing. Instead implement: Suggest Values Logic: Search previous RFQs. If similar project or part exists: Suggest Material Machine Manufacturing Process Margin Estimator must manually accept suggestions. Nothing should auto-apply. No fake AI. --- # STORAGE Private storage only. RFQ Drawings Quote PDFs Signed URLs. Never public. --- # USER ROLES Owner Estimator Sales Different permissions. Implement using Row-Level Security. --- # LANGUAGE SUPPORT Support: English Tamil Kannada Malayalam Translate UI only. Never translate engineering terms. Language stored per user. --- # DESIGN Industrial. Enterprise. Professional. Desktop First. No startup style. No glassmorphism. No excessive animations. Think Siemens, Autodesk, SAP, Linear. --- # USER EXPERIENCE Estimator should never wonder: "What do I do next?" Workflow must always be obvious. Every screen should have one primary action. --- # FUTURE ROADMAP Design architecture for future modules: Approval Workflow Previous Quote Intelligence Supplier Pricing Drawing Analysis Cycle Time Prediction Machine Learning Production Planning Customer Portal Analytics API Integrations Do NOT build these now. Only architect for them. --- # OUTPUT EXPECTED I want you to act like the founding CTO. Produce: 1. Complete product architecture 2. Information architecture 3. Database architecture 4. API architecture 5. Component architecture 6. Frontend architecture 7. Backend architecture 8. Authentication 9. Storage architecture 10. Security model 11. Row-Level Security 12. UX flows 13. Screen-by-screen breakdown 14. Database schema 15. Cost engine design 16. Estimation engine 17. Quote generation engine 18. Suggest Values logic 19. Future scalability 20. Build the complete Version 1 application from scratch using best engineering practices. Whenever you think the product can be improved, explain why and implement the better solution instead of blindly following the specification.