Frequently asked questions

We work with companies that have real workflows and real operational data -- mid-size businesses where the bottleneck is not the absence of AI interest but the absence of structured integration. Size matters less than whether the team actually runs on the systems we would be integrating into. We are not the right fit for early-stage companies without established processes.

We integrate with the systems your team already runs on: accounting platforms, marketplace channels, CRM systems, messaging channels, internal databases, document stores, and reporting infrastructure. If your stack sits on the Turkish business side -- ERPs common among Turkish mid-size companies, e-Fatura, KDV reporting, marketplace integrations -- that is well within our scope. We work at the category level; specific platforms are evaluated during the diagnostic.

Yes. International engagements run in English and are priced in USD. The workflow, the phase structure, and the delivery standards are the same. The only difference is that Turkish-market-specific integrations -- e-Fatura, local ERP connectors, domestic marketplace channels -- are not in scope unless the company operates in Turkey.

Workshops and client-facing sessions run in Turkish by default for Turkish-market engagements. Deliverables are produced in whichever language the team operates in. Engineering work happens in English internally; the client-facing surface follows the client. For international engagements, delivery is in English throughout.

Many consultants deliver an assessment and a slide deck. We deliver integrated systems running in production. The engagement does not end at the recommendation -- it ends when the workflow is operational in your team's hands, measurable against the criteria we set at the start. The distinction is between advice and execution.

Engagements are scoped to the work, not sold from a price list. Typical engagements range from low-five-figures to mid-five-figures USD. Pricing is in USD and can be settled in TRY at the prevailing spot rate. We commit to a number once the diagnostic map is in hand -- not before, because scope determines cost.

The horizon depends on scope. A single workflow integration runs in weeks. A multi-workflow transformation runs across months. We do not quote a fixed calendar date before the diagnostic is complete -- once we have the map, we commit to dates we can stand behind.

If the score surfaces real opportunity and both sides see a fit, we schedule a 30-minute call. From there, a paid Diagnostic maps your workflows, systems, and integration priorities in detail. The Diagnostic output is the document that grounds scope, timeline, and pricing for any subsequent implementation work. The map is yours regardless of what comes next.

Every engagement has phase-level exit criteria defined before the work starts. If a phase does not meet those criteria, we stop and return the unused time on that phase. The diagnostic map and all work product to that point remain yours. We do not bill for scope that did not earn its outcome.

After launch, your team can operate the systems independently. Most engagements close with a structured handover: documentation, runbooks, and a knowledge transfer session. For teams that prefer ongoing coverage, we offer a monthly maintenance retainer for monitoring, updates, and optimization. It is optional, not a condition of the engagement.