Case studies

Real automations, explained simply

Some of our client work is under contract and can't be named, so the examples below are anonymised or clearly marked as demos.

Get the free guideBook a free 15-minute call (opens in a new tab)

Recruitmentmonday.com + MakeClient not named (under contract)

Recruitment: hiring and onboarding

The problem

We know recruitment from the inside. Before founding RDI, Phil built two recruitment agencies, each to an annual turnover of £1.4 million, so we know how much of a recruiter's week goes on admin.

For this client, each LinkedIn job post drew around 200 applicants, most of them unsuitable. Sifting and emailing them all was done by hand.

What we built

  1. An application form (basic details, location, expected salary, CV and cover letter) feeding straight into monday.com.
  2. An automatic acknowledgement email to every applicant.
  3. The recruiter clicks once to reject or progress. Rejected applicants are politely declined and their data deleted.
  4. Shortlisted candidates go to the line manager for a simple yes or no.
  5. Candidates book their own first interview from a calendar invite, and monday updates when they accept.
  6. A thank-you after the interview, then a rejection or a second-interview booking, run the same way.
  7. An offer letter with the agreed salary, sent to sign and return.

Mapped next (designed, not yet finished)

Full onboarding to day one. This covers collecting information and documents and filing them in the right Google Drive folders; first-day details sent 7 days before (line manager, who meets them, start time); one click on arrival to create their company email and Drive; and an end-of-day-one welcome pack (who does what, who to call if sick).

Recruitment, from application to signed offerApplicants fill in one form that feeds monday.com and sends an acknowledgement; the recruiter progresses or declines in one click, the line manager says yes or no, candidates book their own interviews and the offer letter goes out to sign. Onboarding to day one is mapped next.Before: by handEvery applicant handled by hand~200 applicants per postSifted and emailed one byoneInterviews arranged byemailOffer letters typed upAfter: runs on its ownApplicationformInto monday+ thank-youemailmonday.com + MakeOne-clickdecline orprogressLinemanager yesor noCandidatebooksinterviewThank-you,then nextstepOfferletter tosignNext:onboardingto day oneDotted = mapped next, not yet finished
Recruitment, from application to signed offerApplicants fill in one form that feeds monday.com and sends an acknowledgement; the recruiter progresses or declines in one click, the line manager says yes or no, candidates book their own interviews and the offer letter goes out to sign. Onboarding to day one is mapped next.Before: by handEvery applicant handled by hand~200 applicants per post → Sifted andemailed one by one → Interviews arrangedby email → Offer letters typed upAfter: runs on its ownApplication formInto monday + thank-youemail (monday.com +Make)One-click decline orprogressLine manager yes or noCandidate booksinterviewThank-you, then nextstepOffer letter to signNext: onboarding to dayoneDotted = mapped next, not yet finished
Applicants fill in one form that feeds monday.com and sends an acknowledgement; the recruiter progresses or declines in one click, the line manager says yes or no, candidates book their own interviews and the offer letter goes out to sign. Onboarding to day one is mapped next.

The result

Every applicant gets a reply, the recruiter decides with one click, and interviews and offer letters go out without anyone typing the same email again.

Get the free guideBook a free 15-minute call (opens in a new tab)

Real buildmonday.comGmail

How RDI runs itself

The problem

After every discovery call we had to work out the saving, price the job, write a proposal from scratch and remember to follow up.

What we built

Our own call log is a monday.com board that works out each prospect's monthly saving, a suggested price and a care-plan figure automatically. One script turns a call into a branded three-page proposal, and a follow-up email draft is created automatically, ready to check and send.

