Let's Build Your Next Digital Product

Before You Write

What happens after you send that form

Contact pages usually promise a reply and explain nothing. Here is the actual process, so you know what you are getting into and can decide whether it is worth your time.

You will hear from a person, usually within one working day

Submissions go to an inbox read by our team, not into a CRM queue. The first reply is normally either a straight answer or two or three questions we need answered before we can say anything useful. We are in Pakistan Standard Time (UTC+5); if you write in the evening from Europe or North America, expect a reply the following morning our time.

What to include so the first reply is useful

You do not need a specification. You do need enough for us to tell whether we are the right people. The most useful messages include:

• What the software is for and who uses it. One paragraph is plenty.
• Whether something already exists. A live site, a half-finished app, a spreadsheet the business runs on. This changes the answer completely.
• A rough budget range, or a range you are testing. Not a negotiating position — it just tells us whether to describe a PKR 300,000 approach or a PKR 3 million one. If you have no idea, our published cost breakdown will get you to a range in ten minutes.
• Any hard deadline and why it is hard. A trade show, a funding milestone, a contract date.
• Anything unusual. Odd pricing rules, a legacy system that must be integrated with, data that cannot leave a particular country. These are the things that move an estimate.

Then: a call, and possibly a discovery phase

If it looks like a fit, we schedule 30 minutes to talk through scope, constraints and what has to be true on launch day. For a well-defined piece of work we can quote after that call. For anything ambiguous we propose a short paid discovery phase — typically five to ten days — producing wireframes, a technical approach and a firm build quote. The output is yours whether or not you then build with us. It is the cheapest stage of any project, because it is the only one where changing your mind costs nothing but a conversation.

We will sometimes tell you not to build it

If an off-the-shelf product would serve you better than a custom build, or a hosted e-commerce platform beats the bespoke one you were imagining, or you need a good mobile web experience rather than an app, we will say so. That answer has cost us work more than once and it remains the right answer. It is also, in our experience, the fastest way to tell whether an agency is worth hiring — ask three of them and see which one is willing to talk you out of something.

Confidentiality

Please do not send confidential business ideas, inventions or unpublished commercial detail through a public web form. If you need to share something sensitive, ask us for a non-disclosure agreement first — we will sign a reasonable one, quickly. Material sent without an NDA in place is treated as non-confidential, although we will not publish or misuse it. How we handle your details is set out in our Privacy Policy, and the terms covering submissions are in our Terms of Service.

Other reasons to get in touch

• A project that has stalled. If your developer has gone quiet or a build is stuck at "90% done", say so directly — we do rescue work and the first assessment conversation is free. Our list of the nine reasons projects fail may look uncomfortably familiar.
• Maintenance for something we did not build. We take over existing systems, subject to being able to read the code and get access to the infrastructure.
• Jobs and internships. Use the careers page rather than this form — applications there reach an engineer.
• A correction to something we published. Genuinely welcome. Include the page URL and what you believe is wrong; see our Editorial Policy.