How we work.

1. 01

   We start with the operation as it really runs, not with a feature list. Discovery happens with the people who run it: the routine as it happens, not as it is written down.

2. 02

   Scope in writing before the first line of code. What's in, what's out, the schedule, and a fixed price.

3. 03

   Scope changes get an approved estimate before work starts. Nothing is built and billed after the fact.

4. 04

   You test before going live. Acceptance testing in a staging environment, with your team clicking through it.

5. 05

   Goes live with Karu Tech on call. An assisted cutover; documentation included.

6. 06

   It continues afterward, under contract. Maintenance with a defined scope and hours; ongoing development and integrations as the operation needs them.

• Engineering in practice. A staging environment separate from production. Versioned database migrations. Documentation included in every delivery. Every system gets a security review before go-live; the platform Karu Tech operates has been penetration-tested.

• The data is the client's. Exportable at any time. In any exit scenario, the domain and the data stay with the owner.

• Isolation per client. Each client runs on its own instance, with a separate database. No data is shared between clients.

• AI with human review. A design principle: nothing the AI prepares goes out without a person reviewing it.

Security and data, in detail →

• We don't sell development by the hour: what we sell is a project with a defined scope, schedule, and fixed price.
• We don't start a project without discovery and a written scope.
• We don't hand over a system nobody supports afterward.
• We don't keep data beyond what the contract says.