Handing it over without looking disorganised

You built something real with AI help, and now you need a developer to take it further. Maybe you're adding a feature that's too complex to prompt your way through. Maybe something broke and you can't fix it. Whatever the reason, you're about to pay someone money, and you're worried they'll open your project and laugh. They won't. Every developer who works with AI-built projects has seen worse than yours. Here's how to hand it over well.

Say plainly that AI wrote it

Don't hide this or apologize for it. Tell the developer up front: "I built this with Claude Code" or "This came from Lovable" or whatever tool you used. A good developer needs this to know what to expect. Some AI tools generate messy file structures. Some skip error handling. Some duplicate code instead of reusing it. Knowing the tool tells them where to look first. Hiding it just wastes their time figuring out what they could have known in the first minute.

What to hand over, exactly

Developers can't help you with vague access. Send everything on this list before the first call if you can.

• Code access. If your code lives in GitHub, GitLab, or similar, add them as a collaborator. If it only lives inside an AI tool's project, export it or invite them into that project directly.
• Hosting login. Wherever your site actually runs. Vercel, Netlify, Render, Railway, whatever it is.
• Database login. Separate from hosting. Include the database name and which provider it's on.
• Environment values. These are the settings and secret keys your app needs to run, like API keys for payment or email tools. Send them through a password manager's share feature or an encrypted note, never in a plain chat message.
• Domain registrar login. Wherever you bought your domain name. GoDaddy, Namecheap, Cloudflare, or similar.
• A written what-works-what-doesn't. A short document. List the features that work, the ones that are half-built, and anything you already know is broken. This alone can save hours of the developer poking around blind.

You don't need to understand any of these systems to hand them over. You just need to find the login pages and share access. If you're not sure where something lives, ask your AI tool to show you, using a prompt like the one below.

What a fair first task looks like

Don't start with your biggest, scariest feature request. Start small and specific. A fair first task is something that:

• Can be finished in a few hours to a couple of days, not weeks.
• Has a clear "done" state you can check yourself, like a button that works or a page that loads.
• Doesn't require the developer to redesign your whole app first.

Good first tasks: fix a broken form, add a missing page, clean up one messy part of the database. This lets you see how they communicate and how they price their time before you commit to anything larger.

After the engagement ends

When the work is done, and whether it went well or not, rotate every credential you shared. That means generating new passwords and new API keys for hosting, database, environment values, and the domain registrar. Remove the developer's collaborator access from your code repository too. This isn't about distrust. It's standard practice any time someone outside your circle has had access to systems that touch money, user data, or your domain. A developer who does this work regularly will expect it and won't be offended.

Plyo keeps version history and a one-click undo for AI-built projects, which can make this whole handoff easier since a developer can see exactly what changed and when.

None of this requires you to understand code. It just requires you to be organized and honest about where things stand. That's the whole job.