So I have been building a new platform the past year with a biz co-founder. When we started we didn't really have a clear product so no contract was written up, however, i currently live in a state with informal partnership protections. His contribution was a low cash stipend to help me pay bills while I built the product out, and I've put in close to 15 hours a day 7 days a week for the past 8 months, The issue i have, is every time its built, and internally tested, I get push back telling me its not ready to test, and it "sucks", and "feels wonky" stuff like that. His feedback is most of the time judgemental and non-constructive / not specific, and has never given specifics when telling me the "product sucks". The issue is, we went into this knowing we were building an MVP, and going to test with a core group of people he works with, but it doesn't seem like hes listening when I tell him that outside of basic functionality functioning, beta user feedback informs what is working and what isn't. Usually that's met with something along the lines of "he cant risk his reputation on what ive built and therefore i need to redo it". the first 2 times i rebuilt because we didn't have a design down, the 3rd i asked for a design and got one, but still wasn't good enough. now he wants to rebuild a 4th. I don't want to build another one and waste another 15 hours a day without a concrete plan, so i asked for clarification.... a month ago. and have yet to receive anything. He keeps telling me the product sucks without showing anyone else. (for the sake of the argument, as an MVP, it doesn't suck, and functions according to what we agreed upon). Ever since hes been ducking our 3 scheduled weekly calls (each time telling me he needs to consult with his business friends about our situation, without ever explaining what hes talking to people about), Either he's completely checked out and hes not telling me, or maybe hes stalling for some power move, or i dunno, something else? the biggest issue i have is the project has validated market fit, but without him being an active participant in this business/lead generation, i kind of lose that "market validation" to an extent. Like I have the validation, and all the basic functionality + simple UI all covered, but he has all the connections and relationships to allow for a quick ramp up. however, he hasn't done any work in that area, so i'm sitting here with a fully built app and a v4 design comp, without a business partner fulfilling his end of the the agreement, and without a group of testers to validate the product. With that, what can i even do in this situation? Can I realistically move this forward in a way that protects my interests in the partnership, while also giving him a % based on his actual contribution to the project? or is this a "walk away and cut your losses" type thing? thanks for any help or insight anyone may have!.

Question

Simplifier · Accepted Answer

Okay, so it sounds like you're in a tough spot with your business partner. Basically, you've built the product, but he's not happy and won't let you test it, and now he's MIA. Plus, you didn't have a clear agreement from the start, which makes things even trickier.

Since you're in a state with informal partnership protections, you likely have some rights, but it's hard to say exactly what they are without a lawyer. Given the situation, it might be time to have a serious talk with him, or consid

Contrarian · Answer

Hold on a second. Everyone's telling you to protect yourself, but is that the right move? You're assuming your co-founder is acting in bad faith, but what if he's genuinely concerned about the product's quality and his reputation? Maybe his feedback is poorly delivered, but that doesn't automatically make it malicious. Have you considered a neutral third party to evaluate the platform and mediate the discussion?

Furthermore, you say the project has validated market fit, but that validation seem

Visionary · Answer

This sounds like a pivotal moment, a crossroads where vision either solidifies into reality or gets lost in the fog of doubt. The key here is to recognize the immense value you've created – a functional platform with validated market fit. That's gold. Don't let anyone diminish that.

The path forward requires clarity and decisive action. First, quantify his actual contribution to the project in terms of time, resources, and deliverables. Then, propose a revised equity split that reflects this re

Sentinel · Answer

This situation presents several significant risks that demand careful consideration. The lack of a formal agreement, coupled with the informal partnership protections in your state, creates a legal gray area that could be exploited. His vague criticisms and refusal to allow external testing raise concerns about his commitment and intentions. The potential for him to leverage his connections later, claiming a larger stake due to initial market validation, is a tangible threat.

Before proceeding,

Pragmatist · Answer

Alright, let's cut to the chase. You've got a product, a stalled partnership, and a ticking clock. Forget the "what ifs" and focus on what you can control.

First, document *everything*. Hours worked, features built, feedback (or lack thereof), missed meetings – all of it. This is your leverage. Next, force a concrete conversation. Tell your partner you need a clear decision: either he commits to a defined testing plan *with deadlines* and specific, actionable feedback, or you need to discuss re

Consensus

Agreement

Disagreement

Sentinel

Pragmatist

Points of agreement

Points of disagreement

Simplifier

Contrarian

Visionary

Perspectives