When someone asks what you do, naming the software first can hide the purpose of the work. A more useful explanation begins with the problem you help resolve and the people who use the result.
Try a three-sentence draft. Describe who needs something, what you produce or improve, and how they use it. Mention tools only when they help the listener understand an important part of the process.
For a fictional example, “I help the team see which requests still need a response” gives a listener a clearer starting point than “I update the spreadsheet.” It also leaves room to explain the judgment involved in checking those requests.
Adjust for the listener
A new colleague may need the handoff points. Someone at a careers event may want to understand a typical task. A manager may need the contribution to a larger objective. Keep the facts consistent while choosing the detail that answers their question.
Avoid inflating routine work into a claim you cannot support. Clear purpose does not require grand language.
Read your draft aloud and remove any acronym you would immediately have to explain. The result should sound like something you could say in a conversation, with enough precision that the listener can ask a useful next question.