Documents in this cluster
Trademark Licence Agreement
Permission to use marks. Channel brand-use is narrower; this is the IP instrument.
A trademark licence is named before hours start — permission to use marks — the IP instrument, not channel brand-use. Parties, language, and governing-law preference sit as facts for local licensed review.
The Matter Pack for a trademark licence 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 trademark licence 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 trademark licence 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.
IP Licence Agreement
Broader IP licence covering copyright, design, or mixed rights.
Cross-border, a IP licence is paper, not a vibe: a broader grant covering copyright, design, or mixed rights. A destination professional prices review of that named instrument.
For this IP licence the pack lists counterparties, term, territory if any, and the files you already have. Unknowns stay gaps, not extra hours.
A startup sees one IP licence. A mid-market desk sees a template: same skeleton, many counterparties, still reviewed locally per pack.
One IP licence is a single matter unless you already run a cadence of the same form. Extra unnamed paper is not included.
Technology Transfer Agreement
Transfer of technology, sometimes with a registration culture in Vietnam. The pack records what is transferred at a non-secret level.
If the file crosses a border, write the technology-transfer agreement into the pack first — what is transferred, sometimes with a Vietnam registration culture. Unknowns stay gaps.
A technology-transfer agreement 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 technology-transfer agreement 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 technology-transfer agreement price over a second instrument. That is how surprise bills start. Split, or write a change order.
Technical Services Agreement
People delivering know-how without a full licence grant.
Hours do not start on an unnamed technical services agreement — people delivering know-how without a full licence grant. Local licensed review sees who signs and which language is the working draft.
What sits in the pack around a technical services agreement: 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 technical services agreement. Mid-market operators under-specify the program. The pack names the actual count.
A retainer that mentions a technical services agreement still uses a Matter Pack per issuance. Scoped packs, not unlimited advice.
Know-how Licence Agreement
Know-how that is not patented. Non-use NDA is the usual neighbour.
On this corridor the know-how licence is the instrument to price — unpatented know-how; a non-use NDA is the usual neighbour. Orbid records that; it does not advise which form you should have chosen.
The know-how licence 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 know-how licence, one price, approve before hours. Mid-market: the form lives in a retainer quota, each issuance still a pack.
If this know-how licence grows a neighbour — a DPA, a quality paper, a SHA — name the set or pay a second price.
Patent Licence Agreement
Patent licence. Field, territory, and remaining term are pack facts.
Name the patent licence while talks are still cheap — field, territory, and remaining term are pack facts. A listed destination still accepts the scope; a standing lawyer there is not promised.
Record the patent licence 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 patent licence 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 patent licence. Weekly flow of the same form belongs on an annual counsel module.
Franchise Agreement
Franchise is heavier than brand-use. Malaysia’s Franchise Act is a destination hint, not a how-to.
A franchise agreement belongs in the pack — heavier than brand-use; Malaysia’s Franchise Act is a destination hint. Thailand is live review; other corridors stay listed.
Gaps on a franchise agreement — missing signatory, missing language, missing term — stay written. They do not convert into silent hourly work.
Do not put a startup franchise agreement on a retainer because it feels safer. Retainer is for recurring review volume, not for nerves.
You approve the franchise agreement pack before hours. You approve again if the facts move. The price does not jump in silence.
Joint Development Agreement
Both sides invent. Foreground and background IP must be listed as facts the client already believes.
Do not paste an origin joint development agreement across the border unmarked — both sides invent; foreground and background IP are listed as asserted facts. The pack asks which language controls and which entity signs.
The pack treats the joint development agreement 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 joint development agreement. Unlimited chat about the form is not the product.
Listed-corridor joint development agreement work is still scoped as a single matter or a module. Scope is accepted; a named lawyer standing by is not promised.
R&D Collaboration Agreement
R&D collaboration, often with a university or a vendor lab.
The first priced Matter Pack is often this R&D collaboration agreement, given that often with a university or a vendor lab. Local licensed professionals review; Orbid does not draft as counsel.
Who already signed a previous R&D collaboration 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 R&D collaboration agreement may still be scoped — as paper, not as incorporation.
A R&D collaboration agreement change order is the exception path: new scope, new price, your yes. It is not a vibe adjustment on the old invoice.
Source Code Escrow Agreement
Escrow of source so a licensee can survive vendor failure.
Before anyone bills, the source-code escrow is a line in the pack — escrow so a licensee can survive vendor failure. Price-change triggers stay visible.
Working draft versus filing draft for a source-code escrow are two fields. Mixing them in one unmarked file is a gap.
A mid-market source-code escrow program lists which affiliates may sign. A startup pack usually names one origin company.
Retainer quota can include source-code escrow review. It cannot include “whatever else appears.” That is a new pack.
Software Development Agreement
Work-for-hire or commissioned software. Ownership of the repo is a pack fact.
A software development agreement on a cross-border file is scoped, not improvised — commissioned software; repo ownership is a pack fact. Gaps do not become silent hours.
Price-change triggers for a software development agreement are written before hours: new party, new territory, new language. If those appear later, a change order states the new price.
Buy the software development agreement you have, not the library you fear. Startups default small. Mid-market defaults to systems.
Price the software development agreement you named. Related PDFs without names are gaps, not free add-ons.
White-label Agreement
Your product under their brand, or the reverse. Channel and SaaS neighbours.
Put the white-label agreement on the list with the counterparties you already have — your product under their brand, or the reverse. Review is priced after you approve.
The white-label agreement is in the pack so a local licensed professional can see the job. Orbid organizes. It does not replace that review.
The same white-label agreement is a one-off for a seed company and a workstream for a regional HQ. The pack says which.
Orbid does not discount a white-label agreement by drafting it as counsel. Local licensed review prices the work that is in.