Case Study
RawERPConstruction Material ERP
An ERP for building material dealers, builders and contractors, with a Flutter app for the field sales team.
- Industry
- Construction Materials
- Services
- erp development, mobile app development
- Platforms
- Web · Android
- Build phases shipped
- 8/8Build phases shipped
- User roles
- 11User roles
- Web screens
- 31Web screens
- Field sales app
- APKField sales app
1. Project Overview
A cement and steel dealer sells by the bag, the tonne, the brass and the cubic foot. Credit runs long, sites ask for part deliveries, and trucks go out several times a day. Generic billing tools miss most of this.
RawERP covers the full trade: buying from suppliers, selling to builders on credit, sending material to site against a BOQ, dispatching trucks and paying staff. Each company runs as its own tenant with its own branches and users.
At a Glance
- Client
- Own product
- Product
- Construction material ERP SaaS
- Platforms
- Web, Android
- Live since
- June 2026
- Live at
- rawerp.vercel.app
2. The Challenge
- Units that change by material: bags, MT, quintals, CFT, brass and pieces.
- Builders who buy on credit and need a clear outstanding and credit limit.
- Material issued to construction sites that has to be checked against the BOQ and the project budget.
- Trucks, tippers and machinery like JCBs that must be tracked by trip and by project.
- Sales staff on the road who cannot open a desktop ERP.
3. What We Built
- Trading core: materials with HSN and GST rate, suppliers, customers by type, purchases with stock-in, and quotations, orders and GST tax invoices with stock-out.
- CRM: a lead pipeline from new to won, with one-click conversion of a won lead to a customer.
- Stock: adjustments with a reason and a full ledger with running balance for each material.
- Projects and BOQ: planned versus consumed material per site, budget used and balance.
- Logistics: vehicles, dispatch slips with delivery status, and equipment allocation to projects with service dates.
- Finance and HR: expenses, profit and loss, attendance, payroll, and GSTR-1 and GSTR-3B summaries with input tax credit.
- Customer and vendor portals, plus a BI page with sales against purchase trends and top customers.
4. How It Works
Laravel 12 with Sanctum tokens runs the API, and Next.js 16 with Tailwind v4 runs the web app. A tenant trait stamps every record with its company and filters every query, so dealers never see each other’s data. Eleven roles, from company admin to site engineer, decide who sees what.
The GST invoice splits CGST and SGST, prints the buyer GSTIN and carries a signature block. The GST page builds GSTR-1 outward supplies by rate and a GSTR-3B summary of output tax, input credit and net payable.
The Flutter field sales app reuses the same API. A sales manager can search materials, call a customer, record a payment by UPI or cash, and raise an invoice, order or quotation with GST worked out on the phone.
5. The Outcome
All eight planned phases shipped: trading core, CRM, stock operations, projects and BOQ, logistics and equipment, finance with GST and HR, portals with BI, and the field sales app.
The web ERP has been live at rawerp.vercel.app since June 2026, with demo data in every module so a dealer can try a full day’s work before signing up. Plans start with one branch and five users and go up to unlimited branches on the top plan. The Android field sales app ships as an APK, with the server address set inside the app.
- Build phases shipped
- 8/8Build phases shipped
- User roles
- 11User roles
- Web screens
- 31Web screens
- Field sales app
- APKField sales app
- Web ERP live
- Jun 2026Web ERP live
Technologies Used
- Laravel 12
- Sanctum
- Next.js 16
- Tailwind v4
- MySQL / MariaDB
- Flutter
- Vercel
Have a Similar Challenge?
Let’s build a solution that drives real results for your business.