Before the first job
You would be handing
delivery to people you have not met.
So the awkward questions belong here rather than three weeks into a client engagement.
There are four co-founders and no account layer between them and the work. Moiz Khan owns automation architecture and decides what gets built and how it runs. Ibrahim owns build and workflows, and is usually the person your delivery lead ends up talking to week to week. Haad owns growth and client solutions. Ali owns marketing and sales. The company is based in Karachi with 25 engagements across six countries, works month to month rather than on an annual lock-in, and names each of the four with the route they took to get here.
A first job runs on the same shape as any other. The audit takes the first week and produces a written statement of what your client's tools will and will not permit, which is the finding that most often changes a proposal. One named system is live inside a fortnight, so there is something to show before anyone has been committed to a programme. What this cannot do is rescue a pitch already made. A capability sold before anybody checked whether the client's CRM lets an outside system write a record is the usual way these arrangements fail, and it fails on your side of the table, in front of your client.
There is no rate card here, for the same reason there is no price anywhere else on this site. The figure moves on the number of systems, the volume behind them, how much of the client's process exists in writing, and who is answerable in month four. That last one is what agencies price wrongly. A build quoted as a one-off turns into a liability the moment a client expects it to keep working, so the maintenance question is worth settling before the proposal rather than after the invoice. Whether any of this is worth doing is a margin question you can answer with a single job: take one piece of delivery you already sell, cost it honestly as it runs today, and compare.
Ownership is deliberately arranged against us. Systems are built inside your accounts or your client's, under logins you hold, and nothing carries our name. If you stop working with us you own the system and it carries on running. In the other direction there are fixed stops: advertising spend changes, anything published in a client's name, pricing decisions and any serious complaint wait for human approval, and an automation that meets something outside its scope hands it to a person rather than improvising. That is written into each build, because the agency in front of the client carries the consequence when it is not.