2024 & 2025 Ramp Community Product Brainstorm

General
, , , ,
1

Hey everyone, I’m Dexter Bosley and I’m part of the product team working on our core spend management product. When I’m not refining expense management workflows, you’ll probably find me skiing with friends or attending an amateur comedy show. Looking forward to learning and sharing with the Ramp community!

We’re looking to gauge what types of features you would like to see Ramp build in 2024 and 2025. I’ve listed out some of the things we’re thinking about, and we’d love to hear which of these would be most helpful for you and your business. If you want something else entirely, vote ‘Other’ and drop a comment.

Many thanks in advance!

Ramp’s Product Roadmap Brainstorm
  • Employee receipt affidavit when receipt is lost (e.g., “I swear this expense…”)
  • Admin visible flags (e.g., hidden from cardholders)
  • Custom notification for flags, alerts, and reminders (e.g., edit your reminder emails)
  • Custom transaction tags (e.g., ‘client dinner’)
  • Other
0 voters
1 Like
2

I picked other: I would like to see Bill and Card vendors merged and the ability to rename the vendor regardless of source. Having multiple vendors with the same name is just as big of a headache for us as having the same vendor with slight variations in their name. Search is also broken on some pages when Bill and Card vendors have the same name.

5 Likes
6

Here is my wishlist:

Improve Trip Handling and coding for users: Add defaults for accouting fields to a Trip for future transactions - #3 by RHOU)

  • Allowing custom fields/dimensions on Trips to further classify trips (e.g. a dropdown for Customer Visit, Internal Training Visit)
  • These fields/dimensions could then also be configured to automatically be pushed down to the transaction.
  • User Example:
    o I create a trip for a 3 day visit to Orlando for a Tradeshow.
    o I go into the Trip and configure all accounting codes and dimensions for the trip. The fields that will vary per transaction, I will leave empty
    o When a new transaction gets linked to the trip, the system will check the coding of the parent trip and if there is already a field filled in on the trip level, it will automatically copy that value down to the new transaction

Improving the UCSV export to add:

  • Adding ability to add linked trip fields (trip name, start date, end date, etc.) to the transaction export
  • Adding ability to add Attendee Names (e.g. for meals, etc.) so that users don’t have to write those in the Memo field in addition. Right now the info cannot be exported.
1 Like