On the business graph
It reads and writes the same objects as everything else, so it inherits permissions, audit, and dimensional reporting rather than needing its own version of each.
Services
Every business has one workflow that no vendor builds for. It is usually the one that differentiates them, it is currently a spreadsheet, and the person who understands it has been meaning to document it for four years.
Tell us what you need that nobody builds. We will say whether a module fits and what it costs.
Post a coded vendor bill automatically when all of these hold:
The situation
A first-class part of the system, on your data, governed like everything else — not a script bolted to the side.
It reads and writes the same objects as everything else, so it inherits permissions, audit, and dimensional reporting rather than needing its own version of each.
Screens and reports in the same design system, because a module that looks bolted on is a module people avoid using.
Permissions, policy engine, and audit trail apply identically. There is no module-shaped hole in the control framework.
Versioned and carried forward as the platform changes, which is the specific thing handed-over code never gets.
Build quoted at API cost times five with a $5,000 floor, after scoping rather than before. Hosting $250 to $1,000 a month by volume.
Where a module turns out to be useful to others in your industry, we productise it and your hosting fee usually falls.
The modules that work are specific, structured, and recurring. A reconciliation against a bespoke settlement file from an industry clearing house. A compliance register with expiry rules and evidence attached. An allocation formula from a partnership agreement that eleven people currently interpret slightly differently.
A draw schedule with lien waivers. A commission calculation with tiers, clawbacks, and splits. A reorder catalogue that a distributor’s customers use directly. Each of those is a real engagement, and each replaced a spreadsheet that one person maintained.
Attempts to rebuild a mature category. If you need a CRM, buy a CRM — a custom one will be worse, cost more, and never catch up. The same applies to payroll, project management, and document storage.
Also: processes nobody can state the rules for. If four people describe the calculation differently, the module is not the first problem. We will say that at the scoping session rather than after a deposit, and the session frequently ends with a recommendation to settle the rules first.
Customers occasionally ask for the source. We decline, and the reason is not commercial — handed-over code stops being governed. It falls outside the permission model as that evolves, outside the audit schema, outside the regression suite, and outside whoever maintains the platform underneath it.
A year later nobody is sure it still behaves correctly. Two years later the person who wrote it has gone. That is the history of custom ERP development and it is why upgrade projects cost what they do.
A rule that never changes is a policy, not a module. Policies are configured rather than built, cost nothing to host, and do not need maintaining. A surprising share of module enquiries resolve into two policies and a report.
Similarly, a process that runs twice a month with low volume rarely justifies a module. We will tell you when the honest answer is a better spreadsheet with a scheduled export behind it.
Where to start
Ninety minutes with whoever actually runs the process. Free. It ends with a written recommendation, which is sometimes that you do not need a module.
Rules written down, edge cases named, fixed price and hosting fee stated. Ambiguities are resolved here rather than discovered in build.
Three to six weeks, with a working version in front of your team at the halfway point rather than at the end.
Deployed, monitored, versioned through platform changes. Maintenance is the hosting fee, not a change-order relationship.
Questions
The one everyone depends on and one person understands. That is usually the module.