Mental Profit
Private projectI built the first Mental Profit dashboard as a private proof of concept. It takes a therapist profile from invitation and review to two hidden WordPress drafts. A person still checks every important step and decides whether anything gets published.
A therapist profile changes hands several times before publication.
Identity details, professional registrations, biographies, translations, portraits, owner decisions, and WordPress drafts all need to stay aligned. Email and disconnected documents make that process hard to see and easy to misunderstand.
The proof of concept puts those steps in one place. The therapist prepares the profile, the owner reviews it, and WordPress only receives hidden drafts after approval. A person still publishes the final pages manually.
Keep it private while it is being prepared, review it before sending it, and let a person decide when to publish it.
How a profile reaches WordPress without being published.
Invite the therapist
The owner prepares a private profile for one exact Google account.
Prepare the profile
The therapist adds details, compares portrait versions, and reviews both languages.
Review and decide
The owner requests changes or completes the explicit approval checklist.
Create hidden drafts
Only approval sends two linked draft pages to WordPress staging.
I made sure the process stops before publication.
Synthetic data only
The current application and every screenshot use fictional profiles. Real therapist and patient information remain outside the system.
No patient-system connection
The dashboard is separate from James and other patient-record systems.
Owner approval is explicit
The owner checks the translation, portrait, profile content, and team-page position before the process can continue.
WordPress receives drafts
The automation stops at hidden drafts. It does not publish a public therapist page by itself.
What I built for the private workspace.
I connected sign-in, profile details, private portrait versions, editable translations, owner review, and WordPress. The connection can create drafts, but it cannot publish them.
Invite-only Google sign-in
A prepared invitation controls who can enter a private profile workspace.
Structured bilingual content
Facts, professional copy, portraits, and review status stay together.
Translations and portrait options
The tools help prepare the profile, but a person still reviews and approves the result.
WordPress draft connector
Approved information becomes two linked hidden drafts for a person to inspect.
The difficult parts
Privacy changes what I can build
Using real data cannot be treated as the obvious next step. The storage, providers, access rules, and review process all need approval before any small test.
Two languages must stay connected
Shared facts and translated copy need to remain aligned without removing the therapist’s ability to review and edit either version.
Automation must stop visibly
A safe workflow needs a clear end. Here, the end is hidden drafts, not automatic publication.
What I’ve learned from the fictional-data test.
- I need to say plainly what data the tool can and cannot handle.
- Every approval is easier to follow when the responsible person and the current status are visible.
- The automation needs to stop at hidden WordPress drafts.
The full path works with fictional data only.
I have a working Phase 0 proof of concept that shows the full onboarding and approval path with fictional data. It is not approved for real therapist or patient information, and I have not connected it to James.
- I’ll keep the fictional-data version available so the team can review the product and the process.
- The privacy, security, and supplier review must happen before anyone decides to use real data.
- If that work is approved, I’ll define a small therapist test with clear operating rules.