Understand the operation first
Before architecture, we learn how the work actually happens — including the workarounds people have quietly built to keep things moving.
- Home
- About
About / Teslian Tech
A software engineering studio, not a slide deck.
Teslian Tech designs and builds digital products from India — web platforms, mobile apps, SaaS and business systems, and the automation around them. This page explains how we work rather than how good we say we are.
Company Teslian Software Solution LLP Brand Teslian Tech
What we actually do
Most of our work starts the same way: a business depends on software that either does not exist yet, or exists and no longer fits. Someone is holding the operation together with spreadsheets, manual steps and a system nobody wants to touch.
We take that situation and turn it into something dependable — through product definition, interface design, engineering across web, mobile and backend systems, and automation where it removes real work without removing human judgement.
We build our own products too, which is why the constraints of running software in production shape how we build for other people. Billing that has to reconcile, stock that has to be right, a shop counter that cannot wait for the network to come back.
Operating principles / 01
Six rules we do not bend.
These are the decisions that make delivery predictable. They also explain most of the times we push back.
Write the decision down
Trade-offs, boundaries and ownership are documented while they are still cheap to change, not reconstructed from memory a year later.
Ship in increments you can inspect
Progress is shown in working software against agreed acceptance criteria, not in status percentages.
Treat security as product behaviour
Permissions, sanitisation, data handling and failure paths are designed and reviewed, not bolted on before launch.
Design for the second year
The system has to be maintainable by people who were not in the room when it was built. That constrains what we are willing to add.
Say the uncomfortable thing early
If scope, timeline and budget do not fit together, we say so at the start rather than discovering it near the deadline.
Working together / 02
What collaboration looks like.
Projects go wrong in predictable ways. Most of them are avoided by agreeing this up front.
What you get from us
- A named point of contact who understands the technical detail
- Written scope, architecture direction and acceptance criteria
- Working software at review points, not slideware
- Documentation, repository access and a real handover
- An honest answer when something is harder than estimated
What we need from you
- Access to the people who actually do the work being digitised
- One decision-maker who can settle scope questions
- Realistic constraints stated early — dates, budget, compliance
- Feedback at review points while changes are still inexpensive
- Agreement on what "done" means before we start building
Products we run / 03
Software we own, not just software we ship.
These are Teslian platforms you can open and use. Running them is what keeps our engineering opinions grounded.
MyTelephone
Business discovery and communication across responsive web and mobile apps.
Open MyTelephone ↗Sales workspace
Storefront, catalog, media tooling and commerce reporting in one operational workspace.
Open Sales workspace ↗Tesmed
Pharmacy billing, stock, batches, expiries, purchasing and GST summaries.
Open Tesmed ↗TesPOS
Retail point of sale covering inventory, billing, reporting and offline-aware store workflows.
Open TesPOS ↗Client work is listed separately and only where publication has been approved. See selected work →
People / 04
Who you will be working with.
The people listed here are the ones recorded in our own directory. We do not pad this page with stock photography.
amara botha
ios developer
Vishal goshwami
Project manager
Abhishek shah
founder
eliza sheikh
cofounder
Evidence policy
What we will not put on this website.
We do not publish client names, logos or screenshots without recorded permission. We do not publish outcome figures — revenue, conversion, user growth — unless the client has verified them. We do not present internal products or explorations as client case studies.
Where those things are unavailable, we describe the scope that shipped and the engineering decisions behind it. That is less impressive and more useful.
Inspect the work →Start a useful conversation
If this is how you want to work, let's talk.
Bring the problem in whatever shape it is currently in. Clarity is part of the job, not a prerequisite for starting.
Contact Teslian Tech