https://github.com/param302/ripplereach
https://github.com/param302/ripplereach
Last synced: 8 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/param302/ripplereach
- Owner: Param302
- Created: 2024-11-08T15:58:44.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2024-11-13T04:51:23.000Z (over 1 year ago)
- Last Synced: 2025-01-14T13:26:51.113Z (over 1 year ago)
- Language: TypeScript
- Size: 317 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# RippleReach
Cold Email & Reply things
2 API for each email GPT 4o
1st approach to write cold email, include portfolio, if suggest, based on client details
2nd write cold email, based on the agency info, write cold email
email validation 3.5-turbo
company desc 3.5
Reply will contain conversation history
--
+ in the documentation can you write in short bullet points all the touch points to code new modules in the emails? For example right now we have a portfolio module that takes the drive assets and inserts when required (you'd have already done this).
Similarly in future, if I need to code a proposal module that writes and sends a proposal (as a drive link) then what do I need to do...as in what all touch points in code are important to cross check / update. I plan to include two new modules after you give the code: Proposal module + contracts module. Then I'll just turn on the system and go to peaceful sleep.