Skip to content
How we work

One accountable lead, an engineering team behind them

A named lead in your region owns scope, communication and quality. The build team in India does the engineering. You get regional accountability at a cost structure that makes the project viable.

The team shape

Local accountability, global capacity

  • Engagement lead (Finland). Your single point of contact. Runs the plan, the demos and the risks.
  • Engineering team (India). Builds, tests and ships in two-week increments, with the lead reviewing every milestone.

Working hours: the India team typically works 10:00–19:00 IST, which gives about 6.5–7.5 hours of live overlap with a 09:00–17:00 Finnish working day. Other windows can be agreed in the proposal.

The delivery rhythm

Four stages, always the same shape

01

Discover

A short written brief, then a 30-minute call. We agree the goal, the constraints and what “done” means.

Scope brief
02

Propose

A proposal with milestones, team, risks and a price or range. NDA first if you want one.

Statement of work
03

Build

Two-week increments. A demo of working software at the end of each, tests running in CI, a written update every day.

Working software
04

Run

Hand over with a runbook, or stay on a support retainer. Either way the documentation is yours.

Runbook and handover
Practices

What you can rely on

  • One accountable lead. A named engagement lead in your region owns scope, communication and quality. You never chase the India team through a chain of managers.
  • A written update every working day. What was done, what is next, what is blocked. Readable in two minutes, in a shared channel.
  • A demo every two weeks. Working software, in your environment, on a calendar invite that does not move.
  • Tests gate every change. Automated tests run in CI before anything merges. Failures stop the line.
  • Your repository, your cloud accounts. We work inside your systems. Credentials are scoped, rotated and removed at the end.
  • Decisions are written down. Architecture decision records capture why, so the reasoning outlives any one engineer.
Terms

Security, IP and data protection

  • NDA before details. We sign yours or ours before you share anything sensitive.
  • Your IP. Work product is assigned to you on payment, under the agreement.
  • Data protection. We sign a data processing agreement where personal data is involved. You choose the hosting region; engineers in India access your systems remotely under that agreement, with transfer safeguards set in the contract.
  • Access discipline. Least-privilege access, individual accounts, and removal on the last day.

Standard terms; exact wording is set in the contract for each engagement.

See how this would work for your project

Send a short brief and we will reply with the team shape, the first milestone and a sensible way to start.

Prefer to talk? Use the call button at the bottom right of this page, or email info@hsgit.fi.