AmwerahSolutions
About

Four people, and you will meet all of them

Amwerah Solutions is a software company in Ahmedabad. We are small on purpose, and the whole way we work follows from that fact rather than fighting it.

Who we are

There are a great many software companies in Ahmedabad, and most of the ones competing for the same work will tell you roughly the same things. So here is what is actually different, and what isn’t.

What being small changes

There is no account manager between you and the person writing the code. When you ask why something is taking longer than expected, you get the answer from someone who knows, on the same day, rather than a version of it that has passed through two people first.

It also means the CTO reviews every change that ships. On a team of forty that would be a bottleneck and a bad idea; on a team of four it is the reason the code stays coherent enough for a new engineer to be useful in a week.

The trade is capacity. We cannot put twelve engineers on your project next month, and we will say so rather than hiring three contractors and calling them a team. If your project genuinely needs that scale, we are the wrong firm and telling you early is the most useful thing we can do.

What we will not put on this page

You will not find a client logo wall here, a “projects delivered” counter, or a row of testimonials. Not because there is nothing to say, but because we have not been cleared to name client work, and a number nobody can check is not evidence — it is decoration that every one of our competitors has too.

What we can show you instead is how the work runs: the process, the technical positions, the things we decline, and the product we are building right now. Those are checkable. If proof by logo wall is what you need, that is a reasonable thing to want and we are not it yet.

Where we work

From Ahmedabad, Gujarat, for clients in India, United States, United Kingdom and Australia. Our day overlaps comfortably with UK mornings and Australian afternoons; US calls are scheduled early or late by arrangement.

Working across time zones is mostly a writing problem rather than a scheduling one. Teams that record decisions get far more out of a distributed arrangement than teams that rely on someone being tappable on the shoulder, which is why we push for written updates even when everyone happens to be awake.

By the numbers

Every figure here is checkable from this site

There is deliberately no client count and no delivery statistic. Those were never supplied to us, and an invented one is the most common falsehood on a page like this.

4
countries served across India, the US, the UK and Australia
12
services across build, run and grow
6
industries with domain models we have already built
161
screens in design on SPARRAPS, our current product
The team

Who does what

Four people, each with something they own outright. You will deal with all of them at some point in an engagement.

  • Mr Mubin

    Chief Executive Officer

    Client relationships and the commercial shape of every engagement.

  • Mujib

    Managing Director

    Delivery oversight, resourcing and the schedule you are actually held to.

  • Afroze Saiyed, Chief Financial Officer at Amwerah Solutions

    Afroze Saiyed

    Chief Financial Officer

    Contracts, invoicing and the cost model behind every estimate we send.

  • Vasim Shaikh, Chief Technology Officer at Amwerah Solutions

    Vasim Shaikh

    Chief Technology Officer

    Architecture, code review and the technical decisions that are hard to reverse.

How we operate

Six positions we will not trade away

Every one of these costs us work occasionally. That is roughly the point — they are the things you can hold us to.

  • Discovery is paid, and portable

    A free "discovery" that produces a proposal is a sales meeting. A paid one produces a specification you own and can take to any other firm. We think that is the honest version, and it is why we charge for it.

  • Slices, not layers

    Building the database, then the API, then the interface means nothing works until everything works. Building one narrow path all the way through means you can use it in week three and correct us in week four.

  • Your repository, from commit one

    Code lives in your organisation account, not ours. There is no escrow, no licence-back and no per-seat fee on something you paid to have built. Leaving is a normal ending, not a penalty.

  • Written by default

    Decisions get recorded, not just discussed. Across four time zones a written decision record is worth more than any number of calls, and it is what makes a handover possible at all.

  • Boring technology

    We choose the option with the largest hiring pool and the longest support window, not the one that is interesting this quarter. You should be able to hire someone who can maintain this without us.

  • We say no

    To work we would do badly, to a language model where a rule belongs, and to a timeline that can only be met by shipping something we would not run ourselves. Turning down work is the cheapest form of quality control.

Want to know whether we are the right size for you?

Ask on the first call. It is a fair question and we will answer it straight, including when the answer is no.