The programme brief
The supplied programme documents describe a need to bring marketing, reservations, systems and customer experience into one measurable operating model. Enquiries arrived through several channels, and manual follow-ups made progress difficult to see consistently.
What Papi designed and led
The work included CRM pipeline architecture in Zoho Bigin, stage and tagging definitions, ownership rules, follow-up logic, SOPs and training. Website and booking-journey work formed part of the wider programme context.
The portfolio records Outlook communication integration, WhatsApp intake and automation design, together with booking-engine implementation at The Cape Milner. Evaluated tools and proposed workflows are distinguished from deployed components in the source documents.
Method and implementation
The programme applied process-improvement principles and a phased workstream structure across CRM, websites, automation and team enablement. It included process mapping, SOP preparation and pilot testing. Training and adoption were essential parts of the delivery approach.
Outputs and evidence
The personal portfolio documents a CRM and sales-workflow design, training materials, customer-journey illustrations and pilot use. The case material does not provide a complete, independently validated before-and-after commercial results series.
The enduring lesson: a connected system depends on the people and routines that keep it working.
Targets are not results
The original programme material sets out projected improvements in revenue and response compliance. Those projections are not presented as achieved outcomes. The case describes the documented design, delivery approach and lessons from the programme.
Lessons for the next programme
Start with an agreed business problem. Assign clear ownership. Pilot a manageable scope. Make training practical. Build a reporting rhythm that reveals problems early and gives the team a way to improve the process.
