Pricing & Engagement

Are the prices on your site final?

They're indicative, published so you can tell early whether we're in your range. Every engagement still gets a written, fixed-scope estimate based on your actual requirements before anything is agreed — the number on the page is a starting point for that conversation, not a quote.

Do you work fixed-price or hourly?

Both, depending on the work. Scoped projects — custom software, web apps, mobile apps, MVPs — are fixed-scope: one price for an agreed set of deliverables. Team augmentation and day-rate work are billed hourly or monthly, because the whole point is flexible capacity, not a fixed deliverable.

How does payment work?

A fixed-scope engagement starts with a signed statement of work and a deposit of 30% of the first phase; the rest is billed against milestones. Retainers and team augmentation are billed monthly. Full terms are in our Refund & Cancellation Policy.

What happens if the scope changes midway?

It goes through a written change request with a revised estimate before we continue. We don't quietly absorb scope creep into the original price, and we don't stop work to argue about it — you get a number, you decide, and only then does the change happen.

Do your prices include VAT?

No — the published bands are VAT-excluded. Your written estimate will state the applicable VAT treatment for your engagement.

Process & Delivery

What happens after I send an enquiry?

We reply within one business day. If there's a fit, we turn your enquiry into a written, fixed-scope estimate before anything else happens — you're not committing to a sales call to find out roughly what this costs.

How long does a typical project take?

It depends on the service: an MVP typically runs 8–12 weeks, a full custom software or web application build 10–18 weeks, a code audit 2–4 weeks. Your written estimate states the specific timeline for your scope, not a generic range.

Who will I actually talk to during the project?

The engineers doing the work, not a rotating account manager. You get a weekly check-in during active build phases and async updates in between, through whatever channel makes sense for your team.

Do you provide staging environments before launch?

Yes, on every build. Nothing goes to production without going through a staging environment first, and you can look at the staging link at any point during the engagement, not just at the end.

How do you work with clients outside Portugal?

The same way we work with clients in Portugal — remotely, in your working hours. We're a Western European Time studio, which for most of our EU and UK clients means a genuinely overlapping working day, not a handoff across a large time gap.

IP & Ownership

Who owns the code once the project is finished?

You do. Code and IP transfer to you on completion and full payment — that's a standing commitment, not a negotiated extra. There's no licensing arrangement that leaves you dependent on us to keep running your own product.

What about third-party libraries and tools you use?

Where we use open-source libraries or paid third-party services (a payments provider, a hosting platform), those remain subject to their own licences or your own accounts — we'll tell you plainly what's in the stack and what it depends on, so there are no surprises after handover.

Do we get the source code and credentials at handover?

Yes. Handover includes the full source code repository, environment access and a written maintenance guide — not a zip file with no explanation.

Can you sign an NDA before we share details?

Yes. We'll sign a mutual NDA before any scoping conversation that requires sharing confidential information — just ask.

Data & Security

Is our data handled under GDPR?

Yes. We're a Portuguese business operating under GDPR and Lei n.º 58/2019, with the CNPD as the supervisory authority. Our own website collects no personal data server-side by default — see the Privacy Policy for exactly what is and isn't collected.

Where is our data stored, and by whom?

For a client engagement, data handling is agreed as part of the statement of work and depends on your infrastructure choices — we'll document exactly where project and user data lives before we start building. For the website itself, our enquiry form transmits nothing to us; it opens a pre-filled email in your own mail client.

What security practices do you follow during development?

Dependencies are kept current, access follows least-privilege by default, and code goes through review before it merges. For anything handling sensitive data, we agree specific security requirements with you at the scoping stage rather than assuming a default.

What happens to our data and access after the engagement ends?

Access we were given to build or maintain your system is handed back or revoked as agreed at handover — we don't retain standing access to a client's production systems once an engagement ends, unless you've asked us to under an active support retainer.

Still have a question?

Send us the specific thing you're stuck on — we'd rather answer the real question than make you guess from a general FAQ.

support@codebridgelab.com · +351 669 299 026

Ask us anything.

If it's not answered above, ask directly — we reply within one business day.

Choose what you're comfortable with. You can change this at any time from the 'Cookie preferences' link in the footer.

Essential

Required for the site to work — stores your cookie choice only (cbl_consent). Can't be switched off, and doesn't track you.

Analytics

Google Analytics 4 (GA4) — helps us understand how the site is used, in aggregate. Doesn't load until you switch this on.