Between 2018 and 2021, TikTok expanded its North American footprint faster than almost any technology company in recent memory. I was managing capital programs across more than 20 sites during that period — offices, content studios, and operational facilities across multiple markets, multiple landlord relationships, and a pace that didn't slow down for organizational complexity.
The operational workload was significant. The data problem was harder.
Every site had its own executed lease. Each one contained critical dates, financial obligations, restoration requirements, and negotiated rights that needed to be tracked and acted on — often simultaneously. Rent commencement dates. TI allowance draw schedules. Renewal notice windows. HVAC exclusivity clauses. Parking ratios. Data that lived in executed PDFs, broker abstracts, legal summaries, and the institutional memory of whoever had been closest to that particular deal.
When the system is people, the system has a single point of failure
We managed more than 20 programs without missing anything material. But that outcome depended on specific people — their attention, their availability, their willingness to chase down information across three different document repositories before any leadership review.
That's not a system. That's luck operating through competent people.
The risk isn't that something gets missed on one lease. The risk is that as the portfolio grows, the cognitive load of tracking it manually compounds faster than the team does. At five leases, a shared spreadsheet works. At fifteen, it starts to fail. Beyond twenty, you're running on goodwill and institutional memory — neither of which appear on a balance sheet, and both of which leave when people do.
What structured data would have changed
If the data from those leases had been extracted, normalized, and queryable from the start, four things would have been materially different:
- Critical date management would have been proactive, not reactive. Instead of calendar reminders set by whoever last touched the file, renewal windows and notice periods would have been tracked centrally — visible to anyone who needed them, regardless of who executed the original deal.
- Negotiation leverage would have been accessible. Every one of those leases contained precedent — what landlords had accepted on TI allowances, free rent periods, restoration carve-outs. That data existed. It was locked in documents rather than a system. In any subsequent negotiation, we were rebuilding from scratch instead of drawing on what we'd already established.
- Portfolio reporting would have taken hours, not days. When leadership needed a consolidated view of upcoming obligations, committed spend, or lease exposure by market, the answer required manually pulling from multiple sources and reconciling them. With structured data, that's a query. Without it, it's a project.
- Transaction approvals would have moved faster, with less friction. Getting internal sign-off on a new site — from finance, legal, and leadership — meant assembling the same information in different formats for different stakeholders, manually, every time. A structured workflow layer would have formalized that process: submissions tracked from site approval through executed lease, with deposit obligations and payment deadlines surfaced to finance at each stage rather than communicated ad hoc.
The tool I couldn't find
I looked for platforms that could do this. Enterprise lease administration systems were built for accounting teams managing ASC 842 compliance — not for operators managing programs. Lighter-weight tools required manual data entry, which meant the data was only as current as the last time someone updated a spreadsheet.
What I needed was a system that treated the executed lease document as the authoritative source. That extracted structure from the document itself. That kept the data current without requiring a dedicated data entry function.
That gap is what UseSuelo is built to close.
The product exists because the problem is real — not because we identified a market opportunity from the outside, but because we lived the operational cost of not having it. If your team is managing more than five active leases and tracking obligations in spreadsheets or shared drives, the question isn't whether the system will fail. It's when, and what it costs when it does.