Build a Claude AI-Powered Referral Partner, Application Automation & CRM System
Budget: $30 – $250 USD
## Project Overview
We are looking for an experienced Claude AI automation specialist to build a scalable AI-powered system for **GetAdvisor**, an international education and Training & Development platform.
The system should automate four core functions:
1. Find and recruit new referral partners.
2. Onboard and continuously engage referral partners.
3. Submit student applications from GetAdvisor into external education-provider portals using Claude.
4. Record and monitor the entire operation through one centralized CRM with dashboards and statistics.
This is not a chatbot project. We require a complete AI-powered business workflow with minimal manual intervention.
## Module 1 – Referral Partner Sourcing
Claude should:
* Search the public web based on criteria we define, including countries, professions, industries, and target profiles.
* Find suitable potential referral partners without requiring us to provide specific websites.
* Collect publicly available professional or business email addresses.
* Assess and score each lead.
* Explain why the lead is relevant.
* Avoid duplicate leads.
* Exclude existing partners.
* Never invent or guess email addresses.
* Save all qualified leads directly into the CRM.
The sourcing criteria must be editable without rebuilding the system.
## Module 2 – Automated Outreach
Claude should:
* Generate personalized invitation emails.
* Send invitations through our connected email account.
* Personalize messages based on the lead’s background, country, profession, organization, and audience.
* Send automatic follow-ups.
* Stop contacting leads who decline or unsubscribe.
* Track all communication inside the CRM.
The CRM should show each prospect’s current stage, such as:
* New lead
* Qualified
* Contacted
* Replied
* Interested
* Registration started
* Contract signed
* Onboarded
* Rejected
* Unsubscribed
## Module 3 – Email Reply Handling
Claude should automatically:
* Read incoming emails.
* Categorize replies.
* Answer routine questions.
* Explain the referral opportunity.
* Send registration and contract links.
* Follow up until registration is completed.
* Escalate legal, contractual, commission-related, complaint, or unusual requests for manual review.
* Save all emails, responses, classifications, and actions in the CRM.
## Module 4 – Referral Partner Onboarding
Our contracts and portal tutorials are already automated.
After a partner registers, Claude should:
* Send a welcome email.
* Send portal login instructions and tutorials.
* Explain the referral and commission process.
* Explain how to refer students.
* Answer common onboarding questions.
* Identify incomplete onboarding.
* Send reminders.
* Confirm when onboarding is complete.
* Update the partner’s status in the CRM.
## Module 5 – Referral Partner Engagement
Claude should act as an ongoing Referral Partner Engagement Manager.
It should keep partners active and motivated by sending relevant communications about:
* New universities and providers
* New programs
* Scholarships
* Upcoming intakes
* Application deadlines
* Guaranteed progression opportunities
* Training and professional certification opportunities
* Marketing campaigns
* Promotional materials
* Success stories
* Referral tips
* High-demand programs
* Important dates
* Partner achievements
* Reactivation campaigns
Communication should be personalized and segmented based on:
* Country
* Partner interests
* Student audience
* Previous referrals
* Programs promoted
* Activity level
* Referral performance
* Preferred language where available
Claude should identify and contact:
* Partners who registered but never logged in
* Partners who logged in but never referred a student
* Partners with incomplete referrals
* Previously active partners who became inactive
* High-performing partners
* Partners with students requiring follow-up
All engagement activity should be recorded in the CRM.
## Module 6 – Student Application Automation
Students submit their applications and documents through the GetAdvisor portal.
Claude should then:
* Access the submitted application.
* Read student information and uploaded documents.
* Detect missing, contradictory, or unclear information.
* Determine the correct external provider portal.
* Open the portal.
* Log in securely.
* Complete the application form.
* Upload the correct documents.
* Review the information.
* Submit the application.
* Record the external application reference number.
* Update the application record in GetAdvisor and the CRM.
There is no API available for the external portals. The solution must therefore use **Claude’s browser-use or computer-use capabilities**.
Initial portals include:
* Study Group Agent Portal
* INTO Agent Portal
The system should allow additional provider portals to be added later.
Claude must never invent, assume, or change important student information. Missing or uncertain information must be flagged for manual review.
## Module 7 – Application Status Monitoring
Where technically possible, Claude should access external portals and monitor applications for updates such as:
* Application received
* Under review
* Additional documents required
* Conditional offer
* Unconditional offer
* Interview required
* Deposit required
* Application rejected
* Deadline approaching
* Other outstanding actions
Claude should update the CRM and notify the relevant student, referral partner, or administrator using approved templates.
## Module 8 – Central CRM
The CRM must be the central control panel for the entire system.
We should be able to monitor:
### Lead Recruitment
* Leads sourced
* Qualified leads
* Emails found
* Invitations sent
* Delivered and bounced emails
* Replies
* Interested prospects
* Registrations
* Contracts signed
* Partners onboarded
* Conversion rates
* Unsubscribes
### Referral Partner Performance
* Total partners
* Active and inactive partners
* New referrals
* Incomplete referrals
* Applications submitted
* Successful enrolments
* Partner conversion rates
* High-performing partners
* Inactive partners requiring follow-up
* Communications sent
* Engagement campaign performance
### Student Applications
* New applications
* Missing documents
* Applications ready for submission
* Applications submitted
* Applications awaiting review
* Failed submissions
* External application references
* Current application status
* Offers received
* Outstanding actions
* Errors requiring attention
The CRM should allow us to:
* Search and filter records.
* View the complete history of each lead, partner, student, and application.
* View emails and engagement history.
* Assign tasks or cases for manual review.
* Change pipeline stages.
* Export reports.
* View dashboards and statistics.
* Pause or restart workflows.
* Identify automation errors.
* Avoid duplicate leads, partners, students, and applications.
The freelancer may recommend a suitable CRM, but it must integrate properly with Claude, GetAdvisor, email, and all workflows.
## System Requirements
The solution must:
* Be powered primarily by Claude.
* Require minimal manual intervention.
* Be modular and scalable.
* Use the CRM as the central monitoring system.
* Be manageable by a non-developer.
* Include secure credential handling.
* Include activity logs and error logs.
* Include manual-review queues.
* Allow prompts, sourcing criteria, countries, target profiles, templates, follow-up schedules, engagement rules, and portal mappings to be edited.
* Allow workflows to be paused or stopped.
* Avoid duplicate communications and application submissions.
## Deliverables
The freelancer must provide:
* Complete Claude Project setup.
* Referral-partner sourcing automation.
* Personalized outreach automation.
* Email reply-handling automation.
* Partner onboarding and engagement automation.
* Claude-based browser application submission.
* Application-status monitoring where technically possible.
* Fully integrated CRM.
* CRM pipelines, dashboards, reports, and statistics.
* GetAdvisor portal integration.
* Secure email integration.
* Error handling and manual-review queues.
* Workflow diagrams.
* Technical and non-technical documentation.
* Complete handover.
* Screen-recorded tutorials.
The tutorials must explain how to:
* Change sourcing criteria and target countries.
* Edit prompts and email templates.
* Change follow-up and engagement rules.
* Add universities and providers.
* Add a new external portal.
* Change portal field mappings.
* Review failed applications.
* Monitor leads, partners, and students through the CRM.
* Edit CRM pipelines and dashboards.
* View reports and statistics.
* Pause, restart, and troubleshoot workflows.
## Required Experience
Please apply only if you have demonstrable experience with:
* Claude AI and Claude Projects
* Claude browser/computer use
* AI agents
* Web research automation
* Email automation
* Browser-based form submission
* CRM implementation and integration
* Workflow automation
* Document processing
* Prompt engineering
* Secure credential management
Please include examples of similar systems you have built.
## Important
We are not looking for a basic chatbot or a one-time web-scraping project.
We require a Claude-powered system that functions as a virtual Referral Partnership Manager and Admissions Operations Assistant, while allowing us to monitor the complete operation, performance, statistics, applications, communications, and exceptions from one centralized CRM.
We are looking for an experienced Claude AI automation specialist to build a scalable AI-powered system for **GetAdvisor**, an international education and Training & Development platform.
The system should automate four core functions:
1. Find and recruit new referral partners.
2. Onboard and continuously engage referral partners.
3. Submit student applications from GetAdvisor into external education-provider portals using Claude.
4. Record and monitor the entire operation through one centralized CRM with dashboards and statistics.
This is not a chatbot project. We require a complete AI-powered business workflow with minimal manual intervention.
## Module 1 – Referral Partner Sourcing
Claude should:
* Search the public web based on criteria we define, including countries, professions, industries, and target profiles.
* Find suitable potential referral partners without requiring us to provide specific websites.
* Collect publicly available professional or business email addresses.
* Assess and score each lead.
* Explain why the lead is relevant.
* Avoid duplicate leads.
* Exclude existing partners.
* Never invent or guess email addresses.
* Save all qualified leads directly into the CRM.
The sourcing criteria must be editable without rebuilding the system.
## Module 2 – Automated Outreach
Claude should:
* Generate personalized invitation emails.
* Send invitations through our connected email account.
* Personalize messages based on the lead’s background, country, profession, organization, and audience.
* Send automatic follow-ups.
* Stop contacting leads who decline or unsubscribe.
* Track all communication inside the CRM.
The CRM should show each prospect’s current stage, such as:
* New lead
* Qualified
* Contacted
* Replied
* Interested
* Registration started
* Contract signed
* Onboarded
* Rejected
* Unsubscribed
## Module 3 – Email Reply Handling
Claude should automatically:
* Read incoming emails.
* Categorize replies.
* Answer routine questions.
* Explain the referral opportunity.
* Send registration and contract links.
* Follow up until registration is completed.
* Escalate legal, contractual, commission-related, complaint, or unusual requests for manual review.
* Save all emails, responses, classifications, and actions in the CRM.
## Module 4 – Referral Partner Onboarding
Our contracts and portal tutorials are already automated.
After a partner registers, Claude should:
* Send a welcome email.
* Send portal login instructions and tutorials.
* Explain the referral and commission process.
* Explain how to refer students.
* Answer common onboarding questions.
* Identify incomplete onboarding.
* Send reminders.
* Confirm when onboarding is complete.
* Update the partner’s status in the CRM.
## Module 5 – Referral Partner Engagement
Claude should act as an ongoing Referral Partner Engagement Manager.
It should keep partners active and motivated by sending relevant communications about:
* New universities and providers
* New programs
* Scholarships
* Upcoming intakes
* Application deadlines
* Guaranteed progression opportunities
* Training and professional certification opportunities
* Marketing campaigns
* Promotional materials
* Success stories
* Referral tips
* High-demand programs
* Important dates
* Partner achievements
* Reactivation campaigns
Communication should be personalized and segmented based on:
* Country
* Partner interests
* Student audience
* Previous referrals
* Programs promoted
* Activity level
* Referral performance
* Preferred language where available
Claude should identify and contact:
* Partners who registered but never logged in
* Partners who logged in but never referred a student
* Partners with incomplete referrals
* Previously active partners who became inactive
* High-performing partners
* Partners with students requiring follow-up
All engagement activity should be recorded in the CRM.
## Module 6 – Student Application Automation
Students submit their applications and documents through the GetAdvisor portal.
Claude should then:
* Access the submitted application.
* Read student information and uploaded documents.
* Detect missing, contradictory, or unclear information.
* Determine the correct external provider portal.
* Open the portal.
* Log in securely.
* Complete the application form.
* Upload the correct documents.
* Review the information.
* Submit the application.
* Record the external application reference number.
* Update the application record in GetAdvisor and the CRM.
There is no API available for the external portals. The solution must therefore use **Claude’s browser-use or computer-use capabilities**.
Initial portals include:
* Study Group Agent Portal
* INTO Agent Portal
The system should allow additional provider portals to be added later.
Claude must never invent, assume, or change important student information. Missing or uncertain information must be flagged for manual review.
## Module 7 – Application Status Monitoring
Where technically possible, Claude should access external portals and monitor applications for updates such as:
* Application received
* Under review
* Additional documents required
* Conditional offer
* Unconditional offer
* Interview required
* Deposit required
* Application rejected
* Deadline approaching
* Other outstanding actions
Claude should update the CRM and notify the relevant student, referral partner, or administrator using approved templates.
## Module 8 – Central CRM
The CRM must be the central control panel for the entire system.
We should be able to monitor:
### Lead Recruitment
* Leads sourced
* Qualified leads
* Emails found
* Invitations sent
* Delivered and bounced emails
* Replies
* Interested prospects
* Registrations
* Contracts signed
* Partners onboarded
* Conversion rates
* Unsubscribes
### Referral Partner Performance
* Total partners
* Active and inactive partners
* New referrals
* Incomplete referrals
* Applications submitted
* Successful enrolments
* Partner conversion rates
* High-performing partners
* Inactive partners requiring follow-up
* Communications sent
* Engagement campaign performance
### Student Applications
* New applications
* Missing documents
* Applications ready for submission
* Applications submitted
* Applications awaiting review
* Failed submissions
* External application references
* Current application status
* Offers received
* Outstanding actions
* Errors requiring attention
The CRM should allow us to:
* Search and filter records.
* View the complete history of each lead, partner, student, and application.
* View emails and engagement history.
* Assign tasks or cases for manual review.
* Change pipeline stages.
* Export reports.
* View dashboards and statistics.
* Pause or restart workflows.
* Identify automation errors.
* Avoid duplicate leads, partners, students, and applications.
The freelancer may recommend a suitable CRM, but it must integrate properly with Claude, GetAdvisor, email, and all workflows.
## System Requirements
The solution must:
* Be powered primarily by Claude.
* Require minimal manual intervention.
* Be modular and scalable.
* Use the CRM as the central monitoring system.
* Be manageable by a non-developer.
* Include secure credential handling.
* Include activity logs and error logs.
* Include manual-review queues.
* Allow prompts, sourcing criteria, countries, target profiles, templates, follow-up schedules, engagement rules, and portal mappings to be edited.
* Allow workflows to be paused or stopped.
* Avoid duplicate communications and application submissions.
## Deliverables
The freelancer must provide:
* Complete Claude Project setup.
* Referral-partner sourcing automation.
* Personalized outreach automation.
* Email reply-handling automation.
* Partner onboarding and engagement automation.
* Claude-based browser application submission.
* Application-status monitoring where technically possible.
* Fully integrated CRM.
* CRM pipelines, dashboards, reports, and statistics.
* GetAdvisor portal integration.
* Secure email integration.
* Error handling and manual-review queues.
* Workflow diagrams.
* Technical and non-technical documentation.
* Complete handover.
* Screen-recorded tutorials.
The tutorials must explain how to:
* Change sourcing criteria and target countries.
* Edit prompts and email templates.
* Change follow-up and engagement rules.
* Add universities and providers.
* Add a new external portal.
* Change portal field mappings.
* Review failed applications.
* Monitor leads, partners, and students through the CRM.
* Edit CRM pipelines and dashboards.
* View reports and statistics.
* Pause, restart, and troubleshoot workflows.
## Required Experience
Please apply only if you have demonstrable experience with:
* Claude AI and Claude Projects
* Claude browser/computer use
* AI agents
* Web research automation
* Email automation
* Browser-based form submission
* CRM implementation and integration
* Workflow automation
* Document processing
* Prompt engineering
* Secure credential management
Please include examples of similar systems you have built.
## Important
We are not looking for a basic chatbot or a one-time web-scraping project.
We require a Claude-powered system that functions as a virtual Referral Partnership Manager and Admissions Operations Assistant, while allowing us to monitor the complete operation, performance, statistics, applications, communications, and exceptions from one centralized CRM.