Startup CTO
You need a real system in front of users or investors fast, without hiring a full team first.
Senior delivery in 90 days at a fixed price, and you own everything to build on afterwards.
Book a scoping callFixed scope. Fixed price. 90 days.
An MVP, or a production-ready slice, in 90 days.
The 90-Day Production Pilot is the sharpest way to start with Oronts. We fix the scope and the price up front, then a senior, founder-led team with an AI-assisted workflow takes one real use case to running, production-ready software inside a 90-day window. You own the code from the first commit.
90 days
From a signed scoping document to a production slice your team can run
from 25k EUR
One fixed price, agreed before a single line of code is written
Day 1
The repositories and the code are yours, with no vendor lock-in
The 90-Day Production Pilot
The 90-Day Production Pilot is our fixed-scope, fixed-price entry engagement. It is for teams that want to move one real use case from idea to running software without a long pre-sales cycle. We agree the scope and the success criteria up front in a scoping document, then a senior, founder-led team builds against it for a focused 90-day window. Pricing starts from 25k EUR depending on the scope we fix together. You own the code from the first commit. What you get at the end is not a prototype or a slide deck: it is a usable production slice, deployed, monitored and documented, that your team can operate alongside us.
- Fixed scope and fixed price, agreed in a scoping document before we start
- Senior, founder-led delivery, not a junior team handed a backlog
- You own the repositories and the code from day one, with no vendor lock-in
- Ends in a production-ready slice you can run, not a throwaway prototype
What a pilot is, and what it is not
A pilot is deliberately bounded. Naming what sits outside it up front is exactly what keeps the price fixed and the 90 days honest.
Inside a pilot
- One real, agreed use case, a new build or the first step of modernizing an existing system, taken to running software
- A deployed, monitored and documented production slice
- The architecture and the key decisions written down
- Your team onboarded to operate the system alongside us
- A scoping document that fixes scope, price and success criteria
Not in a pilot
- An open-ended backlog or an entire platform at once
- A throwaway prototype or a slide deck
- Hourly billing that drifts past the agreed price
- A junior pod you are handed to after the sales call
- Vendor lock-in of any kind: you can leave with the full system at any point
The 90-Day Production Pilot, day by day
The pilot is our typical focused execution window, not a generic guarantee. Milestones, deliverables, risks and success criteria are scoped individually per pilot; this is the rhythm a typical one follows.
Day 1
Repositories and access live in your organization. The code is yours from the first commit.
Day 3
A deployed environment you can click, even while it is still thin.
Week 1
The first working slice of the real system, demoed against real data where possible.
Day 14
Scope checkpoint: what holds, what moved, what we decided and wrote down.
Week 6
The core flow runs end to end; hardening, tests and observability take over.
Day 90
Production: monitored, documented, with your team operating the system alongside us.
Day numbers describe the typical pilot; your scoping document fixes the real ones.
Who the pilot is built for
Different buyers reach for the pilot for different reasons. It holds up for all of them.
Mittelstand technical lead
You want to prove one use case before committing budget, and you cannot accept vendor lock-in.
Fixed scope and price, code in your own repositories, GDPR-first, with an AVV and TOM on request.
See engagement termsAgency or platform owner
You need senior capacity that ships under your brand without slowing your own roadmap.
A founder-led pilot you can white-label, scoped and priced before it starts.
Talk about partnershipEnterprise procurement and security
You need to clear a new vendor through procurement and security review before any budget moves.
A German GmbH with a full Impressum, a fixed-price contract, code ownership from day one, GDPR-first, with an AVV and TOM on request.
Review trust and securityWhat your buying committee can check
The questions a procurement or security review asks, answered plainly and up front.
- Code ownership
- Yours from the first commit, in your repositories, under your accounts.
- Contract
- A fixed-price pilot agreement with the scoping document attached. German GmbH, full Impressum, Amtsgericht München HRB 288224.
- Data protection
- GDPR-first. A data processing agreement (Art. 28) and a description of technical and organisational measures are available on request before kickoff.
- Delivery team
- Founder-led and senior throughout. The people who scope the pilot are the people who build it.
- Handover
- Deployed, monitored and documented, with your team operating the system alongside us by day 90.
- After the pilot
- Continue with us, take it in-house, or pause. Leaving never costs you the system.
Who you're working with
HRB 288224
Registered in Munich
15+
Years, founder-led
DE · EN · AR
Delivery languages
2
Open source on GitHub
EU
Data residency, Frankfurt
AVV/DPA
Ready to sign, Art. 28
Engagement levels
Oronts works with serious teams that need senior delivery, not low-cost outsourcing.
- Production Pilot
- from 25k EUR
- Custom software and AI projects
- from 50k EUR
- Ongoing technical retainers
- from 15k EUR/month
Exact pricing depends on scope, responsibility, delivery speed, team size, integrations, support expectations and production risk.
Pilot questions, answered
One real use case taken to a usable production slice: deployed, monitored and documented, running in your repositories with the architecture decisions written down. Not a prototype, not a deck. Your team can operate it alongside us at the end of the 90 days.
The pilot is a fixed-price engagement starting from 25k EUR. The exact figure depends on the scope we fix together in the scoping document. We agree the price before the work starts, so there is no open-ended hourly billing during the pilot.
The scoping document is the reference point. If something we both want falls outside it, we name it at the next checkpoint, write down the decision, and either trade it against existing scope or treat it as a separate, separately-priced increment. The fixed price holds for the fixed scope; nothing gets quietly absorbed or quietly added.
A senior, founder-led team. The people scoping the pilot are the people building it. You are not handed off to a junior pod after the sales conversation, and you have a direct line to a senior engineer throughout, answered within one business day.
You own everything, so you are free to continue with us, take it in-house, or pause. If we continue, the next increments are scoped from the working system rather than from assumptions, typically as a follow-on project or an ongoing retainer. Leaving never costs you the system.
Scope your 90-Day Production Pilot
Bring one real use case. In a single call with a senior engineer we shape the scope, the success criteria and the fixed price, before anything is committed.