Trexo Robotics runs on Salesforce now, not Airtable and four forms.

Trexo Robotics builds gait-training devices that help children learn to walk, and the operation behind that was spread across tools that never spoke to each other: Airtable held the processes, four JotForm forms handled patient intake, and two regional Stripe accounts processed payments with no connection to Salesforce. The clearest symptom was that a completed payment created no record anywhere in the CRM. We designed and built a single Salesforce backbone to carry a device from quote to payment to patient care, retiring Airtable and the forms in the process.

Billing was the hardest part, because it had to be both regional and multi-model. Products, prices, and customers now sync to the correct US or Canadian Stripe account through named credentials and write their IDs back to Salesforce, and a Stripe events handler turns paid, failed, and checkout events into transactions, orders, and closed opportunities - so a payment finally creates a record. A single reusable payment component sits on accounts, contacts, leads, opportunities, and orders, offering the right options for each with the price book following the record's currency.

Then there were the three payment models Stripe cannot handle on its own. A one-time purchase is straightforward. The multi-donor model, where several people fund one device against a shrinking balance, required each donor to get their own checkout link capped at the remaining balance, so the total can never be overshot as others contribute. The 36-month lease meant Salesforce itself calculating the total contract value, down payment, and monthly amounts - because Stripe does not - then auto-creating a 36-month contract with line items and a matching subscription. The research finding that Salesforce, not Stripe, had to own the lease math shaped that whole build.

On the care side, intake that used to arrive as unmappable JotForm table-answers - measurements buried in strings like a toe-box width reading - is now parsed into clean fields by a formula, and confirming a form automatically creates the account, contact, opportunity, patient, and assessment. Patient assessments carry conditional forms and an approval process, Calendly automation handles scheduling and reminders, and the operational model that lived in Airtable - training, check-ins, device modifications, compliance - was rebuilt natively in Salesforce with auto-generated record IDs.