How do invoicing and VAT work with an EU vendor?
We invoice from our Polish (EU) entity by standard corporate invoice and bank transfer, typically on 30-day terms. For UK VAT-registered companies the reverse charge applies, so no VAT is added to the invoice; your finance team simply self-accounts for it as with any overseas B2B service.
Does IR35 apply if we engage you?
We deliver scoped services from Poland and document the deliverables, responsibilities and working arrangement. IR35 treatment depends on the actual engagement, not just a fixed-price contract or statement of work. We confirm the arrangement with your finance or legal team before work begins.
Do you sign NDAs before the audit or PoC?
Yes. We sign a mutual non-disclosure agreement before any sensitive data is discussed or shared, and a data processing addendum before any data is handled.
How do you handle security and compliance requirements?
Per engagement, we provide an NDA, a data processing addendum (DPA), a subprocessor list, a data-handling policy, and an AI-use policy. All of these are reviewable in writing by your security and procurement teams before any work begins.
Where is our data stored?
Data can be hosted in the UK or the EU (for example, AWS London or Frankfurt) or deployed inside your own cloud environment, so data residency requirements are respected from day one.
Who owns the intellectual property?
You retain full ownership of your data. For custom software and automation built during the sprint, IP handover terms are written into the contract before work begins.
How are quality, change requests, and acceptance handled?
Every engagement uses written acceptance criteria, weekly demos with the business owner, audit logs for AI and automated steps, and a formal change-order process, so scope changes are documented, not absorbed silently.
Who reviews the technical decisions?
Senior engineers review scope, architecture, AI-use risk, security assumptions, weekly demo outcomes, and handover quality so technical accountability stays direct.
Can an API sprint include OpenAPI documentation?
Yes. API sprints can include OpenAPI-style endpoint contracts, sample requests and responses, auth assumptions, error behavior, tests, and handover notes.
What KPI should we choose for a PoC?
Choose one measurable proof point before build starts: manual steps reduced, API handoff success, extraction accuracy, reviewer acceptance, response time, or pilot-user feedback.
Can the first sprint be a technical second opinion?
Yes. If a proposal or vendor plan is too broad, the first step can be a short technical review before committing to a build sprint.
Which AI models do you build with?
We are model-agnostic and evaluate per use case: current frontier models such as Claude Fable 5 (Anthropic's Mythos-class model, June 2026), GPT, and DeepSeek, alongside cheaper tiers for high-volume steps. Every build includes prompt versioning and an evaluation set, so the model can be upgraded or swapped safely as pricing and capability change, with audit logs showing which model produced each output.