About
A small engineering practice, deliberately.
Who we are, how we work, and the situations where you should hire somebody else.
Teknith Solutions builds and runs software for organisations that need the work done properly rather than quickly. We lead with custom AI because that is where the gap between demo and production is currently widest — and where the cost of getting it wrong is highest.
We are engineers rather than a sales organisation with a delivery arm. The person who scopes your project is the person who builds it, and they will tell you when something is harder than it looks. There is no account manager between you and the work, which is partly a philosophy and partly a consequence of our size — we would rather stay small enough that the arrangement keeps being true.
Small also means we take on fewer projects than we are asked to. A practice this size can either run several engagements shallowly or a few of them properly, and the second is the only one worth buying. It is why the list of work on this site is short, and why every project on it is one we would still describe in detail years later.
We have worked across fintech, healthcare, retail and commerce, logistics, education and public sector. We do not claim a specialism in any of them — the engineering problems rhyme more than the industries differ.
The practice
Only the facts a client could check.
No project counters, no client tallies, no awards page. What is below is either a date on a document or a sector with work on this site behind it.
The practice, in numbers we can stand behind
- Working since
- 2024
Incorporated as Teknith Solutions PVT. LTD. in 2026. The practice and the company have different birthdays, which is ordinary — the work started first.
Sectors we have shipped into
- Building materials
- Retail
- Marketplace
- Gaming
- Professional services
- Precast concrete
- Manufacturing
- Social
- Travel
How we work
Six positions we will not trade away.
We will tell you not to build it
The most valuable thing we can say in a first conversation is often that the project is not worth doing, or not yet. We would rather lose the work than take money for something we expect to fail.
Boring infrastructure, interesting products
Novelty in your deployment pipeline buys you nothing and costs you every on-call rotation. We keep the surprises in the product, where they are worth something.
Work you can take back
No proprietary lock-in, no undocumented magic, no dependency on us. Every engagement ends with a codebase and a set of runbooks another team could pick up.
Estimates with their assumptions attached
A number without its assumptions is a guess with false confidence. Ours come with the reasoning, so you can see which assumptions move the figure and challenge them.
Your accounts, your repository
The work happens in your GitHub organisation, your cloud account, your CI. It costs a little friction in the first week and saves you the month of untangling at the end, because there is nothing to hand over that was not already yours.
Written down while it is still true
A runbook written after handover is written from memory. Ours are written while the decision is still being made — which is the only point at which the reasons behind it are still accurate.
When we are the wrong choice
Four situations where you should hire somebody else.
Nobody on your side has time to set direction
Engineers absorb work; they cannot absorb decisions. If there is no one with the authority and the hours to answer questions, adding us makes the project slower and more expensive rather than faster. A short scoping engagement is the honest version of that request.
The specification is settled and you want it typed
We are at our most useful in the decisions about what to build first, what to defer, and what to refuse. Handed a finished document and asked not to question the parts that will not work, we are an expensive way to get a worse result.
The date is fixed and so is the scope
One of the two has to give, and we will tell you which we think it should be. If the answer is genuinely neither, we are the wrong firm and would rather say so in the first call than in the eleventh week.
You are comparing on hourly rate
We will not be the cheapest quote in the stack, and a comparison run on rate alone will not go our way. The place we are cheaper is the second year, which is not a column on the spreadsheet.
The work each service turns down is listed on the services page.
What that looks like in practice
Positions are cheap to write.
These are the engagements they were written from.
A floor designer in the browser, with an order-ready PDF at the end
An interactive tile design and ordering tool: choose layouts, designs and fills, watch the floor render live, and leave with an order-ready PDF template.
ZishesA marketplace with games inside it, and the pipeline that ships it
A React Native marketplace app with Unity games embedded in it, running on self-managed Kubernetes with GitOps delivery — where a deploy is a commit and a rollback is a revert.
A global professional services firmA form builder that took IT out of the loop
A custom platform letting administrators at a global professional services firm build, manage and analyse internal forms in real time — without raising a ticket for every new one.
Ask us the awkward question first.
Whether it is worth building, whether we are the right people to build it, what it will cost when the optimistic assumptions do not hold. Those answers are free, and they are the ones that decide the project.
Start a conversation