Common questions

Questions before
the first conversation.

Practical answers about scope, data, AI feasibility and working with Zero One Touch. For details specific to your environment, bring the question to our team.

What does Zero One Touch do?

Zero One Touch is a senior-led engineering company in İzmir, Türkiye, founded in 2022. We build enterprise software, AI and data platforms, computer vision systems, integrations, kiosk/offline applications and source-grounded LLM/RAG workflows.

Can you work with our existing systems?

Existing platforms and workflows are part of the starting point. We assess their interfaces, data and constraints before defining the integration and modernization approach.

Do we need a fully defined specification?

No. A conversation can start with the problem, the people affected and the constraints you already know. Discovery helps turn that context into an actionable scope.

How do we start a conversation?

Share the problem you are trying to solve, the systems involved and what a useful outcome would look like. Email info@zeroonetouch.com to begin.

Can we start with a feasibility assessment?

Yes. Where data, integrations or operating conditions create uncertainty, an initial assessment can define what needs to be tested and what evidence would justify a larger scope.

How are project scope and timing determined?

Scope follows the problem, dependencies, acceptance criteria and available inputs. Timing is discussed after these constraints are understood. A useful initial conversation identifies the important assumptions rather than promises a delivery date without context.

Do you replace our internal engineering team?

The collaboration model depends on the engagement. We can discuss a bounded engineering scope and how it connects with your existing team, responsibilities and delivery process.

How are security and data requirements handled?

Data access, permissions, deployment constraints and operational responsibilities should be defined during discovery and architecture. Requirements depend on the application and your environment. Specific controls and responsibilities are agreed around the intended use.

How do you decide whether an AI approach is appropriate?

We identify the task, establish a baseline, examine data readiness and define evaluation criteria. A simpler rule-based system or an improved data workflow may be more appropriate if it meets the need more reliably.

What should we share before a first meeting?

A brief description of the problem, a real workflow example, the systems involved and any known constraints are enough to begin. Do not include credentials or sensitive datasets in an initial email.

Is your question more specific?

Describe your current workflow, the systems involved and the problem you need to solve.

Contact