FAQ
How a project usually works.
Straight answers on scope, languages, guarantees and ownership. If your question is not here, it is a one-message conversation.
Ask us directly → Do you only build AI tools? +
No. AI is one layer. We also build the product interface, workflow, data model, docs, automation and operating controls around it.
Can you work with an existing website or WordPress setup? +
Yes. We can modernize a site, build a new static surface, create product pages, or add an approval-gated WordPress operations layer.
Can media generation be part of a business system? +
Yes. We treat prompts, generated assets, voiceover, captions, review decisions and archives as a production workflow, not one-off creative experiments.
Which languages can we work in? +
Live collaboration is available in English and Turkish. Written briefs, interfaces, documentation and deliverables can be localized for any target language and reviewed before release.
Do you guarantee funding approval or AI Act compliance? +
No. We help scope the project, prepare technical evidence, design workflows and build transparency/readiness systems. Funding decisions and legal compliance opinions stay with the relevant authority or legal advisor.
Can you build personal or always-on research assistants? +
Yes. We can build personal assistants, company assistants and 24/7 deep-research agents that watch sources, summarize changes, draft reports and keep a reviewable audit trail.
How fast can we start? +
Most work starts with a sharp discovery sprint or fixed first milestone. That keeps cost, risk and expectations visible before a larger build.
What do you need from us? +
A clear goal, access to relevant public materials or internal examples, and fast feedback on the first working slice. We shape the technical scope together.
How is pricing structured? +
Fixed-scope packages — prescreen, sprint, discovery, pilot — are quoted up front. Ongoing work runs as a monthly retainer. You always see the scope, the price and what would change them before we start.
Who owns the result? +
You do. Code, content, prompts and documentation are handed over — in your infrastructure and accounts wherever possible — and the handoff package is part of the scope, not an extra.