Offshore software development

Offshore software development where you hold the code and the approvals

A remote team builds in your repository and your tools, from a written scope you approve, with the code and accounts in your name from the first commit.

Get your software build scoped in writing
Trusted by the world's fastest-growing brands

What the word means

Offshore development, with control kept on your side

Offshore software development means handing a build to an outside team that works remotely. Buyers raise the same worries: control, ownership and quality, so those are the parts we put in writing.

Stage approvalsAdmin: Sample LedgerScopeSep 2DesignsSep 16Release 1Awaiting youHand overNextRelease 1 · invoicing softwareFor approvalPreview readyAsk for changesApproveIn your name · you can remove usGitHubHostingStoresDomain

You hold the keys

The repository, the cloud account and the store accounts are opened in your company’s name. We are invited in as members, and you can remove us.

You see the work

Changes arrive as pull requests in your repository, where your engineers or advisers can read them, comment and ask for changes.

You approve the stages

The scope, the designs and each release are written down and approved by you before the next stage starts.

Two ways to staff a build

A remote team or an in-house hire

Both can produce good software. They differ in what you manage, what you commit to and how quickly the work can start.

In-house hireEngineers on your payrollRemote teamEngineers engaged for the project
Starting the workBegins once the roles are filled and onboardedBegins once the written scope is approved
CommitmentSalaries and benefits that continue between projectsA priced milestone, or a team term set in a written scope
Day-to-day contactShared office hours and hallway questionsCalls and chat on business days, 8 a.m. to 1 p.m. ET
Where the knowledge sitsIn your employees, and in whatever they write downIn your repository and documentation, by agreement
Best whenThe product needs engineers for years, on your cultureThere is a defined build, or a skill you lack today
How we decide

A first version that can be listed becomes a project, scoped with a fixed price for its first milestone from $25,000. If you already have engineers, we can add to them under a team term quoted in a written scope. Some products end up with both: a remote team to build, and your own hires to carry it on.

Facts that matter here

Four facts about outsourcing a build

Copyright transfer, work made for hire, review rules in GitHub and NIST’s framework for software buyers, each with its source.

  1. AssignmentCopyright Act

    A transfer of copyright needs a signed writing.

    Section 204(a) makes a copyright transfer invalid unless the owner, or the owner’s authorized agent, signs a written instrument or note of it. Narrow cases, such as transfer by operation of law, are the exceptions. Handing over files is not that instrument. The contract has to contain it.

  2. Work for hireCopyright Act

    The statute lets a commissioned work count as work made for hire only in listed cases.

    Under 17 U.S.C. § 101, work made for hire covers an employee’s work within the scope of employment, or a commissioned work in listed categories when both parties sign a written agreement to that effect. We do not rely on the label. We write an assignment of the code to you.

  3. Code reviewGitHub

    GitHub lets repository administrators require approved reviews before code is merged, and name code owners.

    GitHub’s documentation says administrators can require pull requests to receive a set number of approving reviews before merging into a protected branch. It also lets repositories name code owners. In your repository, you choose those rules and who may approve. Our engineers work under whatever rule you set.

  4. Buyer languageNIST

    NIST says software buyers can use its framework to talk with suppliers.

    NIST’s Secure Software Development Framework recommends a core set of secure development practices. Its abstract adds that purchasers and consumers can use it to foster communication with suppliers. It is guidance, not a law.

How control works

Six safeguards in an offshore engagement

Six answers to the usual worries about outside developers, each one something you can verify yourself.

Sample Ledger accountsIn your nameGitHubRepositoryWriteVercelCloud hostingDeployRegistrarDomain and DNSNoneTrackerIssuesMemberSentryError reportsMemberSlackChatChannel

Accounts in your name

The code repository, the cloud hosting account, the domain and the app store accounts are opened by your company, with the admin role held by you. Our engineers are added as members at the level the work needs. You receive: the admin credentials and an access list you can edit.

RepositoryCloudStores
Development agreementSigned Oct 17. Assignment of work productDeveloper assigns to Client all right,title and interest in the code, designsand documentation it produces for Client.ClientWebzeniaSchedule BLicensepdf-libMITaws-sdkApache-2.0

Assignment in the contract

The contract assigns the code, designs and documentation produced for you to your company, in a writing both sides sign. A list of third-party libraries and their licenses goes with it, so you know what is yours and what is borrowed. You receive: the signed assignment clause and the license list.

First milestoneSigned with the scope$38,000Fixed priceSample Ledger Co.Invoice builder with tax linesInCard payment linksInMobile appLaterChange 01 · pricedApprove

A written scope

The first milestone is described in a document: what is in it, what waits, and the fixed price for the milestone. Changes are written up and priced before work on them starts. You receive: the scope and each approved change.

In scopeLaterPrice
# ledger-buildShared channelENEngineer · Webzenia9:12 a.m.Opened #42, tax lines on invoicesAdd tax lines to invoices#42 · sample-ledger/appChecks passedPOProduct owner9:20 a.m.I’ll approve after the preview.Message #ledger-build

Work in your tools

We take access to the repository, the issue tracker and the chat workspace you already run, and work in them. There is no second backlog to reconcile. You set the permissions and can change them. You receive: a shared channel and a board that show the work as it happens.

GitHubIssue trackerSlack
Pull request #42Openfeature/tax-lines into mainsrc/invoice/totals.ts+2 −1+ const tax = taxLines(invoice.items)+ const total = subtotal + taxApproved by your code ownerChecks passedmain is protectedMerge pull request

Review in your repository

Code arrives as pull requests in your repository. If you set merge rules, such as required approvals, the work follows them. Your engineers, or an adviser you hire, can read and comment on any change. You receive: the pull request history and test builds you can install.

Live window8 a.m. to 1 p.m. ETMon 5Tue 6Wed 7Thu 8Fri 98 a.m.10 a.m.1 p.m.4 p.m.Asked 3:20 p.m.picked up next window

A live window

We are on calls and in Slack from 8 a.m. to 1 p.m. ET on business days. Anything raised outside the window is picked up in the next one, and the work is documented in the repository and the tracker. You receive: the window in writing, in the scope.

How it runs

Scope, set up, build and review, hand over

You sign off a stage before the next begins, and the documents below show what each one hands over.

scope.csv

First milestone scope

Sample · Sample Ledger Co. invoicing software
ItemFirst milestoneYour approval
Customer accounts and sign-inYesBefore build
Invoice builder with tax linesYesBefore build
Card payment linksYesBefore build
Spreadsheet export of reportsLaterWhen scoped
Mobile appLaterWhen scoped
Milestone price$38,000, fixedSigned with the scope
What waits is listed as clearly as what is included.

Our stack

The tools behind the engagement

What the build runs on, in accounts held in your name. Tap any tool for what it does in the build.

GitHub
Why GitHub

GitHub stores source code and lets people propose, review and merge changes.

How we use it

The code lives in an organization you own, and the review rules are yours to set.

ReviewCI/CDActions
GitHubYes
GitLabYes
BitbucketPipes
NoneNo

Questions

Offshore software development, answered

Start here

Get your software build scoped in writing

Tell us what you want built and what worries you about outside developers. We’ll send back a scope with the first milestone, its price and who holds what.