Software built around the actual job
Sometimes the right answer is not another website. A project may need a desktop application, an internal tool, a small automation system, or an integration that handles a repeated workflow reliably outside a browser.
I start with what goes in, what decisions the software needs to make, what should come out, and what happens when something fails. That keeps the scope connected to the real problem instead of turning it into a long feature list nobody asked for.
From the main feature to the unglamorous details
The interface is only one part of custom software. Local state, validation, credentials, errors, installation, updates, and the way a result is verified all affect whether the product is useful. I treat those as product work, not cleanup for later.
SoctuKit is one example: a native Windows workspace for user-directed social-media automation, including scheduled posts, likes, comments, and replies.
The UIU Discord Bot is another: Python automation that retrieves university notices, avoids duplicate posts, and keeps useful information inside a Discord community.
A good first message
Tell me what the current workflow looks like, who uses it, what is repeated or missing, what systems it needs to connect to, and what a successful result should look like. That is enough to start a useful conversation.