Documents in this cluster
Master Services Agreement
A master services agreement is the umbrella for SOWs. Typical for BPO in the Philippines, implementation, and regional shared services. Mid-market default.
A master services agreement is named before hours start — an umbrella for SOWs, typical for Philippines BPO or regional shared services. Parties, language, and governing-law preference sit as facts for local licensed review.
The Matter Pack for a master services agreement records who signs, which language is the working draft, and which missing names would change the price. Orbid does not fill those gaps with legal advice.
Startups usually buy this master services agreement as a first single matter. Mid-market teams that issue the same form many times in a quarter put it inside an annual counsel module.
Default for a master services agreement is one scoped price. A retainer only makes sense when review volume is recurring. If the project changes, a change order states the new price.
Services Agreement
Standalone services, not an MSA. First Thailand market-support or Singapore implementation often starts here.
Cross-border, a services agreement is paper, not a vibe: standalone services, not an MSA — first Thailand market-support often starts here. A destination professional prices review of that named instrument.
For this services agreement the pack lists counterparties, term, territory if any, and the files you already have. Unknowns stay gaps, not extra hours.
A startup sees one services agreement. A mid-market desk sees a template: same skeleton, many counterparties, still reviewed locally per pack.
One services agreement is a single matter unless you already run a cadence of the same form. Extra unnamed paper is not included.
Statement of Work
Attaches to an MSA. The change-order surface. The pack asks for the existing MSA and acceptance criteria you already use.
If the file crosses a border, write the statement of work into the pack first — attaches to an MSA and is the change-order surface. Unknowns stay gaps.
A statement of work pack asks which entity on the origin side contracts, which destination name appears, and whether a bilingual draft already exists.
If this is the first statement of work on the corridor, default is a single matter. If it is the twelfth this quarter, that is a module conversation — Orbid coordinates, and licensed local counsel judges.
Do not stretch one statement of work price over a second instrument. That is how surprise bills start. Split, or write a change order.
Order Form
Commercial face of SaaS or services. Often the only paper a startup actually negotiates.
Hours do not start on an unnamed order form — the commercial face of SaaS or services, often the only paper a startup negotiates. Local licensed review sees who signs and which language is the working draft.
What sits in the pack around a order form: asserted facts, planned entities, and the triggers that would reopen price. Orbid does not choose the clause.
Founders often over-buy a stack around a order form. Mid-market operators under-specify the program. The pack names the actual count.
A retainer that mentions a order form still uses a Matter Pack per issuance. Scoped packs, not unlimited advice.
Sales Agreement
Goods sale, not a distribution appointment. Used when the origin company sells a batch into Thailand or the US.
On this corridor the sales agreement is the instrument to price — a goods sale, not a distribution appointment. Orbid records that; it does not advise which form you should have chosen.
The sales agreement line in the pack is a scope, not a draft. Local licensed professionals review what you approved; they are not Orbid employees giving advice in our name.
Startups: one sales agreement, one price, approve before hours. Mid-market: the form lives in a retainer quota, each issuance still a pack.
If this sales agreement grows a neighbour — a DPA, a quality paper, a SHA — name the set or pay a second price.
SaaS Subscription Agreement
Singapore and US buyers expect English SaaS paper. Hosting region and data-residency claims the client already makes go in the pack.
Name the SaaS subscription while talks are still cheap — English SaaS paper Singapore and US buyers expect, with hosting-region facts. A listed destination still accepts the scope; a standing lawyer there is not promised.
Record the SaaS subscription with the commercial neighbours it actually has — not a dump of every PDF in the folder. Extra unnamed files are a change order.
The first SaaS subscription on a corridor is usually a startup single matter. A net of them is mid-market, and the default flips to an annual module.
Single-matter fits a bounded SaaS subscription. Weekly flow of the same form belongs on an annual counsel module.
Software Licence Agreement
On-prem or hybrid licence, not SaaS. Licence metric and whether source is delivered belong in the pack.
A software licence belongs in the pack — on-prem or hybrid licence, not SaaS, with a metric and source-delivery fact. Thailand is live review; other corridors stay listed.
Gaps on a software licence — missing signatory, missing language, missing term — stay written. They do not convert into silent hourly work.
Do not put a startup software licence on a retainer because it feels safer. Retainer is for recurring review volume, not for nerves.
You approve the software licence pack before hours. You approve again if the facts move. The price does not jump in silence.
End User Licence Agreement
Click-wrap to the destination user. Rarely negotiated; still belongs in a pack when a product is localized.
Do not paste an origin EULA across the border unmarked — click-wrap to a destination user when a product is localized. The pack asks which language controls and which entity signs.
The pack treats the EULA as one priced module unless you name a defined set. A pile of related attachments is not a defined set.
Mid-market counsel modules still scope each EULA. Unlimited chat about the form is not the product.
Listed-corridor EULA work is still scoped as a single matter or a module. Scope is accepted; a named lawyer standing by is not promised.
Service Level Agreement
Uptime, response, credits. Attaches to MSA or SaaS. Numbers the client already sells are facts, not advice.
The first priced Matter Pack is often this service level agreement, given that uptime, response, and credits the client already sells. Local licensed professionals review; Orbid does not draft as counsel.
Who already signed a previous service level agreement, and who still has to, is a fact. Orbid records it. Enforceability is not an Orbid opinion.
If the startup does not yet have a destination entity, the service level agreement may still be scoped — as paper, not as incorporation.
A service level agreement change order is the exception path: new scope, new price, your yes. It is not a vibe adjustment on the old invoice.
API Agreement
Developer access, rate limits, data use. Often skipped until a partner starts writing against the API.
Before anyone bills, the API agreement is a line in the pack — developer access and data use, often skipped until a partner writes against the API. Price-change triggers stay visible.
Working draft versus filing draft for a API agreement are two fields. Mixing them in one unmarked file is a gap.
A mid-market API agreement program lists which affiliates may sign. A startup pack usually names one origin company.
Retainer quota can include API agreement review. It cannot include “whatever else appears.” That is a new pack.
Platform Terms of Service
Marketplace or portal terms for destination users. The pack asks which affiliate is the contracting entity.
A platform terms of service on a cross-border file is scoped, not improvised — marketplace terms for destination users and which affiliate contracts. Gaps do not become silent hours.
Price-change triggers for a platform terms of service are written before hours: new party, new territory, new language. If those appear later, a change order states the new price.
Buy the platform terms of service you have, not the library you fear. Startups default small. Mid-market defaults to systems.
Price the platform terms of service you named. Related PDFs without names are gaps, not free add-ons.