01
Web · Japan client
Elnet — Newspaper Articles Management
Stack
.NET Core Web API + Azure Functions + Azure SQL.
Duration
8 months.
Microsoft .NET development
.NET applications, built and modernised — by a bilingual team.
Web applications, APIs and mobile apps on .NET Core, C# and VB.NET — from new builds to upgrades of systems that have run for years. Our engineers work with your team in Japanese and English, with daily updates and Japanese QA sign-off.
- 20 .NET engineers
- Web · API · Mobile on one stack
- Since 2000 in software delivery
One .NET stack
Web · API · Mobile
SQL Server · Azure
What we build
One stack, from browser to database
We cover the full lifecycle — requirements, planning, development, testing and release — and record the architecture before development starts.
-
.NET Core · MVC
Web applications
Custom business applications on .NET Core and MVC, with React, Vue or Angular on the front end — from enterprise portals to lightweight internal tools.
-
Web API · Azure Functions
APIs and cloud services
.NET Core Web APIs and Azure Functions behind web and mobile apps — the stack of the newspaper articles system we built for a Japanese client.
-
T-SQL · SQL Server
Databases
SQL Server and Azure SQL schemas, queries and stored procedures designed with the application, not after it.
-
Microsoft 365
SharePoint integration
Applications that read from and write to SharePoint, so your data stays where your teams already work.
Hosting on Azure or AWS, deployed through CI/CD pipelines. Node.js and PHP where a service needs them.
Legacy .NET → current platforms
Running an older .NET or VB.NET system? Upgrade it step by step.
Many business systems still run on VB.NET or an older .NET Framework because they work. We move them to current .NET in bounded releases, so the business keeps running while the platform underneath it is renewed.
-
Map what must keep working
Screens, reports, data, integrations and the unusual workflows that experienced users rely on — not just the main screens.
-
Upgrade in bounded releases
Start with one workflow that has clear acceptance criteria, so you can evaluate a working build before the scope grows.
-
Test with your users, then sign off
Each release goes through user acceptance testing on your data. Nothing replaces the old system without your sign-off.
.NET · delivered projects
Systems our clients run every day.
Clients are described by type and country, matching how the work is documented.
02
Mobile · North American client
Automated Electrical Design System
Stack
Xamarin/MAUI + VB.NET web service — pinch-zoom blueprint storage with real-time sync.
Duration
3+ years, ongoing.
The .NET team
A .NET team that works with you in Japanese.
20 .NET engineers, backed by 30 JLPT-certified engineers (N1–N5), 3 bilingual project managers and 2 bilingual QA managers across the company.
How we work- A daily team stand-up at 10:00 IST, with progress shared in Japanese
- Detailed weekly reports in Japanese and English
- Every change through a reviewed pull request
- Japanese QA sign-off before every release
FAQ
Questions we hear first
Can you take over an existing .NET system?
Yes. We start by reading the code and documenting how the system works today, then agree a maintenance or upgrade plan with you. We maintain long-running C# and VB.NET systems, including a 3+ year engagement for a North American client.
Can you upgrade an older VB.NET or .NET Framework system?
Yes. We map what the application must keep doing, then upgrade in bounded releases that your users test and sign off before the old version is retired.
Which front end do you use with .NET?
MVC views for simpler applications, or React, Vue or Angular when the interface needs more interaction. We recommend one during planning and record the reasoning in the architecture document.
Can we work with your team in Japanese?
Yes. Status reports, documentation and QA sign-off can all run in Japanese, with weekly reports in both Japanese and English.
Where will the application be hosted?
On Azure, AWS or your own servers. We set up the deployment pipeline so releases are repeatable, and hand over the documentation with the user manual.