Help Center & FAQs

Send a short description of what you need to [email protected] or through the contact form. You get a reply within two working days. The first conversation is about the problem and costs nothing; a written scope and a fixed quote follow before any work is billed.

Three things. What the software has to do, who will use it, and when you need it working. A list of features is useful; a description of the process you are trying to fix is more useful. If you have an existing site or system, its address and hosting details let us check the technical starting point before quoting.

Yes. A single landing page, a WordPress site that needs rescuing, or one automation that removes a daily manual task are all normal pieces of work. Small projects are quoted the same way as large ones: fixed scope, fixed price, agreed before starting.

That is normal and it is a reason to start, not a reason to wait. The first conversation is about the process you want to fix rather than the software you think you need, and quite often the map that comes out of it removes a step or two before anything is built. What we will not do is quote a fixed price against an unclear scope: that quote would be wrong, and both of us would find out in month three.

A content-managed site with your branding and real content is usually a matter of weeks. A custom application depends on how many rules it has to encode and how much existing data has to be migrated. The honest answer is that the build is rarely what sets the date: waiting on content, on approvals, and on access to a system somebody else controls accounts for most delays, and all three are on your side rather than ours. We say so at the start so the schedule is realistic rather than optimistic.

Usually you, because you know the business. What we do is give you a structure to fill and tell you what each page has to achieve, which is the part most people find hard. If you would rather not write it, we can, and it is quoted separately. What does not work is launching with placeholder text and intending to replace it: sites launched that way still carry the placeholder a year later, and search engines have already judged the page.

Price follows scope, not page count. The three things that move a quote most are how much of the work is custom rather than configured, how many systems the software has to talk to, and how much of your existing data has to be migrated and cleaned. Published market surveys put development rates in Pakistan between $25 and $75 an hour depending on seniority and stack. NUZM quotes per project instead, so the number you approve is the number you pay.

It gets written down and priced before it is built. A change is quoted as its own small piece of work with its own effect on the timeline, and nothing starts until you approve it. Silent scope growth is the most common reason fixed-price projects turn adversarial, so it is handled in writing every time.

You do, on final payment. That includes the source code, the repository, the domain, the hosting account and every third-party account created for the project. Handover is a step in the project, not a favour asked for afterwards.

In stages tied to delivery, not to dates. A typical split is a deposit to begin, a payment when the build is ready for your review, and the balance at handover. Retainer work for marketing, SEO and support is billed monthly.

Yes, before any detail is shared, and at no charge. Your own document is fine; we do not require ours to be used. Client work is not discussed publicly or used as an example without written permission, and that holds whether or not an NDA was signed.

One person, for the whole project. That contact stays the same from the first call to handover, so you never explain the background to somebody new. The people building the work sit behind that contact rather than in a separate queue.

Weekly, in writing, whether or not the week went well. A week with a blocker in it is the week you most need to know about. Between updates you can reach your contact during office hours, Monday to Friday, 8am to 10pm Pakistan time.

Pakistan Standard Time is UTC+5, which overlaps the whole European working day and the first half of the North American one. Written updates carry the work across the gap; calls are booked inside your working hours rather than ours.

Yes. Pakistan Standard Time is UTC+5, which overlaps the whole European working day and the first half of the North American one, so a client in either region reaches a person during their own hours. Written weekly updates carry the work across the gap, and calls are booked inside your working hours rather than ours. Payment in foreign currency is normal and is agreed before work starts.

You see the work on a staging site at each stage rather than at the end, which is what makes this recoverable: a direction that is wrong is caught in week two, not week ten. Work is checked against the written scope before you review it, so a disagreement is normally about the scope rather than about quality, and the scope is a document we both agreed. If a stage is genuinely not what was scoped, it is redone at no charge. If what was scoped turns out to be the wrong thing, that is a change, and changes are quoted before they are built.

Access is requested per system, in your name, with the least permission the work needs, and it is handed back or revoked at the end. Passwords are not emailed and are not kept in a document. Live customer data is not copied onto a developer machine; work is done against a reduced or anonymised copy where real data is not required. If a system cannot be accessed any other way, we say so rather than quietly working around it.

