Straight answersto fair questions.

Every price is agreed for the project at hand. As a rule, a defined scope gets a fixed price per milestone, and open-ended work, such as ongoing improvement, is billed monthly. Either way, the numbers are in the proposal before anything starts.

Yes, before you share anything confidential. We can sign yours or send ours.

Yes. We can build alongside your developers, take on a defined part of the system, or hand over to them at the end. Code and decisions are written so another team can pick them up.

The people doing the work. You get a direct channel to them and a regular review where you see what was built, what comes next and what needs a decision from you.

Yes. We work in English and Romanian, from Bucharest, on Eastern European time. Most collaboration happens remotely, with in-person workshops when they are worth the trip.

You choose. We can stay on under an Operate agreement, or hand everything over with the documentation your team needs to run it without us.

No, and we will not imply otherwise. We complete security questionnaires and explain exactly how the practices on this page apply to your project.

Yes. Where we process personal data on your behalf, an agreement under Article 28 of the GDPR is part of the contract.

Where the project requires it, in EU regions of the providers you choose. Before a system goes live we document which services receive which data.

No. When a project uses AI models, we choose providers and settings that do not train on your data, and we name them before they are used.

Only the people working on your project, each with their own account. Because that access lives in your accounts, you can see it and revoke it at any time.

No. Most of the value comes from connecting systems that are already scattered. Consolidation can follow later, once the workflow proves what actually needs to move.

We scope data access to what the system genuinely needs, keep processing inside infrastructure you control where that is required, and document what leaves your boundary. Specifics are agreed before anything is built.

We design for that. Systems cite sources, surface confidence, and route to a person where a wrong answer would be expensive. Automation replaces the repetitive part of the work, not the accountability for it.

A focused first workflow is usually a matter of weeks rather than months. We deliberately start with one process that matters, prove it in production, and expand from there.

It depends on where the pain is. If the problem is how it looks and reads, a redesign is enough. If the problem is publishing speed, integrations or performance, a redesign will hide the issue for a few months and then it comes back.

Yes. We model the CMS around the way your team writes and hand it over with the structure documented. No developer should be needed to publish a page.

Often. If a design system already exists we build to it. If it does not, we design the parts the project needs rather than an entire brand.

React Native when the product is largely shared logic and speed of delivery matters. Native when the experience depends on platform capability — heavy graphics, deep hardware access, or a specific feel. We decide it from the requirements, in the open.

Frequently, no. If there is no repeated moment of use, a fast mobile web experience will outperform an app nobody installs. We will tell you if that is the case.

You do. We publish under your organisation and hand over the full release process.

None, and you should be careful with anyone who does. What we commit to is a measurable objective, an instrumented system, and a review rhythm where the numbers are visible to you as they are to us.

No. We treat acquisition as part of the product system — the same engineering, analytics and iteration discipline applied to demand instead of to features.

Yes, and they stay yours. We work inside your accounts so the history, the audiences and the learning remain with you.

Yes. The output is a plan your own team can execute. We would rather be useful once than be necessary forever.

Usually weeks, not months. It is deliberately short — its value is in unblocking the build, not in replacing it.

Often, yes — as an audit. A second read on sequencing and architecture is cheap compared with discovering the problem in month four.