ProCraft — PartnerUAE
Accountants, consultants, studios and business-setup firms meet owners who run a business on a spreadsheet and a WhatsApp group. If that’s you, this page is for you. It’s short on purpose — the terms get agreed on a call, and written down before anything else happens.
These aren’t case studies — we don’t publish results before a client confirms them, and we’re not going to invent partner ones. They’re the three situations we’re set up for.
Stock is in a sheet, sales are in a book, and the two don’t agree until March. The accountant doesn’t sell software and shouldn’t have to. They make one introduction, sit in on the first call if they want to, and hear from us when the work is scoped, when it’s signed and when it goes live. If a referral fee is agreed, it’s paid when the client pays us. [client to confirm fee basis and timing]
Six months on, the client asks for a customer portal and an app, and the studio has no developers. We build it under the studio’s name or ours — the studio decides — against a written scope the studio has read first. The studio keeps the relationship. We keep the code working, and the support tickets come to us. [client to confirm whether white-label is offered as standard]
They want RestPOS in the kitchens but not the support desk. We supply the product, the training and second-line support with a name and a number. The consultant does the site visits, the menu setup and the first-line calls. What each side earns is on paper before the first install. [client to confirm revenue share and regions]
Not on this page: platform and technology partnerships — payment gateways, hosting, marketplaces. We don’t run a programme for them. If you think there’s a genuine fit, write anyway; we read everything.
We’d rather turn down a bad introduction than chase a good one. That’s the whole filter.
We want
We’d rather not
Three short lists, one per track. Where a line reads [client to confirm], it’s still being agreed on the call and written into the agreement — not hidden.
Introduce
Build
Install
No dashboard, no login, no tiers. An email thread and a page you’ve signed.
The form below, or info@procraft.ae. Tell us who you meet, where, and how you’d like to work with us. A few lines is enough.
[client to confirm length], you and us. We explain how we scope, what we turn down, and what we pay or charge. You tell us what your clients actually ask for. If it isn’t a fit, we say so on the call. If you’d rather we didn’t speak to your client directly, we work through you.
A short written agreement: what counts as an introduction, what’s paid and when, who talks to the client, what stays confidential, how either side ends it. Nothing we wouldn’t sign ourselves. [client to confirm: existing template, NDA, term]
You make one when it’s right. We reply within one business day, copy you in where you want to be, and send you a line at scope, signature and go-live. The client hears from a person, not a funnel.
Tracking is a dated record, not software: the introduction email, the scope number, the signed date. You can ask to see it at any time.
What kind of clients, where, and how you’d like to work with us. One real example helps more than a pitch. Terms are agreed on the call, not in the form.
If yours isn’t here, ask it on the call or by email. · info@procraft.ae
For introductions, no — you can introduce clients to whoever you like. We ask one thing: that the client knows they’ve been introduced to us and has agreed to a call. For install partners, territory and any exclusivity by city is agreed in writing before the first install — see “What you get” for the Install track. [client to confirm territory and exclusivity terms]
You tell us before we speak to the client — an email or a copy on the thread is enough. There’s no tracking link and no portal. We keep one record of who introduced whom, and you can ask to see your part of it at any time. If the same business reaches us on its own first, we tell you.
If a fee is agreed, it’s written into the one-page agreement before the first introduction and paid when the client pays us, not when they sign. The level and basis are agreed on the call. [client to confirm level, basis — fixed, percentage, or per stage — and whether it applies to renewals and product licences]
Yes, where it’s agreed in advance — your name on the work, ours in the code, and a scope you’ve read before we start. We’ll ask before citing the build in our own record; you can say no. [client to confirm whether white-label is offered as standard and the portfolio rule]
Yes. Ask on the form or in your first email and we’ll send one before the call. Mutual, short, no non-compete hidden in it. [client to confirm a template exists]
We’re registered in Dubai, Abu Dhabi and Sharjah, and our delivery team serves projects in Saudi Arabia and India. For StockFlow and RestPOS we need someone on the ground where the shop or kitchen is, which is where implementation partners come in. Elsewhere by arrangement. [client to confirm whether Oman, Qatar or other GCC states are in scope]
Decided on the call and written down. For an introduction, usually us, with you copied in as much or as little as you want. For studio work, you — we speak to your client only in the room with you. For StockFlow and RestPOS installs, you handle first line and we handle second line, with a name and a number on both sides. Support for what we built still comes to us, so it never lands on your desk. If a client asks us directly, we send them back to you.
No. We build scoped work — what gets built, what it costs and how long — under a written scope. If you need people by the hour, that’s a different kind of company, and we’ll point you to one where we can.
One email is enough. We reply within one business day, from whoever actually reads it.
Looking to start a project instead? See Contact