Roofing client · Scoring
The situation
A clear idea.
A partly working build.
Ben and I knew each other from our local coffee shop. He’d used AI to prototype daily staff scoring to replace paper records and help calculate commission. A development company was beyond his budget, and he was stuck on staff records, calculations, supervisor access and deployment.
A daily score
- Worker
- Worker A
- Quality
- 4
- Productivity
- 3
- Compliance
- 4
- Teamwork
- 4
What still needed work
Multiple staff. Score calculations. Supervisor access. Deployment.
Workflow design · Front-end · Back-end · Authentication · Deployment
How I helped
I helped put
the pieces together.
Ben and I started with the scoring workflow his team needed first. I connected staff records, calculations and supervisor sign-in, then deployed the app. That meant working across the interface and back end to make the first release usable.
Daily capture
One score, recorded once
- Quality
- 4
- Productivity
- 3
- Compliance
- 4
- Teamwork
- 4
15 daily total
The right staff, the right access
- Worker
- Worker A
- Job
- Roof 12
- Record
- Today
Month-end total
- Earlier scores
- 57
- Today
- 15
72 Worker A
Illustrative story visual · Sample data
Workflow design · Front-end · Back-end · Authentication · Deployment
What changed
A working first release.
A way to keep learning.
The first release let Ben test the workflow with his team, then build on it with quality control and other features. Prototyping with AI had helped him clarify what he needed. Getting the app into use gave him a cost-effective way to test the next idea.
“My supervisors find the app very user-friendly.”
Ben · Roofing business owner
Month-end totals
| Worker | Earlier | Today | Total |
|---|---|---|---|
| Worker A | 57 | 15 | 72 |
| Worker B | 50 | 14 | 64 |
Workflow design · Front-end · Back-end · Authentication · Deployment