Startups
Founders who need a first version that is small enough to fund and solid enough to sell. We help decide what not to build.
About
A technology partner for businesses that want to build, automate and scale.
Gimpact is a software company, not a body shop. We take responsibility for the outcome — the product working, the users adopting it, the operation getting easier — rather than for hours logged.
Who we work with
SMEs
Businesses where growth has outrun the spreadsheet, and the next hire would only be needed because the process is manual.
Growing companies
Teams adding a product line, a market or a channel, who need software delivered on a date they have already promised someone.
Established companies
Organisations with existing systems, real compliance constraints and an internal team we work alongside rather than around.
How we work
Business-first thinking
We start with what the project has to change commercially, and let the technology follow. A beautiful build against the wrong problem is still a failure — so if custom software is not warranted, or the timeline is not realistic, we say so before the invoice rather than after.
Transparent communication
Scope, estimates, decisions and weekly progress exist as documents you can re-read, not as things someone remembers from a call. You talk to the people writing the code, and questions are answered by someone who can change the thing being discussed.
Modern technology, chosen not chased
We build on current, well-supported tools — TypeScript, React and Next.js, Python, PostgreSQL, cloud infrastructure defined as code — because a stack your next developer already knows is cheaper to own. We are not interested in using your project to try something new.
Flexible engagement
A fixed-scope project, an ongoing team alongside your own, or a single phase to see whether we work well together. Work is split into funded stages, so the decision to continue is yours at every boundary rather than a single commitment at the start.
Long-term support
Typed code, tests where they matter, and documentation written for whoever inherits it — including a team that is not us. We keep working with clients for years, and that has to be because staying is the better option, not because leaving is expensive.
Who you actually work with
You work with the engineers, not an account layer
The people on your calls are the people writing the code. That is a consequence of being small, and it is the main practical advantage we have over a larger supplier: a question does not have to travel through anyone to reach the person who can answer it.
A team shaped for the project, not a bench to fill
We propose the roles a project genuinely needs — frontend, backend, mobile, design, QA, DevOps or AI — and say which of them we would not staff. If a project needs a specialist we do not have, we will tell you that rather than stretch someone into the role.
Meet them before you commit
We introduce the specific people who would do the work on the first or second call, before any contract. We would rather you judge the team than a page of photographs — which is also why there are none here yet.
The company, factually
- Operating base
- Tashkent, Uzbekistan — delivering remotely, no overseas offices claimed
- Working languages
- English, Arabic, Russian, Uzbek
- Gulf working-hours overlap
- Tashkent is UTC+5 — a one to two hour offset from the GCC, Sunday to Thursday
- Code ownership
- Client-owned from the first commit, in client-held accounts
- Published client work
- Only with written permission — case studies on this site are illustrative
- Accessibility baseline
- WCAG 2.2 AA targeted on every interface we ship
Technologies
Frontend
- Next.js
- React
- TypeScript
- Tailwind CSS
- React Native
- Expo
Backend
- Node.js
- Python
- PostgreSQL
- Redis
- Prisma
- GraphQL
AI
- Claude API
- OpenAI API
- pgvector
- LangGraph
- Whisper
- Evaluation harnesses
Cloud & DevOps
- AWS
- Vercel
- Docker
- Terraform
- GitHub Actions
- Cloudflare
How we handle your code, data and access
The questions an international buyer asks before signing, answered before they have to ask them.
Least-privilege access, removed at the end
Only the people doing the work get access, only to what the work needs, and it is revoked when the engagement ends. We will give you the list of who has access to what whenever you ask for it.
Your accounts, not ours
Repositories, cloud infrastructure and third-party services are opened in your company's name and we work inside them. Your production data does not live on our accounts, and removing us is a permissions change rather than a migration.
Secrets are never in code or chat
API keys, database credentials and tokens live in a secrets manager, not in a repository, a spreadsheet or a WhatsApp thread. Anything shared with us during a project is rotated at handover.
We ask for the least data that works
Development and testing run on anonymised or synthetic data wherever the work allows. We would rather not hold a copy of your customer records, and in most projects we do not need one.
Dependencies watched, not assumed
Automated vulnerability scanning runs on every change, and security patches are applied on a schedule agreed with you rather than when something breaks. Where a project has a support agreement, that schedule is written into it.
Confidential before anything sensitive moves
We sign a mutual NDA before you share anything you would not want seen, and we can work under your agreement rather than requiring ours. Nothing about a client engagement is published without written permission — including on this website.
What we are not
We are a software engineering company, not a compliance consultancy or a penetration-testing provider. Gimpact holds no ISO 27001 or SOC 2 attestation and does not certify anything. Where a project involves regulated data — health records, payment data, personal data under GDPR, PDPL or UK GDPR — we build to the requirements your compliance advisors, DPO and legal counsel set, we document what we did, and we say clearly where our responsibility ends and theirs begins. If your procurement requires a certified supplier, tell us at the first call and we will say plainly whether we can meet it.
Registered address
Tashkent, Uzbekistan. Full registered address is published here once filing is complete — we would rather leave this blank than print something unverified.
Delivery is remote worldwide. We hold no overseas offices and claim none.
12Global delivery
Built in Central Asia. Delivered worldwide.
We work remotely with clients across the Gulf, English-speaking markets and Central Asia, on their working hours and in their language.
Gimpact operates from Uzbekistan and delivers remotely. Regions listed are markets we serve — not office locations.
Markets we serve
Gulf & Middle East
- Saudi ArabiaUTC+3
- United Arab EmiratesUTC+4
- QatarUTC+3
- KuwaitUTC+3
- OmanUTC+4
- BahrainUTC+3
English-speaking markets
- United KingdomUTC+0
- United StatesUTC−5
- CanadaUTC−5
- AustraliaUTC+10
- New ZealandUTC+12
Central Asia
- UzbekistanUTC+5
- KazakhstanUTC+5
Working-hours overlap — Tashkent UTC+5
Next step
Have an idea? Let’s build it.
Tell us what you are trying to achieve. You will get a considered reply from an engineer — not a sales script.
We reply to project enquiries within one business day.