aijakejbPortfolio
Business Operations Applications, built around your trade
Beyond IT Support builds the software that runs an operationally complex business — not a generic package bent around your process, but a system built around it. Two recent builds: a pool service company's field and office system, and a trailer manufacturer's order-to-title production system.
The problem
Most businesses of this kind run on one of three things: software written for them decades ago by somebody no longer reachable, a general-purpose SaaS platform bent awkwardly around their process, or paper and a whiteboard. All three share the same failure mode — the rules that actually matter, tax treatment, per-customer quirks, how a number gets issued, live in one person's head or in code nobody can see or version, and errors compound quietly for years before anyone notices.
What we build
Everything hangs off a single record for the unit of work — a customer, an order, a job — that carries it from first contact through to whatever document has to leave the building with it: an invoice, a certification, a title. It runs in a browser, reached from a desk or a phone on the shop floor, and it runs on the business's own server: the data stays with the business that generated it, with no per-seat subscription that grows every time somebody is hired.
The order record
One record per customer, order, or unit that follows it from first quote through to the documents that legally have to travel with it — nothing re-typed at each stage.
Scheduling & production stages
A stage board and a forward schedule set against real capacity, so the office, the field, and management all read from the same history instead of spreadsheets that disagree by Friday.
Field capture
Technicians and crews work from a phone: what's due at this stop, photographs, serial numbers, readings — recorded at the point of work, not typed up that evening.
Documents that can't disagree
Invoices, certifications, and title or compliance paperwork generated from the order record itself, so they're never out of sync with one another.
Business rules as configuration
Tax treatment, discount structures, surcharge rules, numbering sequences — held as data an office can review and edit, not buried in form code nobody can read.
Role-based access
The shop floor can advance a job without touching a price; a salesperson can't quietly re-stage someone else's unit.
Migration, not re-entry
Existing history comes across and is reconciled against the old system before anything is switched over. The old system stays readable throughout, and nothing is re-typed by hand.
Money & reporting
Revenue, backlog and exceptions on one dashboard, with every figure opening the list it counted — a confidently wrong number is worse than no number at all.
A rule, in practice
In one build, the legacy system issued the next serial number as the highest number so far, plus one, for the year. The moment a unit was entered against a future year — routine, late in a calendar — it drew from the wrong pool and quietly abandoned dozens of numbers before anyone noticed. The fix was to issue the lowest unused number and treat retired numbers as used, so one is never handed out twice. That's the kind of defect that survives for years in a system where the rule lives in nobody's head — and exactly the kind a rewrite has to find by reading the original logic, not by interviewing around it.
Two recent builds
Pool Service Field & Office — for a pool service company running a few hundred to a few thousand customers, built around the shape of a cold-winter season: openings, the season itself, closings, and winter maintenance. Service sold in prepaid blocks is tracked to the visit, and a homeowner portal is kept isolated from the staff system by design.
Trailer Plant Portal — for a build-to-order trailer manufacturer, carrying a unit from a configured quote through VIN issue, the shop floor, and every certification and title document it can't ship without — including the fix to the serial-numbering defect above, found in the plant's own history.
Where this goes next
Every one of these is built the same way Bob is — correct and trustworthy as a normal application first, because that's the standard the work is held to before anyone hands it real operations. Once it's running, the same kind of agentic layer that runs Beyond IT Support internally can sit on top of it: reading the exceptions screen and drafting the fix, watching the schedule and flagging what's gone stale, drafting the customer message and holding it for approval. The application doesn't get rebuilt to add that — the agent gets added to it.
Running your business on something you didn't build?
We start by reading the system you have now — including the rules nobody wrote down — before we talk about what replaces it.