Question 1

Are you a staffing company?

Accepted Answer

No. We deliver outcomes through managed R&D pods, not FTEs you manage. A pod ships against your roadmap with engineering-led ownership, weekly demos, and a clear definition of done. You don't run our timesheets — you accept demos.

In practice this means one accountable Engineering Lead per pod, written sprint updates, and quality gates (tests, code review, CI/CD) that you'd expect from an internal team — not a body shop.

Question 2

What's the difference between an AI Delivery Pod and a Product Pod?

Accepted Answer

AI Delivery Pod — Engineering Lead + Engineer. Best for focused AI workstreams, MVPs, and integration projects where the scope is technical and the roadmap exists.

Product Pod — adds a Scrum/Product PM. Best for end-to-end product delivery where scope shaping and stakeholder coordination are part of the work.

We'll recommend the right shape on the discovery call based on your context.

Question 3

Can we mix capabilities (LLM + cloud + full-stack) inside one pod?

Accepted Answer

Yes. Pods are composed of senior generalists who own delivery end-to-end — data pipelines, model fine-tuning, backend, deployment, observability. For specialist workstreams (e.g. embedded, computer vision at scale) we add a domain expert as an add-on.

Question 4

How fast can a pod start?

Accepted Answer

Within 4 weeks of signature and access provisioning. Ramp-up is typically 3–5 days for setup and backlog shaping. Your first weekly demo lands within 7–10 days of kickoff.

Compare that to a 3–6 month internal hiring cycle — the speed differential is the point of working with us.

Question 5

What if we need to scale up or down mid-engagement?

Accepted Answer

Capacity changes with 2 weeks notice. Add an engineer (1.0 or 0.5 FTE), drop a pod after a milestone, or pause and resume — all without renegotiating the master agreement.

Question 6

Where are your engineers based?

Accepted Answer

All engineers are based in Skopje, North Macedonia. Time zone is UTC+1 (CET) — same as most of the EU. Daily standups overlap fully with European hours and most of UK business hours. Communication is in English.

Question 7

What time zones do you cover?

Accepted Answer

Our standard hours are 09:00–18:00 CET (UTC+1). For 24/7 operations contracts, we schedule on-call rotations across the team. We can adjust core hours for clients in UK, Israel, and East Coast US.

Question 8

Who owns the IP we build together?

Accepted Answer

You do. All code, models, training data, and documentation produced for your project transfer to your ownership. We sign work-for-hire and IP assignment as standard.

We retain only generic, non-client-specific patterns (e.g. internal CI templates, prompt evaluation harnesses) — never your business logic, datasets, or models.

Question 9

Do you sign NDAs and DPAs?

Accepted Answer

Yes — standard before any access. We sign your NDA template (or provide ours), and a GDPR-compliant Data Processing Agreement when handling personal data. SOC 2 / ISO 27001 controls in place where required by client.

Question 10

Are you GDPR compliant?

Accepted Answer

Yes. We operate under EU data protection law (North Macedonia is harmonized with GDPR). Data stays in the EU unless your contract specifies otherwise. Client data is segregated, access-controlled, and auditable.

Question 11

Can we exit if it isn't working?

Accepted Answer

Yes. Engagements are designed to be exit-friendly: docs, handover, and shared repos from day one. Standard notice is 30 days.

We've never been the reason a client wasn't able to take the work in-house cleanly. Knowledge transfer is part of the engagement, not a separate step at the end.

Question 12

How do you handle scope changes?

Accepted Answer

Scope is set at sprint level (1–2 weeks). Changes between sprints are normal — we re-shape the next sprint's backlog with you. Changes mid-sprint require a brief re-plan, but we don't bill change orders for normal product evolution.

Question 13

What process do you follow — Scrum, Kanban, hybrid?

Accepted Answer

We adapt to your method. If you run Scrum, we join your ceremonies. If you run Kanban, we work from your board. If you have an internal model, we follow it. We bring the cadence (weekly demo + written update + quality gates), not a fixed process.

Question 14

Do you have client references?

Accepted Answer

Yes. We share named references after a discovery call and mutual NDA. Many of our clients are early-stage and prefer not to be public, but they'll talk on a call. Our clients have collectively raised €100M+ and we've contributed to 15+ patented innovations across automotive, fintech, agritech, and healthcare.

Question 15

How do you charge — fixed, T&M, or retainer?

Accepted Answer

Pods are monthly retainer — predictable budget for predictable capacity. We don't do open-ended T&M or fixed-price feature work. The retainer model aligns incentives: we focus on velocity and quality, not on billing more hours.

Common questions, honest answers.

About the model

Speed, scale & logistics

Ownership, security & compliance

Process & collaboration

Still have a question?