Verdict

“The success of this venture hinges on navigating the legal and contractual complexities surrounding the software's ownership and the sys admin's employment situation.”

The idea has potential, but its feasibility is heavily dependent on the specifics of the employment contract and the technical details of the software. The fact that the software was developed outside of company time and without a clear agreement on ownership is a positive factor. However, the plan to leverage this software to negotiate with the current employer is risky and could lead to legal disputes. The technical aspect of being able to pull the application layer or move it to the cloud is feasible given the sys admin's access and control. Nevertheless, this could be met with resistance or legal action from the employer, potentially complicating the transition. The timeframe of 4-12 weeks for a solo or 2-person team to build v1 is somewhat ambitious, considering the existing software is already functional and has been sold to other companies. The main task would be to refine or adapt the existing software rather than building it from scratch. The key challenge lies not in the technical feasibility but in the legal and business risks associated with the plan.

“Your leverage is real, but legal exposure could destroy value - secure IP ownership first.”

Your venture has strong revenue potential due to proven demand (sales to other companies) and a unique, problem-solving product in a niche industry. The pricing leverage is high - you can charge a premium (e.g., annual licensing at 20-30% of client cost savings) or even a one-time buyout (your proposed 'year's salary' is conservative; aim for 3-5x given the dependency). Channels are organic (word-of-mouth) but could scale via industry partnerships or direct sales. Gross margins are likely >80% (SaaS-like, with minimal COGS). However, legal risk is critical: even without a signed IP agreement, employment law may grant your employer partial rights if the software was developed using their resources (e.g., hardware, data, or time). Mitigate this by consulting an IP attorney *before* confronting them. Your threat to revoke access is powerful but ethically/legally risky - better to negotiate a clean exit with IP ownership or a spin-off. Cloud migration improves control but adds hosting costs (~10-15% of revenue). Unit economics are strong if you can avoid litigation and scale sales.

“Unresolved IP ownership and a high-risk exit strategy threaten the venture's viability from the outset.”

The venture is highly vulnerable due to unresolved intellectual property (IP) ownership, a confrontational exit strategy, and dependency on a single, hostile entity. Despite developing the software outside work hours and without a signed IP agreement, the employer might still claim rights, especially if the software integrates with or enhances their core systems. The ultimatum approach ('substantial raise or quit and pull the software') is risky; the employer could call the bluff, leading to immediate loss of current sales channel and potential legal action. Furthermore, the plan's success heavily relies on the employer's reaction, which is unpredictable given their described toxic behavior. Churn is not a primary concern here due to the software's reported success, but platform risk (dependence on the current infrastructure/access) and regulatory risks (potential IP disputes, employment law violations) are critical. No-budget customers are less relevant as the software apparently attracts paying clients.

“Ownership of the IP and exclusive control over distribution give the venture a rare, defensible edge, but legal challenges and reliance on a single access point could undermine its durability.”

The venture targets a specific industry pain point that appears unsolved by existing solutions, giving it a clear first - mover advantage. Because the software was created outside of the employer's scope of work and there is no explicit IP assignment, the founder likely retains ownership, enabling independent commercialization. The ability to control distribution via an SSH key and potential cloud migration further creates a barrier for competitors who would need equivalent access mechanisms. However, the differentiation is not absolutely durable: the employer could contest ownership, initiate litigation, or leverage its control over the underlying infrastructure to replicate or block the service. Additionally, the market may be served by generic automation platforms (e.g., UiPath, Automation Anywhere) or custom consulting solutions that could adapt to the same niche, eroding the uniqueness over time. The founder's leverage - threatening to withdraw the application layer - relies on a single point of failure (the SSH key) and on the employer's lack of technical expertise, which could be mitigated if the company hires or outsources IT. Overall, the idea shows strong, defensible differentiation today, but its durability hinges on legal clarity and the sustainability of the access controls.

“Your software's value lies not in holding your employer hostage, but in becoming the industry-standard solution they're too incompetent to build themselves.”

The core idea has strong market potential: you've built a proprietary solution that solves a real, unmet need in a specific industry, and it's already gaining traction outside your employer. This indicates genuine demand and a viable product-market fit. Your technical control over the software (SSH access, cloud migration capability) gives you leverage - but your proposed extortion tactic (threatening to shut down their system) is legally and ethically perilous. Even if you didn't sign an IP agreement, using software developed *on company time or using company resources* (even indirectly) could still be contested in court, especially if the system integrates with their infrastructure. Your leverage is real, but the threat undermines your credibility and exposes you to counter-suits for sabotage or breach of duty. A better path: exit cleanly, take the IP (if legally defensible), and commercialize it independently. You already have paying customers - that's the real validation. The audience is likely niche but high-value: companies in your industry suffering from the same pain point, who would pay for a reliable, secure, supported solution. If you can document the problem's cost (downtime, inefficiency, compliance risk), you can price aggressively. The market size depends on industry vertical, but if even 50-100 companies pay $10k - $50k/year, you're looking at a $500k - $5M ARR business. Your credibility as a founder hinges on ethical execution. Don't burn bridges; build a company.