A multi-city retail orthopedic chain was running on four disconnected subscriptions and spreadsheets. We built a custom CRM that bridges local 3D foot-scan hardware into the cloud—delivering automated WhatsApp reports in under 60 seconds and 100% closed-loop ad attribution.
How in-clinic 3D foot scanners connect through an Electron database adapter into AWS PostgreSQL, automated WhatsApp delivery, and retail POS attribution.
Hover a layer. Only the highlighted chip was built by us — the two above it were the vendor's, and they offered nothing outward.
How disconnected software created data silos, delayed patient biomechanical reports, and blinded digital marketing spend.
- Sees the adone CRM
- Walks into clinicone CRM
- Stands on 3D plateone CRM
- WhatsApp reportone CRM
- Custom orthotic saleone CRM
One record picks up a field at every station, so the ad that caused the sale is still attached when the sale happens.
This is the whole engagement in one move. Select a stage — the sealed box is the vendor's, the middle one is ours, and nothing downstream exists without it.
We reverse-engineered the vendor schema and deployed a background agent that detects new scans in real time, normalizes biomechanical metrics, and pushes them securely to the cloud CRM.
Reports used to be exported and sent by hand, so patients had usually left before theirs arrived. Now the scan finishing is the trigger.
- 01Capture writtenVendor software commits the scan locally.
- 02Adapter picks it upThe agent detects the new row and uploads it.
- 03Report renderedA biomechanical PDF is generated server-side.
- 04Sent on WhatsAppDelivered over the WhatsApp Cloud API to the patient.
The dial measures the budget, not the steps — the record commits to the total and nothing finer, so the sequence carries order only.
A digital ad click, a clinic walk-in, a hardware capture and a POS sale — joined deterministically without data loss.
The four joins are the deliverable. Every step overlaps the one above it because they share a key — which is exactly what did not exist before.
Three numbers the chain could never see side by side, now aggregated per store and per day in real time.
| Ad platform | Lead capture | Scan bridgenew | POSnew | |
|---|---|---|---|---|
| Clinic Walk-ins | ||||
| Consultation conversion | ||||
| Custom orthotic sales |
Two of the four sources could not reach a dashboard at all before this engagement. The number of clinic chips is illustrative — the record says multiple metros and no count.
- Clinic Walk-insCounted informally on spreadsheets, per store, if at all.Logged against the store and the digital campaign that drove it.
- Consultation conversionNo record of who walked in and then received a scan.Walk-in to scan capture, tracked per store and per day.
- Custom orthotic salesAn isolated POS checkout item unlinked from clinic records.Closed back against the scan, the store and the originating ad.
Once the scan existed in the cloud instead of on a desktop, the click, the walk-in, the capture and the purchase could finally be shown to be the same person.
- < 60 Sec
- Scan to report in hand
- Replacing a manual export-and-send queue that ran hours behind.
- 4 SaaS
- Subscriptions retired
- Four disconnected tools and spreadsheets, replaced by one CRM.
- 2–3 Wks
- First sprint shipped
- Deployed to pilot clinics; client owns stack on open-source core.
- Multi-city
- Stores on one dashboard
- Clinic walk-ins, consultation conversion and custom orthotic sales per store.
This chain is described by sector and region rather than by name, so publishing never waits on a client's sign-off. The figures are unchanged either way — our delivery record is independently verifiable on Upwork.
Hardware vendors rarely ship an API, and waiting for one is not a plan. We integrate the device you already bought.
What we ship
- Closed-device and legacy database integration
- Desktop agents for on-premise capture
- WhatsApp Cloud API delivery pipelines
- Ad-to-POS attribution
- Multi-store operational dashboards
- Replacing SaaS sprawl with one owned system