---
title: "How It Works for Businesses | roji.ai"
description: "From application to payout: how you publish a service catalog, how orders arrive already paid, how you talk to an AI client, and how the money reaches your account. Every step, in plain language."
doc_version: f1551e403daa
last_updated: 2026-09-10
---
# How It Works for Businesses | roji.ai

For Business

How It Works

How it works, from catalog to payout

No mysteries and no fine print. This is the entire life of an order from your side of it.

Apply to list your services

The life of an order, from your side

Apply and get verified

Business verification (KYB) through Stripe Connect — your legal entity, your beneficial owners, your payout account — plus a license check where the vertical requires one. Verification is your handshake with buyers who can't interview you. Solo operators go through the same path as companies; a one-person practice is a business here.

Publish your catalog

A listing is a service you already sell, written down so software can buy it: what it is, what you need from the buyer, what you deliver, your price, your turnaround, your refund window, and the jurisdictions it covers. Start from a template for your vertical, or paste your website and let us draft the catalog for you to correct. Pause or edit any listing at any time.

Orders arrive, already paid

An agent finds your listing, fills your input schema, sees the itemized fee preview, and orders. The payment goes through at that moment. The order lands in your queue with the inputs attached and the money already on its way to you — accept it, or set the listing to auto-accept and skip the step. Decline and the buyer is refunded in full automatically.

Do the work — with a client that answers

Hit an ambiguity? Ask a typed question; most answers come back in minutes, and your SLA clock pauses while you wait. Missing a document? Request it and it routes to the agent — or the human behind it. Post status updates on longer work so the buyer's orchestrator can plan around real-world time.

Deliver with instant checks

As you upload, automated checks validate each item on the spot — photo resolution, location tags, document completeness, required fields. You know immediately if something is missing. No driving home from a site visit only to learn three days later that one photo was blurry.

The money is already yours

There is nothing to invoice and nothing to release. The payment settled to your Stripe account when the order was placed and pays out on your normal Stripe schedule. What remains after delivery is the refund window — the buyer's stated period to raise a problem — and then the order closes.

  When things go sideways

      The buyer stalls
      Unanswered questions pause your SLA clock and escalate — first to the agent again, then to the human behind it. A stall on their side is recorded on their track record, not yours, and it can never turn into a missed SLA on yours. If the order is genuinely unworkable without the missing input, cancel it and the buyer is refunded.

      You miss your SLA
      The order refunds automatically and in full — the refund reverses out of the payment you already received, the way any card refund does. This is the honest cost of being paid up front, and it is why the turnaround you publish should be the one you can actually hit, not your best day ever.

      The buyer asks for a refund
      Inside the window you published, a buyer can file a refund request with a reason. It arrives in your queue with the complete order record — every input, question, and delivery. Approve it, or contest it with your own evidence, within 72 hours; silence auto-approves. Contested requests go to platform mediation, which decides from the record.

      Life happens
      Pause a listing, cap concurrent orders, or set the whole catalog to away. Reliability is measured on the commitments you actually published, never on the hours you chose not to work.

See the numbers

How you get paid

## Sitemap

- [Every public page, as markdown](/sitemap.md)
- [llms.txt](/llms.txt) · [AGENTS.md](/AGENTS.md) · [auth.md](/auth.md)
