Example projectBot with a web dashboard
Crew schedule and safety bot
Hypothetical. Not a client, not a result.
// The problem
Superintendents send start times, site closures and safety alerts to a group chat, with no proof who read them and no translation for crews who need it.
// What we would build
A Telegram bot that sends each worker their own site, start time and safety notices in their language, asks them to acknowledge, and gives the superintendent a record of who has and has not.
// What is in it
- Shift and site changes sent per worker, not to a group
- Safety notices with a one-tap acknowledgement, recorded with the time
- Notices in each worker's language
- A simple screen for superintendents to post changes
- A record of acknowledgements for the safety file
// Stack
- grammY for Telegram
- Node.js
- PostgreSQL
- Translation API
- DigitalOcean
// estimate
- Build
- ≈ US$27,600 to US$42,200, delivered within 9 weeksCAD 39,300 to 60,100
- Hosting
- ≈ US$176 a monthCAD 250 a month
- Support
- ≈ US$1,000 a monthCAD 1,425 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
- Commands agreed
- 1.9 to 2.4 weeks
- Working in a test server
- 1.9 to 3.4 weeks
- Hardening and testing
- 0.5 to 1 weeks
- Launch
- 0.9 to 1.4 weeks
How it is paid
- Deposit 30%
- CAD 11,790 to 18,030
- Commands agreed 15%
- CAD 5,895 to 9,015
- Working in a test server 30%
- CAD 11,790 to 18,030
- Launch 15%
- CAD 5,895 to 9,015
- Holdback, 30 days after launch (10%)
- CAD 3,930 to 6,010