Nisbat means relation. That is the whole idea.

Most established businesses are not short of attention. They have traffic, a list, a customer base, and a history of people who once wanted what they sell. What they are short of is a path that carries a person from one of those states to the next without dropping them.

When acquisition, the website, email and follow-up are run as separate projects — often by separate people, on separate timelines — the handoffs between them are nobody's job. The ad spend is measured. The page is measured. The gap between them is not.

That gap is expensive precisely because the demand in it has already been bought.

You cannot fix a conversion problem by only looking at the page, because the page might be converting the wrong traffic. You cannot fix a retention problem by only writing better emails, because the emails might not be arriving. Diagnosing one part in isolation produces confident answers to the wrong question.

So the work spans acquisition, conversion, retention, reactivation and the automation underneath. Not because a studio should do everything, but because the leaks sit between those areas and cannot be seen from inside any one of them.

Nisbat is small on purpose. You work directly with Saad Hussain, who does the diagnosis, writes the plan and builds the system.

In practice that means the thinking and the execution never drift apart, decisions get made in a message rather than a meeting, and there is no account layer translating your problem to someone who has not seen your data. It also means the engagement list is short, and the honest answer is sometimes that this is not the right fit.