Live implementation · Lasso-powered backend
Ticket500. Connected through Stub.
For Ticket500, we connected flyer creation, bookings, reporting, contact management, and customer support through our Lasso-powered backend, branded as Stub.
Five workflows in the same operation
The implementation brings together work that touches promotion, bookings, people, service, and reporting. These five workflows are running today.
- Flyer creation for promotional work.
- Booking workflows.
- Reporting.
- Contact management.
- Customer support.
Lasso underneath. Stub as the brand.
Lasso powers the backend used for the Ticket500 implementation, branded as Stub. The business workflows are part of the configured implementation around it.
The public Lasso project provides another way to inspect our engineering work. Its project page and documentation describe the software itself; this case study describes the Ticket500 deployment.
A platform shaped around the business
The useful pattern is connecting recurring business functions through a system the operator can use under its own brand. That can bring technical work closer to how a business already operates, instead of asking the business to assemble every connection itself.
The specific data sources, tools, permissions, and review points belong to each implementation. We scope those around the operation and the responsibilities of the people using it.
What this example can help you evaluate
- Which recurring workflows could connect in your operation.
- Whether your existing tools can support the required integrations.
- Where a branded interface would make the work easier to use.
- Which actions need review and who owns exceptions.
- Whether a defined build or retained delivery is the right engagement.
Questions about this implementation
Are these workflows live or proposed?
Flyers, bookings, reporting, contact management, and customer support are live in the Ticket500 / Stub implementation.
Does installing Lasso include the Ticket500 workflows?
The Ticket500 workflows are part of its configured implementation. Another business needs its own connections, data access, permissions, and operating design.
What would a connected operation look like for you?
Bring the workflows and the tools your team already uses.