What we have learnt, written down
Notes from the work: what things cost, what went wrong, what we would do again. Written by the engineers and consultants who were there, with the numbers we are allowed to share. No summaries of other people's articles.
01
Standard, configuration or custom: the three words that decide your ERP budgetA requirements document that does not mark each line standard, configuration or custom is a quote you cannot compare.
02
Tally to ERPNext: what to migrate, what to leave behindMigrate masters and opening balances. Leave history in Tally unless a regulator needs it in the new system.
03
Why we build custom work as a separate Frappe app, and what happens at upgrade timePatching core is borrowing against your next upgrade at a bad rate.
04
A hospital on ERPNext: a thousand invoices a day, reconciled without a spreadsheetA doctor passcode on lab reports did more for quality than any dashboard.
05
Voice agents in Hindi for supplier follow-ups: what we are designing forBounded scripts and an exception queue beat a clever assistant.
06
Cameras on the dock: choosing between Jetson, Hailo and a GPU serverCamera count, privacy and who maintains the hardware decide where vision runs; the model is the easy part.
07
How our engineers use coding agents, and what stays humanAgents change how fast we reach a first working version, not who is accountable for the code; review stays human and client data stays out of prompts.
08
Frappe as a product platform, not only an ERPEvery DocType is a table, a form, an API and a permission model at once. For record-heavy products, that is most of the first month's work already done.
09
Seven stages, one roll: modelling a film plant in ERPNextEach stage as its own work order, a batch per roll, kg as the unit. Do not let the BOM pretend it is one step.
10
What drives the cost of an ERPNext implementationCost follows process fit, data and people; a quote that does not show how it treated each of them cannot be compared with another.
11
How we run support after go-liveSupport is decided before go-live: by the handover, the documentation and the named people behind the contract, not by the promise on a brochure.
12
Running a 100-outlet purchase cycle from GRN to bank payment on ERPNextThe payout statement is the product. Design for the supplier who reads it.