From Scattered Vendor Records to a Governed Contract Intelligence Portal

At a glance

• Contract, vendor, transaction, and department data unified into one governed, multi-tenant portal
• Role-scoped access giving every user visibility into their own spend, contracts, and renewal deadlines
• Structured workflows for contract requests, cancellations, renewals, and change requests, replacing email coordination entirely

‍

The Portal That Turned Scattered Contracts
_{Into One Source of Truth}

Techsource manages vendor relationships, software contracts, and spend across multiple departments. As the portfolio grew, so did the difficulty of tracking what was active, what was expiring, and what it all cost. The data existed. Contracts were recorded. Transactions were logged. But no interface connected those records to the people responsible for acting on them.

Finance assembled spend summaries by hand. Operations chased renewal deadlines through calendar reminders and email threads. Department leads had no direct visibility into their own vendor activity. The bigger the portfolio grew, the more coordination it took to answer basic questions.

‍

The bigger the portfolio,
_{the more coordination breaks}

Organizations managing large vendor portfolios hit the same wall. Contracts accumulate across procurement tools, spreadsheets, and renewal calendars. Spend data lives in finance systems. Department ownership sits somewhere else entirely. None of it is built to answer the question operations and finance ask most: what do we have, what does it cost, what's expiring, and who owns it?

For Techsource, the data existed. What was missing was a working interface connecting it to the people responsible for acting on it. At scale, that's not an inconvenience; it's a financial risk: missed renewal windows, untracked spend growth, and no department-level visibility.

‍

A usability problem,
_{not a data problem}

Contract and transaction records lived in a backend system, accessible only to whoever maintained it. No department lead could pull their own spend view. No structured process existed for requesting a new contract or flagging a cancellation. No automatic signal fired when a renewal window was closing in.

There was no governed access model either. Sensitive spend data, vendor terms, and contract metadata were either locked away entirely or exposed without meaningful role separation. The gap between the data and the people who needed it wasn't a feature gap. It was structural.

Every system Techsource relied on connected into one portal:

‍

Why the standard answer didn't fit

The instinctive fix is a shared spreadsheet, a renewal calendar, and a request to finance for spend reports as needed. That works for a small portfolio. At scale, it becomes the bottleneck: every question needs a person in the middle, and every renewal depends on someone remembering to check.

Techsource didn't need better spreadsheets. They needed a production application layer with role-scoped access, structured workflows, and automated reminders, built on top of their actual contract data by a team that had designed this kind of operational portal before.

‍

What Orbit built

The architecture runs on one constraint: every user sees exactly what they're responsible for, and every action they need is available directly in the interface, no report request, no chasing someone over email.

• An organization dashboard with real-time active contracts, annual spend, savings, top vendors, spend by department, and upcoming renewals
• An insights workspace with date-range filtering, owner and department filters, spend trend charts, and transaction-level analysis
• A renewals workspace surfacing term end dates, notice deadlines, status, and owner assignments in one place
• Structured request workflows for missing contracts, new vendor additions, cancellations, renewals, and change requests
• Scheduled renewal reminders that run automatically against contract term data, with zero manual intervention
• A portfolio mode that aggregates reporting across the full account structure for multi-entity organizations
• Multi-tenancy built structurally into the access model from day one, not bolted on as a filter

‍

Tech Stack

‍

How the rollout happened

1. Mapped the model first

The full contract and spend data model got mapped before any screen was designed. Role-scoped access was defined across finance, operations, and department leads, and every workflow type the portal needed to handle was agreed upfront.

2. Built the data layer

PostgreSQL with Drizzle ORM and Zod schemas, structured around organizations, users, memberships, departments, vendors, contracts, reminders, attachments, comments, transactions, and auth sessions, with multi-tenancy built into the access model from day one.

3. Connected the integrations

Google OIDC and Microsoft OIDC for authentication, Zapier webhooks and the Integry marketplace for workflow connections, AWS SES and Google Cloud Storage for delivery and file handling.

4. Shipped the portal

The organization dashboard, insights workspace, renewals workspace, admin modules, and workflow request forms went live, scoped correctly for every user role from the first login.

‍

What changed for the team

Before, contract intelligence required manual assembly at every step. Finance requested exports. Operations kept a separate renewal calendar. Department leads had no direct visibility at all.

• Finance pulls spend reports directly, with zero export requests
• Operations sees deadlines, status, and owner assignments in one renewals workspace
• Department leads see their own vendor activity and spend without involving anyone else
• Renewal reminders run on schedule, with no manual intervention
• Workflow requests follow a structured process tied to real records, not email threads

The data was always there. Orbit built the layer that made it usable for every team that needed it.