Insights - Trellint

Beyond One Vendor - Part 2: The Accountability Gap. The Structure of Your Vendor Relationship Matters.

Written by Kim Wan | Apr 9, 2026 4:57:31 PM

In Part 1 of this series, we explored how the curb evolved from a procedural service into critical public infrastructure. That shift requires a more sophisticated delivery model than either a consolidated mega-vendor or a loose collection of specialists can provide. We introduced the three-layer architecture: specialized execution partners, ecosystem governance, and the deep generalist advisor at the center.

This article focuses on the layer that makes the other two to function effectively: accountability. More specifically, it examines why structural accountability, rather than contractual language, is the most reliable predictor of long-term program performance.

 

The Assumption Beneath Every Procurement

When cities evaluate vendors for complex parking and curb management programs, the evaluation criteria tend to focus on the familiar criteria: technical capability, past performance, staff qualifications, financial stability, implementation approach.

These are necessary questions. But they share a common assumption: that the vendor being evaluated is a coherent, stable, accountable entity with a clear stake in the outcome of your program.

That assumption deserves more scrutiny than it usually gets.

 

Two Models That Fail the Same Way

The parking industry has long debated two competing delivery models: the consolidated full-service vendor versus the multi-vendor ecosystem. The debate is usually framed as simplicity versus specialization. One vendor to manage versus deeper expertise across multiple partners.

Both framings miss something more fundamental.

The real question is not how many vendors are involved. It is whether any of them has a genuine, structural stake in your program’s performance.

A consolidated mega-vendor can win a contract across operations, technology, collections, and analytics, then manage each function as an internal cost center, with no independent accountability for outcomes in any of them. The consolidation that looked like alignment is diffusion. No single part of the organization rises or falls on whether your citation revenue grows, your equity outcomes improve, or your collections rate beats the prior year. It all flows into a larger organizational budget where the signal gets lost.

A loosely assembled consortium can have the opposite problem. Each partner may be genuinely expert in their domain, but without unified accountability, coordination becomes the city’s burden. When something goes wrong, partners point in different directions. The city hired specialists and ended up as the general contractor.

Neither model answers the accountability question well. And without genuine accountability, even capable vendors drift.

 

What Genuine Accountability Looks Like

A vendor has genuine accountability when its organizational structure, not just its contractual obligations, creates a direct incentive to perform on your program specifically.

That structure is most visible in three places: brand identity, cultural orientation, and the relationship between advisory and execution functions.

A vendor operating under its own distinct brand has something an internal division or cost center does not. Its name, reputation, and credibility are directly tied to client outcomes.

When a named organization performs well, that performance is credited to that organization. When it falls short, the same is true. There is no larger portfolio to absorb the signal, and no parent brand to deflect it. The outcome belongs to them.

This is not primarily a financial argument. It is an identity argument. Organizations with a distinct identity tend to make decisions differently than organizations whose identity is subsumed within a larger structure. They hire for fit with their own culture, not a parent’s. They develop institutional knowledge and practices that are specific to their discipline. They build client relationships that persist through leadership transitions because those relationships are anchored to the organization, not to the individuals who happen to be in a particular role at a particular moment.

 

The Specialist Advantage Is About More Than Expertise

The case for specialist vendors is usually made based on depth: a firm that does one thing has had more time, more focus, and more incentive to get very good at it than a firm that does many things adequately.

That argument is correct. But it understates the real advantage.

Specialist vendors do not just know more. They are organized differently. Their culture, their hiring criteria, their internal language, their product roadmap, their client relationships are all oriented around a single discipline. That orientation produces a kind of institutional fluency that generalists cannot replicate through training or acquisition.

Consider what this means in practice for a city managing delinquent receivables. A collections firm thinks differently than a firm that manages collections in addition to payment apps, mobility-as-a-service, EV solutions, etc. That expertise is embedded in processes, in data models, in staff development practices that have been refined over years of focused iteration.

This is where the deep generalist advisor earns a specific kind of value that neither specialists nor the consolidated platform can provide. They can govern across multiple specialists, benchmark their performance independently, and optimize allocation in the city's interest rather than any single vendor's. That capability requires genuine expertise in the underlying discipline (you cannot govern what you do not understand) combined with the structural independence to act on what the data shows.

 

