DaliTaxe: A Tax-Ticketing System Redeployed for a Second Client

Client DaliTaxe · Contract
Role Full-stack + Mobile developer · Contract
  • Laravel
  • Vue.js
  • Java
  • Android

Outcome

Reworked and redeployed the YTAX tax-ticketing system as DaliTaxe for a second client under its own brand.

Context

The existing YTAX product, built before this second deployment, included a Laravel back end, a Vue and Blade web application, and a Java Android app for field collection.

Problem

A second jurisdiction needed its own deployment and brand without losing the proven tax-ticketing workflows already in production.

Constraints

The new deployment had to preserve the shared domain model, role-based collector and controller flows, immutable soft-deleted tickets, and mobile collection workflow while accommodating jurisdiction-specific changes.

Decisions and trade-offs

Rather than rebuild, I used a multi-tenant-by-fork approach with dedicated dali branches of the existing repositories. This kept the second deployment close to the established shared core, allowing applicable fixes to flow to both products while accepting separate branches for client-specific work.

Implementation

Adapted branding, configuration, deployment targets, and the adjustments required by the second jurisdiction across the Laravel, web, and Android applications, preserving the established YTAX product foundation.

Results

The second client inherited a system already hardened in production rather than a first draft. The available material does not record deployment or adoption metrics.

Takeaways

A carefully bounded fork can reuse a proven platform for a second client while preserving a path for shared-core improvements. See the YTAX case study for the underlying architecture and ticket model.

Back to resume