Frequently asked questions.

Four: a turnkey project at a fixed price, a dedicated team, staff augmentation and time-and-materials. The engagement models page compares them in detail.

Two questions decide most of it: how clear the scope is, and who leads the team day to day. Clear scope led by us suits a turnkey project; evolving work led by us suits a dedicated team; if your own lead directs the work, staff augmentation or time-and-materials fit better. We recommend one on the first call and explain why.

An AI-native engineer joins the call. We ask about the system you have, the outcome you need and the constraints around both. There is no pitch deck, and you get a written follow-up either way.

A short piece of work before a larger build. It covers the business outcomes, technical constraints and integrations, and ends with a delivery roadmap and cost ranges you can take to budget.

A dedicated team starts once you have approved the people on it. Staff augmentation starts once you approve the profiles. What sets the pace is usually notice periods and access to your systems; we tell you on the first call what to expect for your case.

Yes. We propose the team by name, you see each profile and the role it will play, and you can interview and say no before anyone starts.

Short sprints with a demo at the end of each, written status and regular steering, at a rhythm agreed with you. You have direct access to the engineers, not a proxy project manager.

Yes, through a written change request. We price the change and agree it with you before any work starts, so the fixed price stays meaningful.

By design — conversions are normal as needs clarify, and the people usually stay the same.

Augmentation adds people to your process; a dedicated team brings its own delivery system and owns outcomes. With augmentation you set the cadence, run the standups and carry the delivery management. With a dedicated team, our lead is accountable for how the work is delivered, design and QA come with it, and the unit is reviewed as a whole. Augmentation flexes faster, person by person; a dedicated team compounds deeper because context accumulates across the group. The two are compared side by side in engagement models.

Tell us once. We coach or replace the person, with paired handover — continuity is our problem, not yours. You do not need to build a case, and there is no commercial penalty for saying it early. Raise it early: a mismatch caught in the first weeks is usually solved by changing the seat rather than the person, and it costs the roadmap nothing.

When the roadmap calls for it, by shape rather than by headcount alone. We look at what the roadmap has become and propose a composition against it, with the cost effect written down before anything changes. Additions are onboarded with pairing so they do not slow the sprint they join; reductions are planned with an overlap period so the areas they owned already have a second familiar engineer.

Senior and staff-level primarily — people with production history you can question in detail. We decline briefs that really need a different shape, such as a first-time-hire role that needs mentoring rather than autonomy, and we suggest what would work instead. Placing someone into a role they will not succeed in helps nobody.

Often it does. When headcount grows and the engagement starts to own outcomes rather than fill a gap, we convert it without changing the people: a lead becomes accountable for delivery, design and QA capacity joins, and the cadence and reporting of the dedicated team model come with it. The conversion is a commercial change, not a restart.

The same way you know it about your own engineers: pull requests, tickets, standups and your review standard. There is no separate timesheet theatre and no report from us describing what your team can already see. The three-way check-in exists for direction and fit, not for supervision — if you are ever wondering whether someone is contributing, that is a fit conversation and we want it early.

Odeontech directs the day-to-day work and owns the delivery. You set the priorities, follow the progress and approve the results.

Yes, that is the point of the model. Priorities can change as you learn, without change requests.

Yes. Once the scope is defined with acceptance criteria, the remaining work can move to a turnkey project at a fixed price, usually with the same people.

You accept the result and we hand over with documentation. If you want ongoing work, it can continue as maintenance and support or with a dedicated team.

Yes. The first call and the written follow-up cost nothing and commit you to nothing. A fuller discovery is a separate, paid piece of work, agreed with you.

An AI-native engineer and an engagement lead. If a product is in scope, the engineer who operates that platform joins. There is no separate sales team to hand you to.

Yes. Send yours, or ask for our mutual NDA. Most first calls don’t need one, but if your situation does, we sign first and talk second.

Teams are distributed across time zones aligned to each client — close enough to collaborate live, broad enough to cover. Tell us where you are and we will propose slots in your working day.

Usually short, Scrum-shaped sprints at a rhythm agreed with you, without ceremony for its own sake. If you already have a process, we can work in it. The process serves the delivery, not the other way round.

In staff augmentation our engineers adopt your process as it is. A dedicated team brings ours, which is much of its value. Either way, it is agreed before we start.

Constantly — a dedicated team for the core plus augmentation into your internal squads is a common, healthy shape.