Why the Deep Generalist Advisor Must Be Independent of Execution

The three-layer model introduced in Part 1 places the deep generalist advisor at the center of the ecosystem. Not as a passive integrator, but as the entity ultimately accountable for whether the system produces the outcomes the city cares about: compliance, revenue recovery, equity, and operational efficiency.

 

In Trellint’s case, accountability is not purely advisory. It includes real execution responsibilities, from managing citation issuance and processing to applying data science to enforcement scheduling and routing, optimizing collection strategy across multiple specialist agencies, and tracking equity outcomes across the full program. This, while simultaneously maintaining the independence to evaluate whether the tools and partners doing that work are the right ones.

What distinguishes this role from a consolidated vendor is not the absence of execution. It is what each party stands to gain.

A deep generalist advisor succeeds when the program succeeds. A consolidated mega-vendor wants those things too, but it also wants its own platforms to keep winning the work. That second interest is what corrupts the advisory role.

When the entity advising on performance also owns the tools being evaluated, the instinct to protect those tools competes with the instinct to surface their gaps. A recommendation that challenges the status quo can be uncomfortable. Saying that a routing approach is producing inequitable results, that a collections firm is underperforming on a particular segment, or that a technology vendor is building toward lock-in will generate internal friction. That friction often works against honest counsel before the city ever hears it.

An advisor whose stake is in outcomes faces no such pressure. If a different collections firm would perform better, the outcome-accountable advisor says so because their reputation rests on whether the portfolio performs, not on whether any particular firm holds the work. If a routing model is generating disparate enforcement patterns, they surface it because the equity outcome belongs to them.

This is the independence that matters. Not independence from execution, but independence from platform loyalty. An organization can be deeply embedded in a program's delivery and still give cities the honest counsel they need, as long as its accountability runs to what the program produces, not to which tools it uses to produce it. 

 

Organizational Identity as a Competitive Differentiator

Organizations that operate with distinct brands and genuine accountability to client outcomes instinctively work to solve problems. It is their name on the work, their reputation is at stake, and their leadership who is directly accountable for outcomes. They cannot absorb a program failure into a larger organizational narrative. They cannot redirect client dissatisfaction upward or outward. The outcome is theirs, and they know it. That ownership produces a different kind of problem-solving orientation.

The most resilient delivery model is one that combines the resources and reach of a larger enterprise with the accountability and agility of an independently operating brand. The key is that independence is real. It must show up— in identity, in culture, in the daily decisions that determine whether a program gets the attention it deserves.


 

 

The Procurement Question That Usually Goes Unasked

Most vendor evaluations ask familiar questions. Can you do this work? Have you done it before? Who will be on the team?

Fewer ask more revealing questions. What is your organizational identity, and does it create a genuine stake in this program’s performance? Is your advisory function structurally separated from the execution functions it will be asked to evaluate? If your program underperforms, whose reputation is at risk, and is that organization present and named in this relationship?

Those questions are not adversarial. They are practical. A vendor with strong self-awareness will have clear answers. A vendor that struggles to answer them is surfacing something worth understanding before the contract is signed rather than after.

 

In long-term public contracts, particularly those tied to revenue integrity, equity outcomes, and data governance, the cost of a vendor’s structural misalignment is borne by the city. That asymmetry is worth naming explicitly in the evaluation process.

 

Accountability Is the Foundation

Capability gets a program started. Accountability is what sees it through.

In complex systems, accountability is not produced by contract language. It is produced by organizational structure. Distinct Identity. Earned Reputation. Advisory functions that are genuinely independent of the execution interests they are asked to assess. Those are the conditions under which vendors solve problems rather than manage relationships, surface gaps rather than protect revenue, and remain focused on your program’s performance rather than their own organizational continuity.

The vertically integrated vendor that controls most of your curb system is not necessarily the most accountable to it.

If you have questions about accountability, vendor structure, or how this model applies to your curb or parking program, contact Trellint to find out more.

 

UP NEXT

Part 3: When Incentives Drift: what cities should know about vendor consolidation, integration risk, and the quiet cost of misaligned incentives.