Engagement at a glance
Client
Foxter
MARKET
Spanish-speaking
STATUS
Completed
DURATION
2–3 months
PROJECT OWNER
Inboundsys
THE RESULT
A new distance-based pricing model was introduced while the customer-facing website and dependent systems remained fully compatible and continuously available.
Business need: add new pricing combinations that could be managed through the existing dashboard.
Core constraint: an undocumented legacy platform and a PostgreSQL view that had reached technical limits.
Engineering response: reverse-engineer the architecture, split the oversized view, and recombine it into a final view with the exact same output structure.
Business impact: broader pricing options, lower operational risk, improved maintainability, and a scalable base for future enhancements
Executive summary
Foxter operates a car-rental business in a Spanish-speaking market. Its internal platform, built with Angular, Node.js, and PostgreSQL, manages fleet information, rental pricing, and rate combinations. Customers, meanwhile, browse vehicles and pricing through a HubSpot-based website. The two environments are operationally interdependent: backend changes must continue to feed the website in precisely the structure it expects.
Foxter wanted to add a new distance-based pricing option to support growth and make rate changes easier to manage. The request appeared straightforward, but the underlying system was undocumented, the company had no in-house technical team, and the central PostgreSQL view had reached database limitations. A poorly controlled change could have interrupted pricing visibility, damaged the browsing experience, or disrupted live rental operations.
Inboundsys approached the engagement as a controlled modernization, not a quick patch. The team mapped processes, reverse-engineered data flows and dependencies, redesigned the database-view architecture, preserved the original output contract, integrated the new logic with the HubSpot website, and supported testing, go-live, and post-launch stabilization.
WHY THIS MATTERED
Foxter gained new commercial flexibility without replacing its platform, taking the website offline, or requiring an internal technical team to absorb the complexity.
Client context
| Dimension | Project context |
| Business | Car-rental company serving a Spanish-speaking market. |
| Customer experience | Vehicle availability and pricing presented through a HubSpot-based website. |
| Internal platform | Angular dashboard, Node.js application logic, and PostgreSQL data architecture. |
| Internal capability | No in-house technical team; Foxter relied on external support for maintenance and enhancement. |
| HubSpot scope | Content Hub plus Data Hub / Operations Hub; Operations and IT functions covered. |
| Project profile | Completed in 1–3 months; primary HubSpot edition and approximate user count were not provided. |
The challenge: growth blocked by hidden complexity
Foxter’s immediate requirement was a new distance-based rate combination. The deeper challenge was introducing it safely into a system whose behavior, dependencies, and data contracts were not documented. The existing PostgreSQL view was already at its technical limit, so the new pricing tier could not simply be appended using the established approach.
Three interconnected risks
01 ARCHITECTURE
- No reliable documentation existed to show how the dashboard, Node.js logic, PostgreSQL views, and HubSpot website interacted.
02 DATABASE
- The oversized PostgreSQL view had reached a limitation, preventing a straightforward extension of the pricing model.
03 PRODUCTION
- Changing the output structure could break the live website or downstream systems, affecting pricing visibility and customer experience.
