Orders
Move an order across shop, ERP, and warehouse systems.
Include status updates, duplicate protection, error handling, and a clear exception queue.
30-Day Workflow Sprint for European teams
Take one manual workflow off your team's hands.
We design, build, test, and deploy it in 30 days. Fixed at EUR 20,000 net. No upfront payment. Pay after acceptance.
30 minutes. Bring one workflow. We will tell you directly whether it fits.
0%upfront
30days to production
EUR 20kfixed price
90days support
What we can take over
One useful workflow, end to end.
Approvals
Turn an email and spreadsheet approval into a tracked process.
Connect the request, decision, audit trail, and final action in your existing tools.
Operations
Route a request from intake to the right back-office action.
Validate the input, assign ownership, update systems, and make failures visible.
These are examples. The Sprint starts with the workflow your team needs most.
Sample projects
Real systems, rebuilt around the work.
Two examples of hands-on delivery. Client names are withheld and operational details are simplified.
Industrial operations
On-premises
Replacing a legacy order and product tracking system
A manufacturer depended on an old Windows application, SQL data, shared folders, Excel workbooks, PDFs, and undocumented links between them.
- Work
- Recovered the real operating model, reconciled legacy data and files, and built a modern web workbench for orders, articles, documents, and reviewed changes.
- Delivery
- Angular and Spring application, audited imports, document versioning, role-based access, tested backups, and an isolated on-premises deployment.
- Result
- A controlled path away from the desktop system without a risky big-bang migration. Legacy operations can continue while each new workflow is verified.
Industrial catalogue
Drupal
Turning an outdated product site into a maintainable catalogue
A technical manufacturer needed to renew an old Drupal site while preserving a large catalogue of specialist products and documentation.
- Work
- Rebuilt the site on modern Drupal and migrated the existing product structure, descriptions, images, technical drawings, brochures, and downloadable files.
- Delivery
- Responsive catalogue pages, individual product pages, CMS editing, locally hosted assets, mobile layouts, and a repeatable import process.
- Result
- A working replacement that keeps technical material accessible and gives the internal team a practical way to maintain the site.
Your project can start smaller. The Sprint isolates one useful workflow from a larger operational problem.
Discuss your workflowThe result
Working software in your environment.
BuiltA production implementation, not a recommendation deck.
TestedAgreed normal flows and failure cases demonstrated before acceptance.
TransferredSource code, tests, deployment setup, and documentation handed over.
Supported90 days of technical support for the accepted scope.
How it works
Four decisions. Then we build.
- 1
Show us the workflow
In a 30-minute call, we map the current steps, systems, owner, and desired result.
- 2
Define acceptance
Before work begins, we agree the exact inputs, outputs, error cases, and acceptance test.
- 3
Watch it become real
You see working software every week. Your team provides access, answers, and one weekly review.
- 4
Accept, then pay
We demonstrate the agreed result in your environment. The full invoice is due after written acceptance.
Have a workflow in mind?We can usually establish fit in one conversation.
Check if it fits
The commercial offer
EUR 20,000 net. Nothing upfront.
The full amount is due only after the written acceptance criteria are met.
Before the SprintScope and acceptance agreed in writing
During the SprintWorking demonstration every week
At acceptanceSource, documentation, and deployment handed over
After acceptanceInvoice issued and 90-day support begins
No lock-in
Your workflow remains yours.
Full handover
You receive the source code, tests, deployment configuration, and technical documentation.
Your infrastructure
We work with your environment and existing systems. No recurring Orkestr software licence is required.
Your AI choice
If AI is useful, you control the model and hosting approach. AI is not forced into workflows that do not need it.
Direct technical responsibility
You work with the person responsible for delivery.
I am Oğuzcan "Can" Ünver, a chemical engineer turned software developer and technology consultant. My experience covers ERP, quality, cloud platforms, AI systems, and enterprise software in environments including Santander, Atruvia, Bundesdruckerei, Panasonic Europe, and ServiceNow.
I lead the Sprint and remain technically responsible from scope through production handover.
Common questions
What buyers usually ask.
What counts as acceptance?
A written test agreed before the Sprint begins. It defines the workflow, expected outputs, important error cases, and the environment in which we demonstrate the result.
What do you need from our team?
One business owner, one technical contact, timely system access, test data, and a weekly review. Orkestr handles implementation, testing, documentation, and handover.
What if the workflow is too large for 30 days?
We isolate the smallest production result that creates value. If no honest 30-day scope exists, we will tell you before proposing a Sprint.
Does this replace our internal hire or implementation partner?
No. The Sprint removes one defined delivery item while your team, programme, or hiring process continues.
What happens after the Sprint?
Your team can operate the delivered workflow with the handed-over source and documentation. The accepted scope includes 90 days of technical support.
Short workflow brief
Describe the workflow. We reply by email.
Five short answers are enough. Can replies personally and tells you directly whether it fits the Sprint.
Please leave out passwords, access details, customer records, and other confidential data.
Brief received.
Next step: pick a time for a 30-minute workflow fit call.
Book a workflow fit callYou can also write to can@orkestr.de.
Start with the workflow
What should your team stop doing by hand?
Bring the workflow, the systems involved, and the result you want. We will tell you if it fits the Sprint.