Chat with us

How we work

Hiring a remote engineering team you have never met is a real risk, and the honest answer to that is specifics rather than reassurance. This page sets out who does the work, where your data goes, what we will sign, and what happens if something goes wrong, so you can judge us on commitments instead of adjectives.

Saqib Ali Javaid, Founder & Engineer at Maltoki Dev
Saqib Ali JavaidFounder & Engineer

You talk to the person who writes the code

Saqib Ali Javaid does the engineering. Not an account manager who relays messages, and not a senior who sells the work before handing it to someone you never met.

This is the one genuine advantage of being small, so it is worth stating plainly: there is no bait-and-switch available to us. The person on the call is the person building it.

Nothing is subcontracted without telling you

If a project needs a specialist we do not have (a particular compliance review, a design pass, a language we do not write), we will tell you before engaging anyone, name them, and let you decide.

We will never put your work in front of a third party you have not been told about. If that is a hard requirement for you, say so and we will put it in the contract.

Hours you can actually rely on

We work 09:00 to 18:00 PKT (UTC+5), with 4+ hours of daily overlap with UK. That is a commitment to be reachable in those hours, not a claim to be awake constantly.

Within them, expect a reply within a few hours. For US clients the overlap is early morning Eastern. If that does not work for how you operate, it is better to know now than to find out in week three.

Your data stays in your accounts

Automations run on infrastructure you own, using credentials you hold and can revoke. We do not copy your data into our own systems, and we do not need a permanent copy of anything to do the work.

Access is requested per system, scoped to what the build needs, and handed back at the end. Where a staging dataset is needed, we would rather you anonymise it than send us the real thing.

Contracts, IP and the paperwork

Scope agreed in writing before any work starts. Fixed-price milestones for larger builds, each approved before the next begins. Source code and intellectual property assigned to you on payment.

NDAs signed on request. We will work from your paperwork rather than insisting on ours.

When it breaks, you hear about it from us

Every build includes error handling that alerts rather than failing silently, plus thirty days of fixes after handover.

After that a Care Plan from $750/month covers monitoring and repairs. Without one, the system is still entirely yours and still documented. You are not stranded, you simply maintain it yourself or ask us for a quote.

Need the paperwork settled before you talk to us? Say so at hello@maltoki.dev and we will deal with the DPA, the standard contractual clauses or an NDA first, without a sales conversation attached. See also our privacy policy and terms.

The questions procurement asks

Can you sign a data processing agreement?

Yes. A DPA covering the Article 28 terms a controller needs from a processor is signed before any access is granted. We would rather work from your own template than insist on ours, since your counsel has usually approved it already and that removes a round of review. Raise it at the enquiry stage and it is handled alongside the scope.

We are in the EU. Is transferring data to Pakistan lawful?

It is, with the right mechanism in place. Pakistan has no European Commission adequacy decision, so a transfer relies on the EU standard contractual clauses (Module 2 for controller-to-processor) alongside a transfer impact assessment. Both are put in place before any access is granted, and we will work from your own counsel’s documents where you have them. For UK clients the equivalent is the UK IDTA or the UK addendum to the EU SCCs. Have your own counsel review them; that is the normal and correct process rather than a sign of a problem.

Who has access to our systems during a project?

One person: the engineer doing the work. Access is requested per system, scoped to what the build needs, and revoked at handover. You can audit and remove it at any point without asking us.

What if we need to stop the project partway?

You can, at any milestone boundary. You pay for completed milestones and receive everything produced so far, including source and documentation. Fixed milestones exist precisely so that stopping is a clean decision rather than a negotiation.

How do we know progress is real?

You see working software rather than status reports. Each milestone ends in something you can use, deployed where you can reach it, plus a short written note on what changed. If a week passes with nothing to show, that is a signal worth raising, and we would rather you raised it.

Still have a question we have not answered?

Ask it directly. A straight answer costs us nothing and tells you more than a brochure.

Five-star client reviews on Fiverr, from Switzerland, France and the United States.