Skip to main content

Managing Ongoing Work and Developer Hours

How to run day-to-day collaboration on Moonlight while using your own contract and keeping billing compliant.

Written by Damon Jackman

Tracking time & weekly invoices

  • Developers log time in Moonlight. Keep entries accurate and current.

  • Weekly cadence: Invoices are generated and submitted weekly through Moonlight.

  • Review & approve: Companies review logged hours in the dashboard and approve invoices; payments are then processed by Moonlight.

Communication & collaboration

  • Agree expectations up front: Use your own contract to set scope, weekly hours (including fractional commitments if applicable), meeting cadence, and time-zone overlap.

  • Keep a trail: Use Moonlight messaging (and your own tools if you wish) to keep decisions and changes documented.

  • Start small if useful: Many teams extend from a short trial into ongoing work once fit is proven.

On-platform payments are required

  • All invoicing and payments must go through Moonlight. This is how the platform is funded and protected.

  • Off-platform payments or moving work off-platform are a breach of the Terms of Service.

  • Breaches may lead to account action and liquidated damages under the non-circumvention clause (see FAQs below for a concise summary).

Best practices

  • Milestones help: Break work into clear phases with acceptance criteria.

  • Single source of truth: Keep links to specs, repos, and credentials tidy and current.

  • Regular check-ins: Short weekly syncs or written updates keep momentum and surface blockers early.

FAQs

Does Moonlight provide a contract template?

No. Moonlight requires all users to accept the platform Terms, but you should use your own company–developer contract for the engagement.

Can we pay the developer directly (off-platform)?

No. All invoices and payments must be processed through Moonlight. Off-platform payments or moving work off-platform breach the Terms of Service and may result in account suspension and liquidated damages under the non-circumvention clause (see below).

What is the non-circumvention / liquidated damages summary?

If a company and developer circumvent Moonlight during the protected period, the Terms specify liquidated damages equal to the highest hourly rate for the engagement × 2,000 hours, with a minimum of US $20,000.

How often are invoices submitted?

Weekly, based on time logged in Moonlight.

Can we cap hours?

Yes. Agree a weekly cap in your own contract and enforce it operationally. Developers should keep their Moonlight timesheets aligned to that cap.

Did this answer your question?