Question 1

How big is the team?

Accepted Answer

Cambotix is a small senior team, and we tell you that up front. You work directly with the engineers building your system. There is no account manager relaying messages, and nobody quietly outsourcing your project. When a piece of work needs a specialist we do not have, we say so rather than improvise.

Question 2

What is the smallest project you take on?

Accepted Answer

Around $2,500, typically for a technical audit or discovery sprint. Below that, the contract, scoping and handover work can cost more than the value you receive. A freelancer on an hourly basis may serve you better, and we will say so.

Question 3

How do you communicate during a project?

Accepted Answer

A written update every week covering what shipped, what is in progress and what is blocked, plus a call whenever it is useful. You get direct access to the person building your system. What we do not do is go quiet for a month and then reveal something.

Question 4

Do you sign NDAs?

Accepted Answer

Yes, before discovery if you prefer. Our standard service agreement already includes mutual confidentiality, and we are happy to sign yours instead.

Question 5

Can you work with our existing team?

Accepted Answer

Yes. We regularly work alongside in-house developers. Sometimes we own one part while they own another; other times we review the architecture. It works when responsibilities are clear from the start, so we define them during scoping.

Question 6

Why is your quote higher than the freelancer we spoke to?

Accepted Answer

Because we may be quoting for different work. A lower quote often excludes discovery, testing, deployment, migration, documentation and handover. Those are the parts that determine whether the system still works in a year. Compare the line items, not only the totals. If the cheaper quote genuinely covers everything, take it.

Question 7

What if the project runs over?

Accepted Answer

On fixed-price phases, our estimate is our responsibility. You pay the agreed amount. Timelines change only when the scope changes or when we are waiting on you, and both are tracked in writing.

Question 8

Do you require payment up front?

Accepted Answer

A deposit of around 40%, followed by milestone payments, with the balance due at delivery. We never ask for 100% up front, and you should be wary of anyone who does.

Question 9

What happens if we want to cancel?

Accepted Answer

You can terminate with written notice. You pay for work completed to that point and you receive everything produced so far: code, designs, documentation. No penalty clause, no held hostage repository.

Question 10

Who owns the code and the data?

Accepted Answer

You do, in full, after final payment. We transfer the repository, documentation and infrastructure access to your organization. We keep no license or kill switch, and the system does not depend on our continued involvement.

Question 11

What if we want to move to another developer later?

Accepted Answer

You can, and the handover is designed for it: documented code, a written runbook, standard technologies and no proprietary framework of ours in the middle. A team that makes itself hard to replace is protecting itself, not you.

Question 12

Where will our system be hosted?

Accepted Answer

On infrastructure you own, using accounts registered in your name. We usually use AWS or a VPS when that fits the budget better. We configure everything and hand over the credentials. Your data never sits in a Cambotix account.

Question 13

How do you handle security?

Accepted Answer

Access control enforced server-side rather than in the client, secrets kept out of the repository, dependencies patched, encrypted transport, and a security review before go-live. For systems handling payments or personal data we scope this explicitly rather than assuming defaults are enough.

Question 14

Do you write tests?

Accepted Answer

We focus testing where failure is expensive, including money movement, access control and order state. We do not chase a coverage percentage. Twenty useful tests are better than four hundred that nobody reads.

Question 15

What is covered by the warranty?

Accepted Answer

We fix any defect in the delivered scope at no charge for 30 to 60 days after launch, depending on project size. New features go through a change request or a retainer.

Question 16

Do we have to keep paying you?

Accepted Answer

No. Plenty of clients take the system in-house after handover, which is a fair outcome. A retainer makes sense when you want continuous improvement and someone accountable for uptime, not because you are locked in.

Question 17

What happens if something breaks at 2am?

Accepted Answer

Under a standard retainer, we respond by the next business day. If your operation needs a faster response, we define and price that commitment clearly. We will not imply a response time we cannot meet.

The answers, including the awkward ones.

Working with us

Cost & contracts

Technical

After launch

Question not answered here?