Services

Four kinds of work, usually in that order.

Almost every project starts the same way: one workflow is eating hours every day, we fix that, and the rest of the system grows out from there. Here is what that work looks like.

Custom internal tools

Desktop and web software for receiving, purchase orders, inventory cleanup, pull lists, location assignment, and the exceptions that never fit the happy path.

  • Screens shaped around how your team actually works
  • Validation and guardrails so bad data gets caught at entry
  • Different views and permissions for different roles

Sortly integrations and sync

Connections between Sortly and whatever else your operation depends on: an ERP, accounting, a BI tool, or the workbook one person maintains by hand.

  • Two-way reads and writes through the Sortly API
  • Scheduled runs with retries, and an alert when a run fails
  • Field mapping and cleanup so downstream reports stop lying

Dashboards worth opening

Views built around a decision someone has to make today: what is missing, what is late, what got counted wrong, which jobs have been sitting untouched since Tuesday.

  • Every number links through to the thing you would do about it
  • Filters by role, location, vendor, or work queue
  • CSV export, because someone downstream will always want a spreadsheet

Admin portals and permissions

Once a tool grows past its first user, the back end starts to matter. I build the layer for user setup, role management, audit history, and customer access.

  • Roles tied to real jobs rather than abstract permission bits
  • A screen where you manage staff and customer accounts yourself
  • Audit history for who changed what, and when

Engagements

How the work usually gets scoped

A

One workflow

For when a single pain point clearly dominates and you want a contained first win before committing to more.

B

Integration plus a UI

For when moving the data is only half the problem and somebody still has to act on it every morning.

C

Hardening what exists

For when a useful tool is already running and now needs auth, permissions, admin controls, or a real deployment.

Next step

Not sure which one you need?

That is normal, and it is usually clear within one conversation. Describe the process that is causing the most rework and we can figure out the shape of it together.

Get in touch Read the approach