Rampart helps large companies reduce procurement costs by leveraging smarter purchasing. To find savings, Rampart needs to analyze the invoices and purchase orders its clients receive from hundreds of vendors.
That sounds simple until you see where the data lives.
Invoices and purchase orders are usually locked inside vendor portals. Each portal is different. Many sit behind logins, anti-bot systems, or 2FA. And because Rampart uses that pricing data to negotiate better rates, or find more cost-effective alternatives, the vendors behind those portals are not always excited to make the data easy to retrieve.
"We use Deck basically to go and fetch thousands of invoices from hundreds of vendors behind logins that usually used to be manual and extremely difficult to get behind. If we can't surpass the anti-bot, it's game over, we just can't run the business."
Samuel Poirier, Rampart
Deck gave Rampart a way through, by operating portals just like a human does: logging in, navigating screens, fetching documents, and reaching workflows regular LLM agents can't complete.
For Rampart, that means Deck can operate behind vendor logins and fetch the invoices that power the business.
Critical data behind locked doors
Before Deck, Rampart had a bottleneck at the worst possible layer: the data that fueled the business was private, fragmented, and difficult to access.
"They'd have all kinds of anti-bot or 2FAs that made it very difficult or extremely manual to go and pull invoices."
Samuel Poirier, Rampart
Manual work was not an option. Rampart works with large customers, but not in a way that justifies putting humans behind every login.
"Our annual contract value is high, but it's not high enough for us to deploy humans to actually do this for every client. And we get flooded with clients on a daily basis."
Samuel Poirier, Rampart
Engineering was the other option. But even with modern LLM agent stacks, that meant Rampart still owned the hard stuff: auth flows, credential management, anti-bot countermeasures, scraper maintenance, and one-off fixes every time a vendor portal changed.
Claude can drive a browser. That part's solved. What Rampart needed was production infrastructure for workflows that live behind logins and actively resist automation — the kind of thing every company ends up building themselves, from scratch, around the model.
"If we had to do it the old way, it would have taken too much of our engineering bandwidth to handle as many integrations."
Samuel Poirier, Rampart
Shipping integrations at the speed Rampart needed
Rampart's first real proof point came fast.
Leveraging Deck's agents, one Rampart developer shipped around 20 integrations in roughly half a day.
"One of our devs shipped it in like half a day, 20 integrations. I was like, what the hell is going on here? There must be an error."
Samuel Poirier, Rampart
That moment changed the team's understanding of what was possible. Deck was not just a faster way to build scrapers. It was infrastructure for a workflow Rampart did not want to own: getting into private portals, navigating them, and retrieving documents at scale.
Rampart also avoided an estimated 2–3 FTEs of engineering effort that would have gone into portal automation, auth, and anti-bot work.
"It's a quick way to get access to private behind-login data for vendors, for logins, or for providers that don't otherwise have an easy-to-use API or don't want you to use an API."
Samuel Poirier, Rampart
The Deck difference
Access where LLMs hit locked doors
Rampart's workflow fails if it cannot get past anti-bot systems. That makes Deck's ability to operate through hostile login environments one of the most important parts of the value proposition.
"What you all have built is extremely impressive, and it's super valuable to us."
Samuel Poirier, Rampart
Browser navigation across portals no API can touch
The rest of the value comes from Deck's ability to operate software like a human: finding the right pages, navigating vendor portals, and fetching invoices across a large, fragmented vendor base.
Engineering focus
Deck lets Rampart avoid building deep internal expertise in anti-bot and portal automation. Instead, engineering can stay focused on the strategic parts of the business.
"We don't want to become the best at anti-bot. With Deck, we can kind of turn a blind eye and focus on building more strategic things for the business."
Samuel Poirier, Rampart