The platform
Two products share identity and stay out of each other's data. This page is the map. Website: https://buildrigs.com/platform
Inside the app
First screen: I am a Customer or I am a Vendor. OTP, Google, or Apple. Screens cycle — tap any step to hold it.
Customer
Vendor
This month
Ledger
BuildRigs
How will you use the app?
Same install. The role is the split.
Then OTP, Google, Apple, or email.
/platform#customer
/platform#vendor
List idle machines, take jobs you would have missed, and get paid against a booking — not a promise.
Start listing (form)Central console
Unique path for the team. The mock below walks Pulse, KYC, bookings, campaigns, WhatsApp, and logs.
Pulse
KYC types we review: GST, PAN, RC, insurance, PUC, fitness, licence, invoice. Until HQ approves, the listing stays pending.
On the first screen pick I am a Vendor. Customer and vendor share the same app; the role is the split.
Name, email, 10-digit Indian mobile, and a password of 8+ characters — or continue with OTP, Google, or Apple.
Business name, type (individual, proprietor, partnership, company), GSTIN, PAN, registered address, city, and service areas.
Upload GST, PAN, RC, insurance, PUC, fitness, and licence. Files go to S3. HQ reviews them. Nothing is live until KYC is approved.
Type, brand, model, photos, city, and rates (hourly, daily, weekly, monthly). Each machine can carry its own papers.
Accept or decline. Share live location. Customer pays on the hire. Your ledger and bank details sit with HQ.
A parked excavator only costs. List it, set rates, take jobs in the cities you already cover.
Contractors search the catalog. You accept or decline. No dealer rolodex on either side.
Approved KYC is what makes you bookable. GST, PAN, RC, insurance — reviewed once, reused on every hire.
The booking carries payment. You see pending and settled in the vendor app instead of chasing cash on site.
Everything the apps do, plus HQ behind them.
Machine type, city, photos, brand, model. Vendors publish what they have — not a brochure fleet.
Hourly, daily, weekly, monthly, min hours, operator fee. Visible on the listing before you book.
GST, PAN, RC, insurance, PUC, fitness, licence. HQ opens files on a review screen. S3 keys only in Mongo.
Request, accept, decline, run, complete. Booking number is the trail.
OTP, KYC, booking, promo — BuildRigs APIs over Twilio and Meta. Quotes from this site still work.
Templates never send. Automation composes. A queue consumer delivers.
Customer pays on the hire. Vendor ledger and bank details sit with HQ.
Vendor pings the machine. Customer sees it when tracking is on.
App alerts and promotion banners from HQ, not a vendor SDK.
Vendors assign operators to machines and jobs.
/platform#os
This is the company product. It does not list machines for hire. Talk to us at /contact to start a workspace.
Create the job, assign a manager, health, estimates, status.
Upload a bill of quantities and keep it against the project.
Supervisors, project managers, subcontractors, labour, skills, roles.
Mark-in, mark-out, overtime, guest labour, auto mark-out.
Stock, usage, purchases, used vs bought, inventory.
Move resources between sites. Track tools, hire, misc spends.
Daily progress, delays, refresh when the job slips.
Budgets, expenses, labour payments and due ledgers.
Plan work and assign it to a supervisor.
Project, labour, material, budget, delay reports.
Progress, budget, material, labour charts.
Company users and role permissions — the OS is multi-seat.