A VP builds a customer shipment desk in one conversation
Harborline Logistics is an invented contract-logistics company with about 3,500 people. Its tracking provider already shows where a truck is. Marcus, its VP of Customer Solutions, wants more: customers who move their own delivery, file a claim, and hear about a delay before they call. That spans four systems. He builds it himself, in one afternoon.
MarcusOur customers call about 600 times a day asking where their freight is. I want them to see it themselves, from PO to delivery.
SK8 builder agentGot it. Who will use it: your customers, your service team, or both?
MarcusBoth. Customers see their own orders. My team sees everything.
SK8 builder agentYour orders are in Körber, appointments in MercuryGate and accounts in Salesforce. Those already exist as datasets in SK8. Tracking is in project44, which isn't connected yet, so I'm building that connector now.
MarcusAnd when a shipment is in trouble, I want the customer to hear it from us first, before they have to call.
SK8 builder agentWhat does "in trouble" mean for you?
MarcusIf the ETA is past the promised window, or we haven't heard from the truck in six hours.
SK8 builder agentWhat should customers be able to do themselves?
MarcusMove the delivery appointment, but not once it's out for delivery, and not more than ten days out. And report damage with photos, straight into our claims queue.
SK8 builder agentIs there anything customers must never see?
MarcusOur carrier cost. And of course, only their own account.
SK8 builder agentDone. The Shipment Desk is running on live data in Harborline's own database. AI assistants can use it as is. Here's a draft screen to show what it can do. Your team can turn it into the real customer page with whatever tool it prefers.
MarcusBefore I open this to customers: how would I explain where an "at risk" flag comes from?
SK8 builder agentEvery value on the page has a path you can follow. For PO 4471, the ETA comes from project44, the promised window comes from MercuryGate, and your rule makes the call.
SK8 builder agentOne more thing. Finance and the warehouse team already run apps on SK8. Your desk reuses their existing datasets for orders, shipments and accounts, so nothing is synced twice. And the next app can reuse what you built today, like your “at risk” rule.
MarcusSo the next app starts from what's already here.
- Data connected, access approved
- "At risk" rule
- Customer actions
- Who sees what
- App live
- Körber WMSOrders, pick and ship statusExisting dataset · from Dock SchedulerApproved for this app by the warehouse systems lead
- MercuryGate TMSLoads, stops, appointmentsExisting dataset · from Dock SchedulerApproved for this app by the transportation systems lead
- SalesforceAccounts, contacts, casesExisting dataset · from Claims RecoveryApproved for this app by the Salesforce admin
- project44Carrier tracking events
- Learning how project44 works
- Found shipments, tracking events and ETAs
- Built the connection and a live event feed
- First sync, after approval: 1,284 events from the last 24 hours
Shipment at risk
The ETA is after the promised window, or there's been no carrier update for 6 hours.
In this app: the customer's coordinator gets an email, and the shipment is listed under "Shipments at risk".
Tested on live data: PO 4471 · ETA 16:40 · window ends 14:00 → at risk
Reschedule delivery
Allowed before the truck is out for delivery, up to 10 days ahead. Updates the appointment in MercuryGate and shows when it's confirmed.
Report a claim
Damage or shortage, with photos. Opens a case in Salesforce and shows the customer the case number at once.
- Customer coordinatorTheir own account onlyCarrier cost hidden
- Harborline service agentAll accountsEverything
The same rules apply on every screen and to every AI assistant.
PO 4471
At risk · 2h 40m late- Picked and packed, 18 pallets
- Departed Reno DC
- New ETA 16:40, window ends 14:00
- Delivery appointment, 12:00–14:00
✉ 11:52 · Email sent to Brightway's coordinator: PO 4471 is running late.
A draft screen the agent generated to show what the app can do. Your team picks the screen tool: Lovable, Power Apps, or none at all. The data, rules and access stay the same in SK8.
Late shipments now trigger an email before the customer calls. Claims get a case number in seconds, not days.
Any customer, agent or assistant can see why a shipment is flagged. Marcus owns the rule, and every change to it is recorded.
Central IT sees every app, every approval and every action in one place. More on that below.
NarratorPress play to watch Marcus build the app.
Watch Marcus build the app
About three minutes, narrated. You can pause or jump to any step.
From request queue to conversation
How a new app gets built today
- IT or an outside integrator builds it. You wait in a queue, the first version takes months, and every change means waiting again
- AI app builders like Lovable produce a first version quickly. Someone technical then has to own it: fix it, connect it to your real systems, and get it past IT and security
- Either way, each app is a separate project with its own upkeep, and the next one starts from zero
How it works with SK8
- The domain expert who knows the process describes the app in plain business language
- The builder agent finds the data, connects any system that is missing, and asks the right questions
- Each system's owner approves what this app can see and change
- A change is another short conversation with the agent, not a new project
Your second app is even faster, because it starts from what the first one built. And IT says yes faster, because access and a record of every action are built in.
Describes the work
What the team does today, what hurts, who should see what, and what people should be able to change. In business words, with no schema or field names.
Asks, then builds
It finds the right systems, asks what things mean and who relies on them, and checks every rule against real examples.
Runs the app
Keeps it running on live data, with your rules, your permissions, and a record of everything it did.
Elsewhere every app starts from zero. Here, every app makes the next one faster.
A page for your customers, or just ask an assistant
The same app works as a web page for customers, or as an AI assistant your team and your customers can simply ask. Your team picks the screen tool: an AI builder like Lovable, Power Apps, or none at all. The data, rules and access stay the same in SK8.
PO 4471
At risk · 2h 40m late- Picked and packed, 18 pallets
- Departed Reno DC
- Passed Truckee checkpoint
- New ETA 16:40, window ends 14:00
- Delivery appointment, 12:00–14:00
This example page was built and hosted with Lovable. Built with Power Apps it would look different, with the same data, rules and access underneath.
Which of our shipments will be late today?
Two: PO 4471 to Sacramento is about 2h 40m late, and PO 4502 to Fresno has had no update for 7 hours.
Move 4471 to tomorrow, 8 to 10 am.
Requested. MercuryGate confirmed the new appointment at 11:58.
IT sees and controls all of it
- Runs in your own cloud, with the data in your own database.
- Each system's owner approves what each app can see, and can take it back without touching any other app.
- Every action is recorded, including the ones that were blocked.
| 11:58 | Brightway's AI assistant | Rescheduled PO 4471 (allowed: not out for delivery, under 10 days) | MercuryGate confirmed |
| 11:41 | Customer user, Northpeak Foods | Tried to open PO 4471, which belongs to another account | Refused |
Show what your IT team would see
Claims Recovery
LiveDock Scheduler
LiveCarrier Scorecard
Being built| App | Körber WMS | MercuryGate TMS | project44 | Salesforce | SAP S/4HANA |
|---|---|---|---|---|---|
| Shipment Desk | Readorders, status | Read + writeappointments | Readtracking | Read + writecases | — |
| Claims Recovery | — | — | — | Read + writeclaim cases | Read + writecredit notes |
| Dock Scheduler | Read + writedock doors | Readinbound loads | — | — | — |
| Carrier Scorecard | — | ReadloadsWaitingcarrier cost | Readtracking | — | Readfreight invoices |
Waiting for the transportation systems lead. Carrier cost would stay hidden from every role except Procurement.
Each permission was approved by that system's owner and can be taken back on its own, without touching any other app.
Is the data fresh?
- Körber WMSupdates within seconds20 s ago
- MercuryGate TMSevery 2 minutes1 min ago
- project44live events8 s ago
- Salesforceupdates within seconds35 s ago
- SAP S/4HANAhourly · Claims Recovery shows "data from 10:20"1 h 40 min
A change is coming. What breaks?
Found before the change ships, from the map of where each number comes from.
| Time | Who | What | Result |
|---|---|---|---|
| 11:58 | Brightway's AI assistant | Rescheduled PO 4471 to Wed 08:00–10:00 (allowed: not out for delivery, under 10 days) | MercuryGate confirmed |
| 11:52 | Shipment Desk | Told Brightway's coordinator that PO 4471 is at risk | Sent |
| 11:41 | Customer user, Northpeak Foods | Tried to open PO 4471, which belongs to another account | Refused by policy |
| 11:30 | Claims Recovery | Created a credit note in SAP for claim 00418 | SAP confirmed |
| 10:02 | Carrier Scorecard, being built | Asked for carrier cost | Waiting for approval |