Questions we are asked.

With a briefing. Tell us what you need to decide or build, and we suggest where to start: a Growth Lab for an open question, or AI Studio for a clear brief or a tender.

No. If you already know what to build, start with AI Studio. Growth Lab is a standalone week, and building what it recommends is optional and agreed separately.

Every step ends in something your team reviews: the decision pack, the scope and acceptance criteria, the design and delivery plan, working software with milestone demos and test evidence, and the release package.

Orveon owns scope, architecture, planning, communication and quality. Specialists from Orveon or a partner join where the work needs them, and you set the priorities and accept what is delivered.

The smallest version that works in production. Each release after it builds on what your team already uses.

Agents and automated workflows, AI-native applications, web and mobile products, and the data and enterprise integrations that connect them to the systems you already run.

Yes. Share the requirements, dates and evaluation criteria, and we put a technical and commercial proposal around them.

Before the build, we agree which data the system may use, who can reach it, where a person reviews or approves its work, and the quality targets and acceptance tests it must pass.

Intellectual property, warranty and support are agreed in the contract before delivery starts, together with the schedule, commercial terms and team.

It is planned with you for each project. We release the smallest working version first and grow it, so your team uses working software early rather than waiting for the whole scope.

One week, with two facilitated sessions of 3 hours each.

A sponsor and around 4 to 6 stakeholders who know the problem from different sides.

A decision pack: the business case, the concept and the scope of a first version, a high-level roadmap, a budgetary estimate and the next step we recommend.

It has a fixed fee, confirmed once we have scoped the week with you. The budgetary estimate it produces is a planning input, not a quotation.

No. Building what the week recommends is optional: with us through AI Studio, with your own team or with a partner.

Sessions run remotely or in person, on dates we set with you.

Software that uses an AI model to carry out a defined task over several steps, with the tools, data and systems it is allowed to reach. In the agents we build, the decisions that matter go to a person. See the glossary for related terms.

Only within limits you agree. We set with you what an agent may do on its own and what needs a person's approval, and the decisions that matter stay with your people.

Agentic software takes on routine work across our own processes, and we design, write, test and review software with AI at every step. Our engineers stay accountable for every change.

We map the process with your team to find where an agent saves real time and where a person must stay in charge. Placing it well is most of the work.

We follow developments closely, try what is promising on our own work first, and bring to client projects what holds up there.

Not yet. AeronUI is a prototype running inside Orveon, developed alongside the products we are building. It is not offered to customers yet. If you would like to follow it, talk to us about AeronUI.

It is the interface layer over Orveon's products and a customer's existing systems. The systems underneath stay; the interface over them is what people will shape.

Yes. We would like to hear from teams who see their own software heading the same way. Talk to us about AeronUI.

No. Radar only reads, and nothing is written back to your tools. Your teams keep working as they do today.

Widely used project management and development tools, with your team's chat for reminders and the Monday digest. We share the current list in a briefing. Projects without a tool can be managed in Radar itself.

Each workspace's data is kept separate. Hosting location and deployment options, including a dedicated environment or on-premises, are covered in a briefing and a security review.

In the pilot, Radar reads the projects you choose, with read-only access. Request a briefing and we will agree the scope with you.

No. Radar is the management layer above your tools: the PMO's view of the portfolio, while each team keeps its own backlog.

Sales teams: the people who manage sales and the people who sell, in the office and at the customer.

LiftCRM is in development. Next: a first pilot with design partners. Until then, you can help shape it as a design partner, or request a briefing.

That is the intent: the mobile app is being built to keep working where there is no signal.

Request a briefing. Teams who want a say in what LiftCRM becomes can work with us as design partners.

Turn LiftCRM, or any CRM or sales data, into insight for sales and marketing teams.

It is not intended to be required: LiftInsight is being shaped to work from LiftCRM or from any CRM or sales data you already have.

Not yet: LiftInsight is in ideation, shaped with design partners. If you want a say in it, become a design partner or request a briefing.

Expenses, requests and approvals, purchase requests and orders, budget control, and reporting for finance and procurement, with e-invoicing through special integrators authorised by GİB in Türkiye.

Yes. Expenco is in production with a multi-location flexible-workspace and coworking operator in Türkiye.

Expenco runs on its own platform at expenco.com ↗ (opens in a new tab). For a walkthrough, request a briefing.

It plans dispatch routes from a sentence: orders go to vehicles within your rules, each route is laid out on a map, and Propt explains each decision.

No. Changes apply only when you approve them, the impact is shown first, and one click undoes them.

Your vehicle capacity, time windows, zones and minimum fill.

Propt runs on its own platform at proptai.co ↗ (opens in a new tab). To talk it through, request a briefing.

Yes. Every role is remote.

No. The graduate talent pool and both internships are open to people without professional experience.

Yes. Both internships are paid; pay, duration and dates are agreed in writing before you start.

No. It is a talent pool for future project-backed roles. When a project creates a role that fits you, we get in touch.

In English.

University students of engineering, mathematics, computer science, data and design. The full eligibility rules will be published with the first edition, before applications open.

Yes, as a team of exactly 2. For now, you can ask for updates on your own, without a confirmed teammate.

It runs from Friday 18:00 to Sunday 18:00, 26–28 February 2027, Istanbul time (UTC+3). The venue and format will be announced before team applications open.

Not yet. This page only collects requests for updates. Fees (if any), capacity, selection rules and the full terms will be published before applications open.

Yes. Be open about the tools and third-party components you use, and be ready to explain and test what you built. Detailed rules come with the challenge briefs.