Modernizing TrueRoll’s platform
When I joined TrueRoll, its core product had been built on Caspio, a low-code platform that had helped the company move quickly in its early stages. That advantage was becoming a liability. The product was supporting increasingly complex operational workflows and larger data volumes. The platform struggled with updates, required manual refreshes, and limited how quickly the team could improve the product. As the company grew, those constraints threatened to become a serious barrier to scale.
I identified the risk early and developed the strategy for moving the product to a modern web architecture.
The problem
TrueRoll’s product helped local governments identify and manage property-tax exemptions. The platform had two major parts:
- A back-end system supporting data and operational workflows
- A Caspio-based front end used to deliver the product to customers
Caspio had been a practical choice for building an initial product, but it was not well suited to the company’s next stage. The limitations were becoming increasingly visible:
- The platform struggled with the volume of data the product needed to process.
- Updates could not be handled cleanly and often required manual refreshes.
- Product changes were constrained by the underlying low-code system.
- The architecture increased the risk that growth would outpace the platform.
- The company depended on a system that would be difficult to maintain and evolve at scale.
This was not merely technical debt. It was a product and business risk.
The strategic decision
I pitched TrueRoll’s founders, including the CEO and CTO, on a Lift-’n-Shift: move the existing product off Caspio and onto a modern JavaScript and React-based front end before the old architecture became an existential constraint. The decision was intentionally pragmatic. The company did not need to redesign every workflow at once. It needed to preserve the working product, move it onto a more scalable foundation, and create room for future improvement.
That meant separating two questions:
- What functionality needed to move?
- What functionality should be redesigned?
The initial migration focused on the first question. Trying to modernize the architecture and reinvent every business process simultaneously would have increased risk and slowed delivery.
My role
As Director of Product Management, I established TrueRoll’s first formal Product organization and introduced a more disciplined approach to product development. For the Lift-’n-Shift specifically, I:
- Identified the low-code platform as a major constraint on future growth
- Framed the issue as a product and business risk, not only an engineering concern
- Built the case for migration and presented it to the founders
- Defined the product strategy for the transition
- Helped separate migration requirements from later functional improvements
- Introduced roadmap planning and Agile product practices
- Coordinated product, engineering, and operational perspectives
- Helped determine the staffing model needed to maintain and evolve the new platform
A central question was whether to rely on a contractor for the migration or invest in permanent internal capability. My view was that the company needed more than a team that could complete the move. It needed people who could maintain and improve the platform afterward. The appropriate model therefore had to account for both short-term delivery and long-term ownership.
Why “Lift-’n-Shift”
The phrase can sound unambitious. In this case, restraint was the point. A migration already introduces substantial risk:
- Existing workflows may behave differently.
- Data may not move cleanly.
- Users may encounter new defects.
- Operational teams may have to support two systems temporarily.
- Undocumented dependencies may surface late.
- Product improvements can become entangled with technical conversion.
The safer approach was to move stable functionality first, test it thoroughly, and make broader product changes after the new architecture was in place. This reduced the number of variables changing at the same time.
What worked
The main Lift-’n-Shift proceeded smoothly because the team treated migration discipline as a product requirement. The approach emphasized:
- Clear warnings about transition risk
- Testing before release
- Preserving known workflows
- Avoiding unnecessary functional changes during the move
- Coordinating technical and operational readiness
- Creating a foundation that could be maintained after launch
A later, smaller migration reinforced the value of that discipline. It was less successful because the work combined the platform move with functional changes whose requirements were not fully understood. That contrast produced a clear lesson: migration and redesign can be related, but they should not be casually combined.
Building the Product function
The platform strategy was part of a broader change in how TrueRoll managed product work.
I established the company’s first Product organization and introduced:
- Product ownership
- Roadmap planning
- Agile delivery practices
- More explicit prioritization
- Cross-functional coordination
- A clearer distinction between customer needs, operational requests, and technical work
This helped move the company away from treating product development as a sequence of founder or customer requests.
The goal was to create a repeatable system for deciding what to build, why to build it, and how to sequence the work.
Business context
The modernization effort supported a company operating in a demanding GovTech market.
Government customers require reliability, security, continuity, and clear implementation planning. They cannot absorb frequent disruptions simply because a vendor is changing its architecture.
At the same time, TrueRoll was pursuing larger opportunities. During my tenure, the company secured a $250,000 engagement with the City of Seattle.
That growth made platform scalability more urgent. A system that was adequate for early customers could not be assumed to support a larger and more complex customer base.
What I learned
The Lift-’n-Shift reinforced several lessons that have shaped my later work.
- Low-code tools can be effective for proving a concept but expensive to outgrow.
- Technical architecture becomes a product issue when it constrains customer value.
- Migration should preserve what works before attempting to improve everything.
- Combining a platform move with unclear functional changes multiplies risk.
- Contractors can accelerate delivery, but permanent ownership is required to sustain a product.
- The right time to modernize is before the current system visibly fails.
- Product leaders need enough technical understanding to recognize when architecture threatens strategy.
The most important lesson was that platform modernization is not primarily a software exercise. It is a decision about when an organization should stop optimizing around the constraints of its current tools and invest in the capability it will need next.
The result
TrueRoll moved toward a modern architecture before the Caspio platform could become a hard ceiling on growth. The work also established a stronger Product function and a more disciplined way to manage platform decisions. The value was not only the new front end. It was the decision to act before the existing architecture became a crisis.