Built for US founders · Indian dev teams

Assemble a bulletproof SOW in five minutes.

Free, and built specifically for US founders hiring Indian dev shops — with the IP, payment, and dispute clauses generic templates skip.

Assemble your SOW free See a sample SOW

No card · Clause library vetted for the US–India corridor

WQ · CORRIDOR BEARING CHARTLIVE LANE

See it first

Read a real SOW before you assemble one.

SOW No. WQ-SAMPLE-2026-001 Airtight Tier

Statement of Work — Customer Portal Rebuild

Between [Client, Inc.] (Delaware C-corp, the “Client”) and [Vendor Technologies Pvt. Ltd.] (Bengaluru, the “Vendor”). Effective date: 14 April 2026.

1 · Scope of work

Vendor will rebuild Client’s customer-facing portal as a Next.js 14 application backed by the existing PostgreSQL database. The rebuild covers authentication (Clerk), account management, billing surface (Stripe), and the document-export flow currently served by the legacy Rails app.

2· Milestones & payment

Total fixed fee: USD 38,400, billed in four tranches. Each tranche is contingent on a reviewable artifact — a working staging URL, a passing test report, or a merged PR tagged for acceptance. “Done” without an artifact is not a billable state.

Full document · 8 sections · IP assignment · SIAC · FEMARead the full sample SOW

Why projects fail

The problem usually isn’t effort. It’s what never made it into writing.

Failure mode+ $15,000

Your $30k quote becomes $45k.

Scope keeps getting redefined in Slack instead of in the project record. Each “small ask” lands as billable change-order weeks later.

Failure modeΔ “done” ≠ shipped

Milestone 2 is “done.” The staging link is broken.

Invoices get tied to vague claims like “done” or “ready,” with no concrete acceptance criteria, staging proof, or reviewable artifact attached.

Failure modeΔ senior → junior

You paid for a senior. A junior wrote the code.

Quotes rarely make role coverage, code transfer, documentation, or repository ownership concrete enough for the client to inspect.

The corridor

What generic SOW tools miss.

Generic templates aren’t written for the US–India software corridor. These three things are.

IP that actually transfers to you

Indian Copyright Act + IP assignment clauses that actually transfer ownership to you — not a vague “work for hire” blurb that lawyers in Bengaluru will tell you doesn’t bind under Indian law.

Payments that actually clear

FEMA, DPDPA 2023, and W-8BEN-E mechanics built in. GST treatment, FIRC handling, and LUT-covered export-of-services status referenced where they matter.

FEMAW-8BEN-ELUT / IGSTFIRC

Disputes that won’t strand you

SIAC arbitration and cross-border dispute structure as default. Singapore seat, English language, sole arbitrator — so a dispute doesn’t mean a five-year case in a Bengaluru civil court.

SIACSingapore seatSole arbitrator

Workflow

One project record. A few tightly-related actions.

Before engagement

Get the brief onto one page

Save the brief, surface missing clarity, and make the scope legible enough to price and document.

Negotiation & planning

Spot what the vendor’s quote left out

Draft the SOW and compare quotes against the same saved project state so omissions stand out quickly.

Execution

Make ‘done’ provable before you approve the invoice

Compare milestone and handoff claims against what the project record says should actually be inspectable.

US founders · Indian dev teams

You’re about to wire $40k. The SOW takes five minutes.

Built by a founder who’s worked both sides of the US–India software corridor.

Assemble your SOW free See pricing