BusPas
BusPas
- ClientBusPas
- StackWeb application · API integrations
- StatusUnder care
Built for the operator, not the buyer
Where the public-facing work explains the program, this is the tooling that runs it. The audience is internal, the sessions are long, and success is measured in how few clicks a repeated task takes.
Application logic, kept out of the CMS
Forcing genuine workflow into a content system produces something fragile that nobody can safely change. Running it alongside, with a clean boundary and its own admin, produces something maintainable.
Integrations were treated as the risky part. Every external service is a dependency that will change underneath you, so each sits behind a boundary we control rather than being called from wherever was convenient.
Two systems, one action
The manual steps that used to sit between two systems collapsed into one, and the parts most likely to break are now the parts that can be replaced without touching anything else.
Before you publish
Editor note: this write-up is placeholder. The client, the scope and the stack are real; the figures and outcomes are not measured. Replace them or cut them before publishing.