> 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/billing-and-payment.md).

# Billing & payment

On Lemon.io’s vetted engineer marketplace, billing runs through pre-paid monthly or weekly subscriptions, processed securely via Stripe — ACH direct debit or credit card. 

Typical hourly rates range **from $60 to $90/hr**, depending on the tech stack, seniority, and scope. All work is billed by the hour; fixed-price projects are not offered.

### Developer engagement types

Developers provided by Lemon.io work as independent contractors. Engagements are ongoing — the same developer can continue on a new project after the first one ends. 

| <p><strong>Full-time</strong></p><p><br></p> | <p>40 hours/week</p><p><br></p>                        |
| -------------------------------------------- | ------------------------------------------------------ |
| <p><strong>Part-time</strong></p><p><br></p> | 20 hours/week                                          |
| **Short-term**                               | <p>From 160 hours (1 position)</p><p><br></p>          |
| **Long-term**                                | <p>Average 8–9 months, often multi-year</p><p><br></p> |

### Developer subscriptions types

Two payment cycles are available:

* **Monthly**, charged on the first Tuesday of each month based on hours reported.
* **Weekly**, charged every Tuesday based on hours reported the previous week.

A prepayment for one billing cycle is collected at the start of the cycle.

<figure><img src="/files/CbJCMvJzGbks5jlboPLw" alt=""><figcaption><p>Subscription management on Lemon.io, client’s side</p></figcaption></figure>

<figure><img src="/files/TGZ1utqVZ6oERdNyKerg" alt=""><figcaption><p>Billing page on Lemon.io, client’s side.</p></figcaption></figure>

### How are subscriptions charged?&#x20;

Subscriptions are prepaid, based on an upfront estimate agreed between a client and a developer (the first week) and then on the developer’s reports.&#x20;

If a developer logs more hours than estimated in a given period, the next cycle is pre-charged accordingly. If they log fewer, the difference rolls over to your balance, and the next estimate adjusts down.&#x20;

**You only ever pay for hours actually worked.**

***Example 1***

A client pre-pays for 40 hours. The developer logs 36. The 4 unused hours roll over, so the following week’s charge covers only 32 hours (36 hours of updated estimate, minus 4 carried over).

***Example 2***

A client pre-pays for 40 hours. The developer logs 46. The next week is charged at 46 hours — as an updated cycle estimation, plus the 6 extra hours worked in the previous cycle.

### How does the rollover work? &#x20;

At the end of each billing period, reported working hours are compared against the hours included in your subscription. **Any unused hours roll over to the next period.**&#x20;

If your project wraps up with unused prepaid hours, you get the money equivalent back.

<a href="https://magic.lemon.io/welcome" class="button primary">Start hiring engineers</a>