Start with the request
Review symptoms, inspection checks, status and the next step.
Browse sample repairs ↗02 / Repair ERP · In development
One device
The whole record
A repair isn't just a ticket. It's a request, a device, an inspection, a part and a conversation. We're building a workspace that keeps them together.
No login needed. Fictional data only. Separate from internal operations, with no operational API or database connection.
A workspace, not another loose spreadsheet
Follow the work
around the device
The project covers more than intake. The public preview presents eleven safe workflow sections without exposing internal policies, costs or administration.
A record with a history
Follow a device back to its repair and forward to its next chapter.
View device records ↗The things a repair needs
Explore sample parts and incoming device purchases, without private cost rules.
Explore sample parts ↗From condition to a listing
See how a product, its device record and a sample sale are related.
Follow a sample sale ↗Keep the handoff visible
Review fictional inbound and outbound shipments in context.
See shipping examples ↗Know what the question refers to
Customer records, enquiries and reviews sit alongside the work they concern.
Read a sample enquiry ↗A fictional case / iPhone 13
A cracked display
Not five separate stories
Sample customer A asks about an iPhone 13 with a cracked display. Open DEMO-1042 in the repair list, then follow its related records. They all refer to the same fictional job.
Open the sample repair listStart here · DEMO-1042
iPhone 13 / Cracked display
Sample stage: Diagnosing. Read the inspection checks and activity history before following the links below.
- 01 / Device
DP-001
The device passport links back to this repair, so the history stays with the device.
- 02 / Part
PT-001
An iPhone 13 display assembly. Read the fictional stock and reservation figures.
- 03 / Parcel
SHIP-001
The inbound repair parcel is marked delivered. This is arrival tracking, not a completed repair.
- 04 / Conversation
INQ-001
The customer asks what happens next. The sample conversation links back to DEMO-1042.
A read-only example, not a real customer case or repair outcome. No carrier, operational database or AI service is connected.
Inside the interface
Built to be read
at a working desk
These captures use the original repair-table and inspection components, rendered locally with fictional data. No live customer records are shown.
About the preview
Explore freely
Change nothing
What can I do in the demo?
Browse eleven sections, search sample records, open details and follow related records. You cannot save, delete, approve, send a message or trigger an operational action.
Is this the internal ERP?
No. The public demo is a separate environment with fictional people, devices and quantities. Private customer information, financial data, internal rules and account administration are excluded.
Is AI already built into the repair workflow?
The Claude enquiry integrations are planned, not live product features. Read what we intend to test and where staff review fits.
Let's talk
Start with the problem
We'll take it from there
Questions about the projects, device enquiries or a software collaboration? Email us or say hello on KakaoTalk. Our services are still in development.