# How Construction One uses Ramp

**75%**: “That cuts Accounts Payable's expense management process down by about 75%, from 40 hours per month to 10 hours per month.”

As published on [ramp.com](https://ramp.com/customers/construction-one). Captured by usedby on 2026-10-07.

- Company: [Construction One](https://www.usedby.ai/companies/construction-one.md)
- Tool: [Ramp](https://www.usedby.ai/tools/ramp.md)
- Teams: Accounts Payable, Finance

## What the story says

Construction One replaced a manual expense process built on individual Google Docs with Ramp's automated expense management. Employees get instant reminders to code expenses, and the finance team uses spend controls to block certain categories and capture spend in real time.

Summary written by usedby from the source page, in English. The figures are those of Ramp and Construction One, not ours.

> "Our AP person would go into 75 different Google docs, make one giant report, turn it into an Excel spreadsheet, and import it into our software," says Chris. This required a time commitment of approximately 10 hours each week, or 40 hours per month.

- **Over $1.4M**: “Over $1.4M saved with cashback and spend controls”
- **30 hours**: “30 hours saved on month-end close”
- **4+ hours**: “Average 4+ hours back per month with accounting automations”

> The whole process was smooth. We were able to customize everything, and Ramp has been able to capture all of our needs.
>
> Chris Moberger, Controller, Construction One

## What usedby checked

We compared the story with its live page on 2026-10-07.

- Checked: the figure 75% is printed word for word on the page, near the name of Construction One.
- Checked: the passage quoted above is copied word for word from the page, near the name of Construction One.
- Checked: Construction One uses Ramp. Confirmed line. Latest check across sources: 2026-10-07.
- Not checked: the result itself. We quote it; we did not measure it.

---
Source: https://www.usedby.ai/case-studies/construction-one-ramp · How we check: https://www.usedby.ai/methodology