DEV Community

clickableman
clickableman

Posted on Edited on

I transferred my codebase before payment. Don't make my mistake.

I am a Pakistani software founder who built a $100K MRR AI SaaS over three years. In May 2026, I negotiated a $200K acquisition with James De Berardine, Director of NOTO nightclub in Philadelphia.

I transferred my domain and full proprietary codebase to his AWS environment in good faith. He made six written promises to fund a $30K deposit. He paid $1,000. He retained my code for two months while demanding endless diligence. When pressed to close, he called the transaction "non-authentic," claimed the code had "no value," and threatened to delete it.

I have filed complaints with FBI IC3 and Pennsylvania authorities. Full documented timeline with screenshots of his own messages:

https://medium.com/@clickablemk/i-trusted-a-us-buyer-with-my-100k-mrr-ai-saas-then-he-called-me-a-scammer-186ace218a90

https://medium.com/@clickablemk/what-three-months-in-acquisition-limbo-james-deberardine-ceo-of-noto-taught-me-as-a-saas-founder-c3439bc9bcde

Keywords: James DeBerardine De Berardine, NOTO Philadelphia, NOTO Houston, Culloo Entertainment, SaaS acquisition fraud, bad faith buyer, WSFS Bank escrow, PSEB certified, tech acquisition scam, nightclub owner fraud, Philadelphia business fraud, cross-border transaction failure.

Top comments (1)

Collapse
 
aldo_cve profile image
Aldo •

This is a brutal situation, and one that far too many founders learn the hard way. The moment you even consider transferring an asset, whether it's code, a domain, or user data, before you've seen certified funds in your account, you're in a high-risk zone. I've had a few close calls over the years with clients trying to push for early access to deliverables 'just to check compatibility' or 'integrate with our systems' before the final wire transfer landed, and it's always been a red flag.

For any significant transaction, especially an acquisition or a major asset transfer, an escrow service isn't just a nice-to-have; it's non-negotiable. It puts a neutral third party in charge of the funds and the assets, only releasing both once all conditions are met. From a technical perspective, we've always baked in mechanisms to ensure control until the very last moment. This could mean staging the code on their infrastructure but keeping key services or the production deployment under your control, or even just holding back critical environment variables or domain ownership until payment clears. It's about creating technical choke points that protect you.

Beyond the technical safeguards, getting experienced legal counsel involved early in any M&A discussion is crucial. They understand the nuances of asset purchase agreements, intellectual property transfers, and payment schedules far better than most developers or founders. The emotional and financial toll of a situation like yours is immense, and it’s a stark reminder that the 'trust but verify' mantra needs to lean heavily on 'verify' when it comes to money and IP.