How to identify your first Power Platform pilot
The first automation project sets the tone. Pick something too big and it stalls; too trivial and nobody cares. A good first pilot is small, painful and visible — and you can score candidates objectively.
What makes a good first pilot
You want a process that is repetitive and rules-based, owned by someone who feels the pain, low-risk if it needs iterating, and visible enough that success is noticed. Avoid anything mission-critical or politically fraught for a first outing.
The pilot scorecard (template)
Score each candidate process 1–5 on these criteria. Add them up — the highest total is usually your best first pilot.
Copy this into a sheet and score 3–4 candidate processes
| Criterion | Score 1–5 | A 5 looks like… |
|---|---|---|
| Frequency | __ | Happens daily or many times a week |
| Manual effort | __ | Eats real, measurable hours |
| Rules-based | __ | Clear logic, little judgement needed |
| Low risk | __ | Safe to iterate; no harm if v1 is rough |
| Clear owner | __ | One person who wants it fixed |
| Visibility | __ | Success will be obvious to others |
| Data ready | __ | Inputs already structured or easily made so |
Reading the score
Interpreting the totals
- 28–35: an excellent first pilot — start here
- 20–27: workable, but tighten the scope first
- Below 20: pick a different process for your first outing
- Any single 1 on "Low risk" or "Clear owner": think twice
A high-scoring pilot gives you a fast, visible win — proof that builds the confidence and goodwill to tackle the bigger processes next.
Want this applied to your business?
A free 30-minute automation review turns any of these ideas into a costed plan for your own processes.