Skip to main content

About

A cabinet.Not an agency.

Mayank and Atul take on projects together. Mayank leads discovery and business decisions. Atul leads architecture and production engineering. You work directly with both of them.

Why two isthe right number.

We have both spent years on the other side of this: inside agencies, inside client programmes, watching the same failure repeat. A senior team wins the work, a junior team delivers it, and eighteen months later there is a platform nobody can operate and a maintenance bill nobody forecast.

What changed is that two people can now carry the workload that used to need a team, if they build with AI rather than talk about it. That is not a marketing line, it is the actual reason this works. It is also why the security discipline is not optional: throughput like that, pointed at production systems with real credentials, is exactly how organisations get hurt.

So the shape of the firm is deliberate. Two senior people, 3 active engagements at a time, no bench to keep busy, and a fixed quote before you commit. When a build genuinely outgrows us we say so and scope it separately, by name, in writing. We would rather lose the work than staff it badly.

We are generalists, not a sector practice. Between us we have shipped in real estate technology, coliving and property management, payments, insurance and consumer products. The skill we actually sell is learning an operation quickly and building for it honestly.

Who turns up

Two people.No bench.

You work directly with Mayank and Atul, from the first conversation through delivery.

What to build, and whether it pays

Mayank Pokharna

Mayank brings eleven years of experience in shared living and property operations. He connects business needs with practical technology choices and uses AI to help build useful products.

He leads discovery, writes the specification, and helps you decide whether the work is worth doing.

LinkedIn

Making it survive production

Atul Kumar

Atul brings fifteen years of engineering experience. He works across architecture, infrastructure, deployment, and security, with production needs considered from the start.

He owns the architecture and deployment, reviews access permissions, and handles production issues.

LinkedIn
More about us and how we work→

How we work

Six positionswe actually hold.

A firm with no position is a vendor. Disagree with any of these on the call and we will have a useful argument.

  1. 01

    Build first, then design, then fix

    We agree the specification, build an initial version, and put it in front of real users. Their feedback helps us refine the design and implementation before release.

  2. 02

    Leave with something useful

    Every engagement produces something your team can use, such as a working screen, a report, or a running workflow. Meetings should move that work forward.

  3. 03

    The line you draw is respected

    You decide where AI belongs in your business and where human judgement should remain. We respect those boundaries when choosing and building workflows.

  4. 04

    Fix the measurement before the workflow

    We agree how to measure the outcome before changing the workflow. If the tracking is missing, we put it in place first.

  5. 05

    Give clear advice and respect your decisions

    We explain our recommendations and raise concerns early. Once the direction is agreed, we focus on delivering the work.

  6. 06

    Choose architecture your team can maintain

    We use pinned model versions, clear data models, and as few moving parts as the work allows. The system should be straightforward to operate and support.

The boring part

How we contract.

Contracting terms
BillingMonthly in advance. USD via Wise or SWIFT.
Fixed-scope workThe Survey, Blueprint, Build and Hardening are each quoted as a fixed number before you commit. Not a range, and never an hourly rate.
Ongoing workMonth to month, 30 days notice either side, rate held for the engagement. No minimum term.
Not includedThird-party software and model API costs. These sit on your own accounts so you see them directly and they stay yours.
OwnershipYours from the first commit. Code, prompts, orchestration, eval sets, runbooks, documentation.
NDAStandard, and we will sign yours. We also have a mutual version that covers AI tool use, screen-share exposure and recording consent, which most templates miss.
Larger buildsWhen a build outgrows two people, there is a Delhi team we have worked with for years. Scoped, quoted and named in writing before anyone touches your systems. Never folded into our fee.
The checkpointOn any ongoing engagement, at four to six weeks, we ask one question: is this worth what you are paying? We give our own answer first.

Still reading?Let us talk.

Book a thirty-minute conversation about your workflow and goals. We will help you decide whether we can make a useful difference.

Book 30 minutes

3 engagements at a time