The verdict in three sentences
For a Singapore group with 8 subsidiaries and 2,000 suppliers, a custom sourcing and supplier portal costs roughly 250,000 to 550,000 SGD, plus 60,000 to 120,000 SGD for an SAP connector. Savings on spend that goes through competitive sourcing typically land between 4 and 8%, which pays the project back within one to two years from about 12 million SGD of sourced spend. The most durable benefit is traceability: every decision is timestamped, justified and auditable.
What a group loses by sourcing over email
Many mid-sized Singapore groups still run RFQs through email and spreadsheets. Each subsidiary keeps its own supplier list, bids arrive in mixed formats and comparison is manual. The result: fewer suppliers invited, the same negotiation repeated across entities, and a weak audit trail when the audit committee or external auditors ask questions.
Scope of an e-procurement portal
| Module | Key features | Indicative budget (2026 ballpark, SGD) |
|---|---|---|
| Supplier master | Self-registration, UEN check, ACRA documents, certifications, categories | 40,000 to 80,000 |
| RFQ and tenders | Specs, lots, Q&A, deadlines, sealed bids | 60,000 to 120,000 |
| Automatic bid comparison | Price and technical scoring, weighting, ranking | 40,000 to 100,000 |
| Approval workflow | Routes by amount and entity, delegations, sign-off | 35,000 to 80,000 |
| Supplier performance | Quality, lead time, compliance scores, history | 25,000 to 60,000 |
| Procurement dashboards | Savings, cycle time, competition rate | 25,000 to 80,000 |
| SAP connector (MM, vendor master, POs) | Automatic PO creation after award | 60,000 to 120,000 |
A first release around 250,000 SGD usually covers supplier master, RFQs, comparison and a simple workflow. The top of the range adds supplier performance, advanced dashboards and full multi-entity support.
Custom vs SAP Ariba and Coupa
| Criterion | SAP Ariba or Coupa (2026 ballpark) | Custom portal |
|---|---|---|
| Upfront cost | Implementation 150,000 to 400,000 SGD | 250,000 to 550,000 SGD |
| Yearly cost | Subscription 120,000 to 400,000 SGD | Hosting and maintenance, 15 to 20% of build |
| Fit with local requirements (UEN, GST, PDPA) | Configurable | Built in |
| Spend analytics and supplier network | Very strong | Focused on your needs |
| SAP integration | Native with Ariba | Built, 60,000 to 120,000 SGD |
| Timeline | 6 to 12 months | 5 to 7 months |
Ariba and Coupa are powerful and bring large supplier networks, but they are sized for much larger spend. For a mid-sized group, the yearly subscription often eats a large share of the savings.
Running the project without stalling procurement
Rollout works best when it starts with one pilot subsidiary and two or three high-volume categories, for example facility maintenance, MRO supplies and logistics. For 6 to 8 weeks, buyers use the portal in real conditions, suppliers report friction and the approval workflow is tuned. Three indicators are enough to steer: average number of suppliers invited per RFQ (target 3 to 5), time from requisition to award (often cut by 30 to 40%), and the share of spend going through sourcing. The contract should include source code ownership, full documentation and 12 months of support after go-live. Keep a single procurement owner per subsidiary to validate category trees and approval thresholds.
Pitfalls that derail procurement projects
First pitfall: trying to cover everything in release one. A clean supplier master and smooth RFQs already deliver most of the savings. Second pitfall: approval chains with five or six signatories, which stretch cycle times and push buyers to bypass the tool. Aim for three levels at most, set by amount. Third pitfall: neglecting data quality when importing subsidiary files, where the same supplier often appears under three different legal names. Plan two to three weeks of deduplication before go-live, using the UEN as the unique key.
Finally, budget for change management: a half-day training per buyer, a supplier help page in English and Chinese if needed, and a monthly review of savings with the CFO during the first year.
Mini case study
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
Wei Ling, head of procurement at an industrial group in Singapore, manages 50 million SGD of spend a year, 25 million of which would go through formal sourcing on the portal.
- Investment: portal 380,000 SGD + SAP connector 90,000 SGD = 470,000 SGD.
- Conservative 5% saving on 25 million SGD sourced: 1,250,000 SGD per year.
- Maintenance at 18% of build: about 85,000 SGD per year.
- Year 1 net gain: 1,250,000 - 85,000 - 470,000 = 695,000 SGD.
Even at a 3% saving, 750,000 SGD, the project pays back in under 10 months after go-live.
FAQ
How long to roll out across 8 subsidiaries?
Plan 5 to 7 months: 6 weeks of scoping, 3 to 4 months of development, then entity-by-entity rollout over 4 to 6 weeks.
How do we get 2,000 suppliers on board?
A registration campaign with a deadline and a 'no registration, no RFQ' rule typically reaches 70 to 80% of active suppliers within 3 months.
Is the SAP connector essential?
Not at launch, but without it POs are re-keyed. It costs 60,000 to 120,000 SGD and removes double entry from the first release.
Where do the 4 to 8% savings come from?
From inviting 3 to 5 suppliers instead of 1 or 2, pooling volumes across subsidiaries and transparent bid comparison.
Does the portal comply with the PDPA?
It must: data hosting, supplier consent and retention rules under Singapore's Personal Data Protection Act are part of scoping.
Let's scope your project. Share your subsidiaries, spend volume and ERP, and we will define releases, the connector and a rollout schedule. Detailed quote within 48 h. WhatsApp +221 77 596 93 33.
Mohamed Bah
Fondateur, Kolonell
Passionate about digital and entrepreneurship in Africa, Mohamed has been helping Sénégalese businesses with their digital transformation since 2020. Founder of Kolonell, he believes every SME deserves a professional and accessible online présence.
