This is written by an Iranian software company, so read it as a party with an interest — and check everything below against your own trial. It is also written to be honest about the obstacles, because a client who discovers them in month two is a client nobody keeps.

The short answer

Iran has a deep bench of .NET and React engineers, rates roughly a third to a half of Western European contractors, and a five-to-six-hour overlap with European working hours. The obstacles are payment routes and, for some clients, compliance. Both are solvable and both should be settled in writing before any code is written. The way to decide is a paid two-week trial on your real backlog, reviewed pull request by pull request.

Why the engineering base is strong

.NET has been the default enterprise stack in Iran for two decades — banks, municipalities, industry — so the talent pool is wide and experienced with large, long-lived systems rather than only greenfield apps. React and Next.js followed the same path on the front end. Universities produce more computer science graduates than the local market absorbs, which is why rates are what they are.

What to check, in order

1. Code, before anything. Ask for a sample repository: architecture, tests, CI. If the sample is a to-do app, ask for something with a domain in it. Then run a paid trial of two weeks on your own backlog and review every pull request as you would your own team's. Quality is visible in a diff; it is not visible in a proposal.

2. Payment. International card processing and SWIFT are not available to Iranian companies. Working arrangements exist — [YOU: the routes Idepoo actually uses — e.g. an intermediary entity, crypto settlement, a partner company abroad] — and the right one depends on your jurisdiction. Settle this before the trial, not after.

3. Compliance. Depending on your country and industry, contracting with an Iranian entity may have legal constraints. This is a question for your counsel, and a serious vendor will tell you so rather than wave it away.

4. Time zone. Tehran is UTC+3:30. That is a five-to-six-hour overlap with Central Europe and a full overlap with the Gulf — daily stand-ups at a sensible hour for both sides.

5. Language and communication. Written English is generally strong among engineers; spoken fluency varies. Ask for the trial to run in your tools (Jira, GitHub, Slack) so you see communication as it will actually be.

6. Infrastructure. Iranian teams work around connectivity limits routinely, but ask how they access your cloud accounts and what happens if a service is blocked. The answer should be specific.

Two ways to work

Project — a written scope, two-week deliveries, a fixed price. Good for a defined build with a clear end.

Extended team — two to four engineers on a monthly contract, on your backlog, under your review. This is where the economics are strongest and the relationship is most like having the team in-house. It is also the arrangement where the trial tells you the most.

What we are

Idepoo is a Tehran software company founded in 2010: .NET 10 and React/Next.js, clean architecture, CQRS where it earns its place, tests on every financial calculation, CI/CD. We have worked with [YOU: countries / kinds of client] and offer both arrangements above. The .NET and React development page describes the method in detail and links to sample code — the trial is how you find out whether it is true.