Home/About

Small studio, Pune

How we work, and who you actually talk to

The firms you are comparing us against lead with 675 staff and twenty years. We cannot match that and will not try. What we offer instead is that you know which engineer is on your project before you sign, you can read their commits, and if you are unhappy you are talking to the person who wrote the code, not an account manager.

Talk to an engineer See the work

Engineers at their desks, working at screens of code

How we work

Four rules we do not break

Every one of these has cost us work. We publish them so the wrong clients can leave early, which is better for both sides than month three.

One client per engineer

Nobody is split across accounts. It halves the work we can take and it is the only way a date means anything.

Two stacks, permanently

React and Node. We turn down PHP, Python and Angular work weekly, including from clients we like.

Written before spoken

Estimates, architecture calls and bad news all arrive in writing first. Meetings are for the argument, not the record.

No night shifts

13:00 to 22:00 IST, earlier for a launch. People who work nights indefinitely leave, and then you have a handover problem.

2023

Studio founded

Vetting stages before placement

Concurrent engagements, max

Client per engineer at a time

If you are deciding whether to work with us, the two pages that will tell you most are hire ReactJS developers India, which sets out exactly how we vet and what our replacement terms are, and Node JS development services, which shows how a fixed scope build runs. Backend engagements have their own terms on the hire Node JS developer in India page, and both live projects are written up with numbers in our work.

Practices

The six things we do not negotiate on

These stay the same on every engagement, whoever the client is. The difference between a studio and a staffing agency is what it refuses to stop doing when a deadline gets close.

Decisions get written down

Every non obvious architectural choice goes into the repository as a short record: what we chose, what we rejected, why. Your next engineer reads it instead of guessing.

Nothing merges unreviewed

Including our work by each other. If your team has no reviewer we say so before starting, rather than discovering it in month two.

We measure before we optimise

No cache, no rewrite and no index without a profile first. This single habit separates the engineers we hire from the ones we turn down.

Estimates come with a range

And the range is honest, which means it is wider than you would like. A single confident number is a sales artefact, not an engineering one.

Bad news travels immediately

A slipping deadline reported on the day is a problem. The same news at the deadline is a crisis. We tell you the day we know.

We say no in writing

If the work sits outside React and Node, or the shape is wrong for us, that goes in an email you can forward, not a soft maybe that wastes a month.

Origin

Why we stay small, deliberately

We worked at larger firms before this, and the pattern was consistent: the person who won the work was never the person who did it.

The client found out in week three, when the engineer from the pitch had moved to another account. That is arithmetic more than dishonesty: a firm carrying a bench has to keep the bench busy.

So the constraint here is deliberate. Two concurrent engagements, no bench and no salespeople. It caps what we can earn and it means we turn work down most months, including work we would enjoy. What it buys is that the person in your interview is the person in your repository, which is the only structural guarantee we can honestly make.

What we are bad at

Scale, obviously. If you need six engineers next month we cannot help, and we will say so on the first call rather than after the contract. We are also poor at discovery work where the requirement is still forming, because that wants a room and a whiteboard rather than four hours of overlap. And we have no design capability at all: we build interfaces from your designs, we do not produce them.

A working day at the studio: dashboards on screen, hands on the keyboard

Questions

What people ask before signing

Six that come up on the call, including the two we would rather not be asked.

+What happens if one of you leaves?

Two people know every codebase, decisions live in the repository as written records, and you hold every account and credential. That reduces the risk without removing it. Being small, the honest answer is that continuity risk is higher here than at a large firm, and you are trading it for direct access to whoever writes your code.

+How do you decide which work to take?

React or Node, a client with a reviewer, and a scope we believe we can hit. If any of the three is missing we say no, which is why we turn work down most months.

+Are you hiring?

Occasionally, through the same six stage process every candidate goes through, written out on the hire pages. We do not keep a pipeline of pre vetted people waiting on a bench, which is also why we sometimes cannot start immediately.

+Where are you based, exactly?

Pune, India. We work 13:00 to 22:00 IST, which is four hours of overlap with New York and seven with London. There is no US office and we are not going to imply there is one.

+Do you use AI tooling?

Yes, as an assistant, reviewed like any other code. It has not changed what we charge or what we promise, and nobody here ships a diff they cannot explain line by line.

If the fit looks right, the fastest way to test it is a two week paid pilot on a real ticket. That is set out in full on hire ReactJS developers in India for frontend work and on hire Node JS developers in India for backend. If you would rather hand over a defined build to a date, Node JS development services covers scoping and handover.

Talk to the person who would write the code.

No account manager in the middle. Thirty minutes, and you pick the engineer's brain, not ours.

Book a 30 minute call

13:00 to 22:00 IST, or your morning.
Pune, India. Four hours overlap with New York.