BuildSuite Platform
BuildSuite Platform is the open-source foundation: Frappe, ERPNext and BuildSuite Core, plus whichever modules a contractor actually needs. Your own IT team — or any Frappe partner — extends it into the exact system a client runs on. No forking, no per-seat licence, no vendor in the middle of your roadmap.
Your app sits on top · base apps stay upgradeable
The stack
Every layer is open source and independently maintained. You inherit the accounting engine, the construction domain model and the framework — and write only what is genuinely specific to your client.
What you can change
Add a Subcontractor Bill Certificate, a plant log, a QA checklist. Custom fields on existing doctypes survive upgrades because they live in your app, not in a patched core.
Approval chains that match the client’s delegation matrix — by value, by project, by role — configured, not coded.
RA bills, measurement sheets and client reports on their letterhead, in the format their QS already signs.
Validation, auto-calculation and posting rules in Python and JavaScript, versioned in your repo.
Row-level rules per project, site or company — so a site engineer sees their site and nothing else.
Every doctype is a REST resource. Push to Tally, pull from a biometric device, sync a bank file — without waiting for us.
The rule that matters
Forking the base apps wins the first month and costs you every upgrade after it. A separate custom app gets the same power and stays mergeable — which is why every serious Frappe implementation is built this way.
Frappe, ERPNext, BuildSuite Core and the construction modules — tested together, released together, on GitHub in the open.
One app, holding your client’s doctypes, scripts, print formats and integrations. Usually a few thousand lines, not a fork of half a million.
Who builds it
Nothing here is gated. Whoever does the work gets the same source, the same docs and the same repos.
A contractor with Python developers can clone the repos, stand up a bench and build their own app. We publish the domain model and the docs; you are not waiting on our roadmap.
Any Frappe or ERPNext partner can implement BuildSuite for their client and keep the relationship. The construction domain is already modelled, so the engagement starts at configuration rather than at zero.
If you would rather not staff it, we implement, host and support it — on exactly the same open codebase, so you can take it in-house or move to a partner later.
What ships already
These are the construction primitives you would otherwise model yourself. Take all of them, take one, or replace any of them with your own.
Ledger coded to project and cost code. Retention, WIP, advances, RA bills and subcontractor recoveries as first-class records.
Bills of quantities off a controlled rate master, versioned, convertible into a client quotation.
Subprojects, work packages, stages and tasks, with daily progress and delays logged from site.
Material requests through approval to receipt, unmatched receipts flagged, stock tracked per site.
Gang attendance, overtime slabs, payslips and WPS bank files in your bank’s exact fixed-width format.
Daily, weekly and monthly reports on your letterhead, generated from site data, exportable to PDF.
Deployment
Hosting, backups, updates and support. Most firms choose this.
Dedicated instance where data residency rules require it.
Clone the repos and run it yourself. Free, unlimited users.
Get started
The whole platform is on GitHub under the MIT licence. Stand up a bench, read the domain model, and decide whether it is worth building on — then talk to us or to a partner.
