Operator tools
Desktop and web apps for the jobs your staff repeat all day: receiving, pull lists, QA checks, transfers, relabeling a whole location at once.
Custom software on the Sortly API
Most teams outgrow Sortly's built-in screens long before they outgrow Sortly itself. I write the receiving tools, purchase-order flows, dashboards, and admin portals that pick up where the app stops, so your staff quit retyping the same numbers into a spreadsheet.
What I build
Desktop and web apps for the jobs your staff repeat all day: receiving, pull lists, QA checks, transfers, relabeling a whole location at once.
The Sortly API talking to your ERP, your accounting system, or the spreadsheet finance refuses to give up. Scheduled, retried, and logged when something fails at 2am.
Roles, permissions, and an admin screen so you can add a user, change what a crew can see, or cut off an account without calling me.
What changes
One flow, one screen. The count that lands in Sortly is the count somebody actually took.
A screen listing the eleven things that need attention today beats a monthly report nobody opens.
Warehouse staff get the warehouse screen. Your customer sees their own items and nothing else.
Everything I build reads and writes through the Sortly API. Your data does not get stranded inside my software.
How it goes
A call or two, sometimes a site visit. I want to see the actual clicking, the actual paper, and the spreadsheet you are slightly embarrassed about.
The first release targets whichever workflow is costing you the most hours. It ships in weeks and your team uses it right away.
Permissions, logging, error handling, and a support path. This is the phase that decides whether the tool is still running a year later.
Good fit
Next step
No spec required. Just describe the process that keeps generating cleanup work. Receiving, POs, counts, permissions, whatever it is. If I am not the right fit, I will say so on the first call.