About

About Zeki Experts

We put one senior engineer next to the person who owns the problem, and remove everything that used to sit in between. That is the whole company. Everything below is a consequence of it.

Easier to judge a company on a call than a page. · Reply within 24 hours

Business analystProject managerSolutions architectCoordinatorONE WORKING DAYOwnerEngineernothing to translate
ModelForward deployed
EngineeringIslamabad
CommercialMountain View, CA
ClientsMostly US
Your codeYours from commit one
Since 2016

Ten years of building software, and what we kept.

The Zeki team has been building software since 2016. The work changed shape over the years. The habit of staying with what we built did not.

  1. 2016

    Founded in 2016

    Zeki Expert Solutions starts building software. The company is from Pakistan, and its engineering team works from Islamabad.

  2. Along the way

    Work we are known for

    Mobile banking for Maldives Islamic Bank, insurtech engineering for SelectQuote, and clinical AI now live in Norway as Talk!t. See the work.

  3. 2023

    The whole team in one room

    The annual get-together in Islamabad in February, then an exhibitor stand at ITCN 2023 a few days later.

  4. Today

    Forward deployed, and AI

    One senior engineer next to the problem owner, a commercial office in Mountain View, and AI built into how clients already work, as an AI implementation partner.

Why we work this way

The chain was the problem, not the people in it.

The standard way to buy software puts four roles between the person with the problem and the person who can fix it. A business analyst writes down what was said. A project manager schedules it. A solutions architect decides how. A coordinator keeps everyone informed. Every one of those roles exists for a reason, and every one of them is a place where meaning is lost and time is spent waiting.

We tried the other shape. One senior engineer, sitting close enough to the business to argue with the brief, who scopes it, builds it, ships it and is still the person you call six months later. No translation layer, because there is nothing to translate between.

When another shape suits the work better, we suggest it on the first call. What it suits is the large category of work where nobody is quite sure what the right answer is yet, and finding out is most of the job.

THE CHAINFaster refundsA portal?FORWARD DEPLOYEDFaster refundsShippedone engineer, same meaning
Each of those roles was solving a real problem created by the role above it. Remove the chain and the problems go with it.
What we hold to

Five commitments, all of them awkward for us at some point.

These are worth writing down precisely because each one costs us something. A principle that only ever helps the company is a slogan.

YOUR SHORTLISTYesNoYesyour questions, your call

You interview everyone

Every engineer we put forward is interviewed by you, with your questions, and you can say no. We publish the questions worth asking on each role page, including what a weak answer sounds like.

Costs us: the shortlist gets rejected sometimes.
your-company / appyourscommit 1

Your code is yours from the first commit

In your repository, under your licence, with no component that stops working when we leave. Nothing is held back to make the next conversation easier.

Costs us: no lock-in to fall back on.
THE RIGHT SIZESMLRecommended

We recommend the right size

Sometimes the honest recommendation is a smaller engagement or a different role. That conversation happens on the first call rather than in month three.

Costs us: the bigger engagements we talk ourselves down from.
THE OUTCOMEOwnernamedAccountableReachable after launch

One person owns the outcome

Not a pod, not a delivery manager, not a shared inbox. A named engineer who is accountable for whether the thing works, and who is still reachable after it ships.

Costs us: we cannot hide a weak hire behind a team.
INVOICEmonthlyEngineer, flat rateProject managementHandoverCoordinationnotice period, no lock-in

No line items for coordination

A flat monthly rate per engineer, billed for the time they are deployed, with a notice period rather than a lock-in. No separate charges for project management or handover, because there is no project management or handover.

Costs us: a revenue line most firms rely on.
HOW WE VETExercise from a real weekRun by someone in the roleMethod over answerPublished on the role pageReverse a binary tree
How the bench works

Ten roles, vetted on work rather than puzzles.

Everyone on the bench has passed four exercises drawn from what that role actually does in a normal week, run by somebody who does that job. No algorithm riddles, because we have never once needed an engineer to reverse a binary tree under time pressure.

The exercises are published. Each role page lists exactly what was tested and, where it is interesting, what share of candidates fail it. A claim of "rigorous vetting" that does not say what was tested is not a claim at all.

Where we are

Two offices, one working day.

Commercial in California, engineering in Islamabad. In practice that means a live overlap with US mornings and a written handover for everything outside it.

HOW OUR WORKING DAYS LINE UPCaliforniaIslamabadLIVE OVERLAP: US MORNINGSPlus a written handover for everything outside it
United States

Mountain View, California

1049 El Monte Avenue
Ste C #684
Mountain View, CA 94040
+1 202-992-5235

Commercial and contracting. Working hours Pacific.

Pakistan

Islamabad

Kickstart, 189 Korang Road
I-10/3
Islamabad
+92 331-111-0214

Engineering. Overlaps US mornings and European afternoons.

Questions

The things people ask about the company.

Small enough that a senior person from Zeki takes the first call on every engagement, and large enough to hold a bench across ten roles. We will tell you the current number on that call rather than put a figure on a web page that goes stale.

You do, in your repository, from the first commit. No escrow, no licence back to us, and no component that stops working when the engagement ends. This is not a negotiating position, it is in the contract.

You keep the code, the documentation and the deployment. We stay reachable for questions, and if you want continued support that is a separate, smaller arrangement rather than something bundled in to make leaving awkward.

No. Every engineer deployed on your work is ours, interviewed by you, and on our payroll. If we ever could not staff something ourselves we would say so rather than quietly broker it.

Because that is where the company is from, and because the talent is genuinely strong and considerably less expensive than the Bay Area equivalent. The honest trade is timezone: you get a live overlap with US mornings, and a written handover culture for everything outside it.

Next step

Bring us the problem, not the spec.

Thirty minutes with the person who runs the company, and a straight answer about whether this shape of engagement fits what you are trying to do.