Averil / Sprints

10 days. One real artefact.

The point is not to finish lessons. It is to ship proof. Every sprint ends with something you can use in a resume, a portfolio, a case study, or an interview.

A real sprint, day by day.

10-day customer health dashboard sprint. Built for someone moving from customer-facing work into operations.

sprint · customer-health-dashboard

Build a customer health dashboard in 10 days

day 8 / 10
D1
Foundations
D2
Foundations
D3
Foundations
D4
Build
D5
Build
D6
Build
D7
Deploy
D8
Deploy
D9
Polish
D10
Polish
today · 45 min1 of 1

Pull the dashboard into a weekly team view.

Turn the raw report into something a manager could use in a real weekly meeting. Save the dashboard and the short explanation, both become proof for your profile and outreach.

Every sprint has the same shape.

01

Read just enough

One concept, one source, 5-10 minutes. No theory dump.

02

Do the work

A focused task in 25-40 minutes. Real tools, real output, no filler.

03

Keep the proof

Each day leaves something behind. By day 10, you have a usable artefact.

04

Get unstuck fast

If you spin twice, Averil points you to focused help or a mentor.

Sprints tied to specific gaps.

Not a course library. A short list of focused programs tied to the gap you are actually trying to close.

10 days · 45m / day

Customer health dashboard sprint

For customer, ops, and support people moving toward CS ops or RevOps work.

10 days · 30m / day

SQL reporting sprint

For people who need analysis proof, not another spreadsheet course.

10 days · 30m / day

Cloud deploy sprint

For software engineers moving toward platform and cloud roles.

Don't finish a course.
Ship something.

Pick a sprint tied to your next move. Show up a little each day. Walk out with proof you can use.