I really appreciate how Rydoo streamlines our expense workflows for our small e-learning studio, especially when we’re juggling freelance instructor stipends, course production purchases, and travel costs for live virtual and on-location training sessions. I’m Jalen Cartwright, E-Learning Operations & Technology Coordinator at Bay Area Digital Learning Studio. Our team is 11–50 people, and we don’t have a dedicated IT or finance admin, so most of the expense setup, vendor onboarding, and reporting falls to me. Before we switched to Rydoo, we relied on a messy mix of shared spreadsheets and forwarded receipt photos. Our freelance instructors would send expense screenshots over email, part-time content producers logged purchases in separate tabs, and I had to manually sort everything, cross-check receipts against our contract terms, and build reimbursement lists from scratch. It was easy to mix up which expense tied to which learner cohort or course module. Earlier this year, we ran a big professional development cohort with 14 contracted instructors. Half of them submitted receipts late, and I spent three full evenings sorting files, only to realize one instructor’s software subscription reimbursement got attached to the wrong course budget line. That threw off our monthly spend report and created extra back-and-forth with our finance lead.
What works so well for me is the clean receipt capture and flexible approval workflow, paired with solid CSV bulk import tools for our freelance vendor roster. Our instructors often buy stock media assets, video hosting add-ons, and background music licenses to build their course modules, and they can snap a quick photo of their receipt directly in the mobile app. Rydoo’s OCR pulls the merchant, date, and total automatically, so they don’t have to type everything out manually. I set up custom fields tied to every expense entry, so everyone submitting a claim can tag it with the course cohort ID, module phase, and instructor contract reference. That way I can instantly tell if a purchase belongs to our beginner leadership track or our advanced technical workshop, no extra digging required. When we onboard a new batch of instructors ahead of a launch cycle, I run CSV bulk imports to add all their user profiles at once. Back in August, we kicked off three new courses simultaneously, and I imported 27 freelance instructor records in a single upload. I mapped our custom fields for contract expiry dates and approved spending limits, then built policy rules that flag any expense over the pre-agreed budget cap before it hits the approval queue. That catches overspend issues early, before I waste time reviewing claims that don’t match our vendor agreements.
I also love how the approval chain is easy to tweak on the fly. We keep a simple two-step flow: I first review all submissions to confirm the expense lines up with the course budget and contract terms, then our studio lead gives final sign-off for reimbursement. The dashboard gives me a clear view of pending claims, approved spend, and anything stuck waiting for a receipt or extra detail. That’s a huge help when I’m putting together my cross-team operational reports each month. I can filter expenses by course, export the filtered data, and quickly calculate how much we’re spending on instructor tools, production assets, and travel for live sessions. The smart duplicate check is another quiet win; it stops the same receipt from being submitted twice, which used to happen occasionally when our instructors forwarded the same photo to both our shared inbox and the expense form.
For a small e-learning studio without dedicated finance staff, Rydoo hits the sweet spot. It’s not bloated with enterprise accounting features we will never use. It takes the headache out of collecting receipts, tagging spend to our individual course cohorts, and onboarding rotating freelance instructors in bulk. It cuts down the hours I used to spend chasing loose receipt images and untangling messy spreadsheets, leaving me more bandwidth to focus on LMS platform maintenance, learner enrollment tracking, and troubleshooting sync issues across our learning tools. Review collected by and hosted on G2.com.
My biggest pain point is the rigid CSV bulk import system for freelance instructor profiles. Our import spreadsheets always include extra context alongside basic contact information: approved spend caps per course, contract end dates, which cohorts each instructor is assigned to, and notes on eligible expense categories like stock media, video software subscriptions, or travel for in-person workshops. Rydoo’s import validator is extremely strict about extra columns and free-form notes. If my sheet includes any metadata outside its predefined field set, those extra columns get discarded silently, or sometimes the whole row fails to import without a clear error message telling me exactly what broke. Back in August, when I loaded 27 instructor records ahead of three simultaneous course launches, 6 entries failed right away. The only reason was that I’d added a short note column listing which modules each instructor was responsible for. I spent close to an hour stripping out all that useful context, flattening the spreadsheet down to only the mandatory fields, just to get the upload to finish. Once imported, I then had to manually add those cohort and module assignments one by one, which defeats the whole purpose of bulk importing to save time.
The custom field logic and policy rules also lack the conditional flexibility we need. I wanted to build automated policy checks that change based on the instructor or cohort: for example, automatically flagging a claim if an instructor for our beginner leadership course submits a purchase outside their $300 media budget, while allowing higher spending limits for our advanced technical workshop instructors. Basic hard spending limits work, but Rydoo can’t layer the rule to read the cohort tag first and apply different thresholds accordingly. A couple months ago, an instructor on our high-budget technical course submitted a $450 video tool license. Since the policy rule couldn’t distinguish their cohort from our lower-budget programs, the expense got incorrectly flagged for manual review. That created unnecessary back-and-forth. After that, I don’t trust automated policy alerts alone for our varied instructor contracts. Now I manually spot-check every submission against the instructor’s contract and assigned cohort, adding consistent routine work to my plate. Review collected by and hosted on G2.com.
