Understand the work first.

From the current process to a working change.

1. Understand the current process

   Who receives the information? Where does it go next? What happens when something is missing? Look at normal work and exceptions.

2. Choose a worthwhile improvement

   Agree which repeated task or delay matters most. Keep judgement with people and automate only where it helps.

3. Check what can be reused

   A better form or a connection between existing tools may be enough. Keep what works instead of replacing everything.

4. Agree scope, then build

   Set the price and a useful first scope before work begins. A small problem can have a small solution; larger work is broken into manageable steps.

5. Test with the people doing the work

   Show working versions early. Try everyday tasks and awkward cases with your team, then correct what does not fit.

6. Arrange care and room to grow

   Agree access, hosting, backups, updates and support where needed. Add users, reports or connections later when there is a clear reason.