Still in production · support on demand
Pharmacon
Turnkey ERP for a pharmaceutical plant-solutions provider — procurement through international offers and quotations, local buying, and the ledger. My primary hands-on build of 2018–2019; the client still runs it, with the last support round in 2024.

A procurement-to-ledger ERP the client still runs.
2018 — 2019Primary build
Turnkey plant solutions do not fit a standard sales CRM. A deal begins as a client requirement gathered on a visit, becomes a request to international principals, comes back as offers and quotations that need comparing, gets negotiated and revised, then turns into local buying, billing, and dues that outlive the original conversation by months.
The shape of the business
Before the system, that lived in documents, inboxes, and people's memory.
The ERP made each deal a tracked object with a status, a value, an owner, and a history — which is the difference between a pipeline you can report on and a pipeline you can only ask about.
What the system does
- Client visits and requirement collection. The front of the funnel captured as structured data rather than as a note.
- International offers and quotations. Principal, item, model, and quantity carried through the offer with cost and client-facing value side by side.
- Status-tracked negotiation. An explicit lifecycle — acknowledged, comparison sheet, price revision, head-office finalisation, at risk, closing date, lost, purchase order — with every change user- and time-stamped.
- Local buying and ledger. Purchase, billing, pending-bill calculation, dues and receivables tracked to the deal that created them.
- Nudges on stagnation. Email notifications and reminders on sales workflows that stop moving, so ageing deals surface themselves.
- Permissions and referencing. Module-level access per team, plus dynamic document IDs with stable URLs so a specific offer can be referenced in a conversation.
- Reporting. Module-level and company-level performance in tables, charts, and graphs.
Why it lasted
A system a client is still running six years later, with only on-demand support, is a design outcome rather than a maintenance achievement. It survived because the model matched the business — deals, offers, and ledger entries as they actually exist in a turnkey pharma supplier — instead of forcing the business into a generic CRM shape.
It is also the project where I learned that enterprise software earns trust in the boring places: reliable notifications, permission boundaries people can predict, and reports whose numbers match what the finance team already believes.
Technical highlights
- 01
End-to-end deal lifecycle: visit → requirement → international offer → negotiation → local purchase → ledger.
- 02
User- and time-stamped status history on every offer document.
- 03
Cost / offer / estimated-profit view carried on the deal record.
- 04
Stagnation detection with email reminders on idle sales workflows.
- 05
Module-scoped permissions and stable document URLs for referencing.
- 06
Tabular and graphical reporting at module and company level.
Impact
- Replaced document-and-inbox deal tracking with a reportable pipeline for a major pharma turnkey supplier.
- Still in production years after delivery, with support only on demand (last round 2024).
- Made ageing and at-risk deals visible without anyone having to chase them manually.
By the numbers.
- Procurement → ledger
- One system
- Still running
- Last support 2024
- Offer workflow
- Status-tracked end to end