A practical guide for US, UK, Canada and Australia buyers: onboarding, access, definition of done, demo cadence, code ownership, security basics and when to stop.
You have already chosen a custom software development partner. The next 30 days are not a formality. They are when you set up access, agree what "done" means, and find out whether the working rhythm will hold. If those things stay vague, the rest of the engagement inherits the mess.
This guide is for product, engineering and operations leads in the US, UK, Canada and Australia starting work with an offshore or remote team. It is not about how to pick a firm. It is about running the first month so both sides can deliver, and so you can stop early.
Set the working agreement before anyone writes code
In the first few days, write the operating rules in a shared document:
- Named owners. One owner on your side who can answer questions within a working day, and one technical lead on theirs who is on the project, not only an account manager.
- Overlap hours. A daily window when both time zones are at a desk. For a US East Coast or UK team with a partner in India, that is usually a morning slot on your side. Put it on the calendar even if you skip some days.
- Tools. One place for tickets, one chat channel, one repo organisation, one document folder. Give access to required tools in the first week, not the third.
- Communication defaults. Who writes the weekly update, by which day, and what it must contain: work completed, work in progress, blockers, and decisions you need to make.
Get access right, in your accounts
This is the step teams skip, and the hardest to unwind later. Create the Git repository in your company's name and invite the partner as collaborators. Do not start in a vendor-owned repo with a plan to transfer later. The same rule applies to cloud accounts, CI, error tracking and design files.
Grant least privilege: the environments they need, not production by default, and not systems the project does not touch. Use named users, not a shared login, with multi-factor authentication. Write down who has what, and how access is removed when the work ends or someone leaves the partner's team.
Do not send production data to a shared drive or a personal email. If they need a dataset, agree a sanitised subset, where it will live, and when it will be deleted.
Write the definition of done before the first sprint
"Done" should not mean "the developer said it works." Agree in writing what must be true before a feature is complete:
- The change is in the main branch, not on a laptop.
- Automated tests for the new behaviour are passing in CI.
- The ticket describes how to verify it, and someone has followed those steps.
- Documentation is updated: a README, an API note, or a short runbook, as needed.
- No new secrets are in the repo, and no obvious errors are in the logs of the target environment.
Add more for your context if you need to. Both sides should be able to look at the same list.
Set a demo cadence you will keep
Weekly demos of working software are the simplest way to see progress across time zones. A slide update is not a substitute. Meet at the same time each week, inside the overlap window, and show software in a deployed environment — even if it is staging or behind a feature flag. Walk through the acceptance criteria, not every file changed. Write decisions into the ticket tracker after the call, not in chat.
If a week produced no demonstrable change, ask why. One quiet week can be onboarding or a blocked dependency. Two or three in a row, with no recovery plan, is a signal to intervene. Send a short written update the same day for anyone who missed the call.
Confirm code ownership in the repo, not only in the contract
Your contract should already say that you own the intellectual property. The first 30 days are when you check that the working setup matches the paper. Repositories, pipelines and cloud resources should be in your organisation. Every change should go through a pull request your team can inspect. List dependencies and third-party services, including who pays for the account. If a release needs a personal token on a vendor laptop, move it to your CI.
By the end of the first month, ask for a short architecture note: what was built, where it runs, how to deploy it, and how to roll it back — enough that another engineer could take over.
Security basics that belong in month one
You do not need a full audit in the first 30 days, but a few habits should be in place before the codebase grows. Keep secrets in a vault or in CI, never in git history, and rotate any committed during setup. Protect the main branch so reviews are required and CI must pass before merge. Pin and scan dependencies for known vulnerabilities. Limit, log and justify access to customer or staff data. If the partner will connect to your identity provider or existing systems, document the scopes and offboarding steps first, and send your security questionnaire in week one.
A simple shape for the 30 days
The tickets will differ, but the shape is similar:
Days 1–5. Working agreement, accounts, access, environments, and the definition of done. A thin deploy to your environment, so the pipeline is real.
Days 6–20. The first vertical slice of the actual product: one path that touches a real system or a realistic stand-in, written to the definition of done and demonstrated weekly.
Days 21–30. A second slice, or a hardening of the first (tests, documentation, rollback). A written handover note, and a short review of the working rhythm.
If the first engagement is itself a scoped paid pilot, such as Axentis's Launch Pilot, these same rules still apply. The point of a bounded first month is not only to ship a slice of software. It is to learn whether you can keep working together.
When to stop
Stopping in the first 30 days is uncomfortable, but better than stopping later in the year. Watch for these patterns and raise them in writing:
- Access still sits in the partner's accounts after you asked to move it.
- You cannot name the engineers doing the work, or they change without notice.
- Demos are cancelled, replaced by slide decks, or show work that cannot be clicked.
- The definition of done is regularly waived.
- Questions that need a decision sit for days with no follow-up, in either direction.
- Your team cannot clone, run or deploy the code without the partner present.
One of these can be fixed. Several together, with no change after you raise them, is a reason to use the exit terms in the contract. Keep the accounts, the repo and the documentation — that is why they were set up in your name.
The first 30 days will not tell you everything, but they will tell you whether the engagement is set up to succeed.
Kapil Singhal, Director, Axentis Technologies
Axentis website: https://axentis.tech
Aranyix (sister product line): https://aranyix.tech
Axentis on LinkedIn: https://www.linkedin.com/company/axentis-technologies
Aranyix on LinkedIn: https://www.linkedin.com/showcase/aranyix/
Top comments (0)