How we work
How an engagement runs.
Five stages, each with a fixed scope and a clear deliverable. At the end of every stage, you decide whether to continue.
01
Discovery call
30 minutes
02
Feasibility study
1–3 weeks
03
Design & prototype
Scoped in writing
04
Build & deploy
Typically 6–16 weeks
05
Tune & support
Ongoing
Stage
01

Discovery call
We talk through the problem, the data you have, and what a good outcome looks like in business terms. If we are not the right fit, we say so on the call.
You receive
A short written summary of the problem and our recommended next step.
Stage
02

Feasibility study
We examine your data, test the core approach on a small scale, and name the risks before you commit to a build.
You receive
A feasibility report, a working proof of concept, and a fixed quote for the build.
Stage
03

Design & prototype
We design the architecture and interfaces, and build a prototype your team can use with real inputs.
You receive
A design document and a working prototype.
Stage
04

Build & deploy
We build the production system, test it against the agreed business metric, and deploy it into your environment.
You receive
The deployed system, source code, trained models and documentation.
Stage
05

Tune & support
Once real data starts flowing, we monitor performance, retrain models and make improvements.
You receive
A monthly performance report and a named engineer to contact.
What you can count on, at every stage.
You own everything
Code, trained models, data pipelines and documentation are transferred in full.
A fixed, written scope
Each stage is priced and scoped in writing before work begins.
Direct to the engineers
You speak with the people building the system.
We stay through the results
Support continues after launch, as the system meets real data.
Common questions.
Who owns the code and the models?
You do. Source code, trained models, data pipelines and documentation are transferred to you in full at the end of the build.
How is pricing set?
Each stage has a fixed price agreed in writing before it starts. There are no open-ended hourly bills.
Can you work alongside our own engineers?
Yes. Many engagements are a joint effort, and we plan the handover so your team can run the system without us.
Which time zones do you cover?
We are based in Lahore. Our working hours overlap with US Eastern mornings and most of the UK and European business day.
What if the feasibility study says no?
Then you have spent weeks rather than months, and you have a written explanation of why — which is useful in its own right.
