When working with a potential cofounder, when do you share code?

Question

earlier this year i built an app[1] and an ex coworker hit me up about trying to raise money on it or the idea. i was cool with working on it if we raised money but he's been pressuring me to give him access to the repo so he can make changes. when asked about what changes he'd make there's no response. he's also not really an engineer, so i'm kinda hesitant to just add him. i currently have a pretty detailed Linear board w/issues so i feel like if he wanted to suggest stuff he could add them there.basically, i'm just trying to figure out if i'm the one being toxic or what. i have concerns about how we'd earn revenue and some other things so for all i know it's a fool's errand anyway.you can see the embedded version here in a music forum[2] or scope out the app in general if you'd like to offer feedback, but that's probably not needed.i would def appreciate any feedback or advice! thanks[1] - https://voteballotbox.com [2] - https://whenthemusicstops.net/forums/music/punk-hardcore-post-hardcore/mewithoutyou

collingreen · Accepted Answer

I think you to need to sit down and have a very serious chat with your potential cofounder and figure out what he is thinking about and set some mutual expectations. Starting a company with someone is a huge deal (people compare it to getting married for a reason) so you're hurting yourself if you don't get to the root of this decisively and together.To me, your cofounder's ask is suspicious. On the other hand, execution over time is what builds a business so the worst case of getting betrayed right now isn't really that impactful (and sooner is better if it is going to happen). If you believe 110% in this idea then you can keep pushing it forward regardless.