Our current delivery stack
Where a client has no existing platform commitment, these are what we reach for, because we can take them to go-live quickly and hand them over without a licence dependency.
Frappe and ERPNext
ERP, CRM, inventory, manufacturing and warehouse modules on an open framework we can extend without forking.
Medusa
Headless commerce where the storefront needs to read the same stock ledger the warehouse works from.
The integration layer
Built as its own component with APIs, events, monitoring and runbooks, so a platform underneath it can be replaced.
We work to what you own
Plenty of clients have already bought something, or have a group standard they cannot deviate from. In that case the platform is an input to the plan, not a decision to revisit.
ERPNext implementation
How we scope, configure and hand over an ERPNext rollout, and when we would tell you it is the wrong platform.
Read the pageMigrating to ERPNext
Moving from Tally, a legacy ERP or spreadsheets. Audit, masters, balances, open transactions, in that order.
Read the pageMedusa.js commerce
Headless commerce wired to the stock ledger the warehouse works from, and when hosted is the better answer.
Read the pageWhy we keep this page separate
A practice that leads with a product ends up recommending that product. We would rather the operation decide. As the practice grows we expect this list to grow with it, including toward the tier-one supply chain platforms, and none of the rest of this site should have to change when it does.
