Existing systems really solve an extreme user's issues or are too limited in their ability to be flexible to a user's (in this case, my) requirements.
Yeah, going ahead with the no-code/low-code solution seems most plausible.
The challenge is to not over-engineer it and make it an ambit for my own fallacies or lapses in behaviour. Keeping it light, balanced, and focused should be the priority.
I think the emotional side of things can come in a bit later as what I am looking for is that core, objective follow-up and motivation for task completion as well as a progress update on every weekend, month-end, and year-end.
This seems like the most straightforward, practical approach.
I am really considering building my own tools this time but I really wanted to get a feel of what worked for other people. I don't want to be in a situation where I have already committed to build something and halfway through, I find a simple-enough solution that works well.
But yeah, sheets is a great way to think about, probably the most objective.