Odri Device Repair ERP
Repair requests, estimates and progress in one workspace, so staff can follow each job from the first inquiry to the next update.
Odri Device · Repair ERP & AI
We're building a workspace for repair requests, estimates and progress tracking. Planned Claude workflows will help organize inquiries and prepare reply drafts for staff review. Explore the public samples without an account.
A simplified, public-facing concept.
Illustrative interface · sample data
Illustrative workspace · not an internal system screenshot
Our development work
Repair requests, estimates and progress in one workspace, so staff can follow each job from the first inquiry to the next update.
We plan to test Claude for request summaries, missing device details and reply drafts. Staff will review the output; the planned workflow will not make repair or pricing decisions.
Software built around business operations. We also use AI to support our development work, from exploring ideas to working through implementation.
VMS system development, shaped around the needs of real operations.
The device still needs a person who can repair it. Our software is for the work around that job: collecting details, preparing estimates and keeping the customer informed.
Public product tour · No login needed
Two short sample views show the repair ERP and Claude-assisted workflow we're planning. Fictional data only: no customer records, internal rules or private admin screens.
A simplified, public-facing concept.
Illustrative interface · sample data
Repair ERP · In development
1. Collect the device and symptoms.
2. Prepare an estimate for review.
3. Record progress and the next customer update.
This sample shows how we want the workspace to organize the job. It is not a working ERP demo.
Illustrative workflow · software in development
My tablet does not charge. What should I do next?
Tablet model, charging symptoms, and any visible damage.
Please share the model and describe what happens when you connect the charger.
Staff review before any response is sent.
Illustrative interface · sample data
Claude-assisted intake · Planned
1. Summarize what the customer reported.
2. Flag missing device details.
3. Prepare a reply for staff to check.
This is a hand-written sample of the intended output. It does not call Claude or send a message.
Proposed workflow · not a live product feature
Claude · Planned integration
We use AI in software development. Our next step is to evaluate Claude for the repair ERP and our team's development workflow; these Claude integrations are not live yet.
Summarize device symptoms, identify missing information and draft follow-up questions. Staff will check the facts and approve every response. Repair assessments and prices stay with people.
Evaluate Claude for implementation support, test cases and documentation. We'll review suggested code and test it before release, rather than treating a generated answer as a finished feature.
We'll start with synthetic repair inquiries, check summary accuracy and reply quality, and measure API cost before deciding what to integrate. Customer-data handling needs to be reviewed before using real inquiries.
Contact
Have a device to repair or a system to build? Start a conversation.