Event systems hub
Hypothetical. Not a client, not a result.
// The problem
A conference organiser copies registrations from the ticketing system into the CRM, the email platform, the badge printer and the accounting system, by hand, before every event.
// What we would build
An integration hub between ticketing, the CRM, the email platform and accounting, so a registration is entered once and reaches each system with the right fields, and a failure is flagged at once.
// What is in it
- Registrations sent to your CRM and email platform
- Badge data ready for printing
- Sales and refunds posted to accounting
- A log of every message, with alerts
- Documented, so a new event tool is easy to add
// Stack
- Node.js
- PostgreSQL
- OpenAPI
- CRM and email interfaces
- DigitalOcean
// estimate
- Build
- ≈ US$43,300 to US$66,200, delivered within 13 weeksCAD 61,600 to 94,200
- 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.4 weeks
- Security, gateway and connections
- 1.4 to 2.4 weeks
- Docs, SDKs and load tests
- 1.4 to 1.9 weeks
- Launch and first callers
- 0.9 to 1.4 weeks
How it is paid
- Deposit 30%
- CAD 18,480 to 28,260
- API contract agreed 7.5%
- CAD 4,620 to 7,065
- Core resources built 22.5%
- CAD 13,860 to 21,195
- Security, gateway and connections 15%
- CAD 9,240 to 14,130
- Docs, SDKs and load tests 7.5%
- CAD 4,620 to 7,065
- Launch and first callers 7.5%
- CAD 4,620 to 7,065
- Holdback, 30 days after launch (10%)
- CAD 6,160 to 9,420