labs@atheron:~/industries/staffing/apps$ build app --web --mobile

Staffing apps

A worker app, and a portal where clients place orders.

Staffing platforms sold off the shelf fit a generic agency. We build the worker app, the client portal and the coordinator console around your order types, your clients' rules and your payroll, so an order is filled in minutes and paid without a dispute.

Start a project See the example projects

// what matters here

What is different in this industry.

Orders filled by the right people

Shifts go only to workers whose tickets, experience and availability match, so coordinators stop calling people who cannot take the job.

Hours approved at the site

Supervisors approve hours on their phone at the end of the shift, so the timesheet is settled before anyone goes home.

Expired tickets caught early

Certifications and right-to-work documents carry expiry dates, and workers and coordinators are alerted before a lapse puts someone on site who should not be.

Fits your payroll

Approved hours flow to your payroll and invoicing systems, so the office stops retyping timesheets.

// example projects

Priced examples for this service.

Each one is hypothetical, labelled as such, and priced live from our rate card. Open any of them in the estimator and make it yours.

Example projectWeb appMobile app

Worker app and client portal

Hypothetical. Not a client, not a result.

// The problem

An agency takes orders by phone and email, fills them by calling workers one at a time and collects timesheets on paper from client sites.

// What we would build

An iOS and Android app where workers set availability, accept shifts, clock in on site and keep their certifications current, with a portal where clients place orders and approve hours and a console where coordinators fill and track every order.

// What is in it

Clients place and change orders in the portal, with the requirements for each role
Workers see shifts that match their skills, tickets and availability, and accept in one tap
Clock-in and clock-out at the site, with supervisor approval on the phone
Certification and right-to-work documents with expiry alerts
A coordinator console showing every open order and who has been offered it
Integration with your payroll and invoicing systems

// Stack

Next.js
React Native
PostgreSQL
Payroll system integration
AWS

// estimate

Build: ≈ US$147,000 to US$225,000, delivered within 30 weeksCAD 209,800 to 320,800
Hosting: ≈ US$492 a monthCAD 700 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: 7.4 to 12.9 weeks
Core features: 1.9 to 3.4 weeks
Full build: 1.4 to 2.4 weeks
First build on devices: 3.9 to 6.9 weeks
Testing and fixes: 0.9 weeks
Store submission: 0.9 to 1.9 weeks
Launch: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

App store review: 1 week
API access from your vendor: 1 to 4 weeks

How it is paid

Deposit 20%: CAD 41,960 to 64,160
Discovery 9.2%: CAD 19,301.60 to 29,513.60
Design approved 9.2%: CAD 19,301.60 to 29,513.60
Core features 7.6%: CAD 15,944.80 to 24,380.80
Full build 5%: CAD 10,490 to 16,040
First build on devices 20.1%: CAD 42,169.80 to 64,480.80
Testing and fixes 2.5%: CAD 5,245 to 8,020
Store submission 6.7%: CAD 14,056.60 to 21,493.60
Launch 9.7%: CAD 20,350.60 to 31,117.60
Holdback, 30 days after launch (10%): CAD 20,980 to 32,080

Start from this example

Example projectWeb appBlockchain

Shared timesheet record

Hypothetical. Not a client, not a result.

// The problem

A large client uses several staffing agencies, and hours, approvals and rates are disputed between the client, each agency and the workers when invoices arrive.

// What we would build

A private permissioned ledger where the client and each supplying agency run a node, and every clock-in, approval and rate is recorded once and seen by the parties it concerns. With only one agency and one client, a shared database does the job and we will say so.

// What is in it

A node for the client and for each supplying agency
Clock-ins, approvals and rate changes recorded once and signed
Each agency sees only its own workers and hours
Disputes raised against a specific entry, with its history
Exports to each agency's payroll and the client's accounts payable

// Stack

Hyperledger Besu (private, permissioned)
Next.js
PostgreSQL
AWS

// estimate

Build: ≈ US$108,000 to US$166,000, delivered within 22 weeksCAD 154,200 to 235,900
Hosting: ≈ US$492 a monthCAD 700 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
Architecture: 0.4 weeks
Design approved: 2.4 to 4.4 weeks
Core features: 1.4 to 2.4 weeks
Full build: 0.9 to 1.4 weeks
Devnet: 2.4 to 4.4 weeks
Testing and fixes: 0.4 weeks
Testnet: 2.9 to 3.4 weeks
Launch: 0.9 to 1.4 weeks
Mainnet: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

API access from your vendor: 1 to 4 weeks

How it is paid

Deposit 20%: CAD 30,840 to 47,180
Discovery 2.5%: CAD 3,855.00 to 5,897.50
Architecture 6.7%: CAD 10,331.40 to 15,805.30
Design approved 2.5%: CAD 3,855.00 to 5,897.50
Core features 7.5%: CAD 11,565.00 to 17,692.50
Full build 5%: CAD 7,710 to 11,795
Devnet 20.2%: CAD 31,148.40 to 47,651.80
Testing and fixes 2.5%: CAD 3,855.00 to 5,897.50
Testnet 13.4%: CAD 20,662.80 to 31,610.60
Launch 2.5%: CAD 3,855.00 to 5,897.50
Mainnet 7.2%: CAD 11,102.40 to 16,984.80
Holdback, 30 days after launch (10%): CAD 15,420 to 23,590

Start from this example

// questions

Questions we get about this.

Can clients place orders in the portal?

Yes. Clients place, change and cancel orders, set requirements per role and approve hours, each seeing only their own sites.

Does the worker app track location during a shift?

Only at clock-in and clock-out, to check the worker is at the site, and only if your policy and the applicable privacy law allow it. Workers are told exactly what is collected.

Can the staffing app work across provinces?

Yes. Rules that differ by province, such as overtime thresholds or required documents, are configured per province and per client rather than written into the code.

Back to the industry: HR and staffing About the service: Web and mobile apps

// next

Not quite your project?

Tell us what you have in mind. We will come back to you with a range and the questions that would narrow it. Or book a call and talk it through.

Start a project Book a call