Replacing Paper-Based Lease Tracking with a Custom NetSuite App

The challenge

Towerstream operated wireless internet service from 200-300+ leased locations across the US — rooftops, towers, building installations. Each one had its own contract terms, escalation clauses, renewal options, and payment schedule.

All of it lived on paper.

Jackie, the lease manager, ran the entire portfolio out of physical folders. There was no central system to query. Looking up the renewal date on any specific lease meant finding the right folder, digging through the documents, and manually cross-referencing. Management complained constantly about how long basic operations took. The bottleneck wasn't dramatic — no single lease was lost, no specific payment was missed — but the cost was constant friction, scaling badly with every new site.

What we considered

The obvious shortcut would have been to shoehorn lease data onto an existing NetSuite record — a Customer or Vendor with custom fields. Less work, faster to ship.

I built it as a custom Lease record instead.

Leases have their own lifecycle: contract terms, escalation logic, renewal cycles, payment schedules, attached documents. Stuffing all of that onto Customer records would have polluted those records with attributes that didn't belong, made reporting awkward, and turned the eventual data model into a maintenance liability when Towerstream's portfolio grew. The custom record was more work upfront but solved all of that at the architecture level.

That's the kind of judgment call that doesn't show up in a feature list. The shortcut would have shipped faster and aged worse.

What we built

• A custom NetSuite Lease record capturing the full lifecycle — location, contract terms, escalation clauses, renewal options, payment cycles, attached lease documents
• Automated rent payment generation on the correct cycle per lease, removing recurring manual AP work
• Approval workflows for new leases and renewals, routed to the right director or VP, with full audit trail
• Expiration alerts surfaced in the NetSuite dashboard so renewals couldn't fall through the cracks
• Architected hand-in-hand with Jackie — every workflow reflected how she actually managed the portfolio day to day

The result

The lease portfolio moved from a physical filing room to a queryable system. The class of errors that comes from re-keying lease data was eliminated. Approvals that used to require physical signatures and folder routing now happened via email-driven workflows. Jackie's time shifted from administrative tracking to actually managing the portfolio strategically.

"I love Jaime — he made it super easy to deal with leases with the custom record he created alongside all the automation." — Jackie, Lease Manager, Towerstream

Why it worked

The custom Lease record was the right architectural call. Years later, when Towerstream's business changed, that data model still held up. If we had shoved everything onto Customer records to ship faster, the system would have collapsed under its own complexity inside 18 months.

The lesson generalizes: the right NetSuite customization isn't always the fastest one to build. Knowing when to spend the extra week designing the data model correctly — and when not to — is the part of the work that doesn't get cheaper as AI accelerates everything else.