> For the complete documentation index, see [llms.txt](https://docs.lemon.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lemon.io/for-developers/30-days-of-engagement.md). # 30 days of engagement The first engagement runs as a formal trial period — four weeks of paid work, up to 160 hours. It is structured and carefully monitored by Lemon.io’s Client & Developer Experience team. **Day 1–2** A developer is introduced to the client via email, given access to repositories, tools, and documentation, and assigned a clear first task. The client is expected to provide full context — the faster you become an individual contributor, the better. **Day 3** The Client & Developer Experience team conducts check-ins for both sides — a safety net to catch access issues, unclear expectations, or early friction before they become problems. **End of Week 1** A developer submits their first timesheet. Both sides complete a quick survey. Any “off” signals are caught and addressed immediately. **Weeks 2–3** You are expected to be delivering real value. The Client & Developer Experience team monitors progress through feedback forms. **Week 4** Both sides complete a closing survey. If the engagement continues, it rolls forward seamlessly. If not, the transition is handled cleanly with no outstanding issues. The trial is not free — a developer are paid your full hourly rate from day one. **The payments are made monthly.**