atombit

SENIOR .NET ARCHITECTURE

Senior .NET Architecture & Development

A senior architect who owns your backend end to end — design, build, deploy and support.

For product teams without a backend lead, and for agencies who have sold the work and need someone dependable to build it. You get one experienced engineer, not a rotating pool.

Engagement profile

Engagement
Retainer or fixed scope
Commitment
Part-time or full-time
Working hours
Overlaps UK & EU mornings
Contracting
Direct or through your agency

01 What we deliver

Everything included in a production engagement.

  • System design, data modelling and API contracts before any code is written
  • .NET 8 service development with EF Core and PostgreSQL
  • Authentication, role-based access control and multi-tenancy
  • Deployment, containerisation and CI/CD setup
  • Code review and technical direction for an existing in-house team
  • White-label delivery — I can stay behind your brand on client work

How we engage

How an engagement starts.

01

Technical call

A working session, not a sales call. We go through what exists, what is breaking and what you actually need next. You leave with a straight answer about whether this is a good fit.

02

Written assessment

For anything involving an existing system, a short written document: what the architecture is, where the risk sits, and a recommended order of work. Fixed price, and yours to keep or hand to someone else.

03

Scope and terms

Scope, monthly commitment, rate and IP terms agreed in writing before work begins. Your repository, your infrastructure, your accounts.

04

Build and support

Weekly demos against a visible board. After go-live, support continues with the same person — there is no handover to a desk that has not read the code.

Frequently asked

Common questions about this capability.

Do you work as a subcontractor for agencies?

Yes — it is a large part of what I do. You keep the client relationship and your branding; I build the system behind it. I can join calls as a member of your team, or stay entirely invisible and deliver through you. Whichever you prefer is fine, as long as it is agreed up front.

Can you work on an existing codebase rather than a greenfield build?

Yes. Most engagements are existing systems. The first step is a read-only pass over the repository and database to produce a written assessment — what the architecture actually is, where the risk sits, and what order to address it in. That assessment is useful to you whether or not we continue.

What timezone do you work in and how much overlap will we get?

I am based in India (UTC+5:30). That gives a full working-morning overlap with the UK and Western Europe, and an afternoon overlap with Australia. For US clients the overlap is limited to early mornings Eastern, so I am usually a poor fit for teams that need same-hours collaboration all day.

Who owns the code and the infrastructure?

You do, from the first commit. Work happens in your repository and deploys to your infrastructure under your accounts. There is no proprietary framework you have to keep paying for, and nothing is held back as leverage at the end of an engagement.

How do you price the work?

Retainer for ongoing work — a fixed number of days per month at a fixed monthly fee. Fixed price for a defined, bounded piece of work where the scope is genuinely clear. I avoid hourly billing because it rewards the wrong thing.

How does contracting work for a company in the UK, the EU or Australia?

As an overseas supplier invoicing your company directly, usually in GBP, EUR, AUD or USD by bank transfer, or through your agency if you would rather keep it on one purchase order. On the UK off-payroll rules: I am not a UK-resident worker and there is no UK entity in the chain, so the usual IR35 status-determination process is not the framework this sits in — but that is your finance team's call to confirm, not mine, and I will supply whatever paperwork they need. EU clients typically handle it as a reverse-charge B2B service.

Where does our code and data actually live if you are in India?

In your accounts, in your region. Work happens in your repository and deploys to your infrastructure — nothing is hosted on my side, and I do not keep copies after an engagement ends. For UK and EU clients that means personal data never leaves the jurisdiction you chose, because I am working inside your environment rather than moving data into mine. A signed DPA is available if your vendor onboarding needs one.

10 Next step

Let's architect the platform your business runs on.

About an hour, directly with the engineer who would do the work. We go through what exists, what is breaking and what you need next. No sales rep, no charge, and no retainer required to start — and if it is not a good fit for one person, you will hear that on the call.

Who replies
The engineer, not a rep
First call
About an hour, no charge
Time zone
UK & EU morning overlap