Web: WordPress, custom PHP and the MERN stack (MongoDB, Express, React, Node). Back-end systems: Elixir, Go, Scala and Clojure. Mobile: Flutter, native Android and cross-platform builds. AI and automation: n8n, Make, custom chatbots, and model fine-tuning including XTTS for voice. The stack is chosen after the requirement, not before it.

Use WordPress when the site is mostly pages and posts, your team will edit it, and the features you need already exist as maintained plugins. Build custom when the software has rules of its own: pricing logic, approvals, integrations, anything a plugin would have to be fought into doing. Choosing custom for a brochure site wastes money; choosing WordPress for an application creates a system nobody can safely update.

The work worth automating is repetitive, rule-shaped and currently done by a person copying between screens. Answering the same twenty customer questions, reading an order email and entering it into a system, chasing an unpaid invoice, sorting enquiries to the right person. NUZM builds these on n8n and Make with custom chatbots on top, so the logic stays visible and editable rather than hidden inside a subscription.

By limiting what it is allowed to answer from. An agent answering from your own documents and your own database, with a defined refusal when it has no source, is a different piece of software from one improvising. Anything that costs money or leaves the company goes to a person for approval before it is sent.

Every build is tested on a low-end Android device on a slow connection, because that is what most visitors in this market are holding. A site approved on a fast laptop over office broadband tells you nothing about what your customers experience. In practice that testing changes the design: it is where oversized images, unreadable type and buttons too small to hit get caught.

Often, and the first step is always an assessment rather than a quote. We look at the code, the hosting and the accounts, and tell you whether it is cheaper to continue or to rebuild. Sometimes the answer is rebuild, and saying so early costs you less than discovering it after three months of patching. Before anything else you will need the repository, the hosting login and the domain registrar account, and if the previous supplier holds any of those, getting them is the real first task.

Technical fixes such as speed, crawlability and structured data can change how a site is indexed within weeks. Ranking for a competitive commercial phrase takes months, because it depends on other sites referring to yours and that cannot be bought honestly at speed. Anyone promising a first-page position by a fixed date is either bidding on your brand name or selling you a report.

Answer Engine Optimisation is the work of getting your pages quoted inside AI answers rather than only listed in search results. It does not replace SEO; it sits on top of it, because an engine cannot quote a page it never crawled. The practical difference is in how a page is written: complete answers near the top, question-shaped headings, plain factual sentences that survive being lifted out of context, and structured data that marks a question as a question.

No, and they are kept separate on purpose. You pay the platforms directly for ad spend, from your own account, so you can see every rupee that was spent and stop it yourself. The management fee is for the work of running the campaigns.

What was done, what it cost, what changed in the numbers, and what is planned next. Rankings and impressions are context, not the point. The figures worth reading are enquiries, calls, and sales, and where they came from.

Yes. Logo work is delivered as vector files (AI or SVG) alongside PNG and JPG exports, in full colour, single colour and reversed versions, with the fonts named. A logo you only have as a PNG is a logo you cannot print, and that is a problem you discover at the worst moment.

Two rounds inside each design stage. In practice the number matters less than the order: direction is agreed before detail, so revisions correct a layout rather than restart a concept. Additional rounds are quoted rather than absorbed, which keeps the first quote honest.

Defects found in the first thirty days are fixed at no charge. Beyond that, support is a monthly arrangement covering updates, security patches, backups and a set amount of change work. You are also trained to run the parts you should be running yourself, because paying an agency to publish a blog post is a waste of your money.

You take everything with you. The code is in your repository, the accounts are in your name, and the site is built on tools another team will recognise. Nothing is written to make leaving expensive.

We set it up in your name rather than resell it under ours. That matters more than it sounds: hosting bought through an agency means your site sits inside their account, and its continuity depends on their business continuing and their bills being paid. An account in your name with your billing details is one you can move, and one nobody can hold.