Yes, become a co-founder or act as one by entirely, completely, unapologetically owning the product by going way beyond the distance regular people go: code, ar

Yes, become a co-founder or act as one by entirely, completely, unapologetically owning the product by going way beyond the distance regular people go: code, architecture, features, marketing, UX, the business side of things, the pitch, legal, relations with prospects, knowledge management, documentation, building tooling for colleagues, building deployment pipelines, making it easier for co-workers to do their work, disseminating knowledge, living good engineering practices, enabling colleagues in areas where you're better, simplifying onboarding, training documents, sales copy, story of the product, everything and I mean everything down to the minute details legal documents have or the phrasing of responses to non-pursuit towards job applications. Own everything. As far as I can tell, many things are limited only by the amount of complexity people are willing to handle and the workload they can support. If you're okay pulling a work-day with co-workers and then another one when they leave, then we understand each other. Some people can pull off 16 hour work days or more, even during the week-ends, even during holidays and think about the product all the time. Some are great and can do that in 4 hours, I personally can't. Find things that suck, fix them, institutionalize that knowledge, document everything, prepare for the eventuality of your disappearing, build an organization, train people to think like that, read a whole lot, become good a things, add a lot of value, become someone you would fear if they were a competitor, have very high expectations of yourself and be afraid to disappoint yourself tomorrow, experiment, demonstrate by building things and implementing things, not just as "ideas" but actual outputs, either codes/graphics/copy/documentation/training manuals/videos. Go for it.