Skip to main content
hendeaux

Post Grad Project

David uses the CRM for his coaching work. The website and storefront are in final review; the course shown here is a local preview, and the client workspace is a prototype.

Story narration

Loading narration…

I built a set of tools for David’s coaching business, Post Grad Project, to organize client information, process coaching calls, and help him prepare follow-ups. The work includes a website and storefront, a streamlined CRM, a course site, a client workspace, and a video editor. David works with the CRM by talking to Claude as well as using its interface in Claude Desktop’s in-app browser.

On the website, someone looking for help with an internship can download David’s email templates by filling out a form. They explain what they are working toward and where they are getting stuck. Those answers go into the CRM and provide the source material for a more informed follow-up email. David can see why the person came to him and review a draft without having to piece together their situation from several places. The point is to give him more time for the conversation itself.

Maya’s request includes her goal and the question she needs help with. Client details in these examples are fictional.
Maya’s goal and question stay beside her conversation history, with a way to prepare a reply from the relevant request.

I also built a site for David’s course, with video hosted through Mux and the learning materials alongside each lesson. Someone learning how to find people with relevant experience can watch David explain the process, work through an exercise, and download a tracker to record their first contact. The lesson and its materials stay together, so they can return to them between coaching sessions.

The course keeps the video, lesson navigation and exercise together. This capture shows a local preview with sample lesson media.

The client workspace brings a goal, saved contacts, and next actions into one place. In the prototype shown here, a client can keep notes about someone they want to contact and choose when to follow up. Sharing progress with David is an explicit choice: the proposed update includes their goal and request for help, while individual contact details and private notes stay in the workspace.

Saved contacts and next actions in the workspace prototype. Sharing progress is optional.

After a coaching call, the transcript automatically becomes context for the AI, which generates a suggested follow-up email in David’s connected Gmail account. He can open the draft directly from the CRM to review, edit, and send it. The same material can inform social content. I built Video Desk so David can watch a rendered clip and request a change at a particular moment. Each request stays attached to the version he reviewed. He can return to that moment, compare edits, and decide whether the clip is ready. The review keeps his feedback beside the work it refers to.

Feedback stays beside the frame it refers to. This example uses David’s public teaching clip; the cut is awaiting review, with one check passed and four pending.

In Video Desk, a feedback request keeps the video version and timestamp from when the reviewer starts writing. A request started at 0:12 stays there even if the reviewer moves ahead while writing. A failed save keeps the draft available to retry. In local checks, saved requests kept their original version and timestamp after a page reload.