How RDI runs itselfEach discovery call is logged on a monday.com board that works out the saving, a suggested price and a care-plan figure; a follow-up email draft is created, ready to check and send, and a branded three-page proposal is generated.Before: by handEvery call: a proposal from scratchCall notes in a notebookSaving and price by handProposal from scratchRemember to follow upAfter: runs on its ownCall logged on theboardmonday.comSaving, price and careplan worked outFollow-up draft tocheck and sendGmailBranded three-pageproposal
How RDI runs itselfEach discovery call is logged on a monday.com board that works out the saving, a suggested price and a care-plan figure; a follow-up email draft is created, ready to check and send, and a branded three-page proposal is generated.Before: by handEvery call: a proposal from scratchCall notes in a notebook → Saving andprice by hand → Proposal from scratch →Remember to follow upAfter: runs on its ownCall logged on the board(monday.com)Saving, price and careplan worked outFollow-up draft to checkand send (Gmail)Branded three-pageproposal
Each discovery call is logged on a monday.com board that works out the saving, a suggested price and a care-plan figure; a follow-up email draft is created, ready to check and send, and a branded three-page proposal is generated.

The result

We use the same kind of automation we build for clients.

DemoBuilt to show how it works, not a client

Removals: from enquiry to booked job

The problem

For a removals firm, every enquiry means working out a price, emailing a quote, chasing a date and writing it in the diary.

What we built

Website form → quote calculated and emailed → customer picks a date → job added to the calendar → reminder the day before → review request after.

Watch the 58-second demo of this example (sample data for Demo Removals Ltd).

Removals, from enquiry to booked job (demo) (demo)In this demo, a website form becomes a quote worked out and emailed, the customer picks a date, the job goes into the calendar, a reminder goes out the day before and a review request after.DEMOBefore: by hande.g. ≈ 6 hours a week, by handEnquiry by emailPrice worked out by handDiary updated by handReminder and reviewforgottenAfter: runs on its ownWebsite formQuotecalculated andemailedCustomer picksa dateJob added tothe calendarReminder theday beforeReview requestafter
Removals, from enquiry to booked job (demo) (demo)In this demo, a website form becomes a quote worked out and emailed, the customer picks a date, the job goes into the calendar, a reminder goes out the day before and a review request after.Before: by hande.g. ≈ 6 hours a week, by handEnquiry by email → Price worked out byhand → Diary updated by hand → Reminderand review forgottenAfter: runs on its ownWebsite formQuote calculated andemailedCustomer picks a dateJob added to thecalendarReminder the day beforeReview request afterDEMO
Demo: built to show how it works. In this demo, a website form becomes a quote worked out and emailed, the customer picks a date, the job goes into the calendar, a reminder goes out the day before and a review request after.

The result

No copying, no forgotten quotes, and every customer gets the same quick service.

Demo build: no client results are claimed.

DemoBuilt to show how it works, not a client

Accountant: document chaser

The problem

Every month, clients have to be chased for receipts and documents, one email at a time.

What we built

Client list → monthly request email → reminders every few days → stops when the documents arrive → files are saved to the right folder.

How invoice and document chasing runs on its ownInstead of checking who hasn't paid and writing reminders by hand, polite reminders go out on day 3 and day 7 and stop by themselves when the reply or payment arrives.DEMOBefore: by hande.g. ≈ 3 hours a week, by handCheck who hasn't paidWrite the reminderRemember to chase againRepeatAfter: runs on its ownInvoice due orrequest sentPolite reminder onday 3Second reminder onday 7Reply or paymentspottedPaid: chasingstops and it'slogged
How invoice and document chasing runs on its ownInstead of checking who hasn't paid and writing reminders by hand, polite reminders go out on day 3 and day 7 and stop by themselves when the reply or payment arrives.Before: by hande.g. ≈ 3 hours a week, by handCheck who hasn't paid → Write thereminder → Remember to chase again →RepeatAfter: runs on its ownInvoice due or requestsentPolite reminder on day 3Second reminder on day 7Reply or payment spottedPaid: chasing stops andit's loggedDEMO
Demo: built to show how it works. Instead of checking who hasn't paid and writing reminders by hand, polite reminders go out on day 3 and day 7 and stop by themselves when the reply or payment arrives.

The result

Documents arrive without anyone writing a reminder.

Demo build: no client results are claimed.

RDI Automation

What's the one job you'd never do again?

Start with our free 12-page guide: a checklist to spot the manual tasks costing you time. Or book a free 15-minute call for an honest view on whether a job can be automated.

Get the free guideBook a free 15-minute call (opens in a new tab)

Get the free guide