Question 1

How much does a project typically cost?

Accepted Answer

It depends heavily on scope, but to give you a realistic anchor: our construction ERP for a German contractor (18 active sites, DATEV integration, offline mobile) was delivered in 8 months with a team of 6. Our auto parts data platform for a German B2B distributor (10M+ SKUs, 40 suppliers, partner APIs) was 9 months with 7 engineers. Most of our engagements land between €80K and €400K total. We're not the cheapest option — if budget is the primary constraint, we'll tell you upfront.

Question 2

How long does a project take?

Accepted Answer

The projects that go fastest are the ones where the client knows exactly what's wrong and can be in the room during discovery. Our ERP for a German construction contractor went from kickoff to pilot site in 10 weeks because the CTO had already mapped their 11 approval chains before we started. Projects where scope is still being defined at kickoff routinely run 2x over initial estimates — and that's true everywhere, not just with us.

Question 3

Who do you typically work with?

Accepted Answer

Mid-market B2B companies, typically 20–500 employees, in EU and APAC, that need regulated or data-heavy systems. We don't do consumer apps, and we're not a good fit for MVP/idea-stage validation — there are faster and cheaper ways to test a hypothesis than a dedicated engineering team. Our best clients already know what they're building and need it done correctly.

Question 4

What is your development process?

Accepted Answer

We run 2-week sprints with a sprint review every fortnight where you see working software, not slides. Every architectural decision gets documented as an ADR (architectural decision record) inside the codebase — so if someone on your side or ours changes, the reasoning doesn't walk out the door with them. We insist on a discovery phase before any code, usually 2–4 weeks. The two ERP attempts that failed before us at a Bau contractor client were both projects that skipped discovery.

Question 5

Will we own the source code and IP?

Accepted Answer

Yes, 100%. Source code, database schemas, IaC configurations, and all documentation transfer to you at each milestone. No licensing fees, no usage caps, no vendor lock-in. This is standard in all our agreements — we'll show you the exact clause before you sign anything.

Question 6

Do you sign NDAs before discovery calls?

Accepted Answer

Yes, always. We sign a mutual NDA before any discovery call where you share system details, data structures, or business context. We'll send it to you before the call so you have time to review — we're not going to ask you to explain your architecture before you've seen our NDA.

Question 7

What timezone do you work in, and how does the overlap work?

Accepted Answer

We're in Ho Chi Minh City (ICT, UTC+7). For EU clients (CET/CEST), our engineers are available from 14:00–18:00 ICT, which is 08:00–12:00 CET — a solid 4-hour overlap for standups, reviews, and live problem-solving. We run async-first: decisions are written, not spoken, so the hours you're not overlapping still produce output you can review in the morning.

Question 8

What happens if a developer leaves mid-project?

Accepted Answer

It's happened. What actually occurs: we have a minimum 4-week handover period, the leaving engineer documents their active work in the codebase, and we pair the replacement with a senior from the same project for 2 weeks. Our ADR practice means the replacement isn't starting blind — the reasoning behind every major decision is already written down. We've never had a project derail from a team change.

Question 9

Can you work with our existing team and systems?

Accepted Answer

Yes. Two of our most common engagements are (1) augmenting an existing internal team with senior engineers who join your standups, use your tools, and commit to your repo, and (2) building a new system that integrates with an existing ERP, LIS, or POS that can't be replaced. We've integrated with SAP S/4HANA, DATEV, Roche Cobas analyzers via HL7 v2, and Windows POS systems via file-based adapters. If it has an export mechanism, we can work with it.

Question 10

What technologies do you use?

Accepted Answer

Primarily .NET 8/9 and Java Spring Boot on the backend, Next.js and Angular on the frontend, PostgreSQL as the primary database, Apache Kafka for event-driven systems, and AWS or Azure for cloud. We're not technology-agnostic in the sense of using whatever sounds current — we use what has a long support window, a strong hiring market, and that we've shipped production systems with. We'll recommend against a technology if we think it's the wrong choice for your situation.

Question 11

Do you provide ongoing support after launch?

Accepted Answer

Yes. Most clients stay with us after launch for retainer-based maintenance (bug fixes, security updates, minor features) or a dedicated team model for long-term product development. For healthcare and regulated systems, we also support audit preparation and documentation updates as regulations evolve.

The questions clients actually ask

Common Questions

Pricing

Timeline

General

Process

Legal

Integration

Technology

Support

Still Have Questions?

Let's Turn Your Idea into Reality