The Brighton Question:
what $16 million built, and what comes next

Before this was a fight about 600 homes, it was a monument to a different idea about how growth works.

In the early 2010s, Lexington County made a bet. It spent more than $16 million in public money to build the Chapin Business & Technology Park at Brighton — grading roughly 200 acres, laying four-lane boulevards, sidewalks, a roundabout, and a decorative fountain. The theory was "if you build it, industry will come." Build the infrastructure on spec, and tenants — factories, tech firms, the jobs that come with them — would follow.

They didn't. For roughly fifteen years, the park drew essentially no tenants. What the county got for its $16 million was, in the words of one local news crew, "four lanes running through vacant lots" — paths leading to dead ends, sidewalks along empty fields, and a fountain at the entrance to nothing. And the empty park wasn't free to keep: the county pays an estimated $200,000 a year just to maintain the vacancy.

It is tempting to read the current fight as growth versus no-growth. But the fifteen-year vacancy reframes it. The status quo is not "no cost." The status quo is a $16 million asset producing zero dollars of tax while costing $200,000 a year to mow. Leaving it empty is not a victory. It is the most expensive outcome on the table.

This is a familiar pattern, and not only in Chapin. The "build speculative infrastructure and wait for industry" model has failed in countless American counties. It front-loads enormous public cost against a payoff that may never arrive. The Brighton park is simply an unusually clean example: a fully-built, fully-paved, completely empty bet.

So the right question is not whether the land should be used. It plainly should — that infrastructure is already in the ground, already paid for, already being maintained. The question is what pattern finally puts it to work, and whether that pattern earns back more than it costs.

Hold the tax system constant. Vary only the development pattern. What happens to the revenue the land produces per acre?

This is the core measurement behind a generation of work by Joe Minicozzi's Urban3 and Chuck Marohn's Strong Towns: annual property-tax revenue per acre. It cuts through the noise because it's the number that actually has to cover a place's long-term infrastructure bill. A development can have beautiful renderings and still quietly lose money per acre. The per-acre lens tells you which is which.

Here are five ways the same 200 acres could perform — four hypothetical patterns plus the realized status quo — under the identical Lexington County tax structure (461.743 mills, South Carolina's 4% / 6% assessment ratios):

Three things jump out — and the third is not the one you'd expect.

First — the original industrial bet was the weakest idea even if it had worked. A fully-tenanted light-industrial/flex park (which this site never became) produces only about $13,000 per acre in property tax. Industrial land is low-rise, low-coverage, and heavy on parking and loading — its economic case is jobs, not property tax. The county spent $16M chasing the pattern that pays the least per acre.

Second — Palatin is, by this measure, a genuinely strong proposal. At roughly $41,000–$49,000 per acre, it is five to nine times more productive than the existing Chapin sprawl pattern (which runs $5,000–$8,000 per acre) and more than three times a conventional new subdivision. The developer deserves credit: a master-planned mix of higher-value homes at moderate density, with real commercial, is far better fiscal land use than what greater Chapin has mostly been building. This is not a low-value sprawl bomb.

Third — and this is the honest surprise — you can't out-produce Palatin much by being "more walkable," at Chapin prices. A walkable, finer-grained traditional neighborhood, built natively for Chapin's price level, lands around $42,000 per acre — essentially a tie with Palatin, even a touch below it, because Palatin's higher-value homes and large commercial component carry a lot of tax. It's tempting to point at famous walkable districts elsewhere that clear $70,000+ per acre, but those run on million-dollar-plus home values; their per-acre numbers are mostly a price-market effect, not a pattern effect. Hold price constant at what Chapin commands, and the pure-pattern bonus on property tax is small.

The pattern question in Chapin isn't "is Palatin productive?" It is. It's "what does this pattern cost to move through for the next fifty years?"

This reframes the debate. The residents who showed up to oppose 600 homes are right that pattern and infrastructure matter — but the answer to those worries is rarely no development on already-built infrastructure. Palatin, by its own numbers, pays its way handsomely. The real unanswered question is the one nobody at the hearing was asking: if it pays its way, who exactly does it pay?

Which is Chapter Three.

Almost every problem in Chapter Three traces to one fact: the Brighton site is unincorporated. The town bears the cost; the county banks the tax. So start there.

The site sits directly against the heart of Chapin — by any common-sense measure it is in the town, more so than many parcels that pay Chapin taxes today. If Chapin annexed it, the mismatch largely dissolves on contact:

• The town would collect municipal property tax from the site — revenue that finally matches the sewer burden it already carries.
• The town would gain zoning and design control — so its "yes" could require the connected, walkable pattern, instead of watching from the sidelines while the county approves a layout the town then has to serve.
• The 600 households would join Chapin's tax base and its electorate — residents with a vote in the town whose infrastructure they depend on, rather than untaxed, unrepresented neighbors.

So why isn't annexation on the table? Because, as with the sewer math, every individual actor's short-term incentive points the other way. The county owns the land and wants the $20.4M sale — annexing into the town first would cede county control and county tax base. The developer often prefers county jurisdiction: fewer approvals, no town design review, more speed. And the current mayor ran on slowing growth — annexing 600 homes is the opposite of the platform, even if it would fix the finances. Everyone's local incentive blocks the move that would serve the public interest. That is exactly the situation an outside analysis exists to name.

Look at what each party gets, versus the courtroom:

The county recoups its full investment (over time rather than today), books the economic-development and jobs win, drops the annual maintenance liability now, and avoids a lawsuit it might not win cleanly. The developer gets sewer certainty and entitlements now instead of years in limbo — and a town-blessed, well-connected, walkable plan that sells at a premium. The town stops subsidizing growth it can't tax: it collects revenue that matches the burden, gets help funding the plant it needs anyway, and gains control over the pattern of what gets built against its front door. The only thing anyone gives up is the fantasy that they'll get everything by force.

The land has sat empty for fifteen years because everyone treated it as win-or-lose. It gets built the moment someone treats it as a deal.

None of this is exotic. Annexation, installment conveyance, tax-increment financing, and capacity-fee schedules are ordinary tools, used across South Carolina every year. What's been missing isn't a mechanism. It's a frame that lets the county, the developer, and the town each say yes on the same day — because the money finally lines up with the obligations. Re-align who-pays with who-benefits, and a fifteen-year stalemate becomes a groundbreaking.