---
title: "Take the first real job"
url: https://services.dev/docs/start/live
---
# Take the first real job

URL: https://services.dev/docs/start/live

> Connect Stripe, deploy live on your builder.domains address, and take a paid order. What test kept, what live changes, and the first payout, yours and each member's.

Everything you built in test runs the same way live. Three commands stand between `dev` and a buyer's money: connect Stripe, deploy, and take the first order.

## Connect Stripe

```txt
$ npx services.dev connect stripe
  opens   https://connect.stripe.com/setup/s/lingua · sign in, or open the account
  account acct_1Q7Hq2 · lingua · charges on · payouts on
✓ connected · every charge, refund and payout runs on your own Stripe account
```

Charges and refunds run on your Connect account, under your brand's name on the buyer's statement. services.dev's take is one line on that ledger, taken only when a charge releases.

## Deploy live

```txt
$ npx services.dev deploy --live
lingua · 4 Services · version 2026-10-27.1
  live    https://lingua.builder.domains · api, mcp, cli, sdk, site, docs and every app
  keys    live keys are minted in the owner console, at /console/keys
  plan    Free (services.dev) · no gated key
```

Every check it makes, and what happens to jobs already running, is on [Deploy](https://services.dev/docs/operate/deploy.md). Free serves every surface and app on `<brand>.builder.domains`. Your own domain is one line in `brand.ts`, `domain: 'lingua.example'`, on Launch. A gated key runs three paid live jobs first; after that, `deploy --live` answers OFFER with the plan it needs and the line that needs it:

```txt
$ npx services.dev deploy --live
OFFER · Launch runs this Service live.
  because roles.translator.pool at services/translation.ts:6 · 3 of 3 sampled jobs released
          subject at services/translation.ts:13 · 1 of 3 sampled jobs released
          clocks.renewal at services/translation.ts:14 · 1 of 3 sampled jobs released
  cure    upgrade to Launch, or services.dev check --fit free
  next    npx services.dev plan upgrade launch
```

## The first live order

A buyer, or their agent, orders on the live address. The charge is held on your Stripe account until the fact the Service names, here delivery and the buyer's accept:

```txt
→ GET https://lingua.builder.domains/jobs/job_7Hq2
← job_7Hq2 · translation · delivered · $49.00 held · simulated: false
  record  draft · ai | review · ai · pass
  ledger  +$49.00 · AI $0.84 · you $48.16
  next    accepted by the buyer, or final 7 days after delivery
← job_7Hq2 · accepted · $49.00 released
```

## The first payout

```txt
$ npx services.dev payouts
  you      $48.16, less services.dev's take · to acct_1Q7Hq2 · on your Stripe payout schedule
  members  none: AI delivered the job
```

Once a step has a person, each member's pay accrues at the act, on its own clock, and pays on the Pool's schedule to the account they connected at `/join`. It never waits on your charge, and it is never clawed back.

What test kept and what live changes, mode by mode: [Test and live](https://services.dev/docs/operate/testing.md#what-each-mode-does).

## Next

**[Your business](https://services.dev/docs/business.md)**: more Services under the same brand, with one console and one ledger. Then [Service()](https://services.dev/docs/service.md): every key the file you just deployed can carry, each on its own page.

---

- Up: [Your first paid job](https://services.dev/docs.md)
- Previous: [Build with your coding agent](https://services.dev/docs/start/agents.md)
- Next: [Your business](https://services.dev/docs/business.md)