FAQ
How we work, how we price, and what happens after launch. If your question is not here, ask us directly.
Working with us
Where is Foxbeta based, and do you work with clients abroad?
Our studio is in Imphal, Manipur, India. We work with clients across India and internationally, including Saudi Arabia, the UAE, the USA, the UK, Australia and Nepal. Almost all of that work is remote, run through scheduled calls, a shared project board and regular demos.
How do you handle time zones with clients in the Gulf, UK, USA and Australia?
India Standard Time (UTC+5:30) overlaps comfortably with Gulf working hours and with the UK morning. For Australia we use the Indian morning, and for the USA we schedule calls in the Indian evening. At the start of each project we agree fixed overlap hours in writing, so you always know when the team is available live.
Do you work with startups or established companies?
Both. We build first versions and MVPs for founders, and we design, extend and maintain systems for established businesses, public bodies and larger organisations. The process scales to the size of the work: lighter for an early product, more formal where governance and compliance require it.
Will you sign an NDA?
Yes. We sign a non-disclosure agreement before discovery, so you can share sensitive details about your business, users and plans from the first conversation.
What kinds of projects do you take on?
Web platforms, mobile apps, e-commerce, ERP and CRM systems, custom software and SaaS, automation, integrations and AI workflows, along with design and consulting. If your project sits outside what we do well, we will tell you early and, where we can, point you to someone better suited.
Pricing & contracts
How do your estimates work?
We start with a short discovery call to understand your goals, users and constraints. We then send a written proposal covering scope, approach, timeline, team and cost, with assumptions stated plainly. If the scope is not clear enough to estimate responsibly, we suggest a small paid discovery phase first.
What engagement models do you offer?
Two main models. Fixed-price projects are split into milestones and suit well-defined scope. Monthly retainers suit evolving products and ongoing work, with priorities set together each cycle. We help you choose the one that fits how certain your scope is.
What are your payment terms?
Fixed-price work is invoiced against agreed milestones. Retainers are invoiced monthly. We invoice in INR for clients in India and in USD for international clients. The schedule and terms are set out in the proposal before any work begins.
Who owns the code and intellectual property?
You do. On full payment, the intellectual property in the code and designs we create for you transfers to you, as stated in our contract. Any open-source or third-party components are listed along with their licences.
How are changes to scope handled?
Change is normal. On fixed-price work, we write up each change request with its effect on time and cost, and nothing proceeds until you approve it. On a retainer, new requests simply join the backlog and are prioritised with you.
Process & delivery
How often will we hear from you?
You will see working software in a demo every week. Between demos, you have direct access to a shared project board showing what is planned, in progress and done, plus a dedicated chat channel with the team. You also have a named project lead who is accountable for delivery.
How do you choose the technology stack?
We choose for the problem, your team and the long term, not for novelty. That means mature, well-supported tools that your future developers can work with, a stack that fits your hosting and budget, and a clear explanation of the trade-offs before anything is decided.
What does a typical project look like?
Discovery to agree goals and scope, design to shape the experience, then build in short cycles with weekly demos. Testing runs throughout, followed by launch and a handover with documentation. The length of each stage depends on the project, and the proposal sets it out in advance.
Can you work with our in-house team?
Yes. We can lead a project end to end, or work alongside your designers and engineers within your tools, repositories and review process. We agree roles and responsibilities at the start so ownership is never unclear.
Support & ownership
What happens after launch?
Most clients move onto a monthly care plan. It covers monitoring, security updates, dependency upgrades, backups, bug fixes and a set amount of time each month for improvements. The scope of each plan is agreed in writing, so you know exactly what is included.
Do we get access to the code and infrastructure?
Yes. Code lives in a repository you own or can access from day one, and hosting and third-party accounts are set up in your name wherever possible. At handover you receive documentation, credentials and deployment notes.
Can you take over a project built by another team?
Often, yes. We begin with a code and infrastructure audit, then give you a written assessment of the risks, quick fixes and longer-term recommendations before agreeing to ongoing support.
What if we want to move the work in-house later?
That is a reasonable goal, and we plan for it. With clean code, documentation and handover sessions, your own team can take over whenever you are ready. You are never locked in.
What happens next
- 01
We reply within one working day
A real person, with first questions about your goals.
- 02
We clarify scope and constraints
A short call about users, timelines, budget and risks.
- 03
You get a written proposal
Scope, team, timeline and a fixed or monthly price.
- 04
We start building
Kickoff within the week, a shared board and weekly demos.
Start a project
Bring the idea. We bring the team that ships it.