UBIKON.ioHow we work
Ubikon is a remote studio in Indore, India, building for founders and CTOs in the US, UK, EU, Australia and the Middle East. This page answers the practical questions that decide whether a remote engagement is workable — overlap hours, who you actually talk to, how progress is visible, and what happens if it goes wrong. Together with our published prices, standards and guarantee, it forms the Glass-Box Method.
Timezone overlap
Where the working day actually meets.
Office hours are 10:00–19:00 IST, Monday to Saturday. This is what that means for you.
| Your region | Live overlap | Best call slot for you |
|---|---|---|
| UK | ~4.5 hours | Morning — lands mid-afternoon IST |
| Europe (CET) | ~3.5 hours | Morning — lands afternoon IST |
| UAE / Gulf | ~7.5 hours | Any working hour |
| US East | ~1 hour | Your morning — evening IST |
| US West | Scheduled | Your early morning — evening IST |
| Australia (AEST) | ~3.5 hours | Your afternoon — morning IST |
Live overlap is where synchronous calls are easy. It is not how much work happens — weekly build reviews are async by default so no one holds a recurring call at an awkward hour.
The week
What a working week looks like.
You get a build you can open, every week
Not a status percentage or a burndown chart — the actual product, deployed somewhere you can use it, with a video walkthrough of what changed and a written changelog. This is the single most important control an overseas client has: if a week produces nothing openable, something is wrong, and you find out that week rather than at a launch date three months away.
You talk to the engineer, not an account manager
The senior engineer directing your build is the person answering your questions. Nothing is relayed through a salesperson to a team you never meet. This falls out of the delivery model rather than being a policy: one senior engineer directing an AI-augmented system does not have a pyramid of juniors to shield.
Decisions get written down
Architectural choices that are expensive to reverse — data model, auth strategy, hosting, whether something belongs on the client or the server — are written down with the reasoning at the time, not reconstructed afterwards. When you take the codebase in-house, that record goes with it, so the next team inherits the why and not just the code.
Scope changes are quoted before they are built
If you add real scope mid-build it gets priced against the same line-item delivery data the original quote came from, and agreed before anyone starts. It is never silently absorbed into a larger final invoice. That is the practical meaning of a fixed quote: the number changes only when you decide it should.
Contracting and payment
A registered company, invoicing in USD.
Who you are contracting with
Ubikon Technologies Pvt. Ltd., a registered Indian company at C21 Mall, Scheme 54 PU4, Vijay Nagar, Indore, Madhya Pradesh 452010. That is the entity on the agreement and on every invoice. There is no foreign shell, no US office, and no claim of one.
NDA first, if you want one
Send yours before the scoping call or ask for ours at the start of it. It costs nothing and gets signed before you describe anything. Most founders do not bother — but nobody should have to argue for it.
Milestone-based payment
Invoiced in USD against the fixed quote, split across agreed milestones with the schedule written down before the first line of code. Third-party running costs — hosting, API usage — are passed through at their real cost rather than marked up, and are named during scoping.
You keep what has been built
Full IP transfer applies to work delivered, not only to a completed project. The milestone structure exists precisely so neither side is trapped in a bad fit: if the engagement is not working, it ends at a milestone boundary and you leave with working code, a private repository and documentation. The commitments this rests on are collected on the Walk-Away Guarantee page.
Straight answers
What overseas clients ask before booking
What timezone do you work in, and how much overlap will I get? +
Ubikon works 10:00–19:00 IST (UTC+5:30), Monday to Saturday. That gives roughly 4.5 hours of live overlap with the UK, 3.5 with most of Europe, all morning with the UAE and Singapore, and an early-evening IST slot that lands in the US morning. Nobody is asked to hold a recurring call at 2am — the weekly build review is async by default, and live calls are booked in your timezone.
Who do I actually talk to during the project? +
The senior engineer directing your build. There is no account manager relaying questions to a team you never meet, and no junior developer learning on your budget. That is a direct consequence of the delivery model: one senior engineer directing an AI-augmented system rather than a pyramid of billable juniors.
How do I know work is happening between calls? +
A build you can open every week, a video walkthrough of what changed, and a written changelog. Not a status percentage, not a burndown chart — the actual product, running. If a week produces nothing openable, that is the signal something is wrong, and you get told rather than shown a green dashboard.
What does contracting look like for an overseas client? +
A written agreement covering scope, milestones, payment schedule and IP transfer, signed before work starts. NDA first if you want one — send yours or ask for ours. Ubikon Technologies Pvt. Ltd. is a registered Indian company at C21 Mall, Vijay Nagar, Indore, Madhya Pradesh 452010, and invoices as that entity.
How does payment work across borders? +
Milestone-based, invoiced in USD against the fixed quote. Payment terms and the exact milestone split are agreed in writing before the first line of code. Ongoing third-party costs (hosting, API usage) are passed through at their real cost rather than marked up, and are called out during scoping so they are never a surprise on an invoice.
What happens if the project goes wrong? +
You keep everything built to that point — full IP transfer applies to work delivered, not only to a completed project. The engagement is milestone-based specifically so neither side is locked into a bad fit: if it is not working, you stop at a milestone boundary with working code, a private repo and documentation, not a half-finished dependency on us.
What happens after launch? +
Store submission, infrastructure and monitoring are part of the build, not a follow-on quote. After that you can take the codebase entirely in-house — it is yours, on a mainstream stack any team can pick up — or continue with a monthly product squad. There is no proprietary runtime you have to keep paying for either way.
One call. One fixed number.
Book a scoping call in your timezone.
30 minutes, no deck. You'll leave with sharper scope, and a fixed quote lands within 48 hours.