Inbound control tower
Hypothetical. Not a client, not a result.
// The problem
A distributor tracks purchase orders, supplier confirmations and inbound containers across the ERP, carrier websites and a spreadsheet, so a slipped vessel is found when customers start calling.
// What we would build
A web control tower that joins ERP purchase orders, supplier confirmations and carrier and port milestones into one view per order, with alerts when a promised date slips and a list of the customer orders it puts at risk.
// What is in it
- Every open purchase order with its supplier confirmation and inbound shipment
- Carrier, port and container milestones pulled from their APIs and EDI
- Alerts when a promised date slips, naming the customer orders affected
- Supplier scorecards on confirmations and on-time delivery
- Planner notes and decisions kept against each order
// Stack
- Next.js
- PostgreSQL
- EDI (X12 and EDIFACT)
- Carrier and port tracking APIs
- Microsoft Azure
// estimate
- Build
- ≈ US$95,000 to US$145,000, delivered within 20 weeksCAD 135,300 to 206,900
- Hosting
- ≈ US$751 a monthCAD 1,070 a month
- Support
- ≈ US$2,500 a monthCAD 3,565 a month
Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.
Timeline by milestone
- Discovery
- 2.9 to 3.4 weeks
- Design approved
- 3.4 to 5.4 weeks
- Core features
- 2.9 to 4.9 weeks
- Full build
- 1.9 to 3.4 weeks
- Testing and fixes
- 0.9 to 1.9 weeks
- Launch
- 0.9 to 1.4 weeks
Outside our hands, and added to the calendar
- Data access from each system's owner
- 1 to 4 weeks
- Supplier EDI testing
- 2 to 6 weeks
How it is paid
- Deposit 20%
- CAD 27,060 to 41,380
- Discovery 7.7%
- CAD 10,418.10 to 15,931.30
- Design approved 7.7%
- CAD 10,418.10 to 15,931.30
- Core features 23.3%
- CAD 31,524.90 to 48,207.70
- Full build 15.5%
- CAD 20,971.50 to 32,069.50
- Testing and fixes 7.7%
- CAD 10,418.10 to 15,931.30
- Launch 8.1%
- CAD 10,959.30 to 16,758.90
- Holdback, 30 days after launch (10%)
- CAD 13,530 to 20,690