Tarik Bateh, a senior director with JLL Capital Markets, is giving a presentation about his thoughts on Lot J. He said there are 4 major and fundamental red flags about the project, but they can all be fixed with "basic and standard" business and governance practices.

First red flag: Due diligence. He said the developers need to provide more information about the project.
"You could not get a mortgage on your house with the information that has been provided about Lot J," he said.
2. He said the developers need to invest their money into the project before the city does, as this is standard practice in the real estate industry.
"This ensures skin in the game," he said.
Bateh said the developers are fully capable of getting a construction loan from a bank, not the city.
Bateh's third point is that no city money should go towards the project until it's completed. City should instead provide a lump sum payment at the completion of the project that the developers do not need to pay.
"This method has proven very successful in revitalizing downtowns" across the county.
Bateh said a gap analysis should be considered to determine how much money the developer should receive. That involves city agreeing what a reasonable profit on the project would be and providing money to bridge the gap between what the profit would be without public investment.
Bateh said DIA is fully capable of performing that gap analysis.
Bateh said city should retain long-term ownership of the Lot J development, as its a highly strategic property. Suggests offering a ground lease for the property
Bateh said the ground lease should contain provisions that would allow city to terminate if the Jaguars leave. It doesn't burden developer but protects taxpayers, Bateh said.

More from Business

The Mother of All Squeezes

How Volkswagen went from being on the brink of bankruptcy to the most valuable company in the world in two days

/THREAD/


1/ At the peak of the 2008 financial crisis, Volkswagen was considered a very likely candidate for bankruptcy.

Heavily indebted and already financially struggling before 2008, with car sales expected to plummet due to the ongoing global crisis.


2/ With GM and Chrysler filing for bankruptcy in 2009, shorting the VW stock would seem a safe bet.

If you are not familiar with stock shorts and short squeezes check my thread


3/ On October 26, 2008, Porsche announced it had increased its stake at VW from 30% to 74%.

This was a surprise to many who were led to believe that Porsche wasn't planning a takeover of VW, based on the company's announcements.


4/ Before the announcement, the short interest was approximately 13% of the outstanding shares, a number considered relatively low.

Porsche had a 30% stake, the Lower Saxony government fund held 20% of the shares, and another 5% was held by index funds.
There are 100s of threads on building and running startups.

Here are 10 that are pure gold:

Fund-raising is hard for all of us.

@justinkan shares some unique insights on how to do it well.


We rarely hear honest reflections from founders on what they messed up.

@apartovi shares his reflections on a deal that went wrong with Steve Jobs.


Some gems in this thread by @agazdecki on a wide variety of founder


shares some solid principles learned from building a multi-billion dollar business.

You May Also Like

A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.

Legacy site *downloads* ~630 KB CSS per theme and writing direction.

6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices

https://t.co/qyl4Bt1i5x


PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.

735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices

https://t.co/w7oNG5KUkJ


The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.

The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.