How a project runs,from first call to support
Before any code is written you have a written plan, a fixed price and a date. After that, there is working software on a link every week.
The process
The same steps for a two-week automation or a three-month product. Only the length of the build changes.
01
A 30-minute call
You tell us which task takes your team the most time. We ask about volumes, the tools involved and anything that can't change. By the end of the call you'll know whether we're a good fit.
If we're not the right people, we point you to someone who is where we can. If an off-the-shelf product would do the job, you'll leave with its name.
30 minutes, free, with Zohaib
Fig. 01Workshop with sticky notes 02
A written plan and a fixed price
You get a short document: what we'll build, how it connects to your systems, where a person approves things, what it costs and when you'll see it working.
Larger projects start with a paid scoping phase that ends in the same document. The price is fixed per milestone. Anything added later is quoted in writing before we start it.
Usually within a week of the call
Fig. 02Wireframes sketched in a notebook 03
Build, with a demo every week
Working software on a link you can click, every week. Automations run on copies of your real data before they touch production.
You'll have a shared channel on Slack, WhatsApp or email, and a weekly call at a time that works across Dubai, UK and US hours.
2–14 weeks, depending on scope
Fig. 03Writing code at a desktop 04
Run it, then improve it
We launch alongside your team, watch the first weeks closely, and fix what real use turns up. Then you choose: a monthly plan with us, or a handover to your own people.
The monthly plan covers monitoring, fixes, updates when tools or AI models change, and a short monthly note on what ran, what failed and what we'd change next.
Fixes included after launch
Fig. 04Analytics dashboard on a laptop
How projects are priced
There is no public rate card because the range is wide: a single automation and a SaaS product are very different sizes of work. After the first call you get a fixed price in writing, and the budget question on the contact form helps us suggest the right scope from the start.
What the contract says
The parts clients ask about most. The full agreement comes with the written plan.
- 1.
Ownership
Copyright in what we build for you is assigned to you as each milestone is paid. Code and workflows live in your accounts from day one.
- 2.
Confidentiality
We sign your NDA, or send ours, before you share anything sensitive. Data processing agreements for projects that handle personal data.
- 3.
Payment
Milestone payments, usually a deposit to start and the rest as milestones are accepted. Invoices in USD or AED.
- 4.
Changes
Anything outside the agreed scope is quoted in writing before we start it. No surprise invoices.
- 5.
Communication
A shared channel on Slack, WhatsApp or email, a weekly call, and a staging link where you can click through the work at any time.
- 6.
Handover
Logins, documentation and a handover call. If you'd rather your own team runs it, we help them get comfortable with it first.
Everything people ask us
Missing something? Ask on the call, or write to hello@encnt.com and we'll add the answer here.
It depends on scope, so we price after a short scoping call rather than from a rate card. A single automation is a small project; a voice agent connected to your calendar and CRM is larger and has monthly running costs for calls and AI usage; a portal or SaaS first release is larger again. You get a fixed price per milestone in writing before any work starts.