Alarm and access data, joined up
Hypothetical. Not a client, not a result.
// The problem
An alarm monitoring firm keeps signals in its monitoring software, access events in two access-control systems and contracts in its billing system, and builds every invoice and client report by hand.
// What we would build
An integration hub that reads signals, events and accounts from each system through its published API, joins them by site and client, and passes billing events and report data on to your billing system and client portal. It reads only: it never arms, disarms or unlocks anything.
// What is in it
- Read-only connectors to your monitoring and access-control systems
- Signals and events joined by site and client
- Billing events passed to your billing system
- Webhooks for the client portal and reports
- Monitoring and alerts when a connector stops
// Stack
- Node.js
- PostgreSQL
- OpenAPI
- Vendor APIs
- DigitalOcean Toronto
// estimate
- Build
- ≈ US$50,400 to US$77,000, delivered within 14 weeksCAD 71,700 to 109,700
- Hosting
- ≈ US$176 a monthCAD 250 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
- API contract agreed
- 2.9 to 3.9 weeks
- Core resources built
- 2.4 to 3.9 weeks
- Security, gateway and connections
- 1.4 to 2.9 weeks
- Docs, SDKs and load tests
- 1.4 to 1.9 weeks
- Launch and first callers
- 0.9 to 1.4 weeks
Outside our hands, and added to the calendar
- API access from each system's vendor
- 1 to 4 weeks
How it is paid
- Deposit 30%
- CAD 21,510 to 32,910
- API contract agreed 7.5%
- CAD 5,377.50 to 8,227.50
- Core resources built 22.5%
- CAD 16,132.50 to 24,682.50
- Security, gateway and connections 15%
- CAD 10,755 to 16,455
- Docs, SDKs and load tests 7.5%
- CAD 5,377.50 to 8,227.50
- Launch and first callers 7.5%
- CAD 5,377.50 to 8,227.50
- Holdback, 30 days after launch (10%)
- CAD 7,170 to 10,970