New Check out our latest insights on AI and Cloud Transformation. Explore Blog

Help center

Questions people ask us before they sign anything

Pricing, timelines, process, technology choices, security and who owns the code at the end. Answered the way we would answer them on a call, including the ones where the honest answer is “it depends, and here is what it depends on”.

Working with OrbixEdge

We offer a comprehensive range of software development services, including custom web and mobile app development, ERP and CRM systems, e-commerce solutions, cloud-based applications, and enterprise software development.
Yes. Launch day is the beginning rather than the end. Our post-launch packages cover active monitoring, security patching, feature work and infrastructure scaling, so the product stays reliable as your user base grows.
We specialize in a wide range of technologies, including PHP, Laravel, Node.js, React, React Native, Flutter, Python, MySQL, PostgreSQL, and cloud platforms like AWS and Azure.
Yes, we work with businesses of all sizes, from startups to large enterprises. Whether you need a simple web application or a complex enterprise-level system, our team has the expertise to deliver high-quality solutions tailored to your specific needs.
We work to an agile process built around transparency. It opens with a technical discovery phase that settles the scope and a fixed cost, then runs in two-week sprints, each ending in a tested increment you can actually use, through to launch and handover.
Security is part of the architecture from day one, not an audit bolted on at the end. We use secure coding standards, automated dependency and vulnerability scanning, role-based access controls, and encryption in transit and at rest. Any compliance requirements specific to your sector are agreed during scoping.
We handle project timelines and deliverables through careful planning, regular communication, and milestone-based delivery. Our project managers work closely with clients to establish realistic timelines and ensure that deliverables are met on schedule.
You do. On final payment, 100% of the source code, repositories, infrastructure access and intellectual property rights transfer to you. We do not lock clients into proprietary ecosystems or licences you cannot leave.

Pricing, contracts and timelines

There is no honest single answer before we know what is being built, which is why we do not publish a price list for custom work. What we do is run a discovery session, write the scope down, and give you a fixed price or a costed range against that document. If a studio quotes a custom platform on a first call without seeing your requirements, the number is a placeholder and the invoice will not match it.
Four: a fixed-scope project for a defined build, a dedicated team for ongoing product work, staff augmentation to fill a specific skill gap in your own team, and a support and maintenance retainer for systems already in production. Each one is set out on our engagement models page, including where it is the wrong choice.
A focused marketing site or a WordPress rebuild is usually weeks. A first version of a custom platform or a mobile app is usually a few months. A full ERP across several departments is longer, and we would normally stage it so the first module is live while the rest is still being built. You get a dated schedule with the scope document, not a range on a call.
It usually does, and that is fine. Anything outside the agreed scope is written up as a change request with its own estimate and its own effect on the schedule. Nothing gets built and invoiced without your approval first, and nothing quietly displaces work you have already paid for.
Yes, with one condition: the budget has to fit the smallest useful version of the idea. We would rather scope a genuine first release you can put in front of users than take a budget that only covers a third of the thing you described and leave you with a half-built system.
Fixed-scope projects are invoiced against milestones, starting with an initial payment on signature. Dedicated teams, staff augmentation and support retainers are invoiced monthly. The full payment schedule is in the contract before any work begins.

Process and communication

We go through what you are trying to achieve, what already exists, who uses it and what it has to integrate with. The output is a written technical scope: architecture, features, integrations, assumptions, what is explicitly out of scope, a schedule and a price. It is a document you own, and it is useful even if you take it to another studio.
The engineers doing the work, plus a project lead. Our discovery and consultation calls are run by an engineer rather than a salesperson, and the same people stay with your project after the contract is signed.
A demo at the end of every two-week sprint on a working environment you can log into, a shared board you can look at whenever you want, and a direct channel to the team. You never have to ask for a status update, and there is no grand reveal at the end.
Yes. If you already run Jira, Linear, Asana or a board of your own, we work in it. Bringing your process to us is not on the list of things you should have to do.
One person who can make decisions and is reachable, timely feedback on demos, and access to the systems we need to integrate with. The most common cause of a project slipping is not engineering — it is waiting on an answer or a credential.

Technology and architecture

From what the system has to do, what your team can maintain, and where you are likely to be in three years — in that order. We are not going to put a niche framework into your business because it is interesting to us. If your in-house team knows Laravel, there needs to be a very good reason to hand them a Go service.
Usually, and usually that is the better call. We start with an audit of what is there, then either extend it, wrap it in an API, or replace it a module at a time with both systems running in parallel. A full rewrite is occasionally right, but it is the most expensive option and it should be argued for, not assumed.
Both, and the distinction matters less than the fit. Most business problems are solved best by integrating an existing model with careful prompting, retrieval over your own data, and a human review step. Training something bespoke is worth it in a minority of cases, and we will say so when yours is one of them.
It is designed to. In practice that means a database schema and indexes that hold up as tables grow, caching where it earns its place, background queues for slow work, and infrastructure that scales horizontally rather than by buying a bigger server. We load-test before launch rather than finding the ceiling in production.
Yes, and they are part of the estimate rather than an optional extra. Automated tests cover the critical paths, and you get architecture notes, deployment steps and a runbook for the routine jobs. It is the difference between owning a system and owning a folder of code.

Security, ownership and life after launch

Yes. We sign an NDA before any detailed discussion, our engineers work under confidentiality agreements, and access to your systems is limited to the people on your project. Your project is not used as a portfolio piece or a case study without your written permission — which is why the case studies on this site name sectors rather than companies.
Deployment to production, a full smoke test on the live environment, monitoring and backups verified as working, DNS and certificates checked, and a rollback plan ready before we start. We schedule launches when the team is available afterwards, not on a Friday evening.
Every fixed-scope project comes with a warranty window: defects in what we built are fixed at no charge. Beyond that, a support retainer covers monitoring, patching and ongoing fixes, with the response windows and escalation path written into the agreement.
That is the intended outcome for most clients. Handover includes the repositories, infrastructure access, environment setup, architecture documentation and a walkthrough with your engineers. There is no dependency on us built into the code, and no licence you have to keep paying for.
Wherever your requirements need it to be. We deploy to AWS, Azure and Google Cloud, and the region is chosen with your data residency obligations in mind and agreed during scoping. The infrastructure runs in your own cloud account wherever you want it to.

Still deciding?

The three pages people usually read next: how we contract and bill, the work we have shipped, and the sectors we already know our way around.

Engagement models Case studies Industries we serve All services

Get In Touch

Ready to turn your vision into a shippable product?

Book a no-obligation 30-minute discovery call with one of our lead engineers — not a salesperson. We will go through your architecture, give you timeline and cost estimates, and map the way forward, whether or not you build it with us.

An OrbixEdge technology consultant ready for a strategy call

Schedule a free strategy call

A 30-minute call with an engineer, not a salesperson. We will talk through what you are building, what it should cost, and how long it takes. No obligation either way.