First we understand the business. Then we build the technology.

A fixed-scope diagnostic typically starts from USD 8,000 and takes two to three weeks. The number moves with the number of systems, sites, and process owners involved. We quote the pre-project company audit before we quote the build.

A map of how the company actually earns money; the processes, data, organisation, and IT systems behind it; bottlenecks and growth points; and a sequenced change plan. You leave with a document you can take in-house — not a slide that only we can interpret.

Usually no. We start from the systems you already run. Replacing a system of record is a last resort, not a default. The typical job is to connect new capability to what already holds the truth.

Yes, when the process, data, and access rules allow it. We connect to CRM, ERP, BI, telephony, document stores, and APIs. If a system cannot be integrated safely, we say so in the pre-project company audit instead of forcing a side chatbot.

The ones that change a measured workflow: assistants and agents in sales, support, documents, HR, finance, and internal knowledge; automation of repetitive hand-offs; analytics that operators actually use. Not a model for every department on day one.

We choose the stack from the task: availability, security, data residency, integrability, and long-term support in your market. That can mean local platforms, international models, on-premise, cloud, or a hybrid — not a fashion choice.

Where the engagement specifies: your tenant, a regional cloud, or a hybrid. We do not move production data into a demo sandbox and leave it there. Residency and access control are part of the design, not an afterthought.

Yes. We design for the cloud, infrastructure, and security rules of the market you operate in. If the requirement is a specific provider or region, that constraint is in the architecture from the pre-project company audit.

Yes. On-premise and hybrid deployments are a normal option when policy, latency, or cost require it. The product still has to connect to the systems of record — hosting is a decision, not the whole design.

A pilot on one process is typically weeks, not quarters. A production slice with integrations is often 6–12 weeks after the pre-project company audit. Scaling to more processes follows measured results, not a big-bang programme.

From a baseline taken in the pre-project company audit: time per task, cost per case, error rate, cycle time, or revenue leakage. We estimate effect on that metric before the build and measure it after go-live. If the case is weak, we recommend not to build.

That is the default. Pre-project company audit → use case → business case → pilot → integration → scale. A pilot is a working slice in the live process, not a disconnected prototype.

Yes. We build customer-facing and internal platforms when the business model needs a product, not only an automation. Internally we use the OBS Pulse SaaS platform under a licence agreement — without handing the full architecture to the market.

Yes. The English site is for international mid-market companies and founders. We analyse how the business works, then design and build what the operating model actually needs.

Yes — after we test the business hypothesis. We do not build an MVP for its own sake. First we decide what must be proven on the market; only then we build the smallest product that can prove it.