Make the handoff visible
Review selected administrative details, consultation requests, scheduling conflicts, callbacks and due tasks. See missing information without receiving unrestricted clinical notes or images.
PLEASANTWORKS PRACTICE APP
Your practice.
Beyond the appointment.
A dedicated, practice-branded client experience for preparation, communication and continuity—connected to a separate workspace for the people doing the work.
BROWSER PROTOTYPE · COMPLETE PRACTICE PRODUCT IN DEVELOPMENT
01 / THE CLIENT EXPERIENCE
A place to return.
A next step to understand.
The app is intended to make the relationship useful between visits, not merely put a logo on a chat screen. Your selected journey determines the fields, content and handoffs.
- 01
Understand the practice
Browse approved service and program information. Administrative AI answers are a selected future workflow, grounded in practice-approved sources.
- 02
Prepare for a visit
Share goals, selected intake and relevant permissions. Preserve original answers, even when AI proposes a structured summary for staff.
- 03
Provide the right source
Where the selected service needs imagery, use authorized capture and quality review. Missing provenance remains unknown; staff can request a retake.
- 04
Discuss and confirm
Use a verified booking handoff and clear status. Only the source calendar confirms an appointment; an illustration or client preference is not a treatment plan.
- 05
Receive approved material
The intended app presents authorized instructions and exact approved illustrations or permitted derivatives. The complete Studio-to-client illustration release is still unfinished.
- 06
Keep in touch
Return for selected messages, check-ins and permitted reminders. Concerns need an accountable person and the practice’s direct contact route.
- 07
Use relevant benefits
Optional membership information, benefits and approved offers use current permission and source-confirmed eligibility. Billing, balances, redemption and renewal are not silently recreated in the app.
02 / THE WORK BEHIND THE EXPERIENCE
The right work.
With the right person.
Keep review in professional hands
Review patient-linked source material and the exact record version. For relevant aesthetic services, use the separate Lip and Tox Studio workflow. Clinical decisions and publication approvals stay distinct.
Manage the service, not every chart
Configure the agreed locations, staff roles, services and operating responsibilities. Business ownership and a paid package do not create clinical authority or automatic access to patient content.
The local prototype exercises practice/location/role memberships, expiry and revocation. Treating-team assignments, production identity and target-host security acceptance are separate release work.
03 / PRACTICE-SPECIFIC AI
Assistance with context.
Not unchecked authority.
| Task | Intended assistance | Human or system authority |
|---|---|---|
| Routine service questions | Retrieve approved practice information and draft an administrative answer. | Staff review generated client-facing replies; unsupported questions are handed off. |
| Intake organization | Propose a summary and identify missing or conflicting information. | Original answers remain visible; authorized staff assess the content. |
| Preparation & follow-up | Prepare selected questionnaires, reminders and work queues. | Only already approved content may use a narrower automatic mode after separate acceptance. |
| Studio preparation | Organize authorized source references and review context. | Professional interpretation, source approval and exact illustration release remain independent decisions. |
One logical AI service does not mean one unrestricted memory across practices, roles or clients. Governed AI and connector scope are allocated explicitly; the app-and-Studio package is not an all-inclusive AI subscription.
04 / CAPABILITIES & SPECIFICATIONS
Built around your practice.
Defined before delivery.
| Area | Specification or agreement |
|---|---|
| Branding | Practice name, approved identity, content and selected service journey. Standard branding uses a shared product; a separate clinic-owned native binary is different work. |
| Interfaces | Browser-first patient and staff prototypes. Intended mobile-optimized client experience and separate professional Studio. Native/store distribution remains separately scoped. |
| Scope & permissions | Explicit practice/location/role membership, patient relationship, purpose and exact source/revision checks. No implicit group-owner, support or cross-clinic override. |
| Source records | Keep patient preferences, illustrative concepts, clinician plans, confirmed appointments, performed treatment and observed outcomes distinct. |
| Connections | Begin with verified handoffs and one selected connector. Scheduling, clinical records, memberships, commerce, email, inventory and finance each retain their agreed authority. |
| Technical foundation | Current application work uses Go and TypeScript. Production PostgreSQL location scoping, identity, recovery and target-host acceptance remain release gates; this is not a deployed production architecture claim. |
| Usage & continuity | Agree model/compute allowances, estimates and spending limits. Usage does not grant permission to run an unsupported task. Record access, consent, audit, export, security and recovery are not proposed as metered AI jobs. |
| Delivery & support | Written milestones, supported devices, reviewer responsibilities, retention, export, recovery tests, support window and incident ownership before real-data admission. |
05 / CURRENT AND PLANNED
See the product clearly.
Know what remains.
| Current evidence | Remaining product work |
|---|---|
| Local fictional patient/staff interfaces, consultation-request flow and scoped memberships. | Production identity, managed practice configuration, treating-team policy and intended-host deployment. |
| Separate synthetic clinician case/research and visualization references. | Complete illustrative edit → exact approval → authorized patient artifact delivery. |
| Recorded email and accounting demonstrations elsewhere on this site. | Accepted live AI, mailbox, booking, membership and financial connections for your chosen workflow. |
| Versioned commercial proposals and disabled entitlement/cost previews. | Signed offer → subscription → enabled capability → usage receipt → invoice reconciliation. Billing remains off in the prototype. |
No finished native app, universal integration, autonomous clinical decision, validated treatment prediction or proven customer uplift is claimed. This marketing page accepts no patient uploads and grants no application access.
06 / SELECT THE RIGHT DELIVERY
One branded product.
Several ways to scope it.
A focused client experience, a paired app-and-Studio configuration and a custom application build are different commercial scopes.
The planned aesthetic launch pairs the client experience with Lip and Tox Studio. A wellness or clinic project selects the modules it actually needs. Governed AI, additional connectors, membership billing, dedicated app-store distribution and advanced cloud work are explicitly included or separately quoted—not assumed.
Productized configuration and onboarding are not the same as commissioning a bespoke platform. A quote separates setup, ongoing support/software, custom work and applicable provider costs.
PRACTICAL QUESTIONS
Know your
next step.
Is this a consumer app or Esmyn?
No. This is a practice-branded client service with a separate staff experience. Esmyn remains an independent future consumer product.
Will we own an app-store listing?
Not automatically. Standard branding and a dedicated clinic-owned native binary or store listing are separate delivery scopes, with their own publishing and support requirements.
Can the app automate clinical advice?
No autonomous diagnosis, prescribing, treatment selection or clinical sign-off is offered. Qualified professionals retain clinical decisions and review requirements.
What do you need from us first?
Your practice type, roles, service mix, current systems and first workflow. Do not send patient information, photographs, medical histories or passwords through this website.
YOUR NEXT STEP
Build the relationship around your practice.
Tell us which client journey and staff handoff you want the app to support.