About us

Hiring a team you have never met is an act of faith. We spend the first week making that faith unnecessary.

Everything below is how we actually run a project, written down so you can hold us to it.

What we build

Websites, mobile apps and custom software, plus the cloud, security and SEO work that keeps them running.

How we start

On paper. You approve the sketch before anyone writes a line of code.

When we are around

Hours that overlap the UK, the EU and the US East Coast morning.

How to reach us

admin@hadiya.in — a reply within one working day.

Who we
work with

Companies that need software built properly but do not want to hire an in-house team to do it. Founders with a product to get in front of users. Operations managers drowning in a spreadsheet that stopped being a spreadsheet years ago.

Most of them have worked with an outsourced team before, and most have a story about it that starts well and ends badly. That shapes how we run things more than anything else.

What they pictured. What arrived.

Five steps, no surprises

How a project runs

Step one

Discovery call

Half an hour, no charge, no pitch. You describe the problem, we ask the awkward questions, and we tell you honestly whether it is something we should be building for you.

Step two

Sketch and scope

We draw the screens and the flows, including the edge cases everyone forgets. You mark it up until it matches what is in your head. Changes at this stage cost nothing.

Step three

Build in the open

Work lands in a staging environment you can open any time, not in a black box that reappears in six weeks. Weekly written updates, and a call whenever you want one.

Step four

Ship and hand over

You get the code, the accounts, the deployment process and the documentation. Everything is in your name. Nothing is hostage to us still being in the picture.

Step five

Support, if you want it

Monitoring, updates and small changes on an ongoing basis, or nothing at all if you would rather take it in house. Both are fine, and we will not make leaving difficult.

Sound like what you need?

Tell us what you are building. The first call is a conversation about your problem, not a sales pitch.

Start a brief
The bits that are not negotiable

What we hold to

You own everything

Code, repositories, cloud accounts, domains. All registered to you from day one. A vendor who holds your infrastructure hostage is not a partner, and we will not put you in that position.

Plain language

Updates you can read without a technical dictionary. If we have to explain a trade-off, we explain it in terms of what it costs you in money, time or risk, not in framework names.

Bad news early

If something is running late or an estimate was wrong, you hear it the week it happens, not the week before the deadline. Late surprises are what actually damages projects.

We will talk you out of things

If a feature is not worth what it costs, we say so, even though building it would earn us more. Being right about scope is worth more to us than one extra invoice.

What working with us actually looks like

The honest answer to the question everyone hiring across a time zone wants to ask.

Hours

Our day overlaps the UK and EU almost entirely, and catches the US East Coast morning. You will not wait a full day for an answer to a simple question.

Replies

Email within one working day, always. During an active build you get a written update every week, whether or not there is something dramatic to report.

Visibility

A staging environment from the first week, so progress is something you can click through rather than something you have to take our word for.

TODO — replace with your real stack

What we build with

Front end

TODO — frameworks you actually use.

Back end

TODO — languages and frameworks.

Mobile

TODO — native, cross-platform, or both.

Infrastructure

TODO — clouds, CI, monitoring.

Still reading? Let us talk.

Tell us what you need built and roughly when you need it. We reply within one working day, and the first conversation costs nothing.