Both, deliberately. It carries outsourcing’s governance — our delivery system, our accountability for outcomes — with capacity’s flexibility, because you set the roadmap and the team rolls quarter to quarter. That is why it is the answer for most long-horizon products.

You convert. Our contracts are written so that changing model is a paperwork exercise, not a re-hire — the engineers already know your system, and in most conversions they are the same people.

Usually, yes. The technologies above are the ones we build and run most; most enterprise estates also contain technologies we have modernised rather than chosen. Tell us what you run and we will say honestly whether it is a fit.

No. We are financially neutral across AWS, Azure and Google Cloud, and the recommendation follows your existing agreements, identity estate and data gravity — not ours.

Yes — Staff Augmentation places specialists into your team, and you interview and approve every profile. For a whole roadmap, a Dedicated Team brings the delivery system with it.

They are our default way of working. Their scope, budgets and service-level targets are agreed with you, according to your needs and budget.

Our engineers work agentically: AI agents take on the repetitive parts of delivery — reading unfamiliar code, writing test variations, drafting migrations and documentation — while engineers own the design, review every change and stay accountable for correctness.

No. Anything an agent produces goes through the same code review, tests and security checks as code written by hand, and an engineer signs off on every merge.

We only use AI tools under terms your security team approves, and we do not send your code or data to tools you have not approved.

A forward deployed engineer works alongside the people who will use the software, learns the process first-hand, writes the code in your systems and stays until it is in daily use. Read more on the FDE page.

When the requirements only become clear once you see how the work is done — typically AI and automation projects, and workflows that live in spreadsheets and workarounds.

A dedicated team builds what your product organisation prioritises. An FDE team is pointed at an operational outcome: it finds the problem with your operators, defines the solution, builds it and stays accountable until it holds up in daily use.

Part of the time, yes — usually one to three days a week at the start, when learning the workflow matters most. The rest is remote. We agree the rhythm up front based on where your people and systems are.

With a short call to pick a candidate problem and a sponsor. If it is a good fit, the team starts with access and shadowing, and the first scope is a single problem with a measurable target.

Four platforms under the ObelusLabs name: Loyalty & Retention for loyalty programmes, Sales Performance for commissions and incentives, Order & Supply Management for order, supply and shipment management, and Workflow & Procurement for approvals and back-office workflows.

Yes, that is a common way to work. The licence covers the platform; integrations, configuration, custom modules and later development run under a separate services contract.

Yes. We can set up a demo on your scenario so you see the product on your own data before you decide.

Yes. All four run on the same ObelusLabs platform with shared data, identity and analytics, so you can add the next product without a migration.

We hire as engagements start, so open roles change through the year. You can send a general application through the careers page; an engineer reads every application.

Each role lists the experience it needs. We are always glad to meet strong people early in their career, and we are honest about fit and timing.

Remote-first within European time zones; the offices in Istanbul (Ataşehir) and at Bilişim Vadisi (Gebze) are there when you want them. If a role needs more time on site, close to the team or to clients, we say so in the first conversation.

Profile review, a technical conversation with the team you would join, and a practical exercise close to real work. No leetcode theatre.

Both, over time — engineers rotate between client teams and our ObelusLabs platforms, which is exactly how the quality bar stays shared.

You will use AI tooling daily and you will still own every change you ship. Generated code gets the same review, the same tests and the same rollout discipline as anything else. The tooling removes typing, not judgement.

Use “Other areas”. We are always glad to meet engineers, designers and delivery people. A profile and something you have shipped is enough, and we will reply.

If your application does not lead to a job, we delete it within 6 months after our last reply to you. If you tick the box for future roles, we keep it for up to 2 years after that date. See the job applicant notice.

Only what it needs to work. Your cookie choice is stored in your browser, and our host Cloudflare can set security cookies. No analytics or advertising runs. See the Cookie Policy.

The Privacy Policy and the KVKK notice explain your rights and how to apply. For a KVKK request by email, write to info@odeontech.com from the address you have already given us and that is in our records.

No. They apply to the website only. Product subscriptions, pilots and engineering engagements are governed by signed agreements.

Short quotations with attribution and a link to the source page are fine. Reproducing whole pages or diagrams, or presenting our content as your own, needs written permission: ask at info@odeontech.com.

Not without written permission. To report a vulnerability, write to info@odeontech.com. Reporting does not authorise testing.

No. Screens, tables and figures on product and industry pages are samples. They do not come from a real customer and are not measured results.

The laws of the Republic of Türkiye. The courts with jurisdiction under procedural law decide, and consumers keep their legal rights.