Custom Software Development on .NET, Next.js and Azure

What we build

Built for Indian business rules

• GST-ready invoices with the particulars Rule 46 of the CGST Rules, 2017 asks for, including: your name, address and GSTIN, and your customer’s (with their GSTIN if they are registered); a consecutive serial number unique for the financial year; the date; a description and the HSN code (businesses with turnover up to ₹5 crore may leave the HSN code off invoices to unregistered buyers); the taxable value; the rate and amount of each tax; and, for inter-State supplies, the place of supply with the name of the State. The CGST and SGST or IGST split is worked out for you, as in our free GST invoice generator (opens in a new tab).
• A UPI QR code on the invoice that the customer can scan to pay the exact amount.
• E-invoicing: a registered business whose aggregate turnover in any preceding financial year from 2017-18 onwards exceeds ₹5 crore must report its invoices, credit notes and debit notes for B2B supplies and exports to an Invoice Registration Portal (IRP) to get an Invoice Reference Number (IRN), with some categories exempt. Since 1 April 2025, businesses with an aggregate annual turnover of ₹10 crore or more cannot report such a document to the IRP more than 30 days after its date. Where e-invoicing applies, the software has to send the data the portal expects and keep the IRN it returns; your chartered accountant confirms what applies to you.
• Personal data: the Digital Personal Data Protection Rules, 2025 were notified on 13 November 2025 and apply in phases. Most obligations on businesses, including notices, consent, security safeguards, breach intimation and people’s rights over their data, apply from May 2027; separate rules for consent managers apply from November 2026. We design for these obligations from the start.

Our stack

.NET 8 and .NET 9 support ends on 10 November 2026

1. 1

   Take stock

   We list the projects, packages and hosting the application depends on, and note anything that blocks an upgrade.

2. 2

   Add tests where they are missing

   Before changing anything, we cover the behaviour that matters to you with tests, so the upgrade can be checked rather than hoped for.

3. 3

   Upgrade in a branch

   We move the code and its packages to the new release, fix what breaks and run the tests until they pass.

4. 4

   Run side by side, then switch

   The upgraded version runs in a test environment alongside the current one until you are satisfied, and then replaces it.

How we work and what it costs

1. 1

   Discovery call

   We look at what the software must do, who will use it and what it has to connect to. To begin, book a free discovery call (opens in a new tab).

2. 2

   Written scope and quote

   We set out the features, the business rules, how you will accept the work, the timeline and the price in a statement of work before the build starts.

3. 3

   Build in small steps

   You see working software early and regularly on a test environment, rather than all at once at the end, so you can change course before much has been built.

4. 4

   Test and deploy

   Automated tests and checks run on every change. We deploy to your Azure subscription or your own servers, with tracing switched on so problems can be found quickly.

5. 5

   Hand over and support

   You receive the code, the documentation and a handover session. Fixes and changes after launch are handled in our support hours, Monday to Friday, 9 AM–6 PM IST, paid for as needed or through a monthly retainer.